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

[Stephen John Smoogen]

On Wed, Jul 21, 2010 at 19:30, Lennart Poettering <mzerqung at 0pointer.de> wrote:
> On Wed, 21.07.10 20:08, Toshio Kuratomi (a.badger at gmail.com) wrote:


> It is needed:
>
> if [ $1 -eq 1 ] ; then
>        # For new installations, hook unit file into the appropriate places via symlinks
>        /usr/bin/systemd-install enable --realize=reload %{unit name}.service > /dev/null 2>&1 || :
> else
>        # For old installations, just reload the configuration, don't change symlinks
>        /bin/bin/systemd-install realize --realize=reload %{unit name}.service > /dev/null 2>&1 || :
> fi
>

Ok from dealing with many years of technical support it has been
hammered into me that if you are replacing a command, make sure the
replacement makes more sense than the thing it 'replaces' (in this
case chkconfig which people seem to intuit means check configuration).
Putting my head into a customers head the first thing before the
complicated syntax is "why am I running something called install to
change a service?"

I will forego the bikeshedding and say it should be sysconfig or
syssetup but I do believe it will cause a lot of complaints.

-- 
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines