Re: [gentoo-user] Re: Au revoir, gnome-3.8
Am 09.08.2013 07:19, schrieb Samuli Suominen: 2.02.99-r1 has it's own upstream systemd files in ~arch now (they are different from what the systemd-love overlay has, AFAIK) $ qlist lvm2 |grep systemd /usr/lib/systemd/system/dm-event.socket /usr/lib/systemd/system/dm-event.service /usr/lib/systemd/system/lvm2-monitor.service /usr/lib/systemd/system/blk-availability.service /usr/lib/systemd/system/lvm2-lvmetad.socket /usr/lib/systemd/system/lvm2-lvmetad.service /usr/lib/systemd/system-generators/lvm2-activation-generator Back then I had the issue that my LVs weren't correctly activated at boot time. That was not that much of a problem as the stuff necessary for booting wasn't on LVs but anyway. I worked around that with my own service-file ... I should/could try if the new unit-files work better (and check for the diffs). I wonder if I should get rid of the systemd-love overlay? After my initial learning curve I am quite happy with systemd on two of my gentoo systems. More and more packages bring their unit-files and things get better. Stefan
[gentoo-user] Re: Au revoir, gnome-3.8
On 08/07/2013 06:17 PM, Canek Peláez Valdés wrote: And in particular, all the GNOME stack includes their necessary unit files. That's good to know. The only reason I haven't already made the switch to systemd is lvm2 -- I just couldn't puzzle out how to get lvm2 started and get the needed logical volumes active and mounted before fstab is read during bootup. I think arch has unit files for lvm2, but I've been too busy to work on it lately. I'll get there eventually.
Re: [gentoo-user] Re: Au revoir, gnome-3.8
On 09/08/13 01:59, walt wrote: On 08/07/2013 06:17 PM, Canek Peláez Valdés wrote: And in particular, all the GNOME stack includes their necessary unit files. That's good to know. The only reason I haven't already made the switch to systemd is lvm2 -- I just couldn't puzzle out how to get lvm2 started and get the needed logical volumes active and mounted before fstab is read during bootup. I think arch has unit files for lvm2, but I've been too busy to work on it lately. I'll get there eventually. 2.02.99-r1 has it's own upstream systemd files in ~arch now (they are different from what the systemd-love overlay has, AFAIK) $ qlist lvm2 |grep systemd /usr/lib/systemd/system/dm-event.socket /usr/lib/systemd/system/dm-event.service /usr/lib/systemd/system/lvm2-monitor.service /usr/lib/systemd/system/blk-availability.service /usr/lib/systemd/system/lvm2-lvmetad.socket /usr/lib/systemd/system/lvm2-lvmetad.service /usr/lib/systemd/system-generators/lvm2-activation-generator
[gentoo-user] Re: Au revoir, gnome-3.8
On 08/07/2013 04:25 PM, gottl...@nyu.edu wrote: On Wed, Aug 07 2013, Samuli Suominen wrote: On 07/08/13 05:25, gottl...@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
Re: [gentoo-user] Re: Au revoir, gnome-3.8
On Wed, Aug 7, 2013 at 7:48 PM, walt w41...@gmail.com wrote: On 08/07/2013 04:25 PM, gottl...@nyu.edu wrote: On Wed, Aug 07 2013, Samuli Suominen wrote: On 07/08/13 05:25, gottl...@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
