[BusyBox] df with post 2.4.18 kernels
Allan (reply to list only)
discard at chickenandporn.com
Mon Jan 13 00:41:04 UTC 2003
Jacques;
Sorry if I don't understand; Busybox seems to be reading and
interpreting the information given by the kernel correctly, as shown by
/proc/mounts.
Are you implying that a "df that works" should make assumptions, such as
"if it looks like the same mount, don't show it again"? Wouldn't an
assumption be a bad thing?
I'm sure you could submit a patch to BusyBox yourself that would skip a
filesystem type "rootfs", but I don't know whether Erik (et al) would
accept your patch. You could try it...
Allan
Jacques Nilo wrote:
>
> The ouput of df (busybox 0.63) for a LEAF "Bering" distro with a 2.4.20
> kernel gives:
> # df
> Filesystem 1k-blocks Used Available Use% Mounted on
> rootfs 6144 4916 1228 80% /
> /dev/root 6144 4916 1228 80% /
> tmpfs 15288 164 15124 1% /tmp
> tmpfs 2048 192 1856 9% /var/log
>
> The corresponding /proc/mounts is:
> # cat /proc/mounts
> rootfs / rootfs rw 0 0
> /dev/root / tmpfs rw 0 0
> /proc /proc proc rw 0 0
> tmpfs /tmp tmpfs rw 0 0
> tmpfs /var/log tmpfs rw 0 0
>
> The ouput of df (busybox 0.63) for the same distro with a 2.4.18 kernel gives:
> # df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/root 6144 4916 1228 80% /
> tmpfs 15288 164 15124 1% /tmp
> tmpfs 2048 192 1856 9% /var/log
>
> The corresponding /proc/mounts is:
> # cat /proc/mounts
> /dev/root / tmpfs rw 0 0
> /proc /proc proc rw 0 0
> tmpfs /tmp tmpfs rw 0 0
> tmpfs /var/log tmpfs rw 0 0
>
> The reason is that apparently A. Viro decided to show rootfs in /proc/mounts
> startting with the 2.4.19 kernel. The thread is here:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.3/0290.html
>
> Any fix/patch planned for df wich could work for all types of 2.4 kernels ?
>
> Thanks
>
> Jacques
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
More information about the busybox
mailing list