Recently, Dropbox has been used to synchronize files between lab computers and laptops. However, some files, such as Bash configuration files, are located in ~ /Directory, it is inconvenient to synchronize, and to facilitate system reinstallation in the future, I will back up some configuration files similar to bashrc and vimrc and store them in a unified manner. Then put these files into the Dropbox for synchronization.
However, sometimes, if you suddenly want to rename some frequently used commands, you must add the alias statement to the. bashrc file. Modifying the backup file after modifying the. bashrc file is particularly inconvenient.
During hard drive File Sorting over the past two days, I suddenly found that ~ The. bashrc file in the/directory is set as a soft connection and linked to the backed up file. Okay, just do it! After that, I also made soft connections to some configuration files of common software, so that after I modified them on a computer and synchronized them through Dropbox, the configuration file of the software on the other computer is also modified (the configuration file on the computer is also changed to a soft connection ).
Then, there will be some files under/etc, such as the fstab file mentioned here. I think it should be okay. Then I did. The tragedy is coming.
After the computer is restarted, there is no problem. When you want to enter the account and load it to the desktop, a problem occurs and you cannot access the user normally.
Since the desktop cannot be accessed, I will not enter the desktop. Go to the console. CTRL + ALT + F2. Fortunately, you can enter, but I cannot enter my account, but you can enter the root account.
I think this problem should occur on fstab, Because I connect fstab to the current user, but I need to use the fstab file when guiding the system, and no partitions have been mounted, therefore, the files attached to the soft connection cannot be found, so the partitions cannot be loaded normally.
So I have prepared to change/etc/fstab to the original file. In fact, if the fstab file is correctly modified at this time, the fstab file can be changed. After the restart, everything will return to normal. However, I did not notice that there was something I did not pay attention to when I modified it. I wrote it wrong. Then I restarted, and the root account cannot be used now. The error is that the partition number in the fstab file is incorrect.
No way. go online and find out how to solve the fstab file problem.
Fortunately, I found one.
Http://www.linuxidc.com/Linux/2010-09/28385.htm
In fact, the main solution is to enter the rescue mode of fedora, find the root partition in this mode, and then mount it to a directory so that you can modify the fstab file.
I have never entered the rescue mode before. This is actually very simple, but I need to install a disk.
Insert the disc into the optical drive, enable the boot from the optical drive in bios, select rescue mode, select the language, select the keyboard, do not set the NIC, finally select a shell, and then follow
The method mentioned in the http://www.linuxidc.com/Linux/2010-09/28385.htm step by step operations, and finally modified after the fstab restart everything to restore the previous situation.
Great.
Files in the root directory cannot be modified at will.