System Note (1)

There is nothing special in this article, but it only records some small details or error-prone places when the younger brother installs and updates the linux system. I hope it will be helpful to those who are interested in it. 1. when installing Kali, be sure to select YES when selecting whether to use the image source. at this time, some problems may occur, but we have finished updating... "/> <scripttype =" text/javascript "src =" http://www There is nothing special in this article, but it only records some small details or error-prone places when the younger brother installs and updates the linux system. I hope it will be helpful to those who are interested in it. 1. when installing Kali, be sure to select YES when selecting whether to use the image source. at this time, some problems may occur. However, after updating the image source, we can go to/etc/apt/source. add an update source to the list, because the younger brother does not find a particularly good update source, it is not provided here. 2. do not install scim (input method) in kali. if it is difficult to use it, files are easily missing. I used apt-get update several times, updated the source several times, but it was fruitless. Finally, I could not bear to directly rm scim *, and then apt-get ibus-pinyin. this should be enabled in the preferences set by the system, and the Chinese language should be added to perfect solution. 3. virtualbox Shared disk: the shared disk must be enabled in the virtual machine settings. vbox does not support direct drag and drop. in Windows, you need to map the drive letters. in linux, you cannot see the drive letters, the file starting with sf _ in media is the shared drive letter. if you want to open it, you just need to make a soft link to the root directory or home directory. 4. use less upgrade when installing the system. you can execute an update after installing the system. this is generally enough. Don't ask me why. I won't even tell you that there is something wrong with the kernel. upgrade can delete things that you have worked hard to install for a long time and all kinds of configurations, while there are few updates, but it is better to use them less. 5. mongodo, which claims to be able to correct errors and avoid sudo paralysis. here, if sudo is paralyzed and the root account is not enabled, livecd or grub will be used for recovery. It seems that it still requires the root permission. there is an error correction option in it, which is said to prevent syntax errors, but it is probably too stupid to steal it as it is not very useful. 6. sudoers: this fool requires the root permission to modify or read-only files. For the sake of security, I usually like sudo and want to get an empty password. I tried various methods on the Internet and summed up only NOPASSWD. none of them is correct, attackers grub several times, and the Machine almost finished. The solution is % sudo ALL = (ALL) NOPASSWD: ALL. restart (some systems can take effect directly. 7./etc/sudoers, that is, after the sudo configuration file is paralyzed, liveCD or grub must be restored. I have tried two methods and will share them with you. (1 ). liveCD boot with a CD, attach your hard disk, change sudoers back, and then unmount the hard disk. (sudo command will still be used in the middle) (2) grub # shift to grub, press e to select the recovery mode # select the root account # chmod 666/dev/nullmount-o remount rw/# nano/etc/sudoers to restore the content of this file and save it to the disk. KO! ===== Enjoy Yourself! ====