Hallo, * Miles Fidelman [Sun, Nov 16 2014, 02:41:14PM]: > Andrei POPESCU wrote: > >On Du, 16 nov 14, 11:50:25, Miles Fidelman wrote: > >>So... with systemd, one has to: > >>- rely on packagers to generate systemd service files, and/or, > >>- rely on systemd's support for sysvinit scripts, which > >> > >>In the later case, one just has to read: > >>http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/ > >>to get very, very scared > >I don't see any item that would matter on a Debian system, care to > >elaborate? > > > > It's very simple. I have a bunch of stuff running on my system that I > compiled from upstream code, including init scripts that work just fine. > Now I have to worry that some of those scripts are incompatible with > systemd. You have already opened the Pandora box when you started relying on self-compiled software which is installed aside of any knowlege of dpkg. Now you hope to reduce your own efforts on upgrading by holding back any progress. Is this fair? I don't think so. If you don't see what I mean, think about all the other packages where Debian does not promise backwards compatibility (Perl/Python/... modules, etc, i.e. all that beasts that make a transition in big clusters). You already have to read the release notes now, why should we make an exception here for startup related parts? Apart from that, have ever read those init scripts from upstream packages or is this all this aversion just lazyness and fear / panic to "not touch a running system" (but do a system upgrade, ha, ha, ha)? Regards, Eduard.
Attachment:
signature.asc
Description: Digital signature