On Sat, Jun 11, 2011 at 08:29:17PM +0200, jdd wrote:
Le 11/06/2011 18:39, Greg KH a écrit :
It should "just work" so there should not be anything you have to learn about, right?
wrong.
I had quite often to edit init scripts for adapt to local situations, so I don't see why systemd could be any better in this respect (it's not it's fault), so if these scripts are no more used I will have to learn new things
Of course if you need to customize things you will have to adapt, to think otherwise is crazy. But for the majority of people out there, they never have to edit an init script. Heck, I haven't had to touch one myself for many many years now and I use Linux in all sorts of different situations.
The moves from lpr to cups and to come from grub to grub2 or xorg.conf removed did no good for my configs, hal to udev also
That is application configurations, and have nothing to do with systemd.
not to say we don't have to make moves, but often it is moving from something simple to something complicated that don't always work
systemv simple? Hah.
by the way I have a bug against systemd with no usefull answer (and only one answer, by the way), so I wonder if the debugging is already done
if you remember, openSUSE did some bad moves in the past, so don't be surprised if people are frightened.
People are always worried about change, I understand. Personally I think they should go use slackware if they are that concerned about change :) It's as if people here don't trust the developers of the system that they use to do the right thing. And that's an attitude that is not very wise, or useful. greg k-h -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org