From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 185A81381F3 for ; Thu, 16 May 2013 02:30:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C5CF0E08F3; Thu, 16 May 2013 02:30:37 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [74.208.4.201]) by pigeon.gentoo.org (Postfix) with ESMTP id D4338E08E2 for ; Thu, 16 May 2013 02:30:36 +0000 (UTC) Received: from [192.168.1.144] ([70.40.230.100]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0MFdTP-1UgQbh1EjV-00Efp8 for ; Thu, 16 May 2013 04:30:36 +0200 Message-ID: <519444CA.5050308@gmx.com> Date: Wed, 15 May 2013 21:30:34 -0500 From: Daniel Campbell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: Re: [gentoo-dev] Making systemd more accessible to "normal" users References: <20130508190832.0ea16c88@gentoo.org> <518A8901.6030302@gmail.com> <20130510094500.62b0c958@sera-20.lan> <5191F8B7.9080006@gentoo.org> <20130515141755.4d53f21e@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:PNzkAsCceX6lngLiPh9KymClNrQAYzGeux1LQDR2SanORr0uP2z 6TiYRdWZYZZnuZCmEVB/tlnql/4XNellp3YQjLdK0KhLASADNN6BMtduwhCY0t/AopKajE7 XEYabh7XC8M43eO2LZgWtCmwkk78uxKX6lBGUwkUPuUnVn0YV2n6VMlQiNxlCD0Qs8QzYhN N/XkulTvoy2S+0ywopzaQ== X-Archives-Salt: 691a8aec-a9f7-46b7-a58e-840eec38271e X-Archives-Hash: 85fd696a487cda497e226b3e8fa22cd7 On 05/15/2013 08:41 AM, Fabio Erculiani wrote: > Are we realizing that in order to keep systemd out of our way, we're > currently writing and maintaining drop-in replacements for the > features that systemd is already providing in an actively maintained > state? openrc-settingsd was the first thing that we as Gentoo > developers (Pacho?) had to write in order to merge GNOME 3.6 into our > tree. > > And now that GNOME 3.8 is out, the game starts over again: logind is a > hard requirement, logind is part of systemd, starting logind (which > replaces consolekit) is not that trivial as you may think (and is the > thing I started to work on anyway). > > And if this wasn't enough, it means that if you want GNOME 3.8, you > need to get logind, which may or not may get included in our udev > ebuild and if it won't, it means that you will be forced to use > systemd as device manager if you want GNOME 3.8, which is believe it > or not, the thing that Ubuntu did. > > The problem will only increase in size as the clock moves. > > And (and!) how does all this fit together with eudev? If the idea is > to either put logind in udev (thus, not creating a separate logind > ebuild), it means that eudev is already a dead end for GNOME users, > unless the eudev team is going to provide logind as well. > > I don't want to start a flamewar here, I was the one who called > Lennart software lennartware, but science is science, and a reality > check had to be done: at some near point in the future, our users will > be forced to replace udev/eudev with systemd. Like it. Or not. > > While I successfully use both openrc and systemd, I _do_ think that > (and expect to see) more and more users (and developers) will be > switching to systemd. > Is there anything we can do? Besides "being prepared", I don't think so. > Do we control upstreams? No, sorry. > > So what do we want to do then? Isolate from the rest of the world? > (It's not a sarcastic question). I hope that everybody does their own > reality check. > The solution is to pressure upstreams not to depend on a specific init system in order to function. How many pieces of software depend on SysV, runit, openrc, or upstart? The only ones I can think of are the pieces that are designed specifically for making those init systems easier to administer, not user-facing software like desktop environments. I sincerely believe that each user and distro reserves the right to choose which software to boot the system with, and desktop environments and other user-facing software should not care about which init system it's running on. In the case of GNOME, I think they're going too far by depending on these things. GNOME devs haven't cared much for user responses (especially wrt GTK+ 3.x), so they are likely to continue integration with systemd. They're free to, but we're free to not use it, too. Personally, I will not have systemd on my box(es). I don't agree with its motives, its methods, or its design. I will not use software that depends on it. If the situation gets bad enough, then I may be forced to switch to another OS... that bothers me, to a degree, but as long as it's on my hardware, I have a say. It would not bother me if distros ostracized Lennart and his projects from the free software world, as he approaches free software with a toxic attitude. We wouldn't miss much IMO. As for Gentoo itself, I'm happy as long as choice remains the governing principle.