Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Tim Watts Newsgroups: comp.os.linux.misc Subject: Re: What distros *don't* use systemd ? Date: Fri, 05 Sep 2014 15:26:40 +0100 Lines: 18 Message-ID: <0qtodb-lti.ln1@squidward.local.dionic.net> References: <2kqldb-3h6.ln1@squidward.local.dionic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net AeLd9iQ4pJ3oX5Rdk6a8bwUS+ox74iRLeK1wQUnEUCnbe5ta71 X-Orig-Path: squidward.local.dionic.net!not-for-mail Cancel-Lock: sha1:tFTDGOD53QhpqXpm4iNux04GOu4= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: Xref: csiph.com comp.os.linux.misc:11959 On 05/09/14 14:47, William Unruh wrote: > They made more and more stuff in the boot process dependent on libraries > and programs in /usr/{bin,lib} rather than just in /lib. So one either > moved all of those things into /{bin,lib} or left them where they were > and used /usr/{bin,lib} The problem is that lots of people have /usr on > a different partition from /. So you must eitehr demand that /usr be > mounted in initrd or that it be onthe same partition. Once you had done > that then maintianing separate /{bin,lib} from /usr/{bin,lib} became > pointless. The post facto rational was what you list below, but that was > certainly not the reason. It was that the whole push to udev/systemd had > become a {fat pig,feature laden} which depended on far to much userland stuff. That does seem to explain it very well. Though I cannot see exactly where the deps are.