On 20150330_1433-0400, Ric Moore wrote: > On 03/30/2015 12:40 PM, Andrew McGlashan wrote: > >On 31/03/2015 3:18 AM, Andrew McGlashan wrote: > >>On 31/03/2015 1:00 AM, Renaud (Ron) OLGIATI wrote: > >>>http://distrowatch.com/weekly.php?issue=20150330#community > >> > >>It's too early for an April fools joke, no matter where you live. > >> > >>>Or is it serious ? > >> > >>Lennart Linux lives on.... give us back Linus Linux, please! Enough of > >>this systemd nonsense already before it really is too late. > >> > >>A. > > > >https://github.com/systemdaemon/systemd/issues > > > >Clearly an early April Fools.... but it is very plausible, this is where > >Linux IS going.... :( > > If you cock your head to one side, close one eye and squint, it actually > makes sense. Unpopular? Maybe so, but it still makes sense, if only to make > Linux less of a moving target for people to develop on. > > I'd LOVE to see one unified directory structure to rule them all, for > instance. Imagine nVidia could deliver it's driver and have only one spot to > install to across all of the distros. Yes, I would love to get rid of > network manager as long as something BETTER replaces it. There's the rub as > well. It's a lack of portability that keeps the Linux Desktop down there > with the bottom feeders. > > One thing is for sure, systemd BETTER work as advertised, for all the > controversy they have created. :/ Ric
When I first heard about systemd, which was not so long ago, the decision for Debian to actually switch to systemd seemed to me to have already been made. I'm not responsible for some computer systems in some large organization, so my major concern was can I understand this new stuff? I noticed the new word 'cgroup'. I soon found out (from Wikipedia) that this was a major new feature that, after a long development, was finally a part of the Linux kernel, and differentiated it from other OS kernels. It seems to me there are many other ways of using cgroups than just systemd. They were not invented for the purpose of a disruptive departure from the Unix/Posix tradition, but for solving problems that were entirely within the kernel, or so it seemed at the time. If there is any reality to systemd people forking the kernel, I'm sure there will be plenty of kernel developers who will be happy to see them go, so that they can get on with the fun of applying cgroups to the problems for which they were developed, so it seems. There may be kernel developers who are interested in forking systemd and cleaning out the cruft brought on by a rushed development. ;-) -- 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/20150330224359.ga20...@big.lan.gnu
