Linda Walsh wrote:
Another reason I have "smallish" system drives .. I use 15K SAS drives which are smaller. To get the space I have & optimize speed, I 'short-stroke' the array, using only the first half of 3-72GB drives, with 1 being parity. Effectively I only have 72GB for all of '/', '/usr', 'var, var/cache, swap, boot.
That ought to be more than plenty, even for a desktop machine? I mean, I usually allocate 10Gb for a server (without data volumes), and a typical install will usually take up about 2-3Gb.
I don't even have room for /usr/share on the root drives anymore -- it grew too big -- so my /usr/share lives on /home/share, which is then mounted via bind to /usr/share.
Hmm, you have 72Gb for your root filesystem, but not enough for /usr/share ??
One thing that doesn't get advertised much, is that /usr/share -- specifically meant to be non-arch-specific, shared-content, is ALSO being required now in order to boot.
I agree, I haven't seen that mentioned, but then I also haven't seen (m)any convincing reasons for keeping it on a separate filesystem.
So it's not just /usr, but /usr/share as well (and likely others will be added over time). But as an example, my /usr/share is in /home/share, that means /home needs to be mounted as well -- all of this worked fine under 12.1.
Even with /usr mounted, the newest stuff in factory won't necessarily boot -- as /usr/share wasn't mounted.
Right.
Someone put in a superfluous and ill-considered check to make sure your root disk is read-only upon booting, because they "know"[sic], that you can't run a file system's "fsck" script on a writable disk.
I could be wrong, but hasn't openSUSE been like that for years and years? I.e. first mount root read-only, then remount as read-write? I built a smallish cluster with SUSE 8.0, I seem to remember stuff like that when I started taking things apart (for booting with root on NFS).
It's bad enough when one can't mount /usr because mount is on /usr, but if you can't get udev running, and that forces /usr/share to not be mountable (which udev needs), OpenSuse has created a maintenance nightmare.
Isn't your /usr/share issue a bit contrived, Linda?
The idea of spreading dependencies out across all of the disks is going to lead to more circular logic problems (just like the need to mount /usr one needs 'mount', but some rocket scientist put that in /usr/bin.
I also find the move /usr to be a solution looking for a problem, but I personally don't have a real problem with it as long as /usr can still be put on a separate filesystem (nfs etc). I guess that is taken care of by keeping /usr/bin/mount in the initrd. -- Per Jessen, Zürich (3.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org