by Sorry, I didn't find this answer in the FAQ or other sources. I've just
installed a base Linux system and everything works fine except that when
I boot from LILO, the system boots read-only--and *stays* there.
I know that the kernel is supposed to boot read-only so that e2fsck can
be run on it. But it's not supposed to *stay* that way, right...? Seems
to me that immediately after running e2fsck, the init process should
somehow give write access to me. Can't find that point in inittab or any
of the other startup files, though.
My temporary fix has been to use rdev to tell the kernel to boot
read-write, then cat vmlinuz > /dev/fd0 and use that floppy to boot. It
gives me an error since the read-write filesystem can't be checked, but
at least I can make changes to the system then.
Anybody know what's happening with this and what I need to do?
--Clay