From: William Hubbs <williamh@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: What happened to boot.msg?
Date: Fri, 23 Oct 2009 14:00:33 -0500 [thread overview]
Message-ID: <20091023190033.GA2907@linux1> (raw)
In-Reply-To: <200910231900.34627.peter.ruskin@dsl.pipex.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Fri, Oct 23, 2009 at 07:00:34PM +0100, Peter Ruskin wrote:
> On Friday 23 October 2009 16:11:25 walt wrote:
> > On 10/23/2009 07:18 AM, Peter Ruskin wrote:
> > > I just got a new computer and I'm running ~amd64 for the first
> > > time. On my previous x86 machine (some of) the boot process was
> > > logged to /var/log/boot.msg. It doesn't do this on the new
> > > machine and I can't for the life of me recall what setting
> > > invoked this behaviour. Help??
> >
> > /etc/conf.d/rc
>
> Thanks for the reminder, walt. I have RC_BOOTLOG="yes" stored there
> and had emerged app-admin/showconsole and don't have boot splash,
> but I still don't get /var/log/boot.msg.
If you are running ~amd64 you are probably using baselayout-2 and
openrc. In that case the file you should be looking at is /etc/rc.conf and you
should not use app-admin/showconsole.
Just set RC_LOGGER to yes as shown in the comments.
--
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-23 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 14:18 [gentoo-user] What happened to boot.msg? Peter Ruskin
2009-10-23 15:11 ` [gentoo-user] " walt
2009-10-23 18:00 ` Peter Ruskin
2009-10-23 18:09 ` Peter Ruskin
2009-10-24 13:07 ` covici
2009-10-23 19:00 ` William Hubbs [this message]
2009-10-23 19:06 ` Peter Ruskin
2009-10-24 13:15 ` covici
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=20091023190033.GA2907@linux1 \
--to=williamh@gentoo.org \
--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