* [gentoo-user] What happened to boot.msg?
@ 2009-10-23 14:18 Peter Ruskin
2009-10-23 15:11 ` [gentoo-user] " walt
0 siblings, 1 reply; 8+ messages in thread
From: Peter Ruskin @ 2009-10-23 14:18 UTC (permalink / raw
To: gentoo-user
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??
--
Peter
========================================================================
Gentoo Linux: Portage 2.2_rc46 kernel-2.6.31-gentoo-r3
AMD Phenom(tm) 9950 Quad-Core Processor gcc(Gentoo: 4.3.2-r3)
KDE: 3.5.10 Qt: 3.3.8b
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: What happened to boot.msg?
2009-10-23 14:18 [gentoo-user] What happened to boot.msg? Peter Ruskin
@ 2009-10-23 15:11 ` walt
2009-10-23 18:00 ` Peter Ruskin
0 siblings, 1 reply; 8+ messages in thread
From: walt @ 2009-10-23 15:11 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
2009-10-23 15:11 ` [gentoo-user] " walt
@ 2009-10-23 18:00 ` Peter Ruskin
2009-10-23 18:09 ` Peter Ruskin
2009-10-23 19:00 ` William Hubbs
0 siblings, 2 replies; 8+ messages in thread
From: Peter Ruskin @ 2009-10-23 18:00 UTC (permalink / raw
To: gentoo-user
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.
--
Peter
========================================================================
Gentoo Linux: Portage 2.2_rc46 kernel-2.6.31-gentoo-r3
AMD Phenom(tm) 9950 Quad-Core Processor gcc(Gentoo: 4.3.2-r3)
KDE: 3.5.10 Qt: 3.3.8b
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
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
1 sibling, 1 reply; 8+ messages in thread
From: Peter Ruskin @ 2009-10-23 18:09 UTC (permalink / raw
To: gentoo-user
On Friday 23 October 2009 19:00:34 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.
Ahhh ... I found it. It's now stored in /var/log/rc.log.
--
Peter
========================================================================
Gentoo Linux: Portage 2.2_rc46 kernel-2.6.31-gentoo-r3
AMD Phenom(tm) 9950 Quad-Core Processor gcc(Gentoo: 4.3.2-r3)
KDE: 3.5.10 Qt: 3.3.8b
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
2009-10-23 18:09 ` Peter Ruskin
@ 2009-10-24 13:07 ` covici
0 siblings, 0 replies; 8+ messages in thread
From: covici @ 2009-10-24 13:07 UTC (permalink / raw
To: gentoo-user
Peter Ruskin <peter.ruskin@dsl.pipex.com> wrote:
> On Friday 23 October 2009 19:00:34 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.
>
> Ahhh ... I found it. It's now stored in /var/log/rc.log.
However, mine is an empty file even though I have rc_logger="yes"
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
2009-10-23 18:00 ` Peter Ruskin
2009-10-23 18:09 ` Peter Ruskin
@ 2009-10-23 19:00 ` William Hubbs
2009-10-23 19:06 ` Peter Ruskin
2009-10-24 13:15 ` covici
1 sibling, 2 replies; 8+ messages in thread
From: William Hubbs @ 2009-10-23 19:00 UTC (permalink / raw
To: gentoo-user
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
2009-10-23 19:00 ` William Hubbs
@ 2009-10-23 19:06 ` Peter Ruskin
2009-10-24 13:15 ` covici
1 sibling, 0 replies; 8+ messages in thread
From: Peter Ruskin @ 2009-10-23 19:06 UTC (permalink / raw
To: gentoo-user
On Friday 23 October 2009 20:00:33 William Hubbs wrote:
> > 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.
Thanks - RC_LOGGER was already at yes, so I've uninstalled
app-admin/showconsole
--
Peter
========================================================================
Gentoo Linux: Portage 2.2_rc46 kernel-2.6.31-gentoo-r3
AMD Phenom(tm) 9950 Quad-Core Processor gcc(Gentoo: 4.3.2-r3)
KDE: 3.5.10 Qt: 3.3.8b
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: What happened to boot.msg?
2009-10-23 19:00 ` William Hubbs
2009-10-23 19:06 ` Peter Ruskin
@ 2009-10-24 13:15 ` covici
1 sibling, 0 replies; 8+ messages in thread
From: covici @ 2009-10-24 13:15 UTC (permalink / raw
To: gentoo-user
William Hubbs <williamh@gentoo.org> wrote:
> 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.
I discovered that the reason its blank is there is something rotating
the file, even though I don't have it in logrotate.conf or logrotate.d
-- very strange.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2009-10-24 13:16 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2009-10-23 19:06 ` Peter Ruskin
2009-10-24 13:15 ` covici
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox