FreeBSD fatal Bug 1. -- I have not come across any recorded twice, just Bahrain system, the normal download several times, not a sudden entry, and then to another user account recorded words, it seems like the password to rehabilitate, but not computer to connect to the Internet, a change of passwords is not possible! It is not recorded! ! They had no choice but reloading system! ! ! Em07 : : 2. As the two-level installation, set up after the restart rc.conf reported rc.conf grammatical mistakes, it is not possible to conduct follow-up to the start. Then the state can enter # to check rc.conf really wrong, but all the documents are read, can not be amended. : : Drawing lessons from the bitter experience of despair, eyes heavy-system! Em08 : : FreeBSD fatal Bug Ha ha First, I used the FreeBSD more than three years, never before encountered. Try to amend root password into single-user mode and then check the relevant log to see what has gone wrong password. Does the Secretary has damaged password, or have forgotten their password, to turn over their passwords but forgotten. Secondly, rc.conf into single-user mode can be written. Even without the authority to root w, single-user mode can be forced into the vi wq! forced into by : FreeBSD fatal Bug Brother, forget the password instead. I spent five years FreeBSD has not met once! FreeBSD fatal Bug [quote][i] Original note from the "books"] 1. -- I have not come across any recorded twice, just Bahrain system, the normal download several times, not a sudden entry, and then to another user account recorded words, it seems like the password to rehabilitate, but not computer to connect to the Internet, a change of passwords is not possible! It is not recorded! ! No? . . . . . . . . . [/quote [/i] Released : Ah, you are there! ! ! ! : : : : : : Hey you did not expect such a treatment still has not old! ! ! ! Em04 em04 : : : : : : : em02 : em02 FreeBSD fatal Bug Hahahha, o le nideyingpankenengyaogame over FreeBSD fatal Bug Is! I have a hard disk quickly nullified, there were problems into the void. . Disk mode is not correct, may be activated, but into a problem. . FreeBSD fatal Bug Is your dream to me then? No hard disk, no way to access single-user mode count all "read"! FreeBSD fatal Bug Take a look this one : Http://www.openbsd.org/faq/faq8.html#LostPW I met the same problem (i mean rc.conf syntax error). I did exactly the same way as above. Enter single user mode. mount / and make / writeable; mount /usr so that you can use vi. /etc/rc.conf, 1976. correct it and save it. umount / and /usr. reboot machine. that 's it. Don 't reinstall your OS. it wastes a lof time. Good luck FreeBSD fatal Bug I also encountered just packed machine manually allocated on a xfree86 suddenly become root toor, can no longer be written off after the download. FreeBSD fatal Bug Thank you, Peter, immediately try! FreeBSD fatal Bug Ok, thank peter! FreeBSD fatal Bug You list on the main growth document vulnerable systems (such /var category, or log documents and other common file system) above is a very bad idea, if the area is filled with paper, you should quickly roll information, dark executing orders, the dark using echo guess you emptied the document. It was not until the space was unloading, you can normal operation. FreeBSD fatal Bug [quote][i] Original note from the "books"] 1. -- I have not come across any recorded twice, just Bahrain system, the normal download several times, not a sudden entry, and then to another user account recorded words, it seems like the password to rehabilitate, but not computer to connect to the Internet, a change of passwords is not possible! It is not recorded! ! Not here. . . . . . . . . . [/quote [/i] Released : 1. I never came across any. 2. Why not try to mount -w? see that the man FreeBSD fatal Bug Share 2 Laws is the wrong time, single-user access, and could not amend (/ File System for readonly), even in the hard disk of another district /usr Contents (automatic district, as well as the setup), this solution : Mount /usr In /usr/home/myhome/ catalog, the creation of a provisional list temperature Mount the / Contents of temperature, it is time temperature be written. CHROOT temperature /bin/sh Then ed under the revised document /etc Of course, there are also complicated to temperature vi system, which can screen editing. FreeBSD fatal Bug A few days ago I met a row twice this situation, any user can restart after landing, but they could in Windows using ssh landing, but could not su to root after the landing FreeBSD fatal Bug What version are you using man? FreeBSD fatal Bug I have tried the above methods are not successful Landing, regardless of what users have suggested Login incorrect 1 LONGIN FAILURE ON ttyv0 But even in single-user mode can not see the contents /dev/ttyv0 [ Closed window ]