Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a server at running debian 6.0.7, after a while I noticed when I run df -h / is twice as you can see below. After the installation it didnt show any UUID nor rootfs
Is this critical or there isnt nothing to worry about,
I added to /etc/profile those lines to hide the rootfs but it is only for rootfs. Still display the UUID for /
just done a little reading around the subject ( my Debian Jessie does not have the UUID issue )
It seems that the initramfs *might* be using busybox to mount the root is causing the UUID to be used in proc/mounts
I have 'emulated' this by using busybox to mount via UUID, and indeed I have a mixed df output now.
As you are otherwise booting fine and this is a cosmetic issue, I would be reluctant to fix the initramfs ( it isn't very broken ).
Instead I would look at using the output of either ; /sbin/blkid or ls -l /dev/disk/by-uuid/ to substitute the UUID with the block device using a script
Guess it depends on how important an issue it is.
For reference here is what pointed me to busybox http://lwn.net/Articles/549363/
It might turn out not to be the culprit, I didn't do too much work here.
I guess another option is to not use UUID in /etc/fstab or grub.. depends if you are in the habit of adding/moving drives around ( physically )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.