Anton Aylward wrote:
The way I look at it the CORRECT way is to have an initrd that does what you want and only what you want.
What does initrd have on it that does the mounting of '/usr'? Isn't it a "script" and a copy of "mount"?
Proper configuration or script? Set up the configuration properly (drakut makes this easier) and you get a properly built kernel and initrd every time :-)
drakut determines what modules your kernel needs, and unless you add plugins, it won't add mounting code for /usr. According to it's mission statement, it is designed to only put the *modules* on the initrd necessary for booting your specific HW. Something else must then take control and execute some copy of 'mount' to make sure /usr is mounted.
Of course you could always pre-empt the future and run a system that has a single unified root+/usr. That's how its going to be.
---- Ok, but what about all the directories under /usr? How many of them also have to be mounted? /usr/homes could be a place where people put home directories. /usr/share is supposed to be arch independent material that can be 1) quite large, 2) should be shareable, 3) quite likely should be 0n a separate partition from /root and /usr as the size of /usr/share can easily be larger than the combined size of root and /usr. 15G vs. 10.6G on my system. However, reviewing my boot log just now, I see that arbitrary directories seem to be required from /usr/share for boot: udevd[602]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 512 09': No such file or directory udevd[603]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 896 09': No such file or directory udevd[604]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 256 09': No such file or directory udevd[607]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 384 09': No such file or directory udevd[608]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 768 09': No such file or directory udevd[609]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 0 09': No such file or directory udevd[610]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 128 09': No such file or directory udevd[611]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 640 09': No such file or directory udevd[619]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 769 00': No such file or directory udevd[623]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 1 09': No such file or directory udevd[631]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 3 00': No such file or directory udevd[632]: failed to execute '/usr/share/virtualbox/VBoxCreateUSBNode.sh' '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 2 00': No such file or directory ---- This means arbitrary shell scripts are needed to *cleanly* "boot" before I could even get a shell prompt. Are those "signed" kernel modules being loaded? I don't get a good feeling about the security of needing to load shell scripts off of /usr/share in order to boot. In short -- we see shell scripts being called even when booting to mode 'S'... Requiring /usr is bad enough (8.0G v. root at 4.6G). Now it used to be root was larger and /usr was smaller. But the only reason /usr needs to be mounted is the 2-4G of material that was moved off of /root into /usr. I.e. it created a problem that didn't exist: # ll -h /backups/Ishtar/root/*-0-* -rw-rw---- 1 6.7G Sep 1 04:32 /backups/Ishtar/root/root-120901-0-0430.dump -rw-rw---- 1 7.1G Oct 1 04:32 /backups/Ishtar/root/root-121001-0-0430.dump -rw-rw---- 1 7.4G Nov 1 04:31 /backups/Ishtar/root/root-121101-0-0430.dump -rw-rw---- 1 3.7G Dec 1 04:31 /backups/Ishtar/root/root-121201-0-0430.dump -rw-rw---- 1 4.1G Jan 1 04:31 /backups/Ishtar/root/root-130101-0-0430.dump # lh /backups/Ishtar/usr/*-0-* -rw-rw---- 1 6.5G Sep 1 04:35 /backups/Ishtar/usr/usr-120901-0-0432.dump -rw-rw---- 1 7.3G Oct 1 04:36 /backups/Ishtar/usr/usr-121001-0-0432.dump -rw-rw---- 1 7.1G Nov 1 04:35 /backups/Ishtar/usr/usr-121101-0-0431.dump -rw-rw---- 1 7.5G Dec 1 04:34 /backups/Ishtar/usr/usr-121201-0-0431.dump -rw-rw---- 1 7.6G Jan 1 04:35 /backups/Ishtar/usr/usr-130101-0-0431.dump As I've upgraded from 12.1->12.[23], more and more files are being moved off /root onto /usr. So let's say I combine /usr and /root. Where does it stop? Do I need all of /usr/share as well -- the largest parts being font, icons, clipart and docs: # du -sh *|hsort -s|tail -10 184M clipart 198M kde4 246M locale 338M man 714M texmf 753M icons 1.7G doc 6.5G fonts ---- ----- 12.5G TOTAL My system disk currently fits in <18G. (that doesn't include 'share'). It was sized small with a fast (15K SCSI) disk, with the idea that most larger progs could be on the LVM-managed slower-seek + faster throughput large RAID. Will /usr/local also be required for boot? That's historically been for site-local material. This is why I am asking for specifics -- when you say /usr, are you including those who have /usr/home? (likely not as that's an uncommon config, BUT, running shell scripts off of /usr/share in order to boot used to be uncommon as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org