On 09/04/2012 05:15 PM, Claudio Freire wrote:
On Tue, Sep 4, 2012 at 3:30 AM, Vincent Untz
wrote: Another sample: openSUSE rccrypto scripts, they do not work, and are not going to be repaired.
It's simply because things work differently in systemd. The features provided by rccrypto scripts in sysvinit are also present in systemd, but just provided another way.
Or am I missing something?
IMVHO, instead of breaking everything, rccrypto scripts should have invoked that functionality you mention to make it transparent to the user.
This is all assuming that functionality is there and really equivalent as you say (which in some cases I remember it was not, like the case of vmware stuff and everything status-querying-related).
Why do I think so? Because sysadmins all over the place (and end users too) have a large body of scripts they will want to... not rewrite. You can't remove "rcstuff" and say it's ok, it's not on your users eyes. If you don't care, well, you're entitled not to care. As your users are entitled to be upset.
In the past there was a lot of difference on how distros booted and how you interacted with your init systems. Systemd allows to unify some of that - and I think that's good. Btw. in general rcXXX contains to work fine on openSUSE with systemd, the engineers took care that it works - instead of declaring it as obsolete etc. A couple of guys did take care that many of the ways you interact today with SysV init work the same way with systemd - that makes the transition easier... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org