From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Au revoir, gnome-3.8
Date: Wed, 7 Aug 2013 20:17:53 -0500 [thread overview]
Message-ID: <CADPrc83PJ3_Bsps0BCZzOnrwSLNKAHXXqPqanHV8khfixopL+A@mail.gmail.com> (raw)
In-Reply-To: <5202EAD1.8080902@gmail.com>
On Wed, Aug 7, 2013 at 7:48 PM, walt <w41ter@gmail.com> wrote:
> On 08/07/2013 04:25 PM, gottlieb@nyu.edu wrote:
>> On Wed, Aug 07 2013, Samuli Suominen wrote:
>>
>>> On 07/08/13 05:25, gottlieb@nyu.edu wrote:
>>>> On Tue, Aug 06 2013, Samuli Suominen wrote:
>>>>
>>>>> that's only because gnome 3.8 hasn't been stabilized yet. as in, there
>>>>> are no plans in keeping gnome 2.x available after gnome 3.8
>>>>> stabilization.
>>>>
>>>> Am I correct in believing that gnome-3.8 (whether in testing as now, or
>>>> stable later) requires init=systemd? I am converting an old ~amd64
>>>> machine to systemd for practice so that I can convert my main laptop
>>>> (also ~amd64) to systemd. The purpose of the conversions is to run
>>>> gnome-3.8 and higher. I have other machines running stable. Will I
>>>> need to convert them to systemd when gnome-3.8 becomes stable and if so
>>>> will the systemd wiki be expanded.
>>>
>>> Yes, GNOME 3.8+ does require sys-apps/systemd installed and running as
>>> init= for full functionality[1]
>>>
>>> However if you don't care about full functionality[1] you can still
>>> run GNOME 3.8+ with OpenRC while sys-apps/systemd is installed
>>> (because sys-apps/systemd has it's own copy of udev that still works
>>> with OpenRC)
>>>
>>> [1] HW support, like (auto)mounting and suspend/hibernate
>>
>> Thanks for the explanation. Since suspend/resume is important for me, I
>> will keep up the effort to go to systemd.
>
> I like systemd a lot more than some other gentoo users in this group but
> as I implied in my original post, it is still very much in development,
> in gentoo anyway, and some important gentoo packages still lack the
> *.system config files that systemd absolutely needs to work with those
> packages.
>
> A good way to learn about the *.system config files is to look at other
> distros that have already switched to systemd, like fedora and arch, for
> example.
>
> I've said all this before several times in other threads, so I beg the
> forgiveness of the other old farts that hang out here :p
Just for the record, there are no "*.system config files", and systemd
comes with all its configuration files included.
What it's missing are some *.service files and (perhaps) *.socket
files for some packages; but that is easily solved by checking units
in
http://gpo.zugaina.org/sys-apps/systemd-units
or in
https://github.com/mgorny/gentoo-systemd-units
or in
https://github.com/mkszuba/systemd-gentoo-units
or even perhaps in the packages of other distributions. With systemd
is usually easy to adapt the unit files, and sometimes even to use
them directly.
And in particular, all the GNOME stack includes their necessary unit files.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-08-08 1:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 0:38 [gentoo-user] Au revoir, gnome-3.8 walt
2013-08-07 1:43 ` Samuli Suominen
2013-08-07 2:25 ` gottlieb
2013-08-07 11:02 ` Samuli Suominen
2013-08-07 23:25 ` gottlieb
2013-08-08 0:48 ` [gentoo-user] " walt
2013-08-08 1:17 ` Canek Peláez Valdés [this message]
2013-08-08 22:59 ` walt
2013-08-09 5:19 ` Samuli Suominen
2013-08-09 8:49 ` Stefan G. Weichinger
2013-08-09 9:13 ` [gentoo-user] " András Csányi
2013-08-09 9:15 ` Stefan G. Weichinger
2013-08-09 9:33 ` Alan McKinnon
2013-08-09 11:19 ` Peter Humphrey
2013-08-09 11:23 ` Alan McKinnon
2013-08-09 12:25 ` Bruce Hill
2013-08-09 12:48 ` hasufell
2013-08-09 12:58 ` Bruce Hill
2013-08-09 16:13 ` Henry W. Peters
2013-08-09 16:31 ` Canek Peláez Valdés
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPrc83PJ3_Bsps0BCZzOnrwSLNKAHXXqPqanHV8khfixopL+A@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox