On 06/08/2014 05:02 PM, Linda Walsh wrote:
Soon as you show me how to upgrade root w/o rebooting, let me know. I have updated /usr w/o a full reboot and certainly /usr/share is fairly trivial.
Depending on your definition, yes I do all the time. If you mean kernel updates, that's another matter. But anything in user space I can restart. That may require logging in again, but that's a matter to do with KDE or Gnome.
I said from day one that combining root+usr made system maintenance and recovery far more difficult.
Any piece of junk that requires a monolith of 27G in backing libs, configs and files is just that: junk. Just because systemd is broken into parts doesn't mean it can boot off of root -- it has huge disk space requirements for what needs to be mounted in order to boot. That's where it is monolithic and non-sub-dividable.
Again it depends on your definition. If you mean 'get to the 'graphical login' the lets compare apples to apples. Sysvinit required the shell, grep, some awk and more, as well as utilities such as mount and more to get to that point. If we drawn the line at where the old sysvinit started running the scripts in /etc/rc5.d or /etc/rc3.d as having completed boot and now starting user services then I think we can have a meaningful discussion, but I don't think that's where YOU are drawing the line. But if you do mean 'get to the 'graphical login' when you say 'boot' then your assertions about what's required by systemd needs to be compared to what is required - all the functions & libraries and resources used - by sysvinit to get to the same point. When we factor out the common parts I don't think its anywhere near that dramatic. One of the purposes of systemd was to be able to get many services up and running without needing to make use of shell or shell tools. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org