On 2013-02-07 05:27 (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? ;-)
I won't be guessing. If you have Factory enabled on a 12.1 system I'm outa here. If I want a package from an alien repo, I download the package and install locally if it will let me without complaining about incompatible deps. Sysvinit-init except from a 12.1 repo isn't likely to be anything more than a problem creator. Mixing basesystem packages from different release versions can't be good for much other than making trouble. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org