[HEADS-UP] systemd for F14 - the next steps

drago01 drago01 at gmail.com
Wed Jul 21 15:16:40 UTC 2010


On Wed, Jul 21, 2010 at 3:14 PM, Chris Adams <cmadams at hiwaay.net> wrote:
> Once upon a time, "Jóhann B. Guðmundsson" <johannbg at gmail.com> said:
>> And as the general rule goes "native configuration breaks legacy
>> configuration" so if a native systemd $service file does exist than
>> changing service via chkconfig no longer will work.
>
> As an admin, this is crap.  Where does this "general rule" come from?
> As strong desire to piss off the people that actually use your software?

So "different == crap" ?

If it does provide a hard to use interface I'd understand the
frustration but only because it is NEW / DIFFERENT does not mean that
the world is falling over.

Seriously an admin that refuses to learn anything new ("omg it isn't
the same as I have been doing for the last 10 years)  he should really
consider changing job / profession.

Changes aren't bad for the sole reasons of being changes.

If the new interface is crap ok complain about it but it being
different (as long as it is documented) is a non issue IMO.


More information about the devel mailing list