public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: renaming "rc" binary in OpenRC
Date: Sat, 14 Dec 2013 12:47:47 +0000 (UTC)	[thread overview]
Message-ID: <pan$92a69$819486e$f3c278cf$c228954a@cox.net> (raw)
In-Reply-To: 20131213220357.GA18419@linux1

William Hubbs posted on Fri, 13 Dec 2013 16:03:57 -0600 as excerpted:

> On Fri, Dec 13, 2013 at 07:53:59PM +0000, Duncan wrote:
>> William Hubbs posted on Fri, 13 Dec 2013 11:23:07 -0600 as excerpted:
>> 
>>>  There are reasons to run the rc binary directly; this is how you
>>>  should be changing runlevels.
>> 
>> ???
>> 
>> init 9 (or telinit 9, yes, I have a runlevel 9, basic, just gpm as it
>> happens) isn't appropriate?
> 
> Well, I have to qualify what I said.
> 
> There are two "runlevels" you have to worry about.
> The OpenRC runlevels are named; you can switch between these using rc
> directly, for example:
> 
> rc default
> rc single
> rc nonetwork
> 
> The sysvinit runlevels are the numbered ones, and these are mapped to
> things to run, like 3 is mapped to /sbin/rc default. I believe runlevel
> 3 is mapped to other things in inittab, so, I guess the best answer is,
> it depends on what you are wanting to change. Does that make sense?

Yes, it does.  Thanks.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



      reply	other threads:[~2013-12-14 12:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 20:41 [gentoo-dev] rfc: renaming "rc" binary in OpenRC William Hubbs
2013-12-11 20:47 ` Alon Bar-Lev
2013-12-11 21:04   ` William Hubbs
2013-12-11 20:47 ` Chris Reffett
2013-12-11 20:53   ` Markos Chandras
2013-12-11 21:28     ` [gentoo-dev] " Duncan
2013-12-11 22:46       ` William Hubbs
2013-12-11 20:56   ` [gentoo-dev] " Paul Tagliamonte
2013-12-11 21:09     ` Markos Chandras
2013-12-11 21:14       ` Paul Tagliamonte
2013-12-11 22:50       ` William Hubbs
2013-12-11 21:28   ` Rich Freeman
2013-12-12  0:41     ` Patrick Lauer
2013-12-12  8:26       ` [gentoo-dev] " Martin Vaeth
2013-12-12 12:56       ` [gentoo-dev] " Rich Freeman
2013-12-12  0:37 ` Patrick Lauer
2013-12-12  1:38   ` Doug Goldstein
2013-12-12  7:41 ` Samuli Suominen
2013-12-12 15:15   ` William Hubbs
2013-12-12 15:46 ` Alexander Berntsen
2013-12-13 12:31   ` Samuli Suominen
2013-12-13 13:31     ` Alexander Berntsen
2013-12-13 15:59   ` Mike Gilbert
2013-12-13 17:23     ` William Hubbs
2013-12-13 19:53       ` [gentoo-dev] " Duncan
2013-12-13 22:03         ` William Hubbs
2013-12-14 12:47           ` Duncan [this message]

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='pan$92a69$819486e$f3c278cf$c228954a@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@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