On 20140519_1645+0100, Brian wrote: > On Tue 20 May 2014 at 01:16:34 +1000, Chris Angelico wrote: > > > On Tue, May 20, 2014 at 12:51 AM, Brian <a...@cityscape.co.uk> wrote: > > > (presumably quoting someone else's post) > > > Per 6.3.2, I use my casting vote to choose D as the winner. > > > > Sorry for the dumb question, but what does the section number refer > > to? I feel I've missed some context here. > > The section number: > > https://www.debian.org/devel/constitution > > The context and the mail I quoted from: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708
At this point in reading this long thread, I broke off on it and started reading the long thread on bug=727708. In that I discovered the claim that Systemd will never support or be compatible with either BSD or HURD. I surmise, on my very limited knowledge that this is because only Linux implements Linux cgroups, and/or because Linux implements some other feature that is made possible by cgroups. But there was a time when this was not true of Linux. Cgroups are a recent addition to Linux, a kind of 'disruptive' technology. I wonder why it is assumed that BSD and/or HURD could not be modified (improved ;-) to also support cgroups. Personally, I am intrigued by the claims made for cgroups, and systemd. Are they really so disruptive as they appear to be. There certainly is a lot of disruption here on this list. Can the forces of caution really overcome the forces of progress? If Debian succeeds with systemd, as I hope it will, how long will it take the developers of BSD and/or HURD to implement a forward looking response? Not long, I guess. But this post is here, not because I know, but in order to provoke some intelligent, reasoned, and informed discussion of this suggestion. Have at it, intelligent people ;-) -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140520025456.gb30...@big.lan.gnu
