From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] a few blockers I can't figure out
Date: Mon, 31 Aug 2015 09:37:10 -0400 [thread overview]
Message-ID: <20150831133710.GA546@apio.adsroot.itcs.umich.edu> (raw)
In-Reply-To: <55E44B22.9090806@gmail.com>
On Mon, Aug 31, 2015 at 02:40:02PM +0200, Alan McKinnon wrote:
> On 31/08/2015 13:49, covici@ccs.covici.com wrote:
> >> A clue is in the ebuilds for systemd:
> >> >
> >> > sysv-utils? (
> >> > !sys-apps/systemd-sysv-utils
> >> > !sys-apps/sysvinit )
> >> >
> >> > That's a hard blocker, no way round it. It's in all the systemd ebuilds
> >> > for the current unstable versions.
> >> >
> >> > Do you have USE="sysv-utils" set for sysvinit?
> >> >
> >> > If so, to have both sysvinit and systemd, you will have to disable that
> >> > USE flag and see what comes next.
> > I put that use flag in there because I thought it would allow systemd to
> > generate a service from a script in /etc/init.d, but I will see what
> > happens when I remove that flag or maybe if there is another way to
> > accomplish that?
> > Well, that did it! It still is downgrading systemd, but that's not too
> > bad, thanks guys.
>
> $ euses -sf sysv-utils
> sys-apps/systemd:sysv-utils - Install sysvinit compatibility symlinks
> and manpages for init, telinit, halt, poweroff, reboot, runlevel, and
> shutdown
>
>
> That description is quite vague, and could mean many things. I'm no
> expert on systemd, but I would imagine that it already has it's own
> scripts to deal with those listed functions. I wonder what the use of
> the flag is then? Perhaps an old compatibility layer than is not needed now?
This means that it installs /bin/poweroff, /bin/reboot, etc. and the
relevant manpages. I'm pretty sure that's all it does.
It is not needed at all, as long as you don't mind typing `systemctl
poweroff' instead of `poweroff', and so on and so forth. I guess the
/bin/init symlink would be helpful so that you don't have to add
`init=/usr/lib/systemd/systemd' to the kernel commandline, but whatever.
Alec
next prev parent reply other threads:[~2015-08-31 13:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 4:19 [gentoo-user] a few blockers I can't figure out covici
2015-08-31 8:50 ` Neil Bothwick
2015-08-31 9:04 ` covici
2015-08-31 9:36 ` Alan McKinnon
2015-08-31 11:03 ` covici
2015-08-31 11:10 ` Alan McKinnon
2015-08-31 11:49 ` covici
2015-08-31 12:40 ` Alan McKinnon
2015-08-31 13:37 ` Alec Ten Harmsel [this message]
2015-08-31 14:03 ` covici
2015-08-31 14:53 ` Alan McKinnon
2015-08-31 16:54 ` covici
2015-08-31 17:02 ` Neil Bothwick
2015-08-31 18:12 ` covici
2015-08-31 22:18 ` Alan McKinnon
2015-09-01 0:12 ` covici
2015-09-01 9:55 ` Alan McKinnon
2015-09-01 10:15 ` Rich Freeman
2015-09-01 11:13 ` covici
2015-09-01 11:45 ` Rich Freeman
2015-09-01 11:54 ` covici
2015-09-01 10:18 ` Marc Joliet_1
2015-09-01 10:46 ` Alan McKinnon
2015-09-01 11:03 ` covici
2015-09-01 11:15 ` Alan McKinnon
2015-08-31 23:51 ` Jeremi Piotrowski
2015-09-01 0:22 ` covici
2015-09-02 11:57 ` [gentoo-user] " walt
2015-09-02 12:45 ` Rich Freeman
2015-09-02 13:06 ` Jeremi Piotrowski
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=20150831133710.GA546@apio.adsroot.itcs.umich.edu \
--to=alec@alectenharmsel.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