Hi all,
for me I've solved it by changing back to sysvinit which is way more
fast for me on my system and less buggy it didn't mess up with my
raids which systemd still did 2 times by now, despite of the fix in
md.service. With sysvinit my system is up and runnign all services in
round about 15 seconds from the time grub starts booting to all
services up and running. For systemd it took over 5 minutes until all
network services were available.
I'll give systemd a next try in 12.2 ;)
Thanks all for your help with systemd but its still to new so I'm
personally stick with the old sysvinit in the 12.1 release until
systemd lost all its initial problems. Sorry for not helping in
further debugging but now I need to set up the machine to production
and I'm not able to risk any problems with the RAIDs again.
Greetings,
Andreas
On Tue, Nov 15, 2011 at 07:02, Raymond Wooninck
On Monday 14 November 2011, Roger Luedecke wrote:
That all seems rather odd as I haven't experienced any network anomalies whatsoever in RC2. But what that is really saying is the bug is more complicated than it may seem on the surface. --
Hi Roger,
But did you ever tried to boot the system without a network connection ? In the meantime I have found the little bugger and I will discuss the issue further with Frederic Crozat to see how we can resolve it.
Regards
Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org