![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
On 2012/04/24 19:16 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
On 2012/04/24 15:26 (GMT+0200) Carlos E. R. composed:
Felix Miata wrote:
There is no need to install/remove anything.
No, but it's a logical thing to do if booting that way solves the problem(s).
I think it is preferable to leave it installed, in order to learn if the problem has been solved. I assume that all those problems are reported to Bugzilla, and I know for certain that the maintainer is quite active because I have reported several.
For a tester, I can't disagree, or for an ordinary bug. Systemd trouble is no ordinary bug, while the OP certainly seems to be no willing tester. Systemd is a whole class of bugs like KDE4.0-4.5 was, betaware foisted on users prematurely. Ordinary mortal users who need their systems to just work don't need and shouldn't be bothered by major system overhauls that are incomplete, unless the devs' goal is to get them to switch to some other distro.
You need to be.
Need to be what? You probably should carefully read the whole thread, including the subject, when you're fully conscious. I'm not the OP. All my 12.1 systems have sysvinit-init installed, but not all of my 12.2 systems do, so that I might be able to spot or test fixes to systemd bugs in a test environment, and not be bothered by betaware in a need to get real work done environment. https://bugzilla.novell.com/show_bug.cgi?id=746594 https://bugzilla.novell.com/show_bug.cgi?id=746595 -- "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