--- Chmouel Boudjnah <[EMAIL PROTECTED]> wrote:
> Eugenio Diaz <[EMAIL PROTECTED]> writes:
>
> > Eugenio Diaz wrote:
> >
> > > After upgrading to kernel-2.4.4-6mdk, the boot process halts to single
> > > user just after the "Checking file systems" message. It complains about
> > > filesystem being mounted; which I traced back to fsck ... Anyway, after
> > > a few minutes of troubleshooting I determined that the kernel is first
> > > mounting the root filesystem as read-write instead of read-only as it
> > > should be; and as expected, fsck complains, dropping into single user
> > > mode.
> > >
> > > I don't know why this is happening, or where to properly fix it. Is this
> > > hard coded when the kernel is compiled, or is this configurable by lilo?
> > >
> > > I fixed it temporarily by adding the following line to rc.sysinit just
> > > before fsck is called:
> > >
> > > mount -n -o remount,ro /
> >
> > I just remembered that the "read-only" directive in the lilo.conf is what
> > controls this.
> >
> > Well, then there most be something wrong with either lilo, or the kernel,
> > since: a) I haven't changed my lilo.conf, and b) it contains the
> > "read-only" directive.
> >
> > I suspect the kernel is at fault.
>
> yep fixed in 2.4.5-ac2
Is this already in cooker? I don't see it on the mirrors.
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
