[gentoo-user] Re: systemd - are we forced to switch?
On 07/26/2013 06:39 AM, gottl...@nyu.edu wrote: must I check that every entry previously in /etc/init.d now has an entry in /usr/lib/systemd/system? What do I do if there is no corresponding entry? I actually had to write a few of my own *.service files, which belong in /etc/systemd/system/ instead of /usr/lib64/systemd/system. (systemd looks in both places for service files) I started playing with systemd on a virtual gentoo machine many months ago when gentoo's systemd was still very incomplete and lacked *.system files for several important packages. I'm hoping the gentoo devs have made progress with that problem, but fedora and arch linux have already made the switch to systemd and you can steal *.service files from those if you need to. BTW, I'm still using systemd only on my virtual machines so far. The recent upgrade on ~amd64 is an ugly mess IMHO.
Re: [gentoo-user] Re: systemd - are we forced to switch?
walt w41...@gmail.com wrote: On 07/26/2013 06:39 AM, gottl...@nyu.edu wrote: must I check that every entry previously in /etc/init.d now has an entry in /usr/lib/systemd/system? What do I do if there is no corresponding entry? I actually had to write a few of my own *.service files, which belong in /etc/systemd/system/ instead of /usr/lib64/systemd/system. (systemd looks in both places for service files) I started playing with systemd on a virtual gentoo machine many months ago when gentoo's systemd was still very incomplete and lacked *.system files for several important packages. I'm hoping the gentoo devs have made progress with that problem, but fedora and arch linux have already made the switch to systemd and you can steal *.service files from those if you need to. BTW, I'm still using systemd only on my virtual machines so far. The recent upgrade on ~amd64 is an ugly mess IMHO. Any documentation on what is in a service file? It does not look too bad, but I would rather see the full documentation on what you can have in there and exactly how they work. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: systemd - are we forced to switch?
systemd.unit (5) systemd.service (5) On Jul 28, 2013 6:26 AM, cov...@ccs.covici.com wrote: walt w41...@gmail.com wrote: On 07/26/2013 06:39 AM, gottl...@nyu.edu wrote: must I check that every entry previously in /etc/init.d now has an entry in /usr/lib/systemd/system? What do I do if there is no corresponding entry? I actually had to write a few of my own *.service files, which belong in /etc/systemd/system/ instead of /usr/lib64/systemd/system. (systemd looks in both places for service files) I started playing with systemd on a virtual gentoo machine many months ago when gentoo's systemd was still very incomplete and lacked *.system files for several important packages. I'm hoping the gentoo devs have made progress with that problem, but fedora and arch linux have already made the switch to systemd and you can steal *.service files from those if you need to. BTW, I'm still using systemd only on my virtual machines so far. The recent upgrade on ~amd64 is an ugly mess IMHO. Any documentation on what is in a service file? It does not look too bad, but I would rather see the full documentation on what you can have in there and exactly how they work. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: systemd - are we forced to switch?
Mark David Dumlao madum...@gmail.com wrote: systemd.unit (5) systemd.service (5) On Jul 28, 2013 6:26 AM, cov...@ccs.covici.com wrote: walt w41...@gmail.com wrote: On 07/26/2013 06:39 AM, gottl...@nyu.edu wrote: must I check that every entry previously in /etc/init.d now has an entry in /usr/lib/systemd/system? What do I do if there is no corresponding entry? I actually had to write a few of my own *.service files, which belong in /etc/systemd/system/ instead of /usr/lib64/systemd/system. (systemd looks in both places for service files) I started playing with systemd on a virtual gentoo machine many months ago when gentoo's systemd was still very incomplete and lacked *.system files for several important packages. I'm hoping the gentoo devs have made progress with that problem, but fedora and arch linux have already made the switch to systemd and you can steal *.service files from those if you need to. BTW, I'm still using systemd only on my virtual machines so far. The recent upgrade on ~amd64 is an ugly mess IMHO. Any documentation on what is in a service file? It does not look too bad, but I would rather see the full documentation on what you can have in there and exactly how they work. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com Heavens, never thought of actual man pages for those! Must be getting long in tooth. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: systemd - are we forced to switch?
Canek Peláez Valdés can...@gmail.com wrote: On Tue, Jul 23, 2013 at 2:04 AM, András Csányi sayusi.a...@sayusi.hu wrote: On 23 July 2013 08:54, Nikos Chantziaras rea...@gmail.com wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? Is there a migration guide? According to google there is no any. (or I haven't spend enough time to search) You have the wiki: https://wiki.gentoo.org/wiki/Systemd I believe it covers the most important aspects of the migration. Also, it is so much easier now; we even have a stable version on systemd in the tree. Couldn't emerge systemd its blocked by udev -- did a google search, but found some very confusing posts to do with static-libs. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: systemd - are we forced to switch?
On Wed, Jul 24, 2013 at 12:28 PM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Tue, Jul 23, 2013 at 2:04 AM, András Csányi sayusi.a...@sayusi.hu wrote: On 23 July 2013 08:54, Nikos Chantziaras rea...@gmail.com wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? Is there a migration guide? According to google there is no any. (or I haven't spend enough time to search) You have the wiki: https://wiki.gentoo.org/wiki/Systemd I believe it covers the most important aspects of the migration. Also, it is so much easier now; we even have a stable version on systemd in the tree. Couldn't emerge systemd its blocked by udev -- did a google search, but found some very confusing posts to do with static-libs. systemd *is* udev; they are the same package. Uninstall the Gentoo packaging of udev (which basically strips systemd), install systemd, and it includes the official udev. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: systemd - are we forced to switch?
Canek Peláez Valdés can...@gmail.com wrote: On Wed, Jul 24, 2013 at 12:28 PM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Tue, Jul 23, 2013 at 2:04 AM, András Csányi sayusi.a...@sayusi.hu wrote: On 23 July 2013 08:54, Nikos Chantziaras rea...@gmail.com wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? Is there a migration guide? According to google there is no any. (or I haven't spend enough time to search) You have the wiki: https://wiki.gentoo.org/wiki/Systemd I believe it covers the most important aspects of the migration. Also, it is so much easier now; we even have a stable version on systemd in the tree. Couldn't emerge systemd its blocked by udev -- did a google search, but found some very confusing posts to do with static-libs. systemd *is* udev; they are the same package. Uninstall the Gentoo packaging of udev (which basically strips systemd), install systemd, and it includes the official udev. ahhh! I see and it looks like I still don't have to use it as my init till I figure all of it out, so that will at least be a good thing. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Re: systemd - are we forced to switch?
On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead?
Re: [gentoo-user] Re: systemd - are we forced to switch?
On 23 July 2013 08:54, Nikos Chantziaras rea...@gmail.com wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? Is there a migration guide? According to google there is no any. (or I haven't spend enough time to search) -- -- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- http://facebook.com/andras.csanyi -- Trust in God and keep your gunpowder dry! - Cromwell
Re: [gentoo-user] Re: systemd - are we forced to switch?
On 23/07/13 09:54, Nikos Chantziaras wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? sure, I'm all for systemd but it's not the default yet... or rather, not tested enough to be the contigency plans. need to have contigency plans. :)
Re: [gentoo-user] Re: systemd - are we forced to switch?
On Tue, Jul 23, 2013 at 2:04 AM, András Csányi sayusi.a...@sayusi.hu wrote: On 23 July 2013 08:54, Nikos Chantziaras rea...@gmail.com wrote: On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally intended. not possible, logind since systemd = 205 requires systemd and won't work on openrc, upstart, and such as in, the idea of using logind outside of systemd is a dead end so keeping ConsoleKit in portage for long as it works for long as we need openrc for Linux based systems and when it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead? Is there a migration guide? According to google there is no any. (or I haven't spend enough time to search) You have the wiki: https://wiki.gentoo.org/wiki/Systemd I believe it covers the most important aspects of the migration. Also, it is so much easier now; we even have a stable version on systemd in the tree. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
