- Problems with installing Ubuntu:
- Open the mirror. iso file, v-box it seems that it does not recognize this format, it is recognized as if it is a. vdi format, so to open a mirrored installation with a VM virtual machine
- After you open the mirror, follow the steps to install it, after a long installation, the problem occurs. initial suspicion is to read the image file error, take action, replaced by a mirror (at the time of the download, there are two images, one is Ubuntu,ubuntulyn as if the difference between the Chinese and English version), and later changed a mirror, or so, restart, You can get to the normal desktop state.
- Issues with updating the software source:
- Select the system files after the update option, in the selection of the server, see the Practice Guide, recommended Sohu and 163, but in the China option, only Sohu, use this, but also Baidu Sohu, and baby installed ubuntu16.04 software update source address.
- Software source update address basically the same, as long as the modification of a place, modified to the corresponding version number of the code
- Remember to back up the sources.list and then overwrite the original file with the 10 addresses of the software source. (Remember to overwrite all, do not add #, #是注释用的), use sudo to change the file.
- After you save, update, update, and then a little bit of a small error, such as
- When installing the software: Sometimes the software does not appear to function, such as vmare-tools, Sogou input method, etc., is to restart to use.
- When editing the command: In many cases the problem is that you don't have enough permissions (such as the file cannot be saved), you can add the sudo + command to the command before you try it out.
- When using Winscp,putty to log in:
- Using the IP of the virtual machine, the command to view the virtual machine IP is ifconfig, using the IP address of the following picture red box
- Note that this IP can sometimes be restarted. If the putty login connection times out, you can check the IP address, or you can restart SSH, check the process, whether there is sshd and so on.
- (Can not connect, not because of network problems, the host and virtual machine is the same network segment, do not need to be networked or log on)
- With respect to certificates, this problem may occur when the client generates a public private key pair, and the public key is written to the virtual machine:
- Guess this is a key file, and the files here are impossible to write.
- Can try to use sudo permissions, do not know, do not solve this problem, replace a method to generate a certificate
Linux practice One: Problems and solutions