The safest thing would be to boot the rescue system, and run fsck from there. But if you telinit S, and make sure no processes are running, it should be fine. Anders On Monday 25 June 2001 03:44, dizzy wrote:
Anders Johansson wrote:
OK, so your system is already rw. Then why couldn't you edit /etc/passwd (and I don't think this is the source of your problems, btw).
rite... but *somehow* the /dev/null got passed to the bash profile...(or users logon) The only way I think this could have happened is when I made the entry in /etc/passwd for the samba user....
Looking at the boot messages, your system starts by mounting your root system read-only, which is normal. Then when it tries to fsck it, it doesn't for some reason.
I honestly can't tell the difference between your system and mine. I was certain you had done something with fstab, like setting the last parameter on / to 0 or something.
The only thing I can think of is a manual fsck
fsck /dev/hda2
followed by a reboot. Try it, and report the results
Ok fsck wont run if in the current ro state ERROR couldnt open /dev/null
If I mount the fs then try to rn fsck I get the stern warning of
WARNING!!! running fsck on a mounted filesystem can cause serious damage do u want to continue y/n
not sure if this is safe??
rob