On Monday 20 June 2011 06:49:30 Linda Walsh wrote:
Greg Freemyer wrote:
openSUSE may or may not support a separate /usr which systemd rolls from what I understand.
It depends if it is decided to move enough logic in initrd to allow /usr to be mounted early in the boot process.
I for one believe openSUSE should support it as much as feasible. There are too many machines out there with them being separate.
I know I have at least 4 servers I setup about 10 years ago (8.1 days) which I've just been upgrading. They all have separate /usr.
Having 12.1 break on those machines would be a real concern for me as a opensuse user.
Greg
----- (am in agreeance*! *-that is a word!) Why it it that every time someone decides to go with some new wizzy software thing, they have no problems throwing out current features that MANY people use and rely on?...
Please inform yourself before ranting. If you would have read the link I gave (or the other mails in this thread) you would know nothing you just said makes any sense. Hint: systemd is NOT the problem, the rest of the linux tools doesn't support it properly. Read before you rant please.
There is a reason windows was as successful as it was...it maintained some level of compatibility up through XP....with Win7, they broke it to introduce DRM...which I still detest them for and Win7 still has worse perf and more probs than I ever had with XP.
But I have separate boot and root and usr.... The only time I have problems with my setup is during SUSE upgrades, which I fear greatly....
I still haven't fully recovered from an upgrade to 11.4 though most things work fine and am glad I did it...but the initial upgrade... After I I had upgraded the packages, it jumped into the installer a second time with some small subset of packages -- what I didn't catch was it was doing some minimal install into the 'dead' area at the end of my disk (an area I leave unused on my boot disks due to speed) and then booted from there.
Thank god for rescue disks...
Also why can't /usr be mounted early on? I was always taught you put your static boot progs in /lib /sbin and /bin, then /usr was where the "runtime" was that was accessed when the system was booted.
Just like the jump to throw out xfs because grub was broken, or throw out lilo because it didn't had problems -- rather than fix the problems, grub has caused me more problems than I want to think about....
I tried it twice willingly, and about 4-5 times unwillingly during various upgrades....I DO still use it on some of my test systems, but it's too unreliable and slow for my main system.
Except for a few months when I couldn't upgrade my kernel due to the lilo size constraint, I've never had problems with it. I DID have problems with grub and XFS....but not with lilo and XFS....
It really bothers me to have so much done on the ram disk -- it makes it impossible to debug boot problems and completely mangles the normal unix boot process of init starting things...
OTOH, Win7...sorta went the same way--- They allocate a 100MB partition just for their System boot partition....all hidden and inaccessible to the user...just so they can control the boot... (and control the OS/HW layer, to provide DRM)... Is that where OSuse is going?