> 
> 
> On Fri, 26 Apr 2002, Michael Dreher wrote:
> 
> > dreher@karpfen:~ > df
> > Filesystem           1k-blocks      Used Available Use% Mounted on
> > rootfs                 7060308   6276188    425472  94% /
> 
> df(1) is wrong.  There is (see /proc/mounts below) rootfs mounted as
> root (ramfs, actually) and ext3 mounted over it.  df sees two entries
> in /etc/mtab (on your box - /proc/mounts) with mountpoint "/" and
> does statfs("/", &buf); for both.  Surprise, surprise, results of
> two calls of statf2(2) are identical - what with arguments being
> the same both times - and refer to the filesystem where your "/"
> lives.  I.e. to ext3.
> 
> > /dev/root              7060308   6276188    425472  94% /
> > /dev/hda4              3794936   3042316    559840  84% /home
> > 
> > dreher@karpfen:~ > cat /proc/mounts
> > rootfs / rootfs rw 0 0
> > /dev/root / ext3 rw,noatime,nodiratime 0 0
> > proc /proc proc rw 0 0
> > /dev/hda4 /home ext3 rw,noatime,nodiratime 0 0
> > usbdevfs /proc/bus/usb usbdevfs rw 0 0
> > devpts /dev/pts devpts rw 0 0
On a related note (the listing of /dev/root reminded me), as of
2.4.19-pre7-ac2, I can no longer boot with a "root=/dev/discs/disc0/part1"
command line, I have to use "root=/dev/ide/host2/bus0/target0/lun0/part1".  My
previous kernel (2.4.19-pre4-ac2-radix) and all ones before that worked fine
with the first version of the command line.  Is this an intended change or is
it a bug?  I can give more information if necessary, and it's happening on two
different AMD based systems with different chipsets.
Daniel
--- 
Recursion n.:
        See Recursion.
                        -- Random Shack Data Processing Dictionary
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/