| 1 |
On Wed, Aug 7, 2013 at 7:48 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> On 08/07/2013 04:25 PM, gottlieb@×××.edu wrote: |
| 3 |
>> On Wed, Aug 07 2013, Samuli Suominen wrote: |
| 4 |
>> |
| 5 |
>>> On 07/08/13 05:25, gottlieb@×××.edu wrote: |
| 6 |
>>>> On Tue, Aug 06 2013, Samuli Suominen wrote: |
| 7 |
>>>> |
| 8 |
>>>>> that's only because gnome 3.8 hasn't been stabilized yet. as in, there |
| 9 |
>>>>> are no plans in keeping gnome 2.x available after gnome 3.8 |
| 10 |
>>>>> stabilization. |
| 11 |
>>>> |
| 12 |
>>>> Am I correct in believing that gnome-3.8 (whether in testing as now, or |
| 13 |
>>>> stable later) requires init=systemd? I am converting an old ~amd64 |
| 14 |
>>>> machine to systemd for practice so that I can convert my main laptop |
| 15 |
>>>> (also ~amd64) to systemd. The purpose of the conversions is to run |
| 16 |
>>>> gnome-3.8 and higher. I have other machines running stable. Will I |
| 17 |
>>>> need to convert them to systemd when gnome-3.8 becomes stable and if so |
| 18 |
>>>> will the systemd wiki be expanded. |
| 19 |
>>> |
| 20 |
>>> Yes, GNOME 3.8+ does require sys-apps/systemd installed and running as |
| 21 |
>>> init= for full functionality[1] |
| 22 |
>>> |
| 23 |
>>> However if you don't care about full functionality[1] you can still |
| 24 |
>>> run GNOME 3.8+ with OpenRC while sys-apps/systemd is installed |
| 25 |
>>> (because sys-apps/systemd has it's own copy of udev that still works |
| 26 |
>>> with OpenRC) |
| 27 |
>>> |
| 28 |
>>> [1] HW support, like (auto)mounting and suspend/hibernate |
| 29 |
>> |
| 30 |
>> Thanks for the explanation. Since suspend/resume is important for me, I |
| 31 |
>> will keep up the effort to go to systemd. |
| 32 |
> |
| 33 |
> I like systemd a lot more than some other gentoo users in this group but |
| 34 |
> as I implied in my original post, it is still very much in development, |
| 35 |
> in gentoo anyway, and some important gentoo packages still lack the |
| 36 |
> *.system config files that systemd absolutely needs to work with those |
| 37 |
> packages. |
| 38 |
> |
| 39 |
> A good way to learn about the *.system config files is to look at other |
| 40 |
> distros that have already switched to systemd, like fedora and arch, for |
| 41 |
> example. |
| 42 |
> |
| 43 |
> I've said all this before several times in other threads, so I beg the |
| 44 |
> forgiveness of the other old farts that hang out here :p |
| 45 |
|
| 46 |
Just for the record, there are no "*.system config files", and systemd |
| 47 |
comes with all its configuration files included. |
| 48 |
|
| 49 |
What it's missing are some *.service files and (perhaps) *.socket |
| 50 |
files for some packages; but that is easily solved by checking units |
| 51 |
in |
| 52 |
|
| 53 |
http://gpo.zugaina.org/sys-apps/systemd-units |
| 54 |
|
| 55 |
or in |
| 56 |
|
| 57 |
https://github.com/mgorny/gentoo-systemd-units |
| 58 |
|
| 59 |
or in |
| 60 |
|
| 61 |
https://github.com/mkszuba/systemd-gentoo-units |
| 62 |
|
| 63 |
or even perhaps in the packages of other distributions. With systemd |
| 64 |
is usually easy to adapt the unit files, and sometimes even to use |
| 65 |
them directly. |
| 66 |
|
| 67 |
And in particular, all the GNOME stack includes their necessary unit files. |
| 68 |
|
| 69 |
Regards. |
| 70 |
-- |
| 71 |
Canek Peláez Valdés |
| 72 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 73 |
Universidad Nacional Autónoma de México |
Archives