User: Password:
|
|
Subscribe / Log in / New account

Evil

Evil

Posted Jun 23, 2013 15:43 UTC (Sun) by mathstuf (subscriber, #69389)
In reply to: Evil by zblaxell
Parent article: Changes coming for systemd and control groups

> I'll help Debian maintain a fork with sensible defaults if they ever adopt systemd, but I have no hope for upstream.

Please don't. One of the goals of systemd was to help standardize another layer of Linux. By doing the above, you'd only make a Debianism and make things still need distro checks for behavior.


(Log in to post comments)

Evil

Posted Jun 26, 2013 13:04 UTC (Wed) by hummassa (subscriber, #307) [Link]

Debian is not only Linux.

There are Debians with FreeBSD and NetBSD kernels, Solaris, and even Hurd. Systemd is (as it should be) available as an OPTION for Debian, but it should not be the default until it works at least as well as sysvinit in the other platforms.

Evil

Posted Jun 26, 2013 13:10 UTC (Wed) by micka (subscriber, #38720) [Link]

Is the default init system necessarily the same on all kernels ? I'm sure there are far more differences.

And if those other kernels are a technical obstacle to some progress, maybe the alternate kernel subproject should be asked to fix the problem themselves ?

Evil

Posted Jul 3, 2013 13:55 UTC (Wed) by zblaxell (subscriber, #26385) [Link]

It wouldn't be the first time someone tried to import some insane bug from some other community to Debian in the name of cross-distro consistency. I can't see any reason why I wouldn't work to push it back out again just like others before.

I realize some people disagree with me on this point. Several of them have posted here, repeating the assertion that they are not wrong after I just finished pointing out why they are. ;) Forks happen if your code's behavior as distributed is insane. This is one reason why we have different distributions.

I would likely only advocate a change to the default behavior, since the feature does have sane special cases and there seems to be commitment from upstream to maintain both behavior modes (although if it has to be configured in hundreds of separate places then a new global configuration point might still be preferable).

Packages that explicitly depend on having their processes killed under a possibly unconstrained list of scenarios defined by strangers from the future can always explicitly request that in their systemd configuration glue to ensure consistent cross-distribution behavior. All other packages will be much happier (and safer!) if left alone.


Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds