Package: coreutils Version: 8.13-3.2 Followup-For: Bug #656067 Debian/sid still listed my rootfs twice: as "rootfs" and as the UUID device. After setting GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub (and running update-grub) the rootfs is still listed twice, but at least the long UUID entry is gone from df(1):
$ df -h [...] rootfs 4.0G 2.3G 1.5G 61% / /dev/sda1 4.0G 2.3G 1.5G 61% / Now /proc/cmdline also lists /dev/sda1 instead of the UUID name: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=/dev/sda1 ro FWIW, on Fedora 17 (grub2) rootfs is listed twice too and without the long UUID name in df(1) output. Its kernel commandline _does_ specify root=UUID=... though. Then again, the boot process in Fedora seems to be very different from Debian's approach, I assume. openSUSE 12.1 (grub 0.97) lists rootfs twice and without the long UUID name in df(1) output, its kernel commandline does specify root=/dev/sdaN. Not sure about Windows though :-) Personally, listing rootfs twice is fine with me (especially since "df /" lists /dev/sdaN i.e. the real device name. But df(1) should not list the long UUID name, IMHO. C. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coreutils depends on: ii dpkg 1.16.8 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-35 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
