On Tue, Aug 24, 2010 at 09:33:50PM +0200, Lennart Poettering wrote:
What would make sense to add to chkconfig is something that checks
whether a systemd unit is installed and then prints "Hey, you have a
systemd unit installed, chkconfig won't do what you think it will do for
this unit" or so.
This is a very big change. chkconfig has worked for a long, long time. Its
elegance and simplicity is one of the nice administrative features of Red
Hat based distributes. People like it.
If you take it away and print a message about how the user is doing it
wrong, this will create negative energy. I think I gave the example of
nslookup vs. host and dig -- that created a huge amount of grumbling among
sysadmins, and _the new thing was clearly better_.
It may be that the change is worth it. But then, you have to do three things:
1) sell the advantages of the new thing really hard. There MUST be cake.
2) DO NOT discount the pain of changing. Cuddle people; be on their side.
If you overlook the importance of this, you're shooting systemd in the foot
and it's going to have to limp up the hill.
Even if chkconfig is just one silly command that doesn't matter very much.
Really! It is the case.
I'm starting to feel a bit like Cassandra here.
Matthew Miller <mattdm(a)mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Harvard School of Engineering & Applied Sciences