From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: heads-up: 2011-05-01 baselayout news
Date: Mon, 02 May 2011 17:16:54 -0700 [thread overview]
Message-ID: <ipnhhm$q8f$1@dough.gmane.org> (raw)
In-Reply-To: <201105021044.00925.michaelkintzios@gmail.com>
On 05/02/2011 02:43 AM, Mick wrote:
> I've been through the migration guide. In the section about udev it mentions
> /etc/runlevels/sysinit. Is this something added by baselayout2/OpenRC? I
> don't seem to have this in my runlevels:
>
> $ ls -l /etc/runlevels/
> total 16
> drwxr-xr-x 2 root root 4096 Jan 18 20:39 boot
> drwxr-xr-x 2 root root 4096 Jun 8 2010 default
> drwxr-xr-x 2 root root 4096 Jan 21 2010 nonetwork
> drwxr-xr-x 2 root root 4096 Jan 21 2010 single
The confusion with all of this booting stuff goes back to the very dawn
of unix, long before linux appeared. I learned at the knee of someone who
actually remembers the dawn -- but of course I'm much too young myself :p
The conflict between "environment" and "profile", the origins of ".profile"
and ".bashrc" go back IIRC to the competition between sh, csh, and bash for
dominance -- not to mention ksh, tsh, foosh, and barsh, bahsh etc, etc.
Each shell had its own private configuration file(s), which needed distinct
names, of course, to avoid chaos. Chaos prevailed, predictably, because of
these conflicting standards, and you/we are still dealing with the problem
today. (No, I am NOT complaining, I'd be bragging except I had nothing to do
with any of it. But I did have the honor of meeting many very smart people
who do have real bragging rights.)
Anyway, to answer your specific question,
#equery b sysinit
* Searching for sysinit ...
sys-apps/openrc-0.8.2-r1 (/usr/share/openrc/runlevels/sysinit)
#equery b inittab
* Searching for inittab ...
sys-apps/sysvinit-2.88-r1 (/etc/inittab)
Why did I search for inittab? Here's a wee hint while I'm off to bed:
#grep sysinit /etc/inittab
si::sysinit:/sbin/rc sysinit
prev parent reply other threads:[~2011-05-03 0:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 9:03 [gentoo-user] heads-up: 2011-05-01 baselayout news Thanasis
2011-05-02 9:11 ` Thanasis
2011-05-02 9:31 ` Mick
2011-05-02 17:11 ` Mark Knecht
2011-05-02 17:36 ` Mick
2011-05-02 17:55 ` Mark Knecht
2011-05-03 2:23 ` William Hubbs
2011-05-02 18:02 ` Neil Bothwick
2011-05-02 18:16 ` Mark Knecht
2011-05-02 18:48 ` Neil Bothwick
2011-05-02 18:54 ` Mark Knecht
2011-05-02 22:07 ` Mark Knecht
2011-05-03 5:07 ` Mick
2011-05-02 19:00 ` Felix Leif Keppmann
2011-05-02 10:18 ` Dale
2011-05-02 9:43 ` Mick
2011-05-02 10:05 ` Mick
2011-05-02 10:26 ` Thanasis
2011-05-02 10:50 ` Mick
2011-05-02 11:25 ` Thanasis
2011-05-02 11:52 ` Alex Schuster
2011-05-02 12:35 ` Mick
2011-05-05 8:25 ` Alex Schuster
2011-05-05 9:06 ` Alan McKinnon
2011-05-05 19:57 ` Mick
2011-05-02 10:06 ` Thanasis
2011-05-03 0:16 ` walt [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='ipnhhm$q8f$1@dough.gmane.org' \
--to=w41ter@gmail.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