Mailinglist Archive: opensuse (1786 mails)
| < Previous | Next > |
Re: [opensuse] 12.1 OK, how do I switch back to if-up control
- From: Felix Miata <mrmazda@xxxxxxxxxxxxx>
- Date: Mon, 21 Nov 2011 01:55:15 -0500
- Message-id: <4EC9F5D3.6020201@earthlink.net>
On 2011/11/20 22:33 (GMT-0800) Bruce Ferrell composed:
It worked as advertised on a dozen or so systems here. How many did it fail for you for? Are you sure there wasn't also something else wrong from your previous attempts to get "rid" of systemd? I went through something like what you described up thread back in the M3-M5 devel period. When I quit trying to eliminate systemd by removing stuff, I was rid of systemd control of the init process, perfectly reverted to sysvinit AFAICT. Let's see:
https://bugzilla.novell.com/show_bug.cgi?id=723041#c1
https://bugzilla.novell.com/show_bug.cgi?id=727092
Whaddayaknow, it's in the relnotes: http://www.suse.de/relnotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html#12
Seems my response was quite accurate.
--
"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@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
Felix Miata wrote:
On 2011/11/20 22:02 (GMT-0800) Bruce Ferrell composed:
Thank you very much for playing the game, but no Felix, that is NOT correct.
It merely make system V init available. It dos NOT make it default. I know, I
tried it just today.
Per the posts I received, I installed that, removed systemd and removing
systemd removed numerous packages as systemd was marked as a requirement for
them.
I didn't write anything about removing anything, only installing. What I wrote
worked here on about a dozen systems, but not by removing _any_ of *systemd*.
AFAICT,
sysvinit-init does nothing _except_ make sysvinit the default. From the rpm:
"Summary: Provides /sbin/init for sysvinit; Description: Just some symlinks."
Felix, I installed the package indicated by someone else, NOT you, and
rebooted. systemd controlled the boot. Then I removed systemd as was
suggested by someone else. This
gutted my system. At no time did I say that you had suggested this actions. I
did say that your information was... inaccurate.
It worked as advertised on a dozen or so systems here. How many did it fail for you for? Are you sure there wasn't also something else wrong from your previous attempts to get "rid" of systemd? I went through something like what you described up thread back in the M3-M5 devel period. When I quit trying to eliminate systemd by removing stuff, I was rid of systemd control of the init process, perfectly reverted to sysvinit AFAICT. Let's see:
https://bugzilla.novell.com/show_bug.cgi?id=723041#c1
https://bugzilla.novell.com/show_bug.cgi?id=727092
Whaddayaknow, it's in the relnotes: http://www.suse.de/relnotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html#12
Seems my response was quite accurate.
--
"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@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
| < Previous | Next > |