what baselayout do you guys use?
----- Original Message -----
From: "Wes Gray" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 6:08 PM
Subject: Re: [gentoo-user] Kernels > 2.4.20 don't work with reiserfs
> On Thu, Dec 04, 2003 at 12:29:21PM +0100, Christian Anthon wrote:
> >
> > Same problem here. I had to comment out rootfs checking in checkrootfs
> > during bootup since I had no old kernel to use. The problem probably
> > lies with reiserfs tool and not the kernel.
>
> My problem does occur in /etc/init.d/checkroot, but the checking
> of the filesystem goes fine, it's the remounting that fails. The
> output looks like this:
>
> * Checking root file system
> Reiserfs super block in block 16 on 0x304 of format 3.6 with standard
journal
> Blocks (total/free) 15526822/2297961 by 4096 bytes
> Files system is cleanly unmounted
> Filesystem seems mounted read-only. Skipping journal replay
> Checking internal tree..finished [ok]
> * Remounting root files system read/write...
> * Root filesystem could not be mounted read/write:( [!!]
>
> The code which does this in /etc/init.d/checkroot comes right after the
> check:
>
> # Should we mount root rw ?
> if mount -vf -o remount / 2> /dev/null | \
> awk '{ if ($6 ~ /rw/) exit 0; else exit 1; }'
> then
> ebegin "Remounting root filesystem read/write"
> mount / -n -o remount,rw &>/dev/null
> if [ "$?" -ne 0 ]
> then
> eend 2 "Root filesystem could not be mounted read/write:("
> /sbin/sulogin ${CONSOLE}
> else
> eend 0
> fi
> fi
>
> So that "mount /" command is failing. Maybe I will learn more by removing
> the "&>/dev/null" from the end of the mount command.
>
> --
> [EMAIL PROTECTED] mailing list
>
>
--
[EMAIL PROTECTED] mailing list
