Rahul wrote:
Thats a later addition I assume? The one time I actually had a problem with it was back about FC2 time IIRC, and it may have attempted to, but fubared the video mode doing it, repeatedly. Long time back up the logs now of course, but thats had me removing it asap since. Thanks for the heads up.Gene Heskett wrote:Paul Smith wrote:Thats a root only command for starters, and it should have made the machine reboot, during which the fsck on the file systems would have been done, however you may have to edit /boot/grub/grub.conf to remove the 'rhgb' from the kernels boot command line before you would see anything because it would otherwise be hid behind a graphic and all you would see is a longer bootup time. rhgb is the work of somebody trying to make it more like a (spit) windows experience. Its a bad idea. We want to KNOW what its doing while booting.On 7/14/06, Eric Donkersloot <eric.donkersloot@xxxxxxxxx> wrote:You could boot the system in single user mode and check the file system manually or you could reboot the machine with 'shutdown -rF now'Thanks, Eric. I have just run the command 'shutdown -rF now'. How can I now check whether my file system is not corrupted? The point is that I do not see the result of 'shutdown -rF now'... PaulRHGB falls back to text mode on any warnings or error messages including fsck process. So your comment is misleading.Rahul
-- Cheers, Gene
