friends,
has anybody else come across the problem updating their initscripts and
breaking network booting in the last few months?
right when checkroot says "Remounting root filesystem read/write..."
the system hangs, and eventually init says it couldn't be mounted
read/write and frowns, and suggests I give the root password or
reboot.
I've tracked down the problem. Seems as though statd can't start
because the root filesystem is mounted read-only, but the filesystem
can't be mounted read-write until statd starts. I have not been able
to convince statd to run without logging its pid in /var; thus it
requires write access to var.
The only workaround I've concocted so far is to bind a bit of /dev over
to /var, where it can be written to. Unfortunately, that mounting
point is likely lost when / is remounted read-write, thereby destroying
any record of the pid statd was so insistent about documenting.
Needless to say I'd like to solve the problem the right way. However,
the init scripts are a complex bunch for me and I'm not sure how to go
about fixing this.
I was hoping one of you might be able to guide me. Any thoughts?
Thanks,
Dan Farrell
--
[email protected] mailing list
