From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] changing inittab
Date: Fri, 03 Aug 2007 11:56:43 -0700 [thread overview]
Message-ID: <1186167403.8470.14.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <20070802202809.GP18333@ifa.hawaii.edu>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
On Thu, 2007-08-02 at 10:28 -1000, Joshua Hoblitt wrote:
> > <rhetorical>
> > Why don't people trust that the guy who writes all this crap knows what
> > he's talking about?
> > </rhetorical>
> >
> > :P
>
> Your assertion is that it's completely obvous that a variable named
> "bootargs", that passes options to the kernel, would have other magical
> side effects?
No, my assertion is that when I provide a solution to someone's query
that I might know what I'm talking about. ;]
> > Normally, yes, it would only be good for kernel output, but as someone
> > else mentioned, you have livecd-functions.sh that re-writes the inittab.
> > Well, guess what triggers it? That's right, a "console=" option on the
> > command line. If you type (or via catalyst, add) console=something,
> > livecd-functions.sh (via functions.sh in baselayout) will interpret it
> > and modify inittab accordingly before we ever even hit runlevel 3, so it
> > starts a console on that serial line for login.
>
> Seriously, can you cut and paste that paragraph into the manual?
Ehh... What manual?
There's no manual for catalyst that is current. Also, I don't have the
time (or the desire) to document all of the idiosyncrasies of the
packages that make up a Gentoo LiveCD build. We use quite a few
packages that other people don't need to use on their own media.
Remember that everything written by Release Engineering is designed for
Release Engineering consumption. No guarantees are made to anyone else
on anything. We guarantee that it will build a release the way we want
it given a particular package set with specific versions, the exact ones
used by us for our builds. Also, realize that livecd-tools is *not*
catalyst and shouldn't be documented with catalyst.
> Thanks for your help.
You're quite welcome. This list is pretty much here just so people can
get help using catalyst, so feel free to ask anything that you need.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-03 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:13 [gentoo-catalyst] changing inittab Joshua Hoblitt
2007-08-01 10:26 ` Nelson Batalha
2007-08-01 14:00 ` Scott Biddlestone
2007-08-01 16:58 ` Chris Gianelloni
2007-08-01 21:55 ` Joshua Hoblitt
2007-08-02 0:26 ` Chris Gianelloni
2007-08-02 20:28 ` Joshua Hoblitt
2007-08-03 18:56 ` Chris Gianelloni [this message]
2007-08-02 23:05 ` Joshua Hoblitt
2007-08-03 0:01 ` Andrew Gaffney
2007-08-03 19:01 ` Chris Gianelloni
2007-08-04 8:55 ` Joshua Hoblitt
2007-08-04 21:11 ` Andrew Gaffney
2007-08-03 19:00 ` Chris Gianelloni
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=1186167403.8470.14.camel@inertia.twi-31o2.org \
--to=wolf31o2@gentoo.org \
--cc=gentoo-catalyst@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