Kay Sievers wrote:
On Fri, Jul 8, 2011 at 21:10, Rob OpenSuSE
wrote: On 8 July 2011 18:18, Kay Sievers
wrote: I'd like to do some notes on the topic how become systemd or should I better say udev better integrated in the current system scheme regardless of the used init. /usr should just be mounted from initramfs. That solves all the
On Fri, Jul 8, 2011 at 18:43, Dr. Werner Fink
wrote: problems. The artificial split of / and /usr makes not much sense in today's setups. What / was for UNIX, is the initramfs for Linux. That's good insight! If there's difficulties mounting /usr from initramfs perhaps it's better to not support seperate / & /usr.
But things that worked in the past for people, should just continue to work as it is.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Bottom line. Agreement! by inference, separate user will still work and ideally, still work w/o ram disk (as my system currently boots). Modern systems disks spin up to speed fast enough (faster with SSD's) to make a RAMDISK an extra-complexity that isn't always needed. But why do I want separate partitions: I have been known to run 'pre-production SW... (GOSH!)....and if anyone here thinks this doesn't apply to them they are in naive, I mean who here, doesn't? As a result, things like the kernel and file systems sometimes crash in inconvenient and bad ways. ***LIKE, in 11.4 ***...last night -- a 'normal' /etc/rc.d/restart. Except that it wasn't...didn't come up like it was supposed to. (I still have NO idea what caused it!) "/var" somehow had gotten corrupted going down and wouldn't mount. Fortunately, damage was *contained* to a small partition of files that didn't even need to be restored. boot-rescue, run xfs-repair, -- back in business. if it was my whole disk -- I might still not be up. But more important is that over the years, I've had various partitions get "hosed" separately. I STRONGLY appreciate the containment of damage I've lost /usr by itself, but was still able to boot to single user at the time (an older suse that had all it's boot stuff in /bin, /lib, /sbin).... I was even able to repair (restore actually) by mounting a /usr partition from a repair DVD!...).... have also lost /home, and data partitions (and root, but never yet 'boot')... ... I mean we are talking maybe once of each of those over the past 10 years. I've almost always been fortunately to have daily backups to recover from (cept when backup drive and a regular drive both went dead in similar time frame....but fortunately even that I had a copy as had upgraded the hard disk recently, and still had a fairly recent copy).... Those are my strongest reasons and feelings for wanting to keep things separated into smaller containers --- with LVM it becomes even more possible since you can dynamically resize partitions after the fact! And even 15-20 year old file systems can expand to fill a larger paritition! So with software become less stable and predictable as it gets more complex, and running downloaded SW with latest features, as well as keeping current on my suse release, having damage containment has been a help -- because damage *will* occur. It's just a matter of how ugly or just time-consuming to recover from it. One of the reasons I went to a RAID system (including for backup) was exactly being able to recover more quickly. With it taking hours to restore 1 large HD (a full speed disk image of 2TB would take over 5 hours) -- more if you you are going through a file system. So it's not about "big iron" or corporate customers....it's about a home user who's grown tired over the years of waiting around spinning thumbs while a system is down, and who's health isn't as great, for who a working computer is important -- and 'downtime' measured in hours gets very unhealthy for me (since I have no one to repair or fix it, but me!)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org