On 07/21/2010 04:03 PM, Jeff Spaleta wrote:

Would it be reasonable to extend chkconfig so that it can know which
services it can no longer control and provide a pointer blurb to
admins when they try to use chkconfig with those services in the F14
timeframe. The reality is any change to scriptable behaviour is a
pitchfork wielding mob scenario. (mental note: this would make a good
Simpson's episode)


If we are breaking curmudgeony workflows it be really nice to provide
some breadcrumbs along the way to help us old dogs learn new tricks.
Admins are going to need to learn how to use and configure systemd
native configs in the F14 timeframe, feedback from the "legacy" system
tools when we need to recondition our muscle memory and are scripted
actions would go a long way to lowering the frustration level...if the
native/legacy tool break can't be avoided.

FYI. There is work being done to allow as smooth transaction as possible.

Lennart has added to his todo list to look at letting systemd-install fallback to chkconfig if no native systemd service file is found which will smooth the transaction from the legacy chkconfig to systemd-install enable/disable $foo.service.

There is an RFE for the same compatibility from chkconfig #616857 as in chkconfig will try to use systemd native files first and spill out a deprecation warning or just spill out deprecation warning hinting users ( Written in C patches welcome ) and #612728 is dealing with users that directly run /etc/init.d/foo along the way cleaning some other stuff which should have been done eons ago and I suspect /sbin/service will be fixed at the same time.

< rant at those nei sayers >

I must say it's interesting to see how the community holds so dear to the code that was forge by putting holes in paper and have absolutely no problem screaming at baby when it's barely out of it's birth canal. . .

Regular desktop end user wont notice any other change other than perhaps faster bootup and the people that call themselves "power/advanced/admin" users should have no problem to adapt and are urged from the start to use systemd-install and systemctl however if there is nothing but air in that power and the only thing they are capable of administrating are themselves with the only advancement they show is getting closer to the door on their way out, there is a point and click operating system waiting for them around the corner which they can play power/advanced/admin crossword pussle by checking random boxes to make things work for them or they can choose to stay on F13 until it EOL then switch to F15 which hopefully all upstream has provided native systemd service files for their daemon and most if any cruff has been sorted out.

For god sakes people alpha aint even out the door yet!

</rant at those nei sayers >

JBG