Felix Miata wrote:
On 2013-02-06 13:30 (GMT-0800) Linda Walsh composed:
# why have you not installed # sysvinit-init to dispense with it if you think systemd is your problem?
I had it installed. Twice I've been "upgraded" to systemd.
# zypper in sysvinit-init # zypper al sysvinit-init
Then no more "upgrading" to systemd-init.
Systemd is much more mature in 12.2, so if and when you upgrade to it, you might want to allow it to do init. IIRC I've got about a 5:1 ratio of 12.1 installs with sysvinit-init to those with systemd-init, but somewhere between diametrically opposite and 50:50 with 12.2. Sysvinit-init is scheduled for removal in 12.3.
zypper in sysvinit-init Loading repository data... Reading installed packages... 'sysvinit-init' is already installed. There is an update candidate for 'sysvinit-init', but it comes from repository with lower priority. Use 'zypper install sysvinit-init-2.88+-82.2.x86_64' to install this candidate. --- It is asking me if I want to update to the one from factory... I would guess not? ;-) Note -- My biggest issue with systemd is the fact that to force it's usage, people are moving binaries from /bin and /sbin -> /usr/bin and /usr/sbin. If that was stopped/reversed/fixed, then it becomes something that is just newer and more complex and trade-offs could be measured, but as long as I have to write scripts and recompile packages to put binaries back on the root partition then systemd is off the table. As near as I can tell -- there is no reason other than malice to do this. All of my problems are disappearing as I migrate binaries from /usr back to /. The whole issue would go away if the equivalent of "boot.localfs" could be made a pre-req before starting the network, or DNS, or the desktop. I had previous boots trying to load drivers for virtual machines (WHICH I don't have enabled!!!) BEFORE the local FS was loaded. WHY can't the local FS be loaded before all the rest of the scripts run? What are people saying "you can't run a local mount-script" before you start systemd. Why is that? BTW -- my screen blank probs went away when I compiled-out that driver. now it comes up in the BIOS set VGA mode and stays there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org