From: Robert Crawford <flacycads@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ...startup information on screen...
Date: Fri, 10 Feb 2006 04:32:01 -0500 [thread overview]
Message-ID: <200602100432.01351.flacycads@cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0602100904170.1697@jmaa.math.ist.utl.pt>
Same problem here- I've tried for a while to figure it out, with no luck. I'd
also like to not have it not overwritten with each boot, and appended
instead.
On Friday 10 February 2006 04:09, Jorge Almeida wrote:
> On Mon, 6 Feb 2006, Neil Bothwick wrote:
> > On Mon, 6 Feb 2006 14:39:38 +0100, Fredrik Lundgren wrote:
> >> Is the information that runs on the screen before and after X is
> >> started or closed saved in some place or can it be saved or retrieved
> >> somehow?
> >
> > The early part of the startup information is available from
> > dmesg. The next stage can be logged if you set RC_BOOTLOG
> > in /etc/conf.d/rc. see the comments in that file.
>
> I gave it a try, and it seems that not everything gets logged:
> $ cat /var/log/boot.msg
>
> * Activating (possible) swap ...
> [ ok ]
> * Checking root filesystem ...
> /home: clean, 48404/256512 files, 122807/512064 blocks
> [ ok ]
> * Remounting root filesystem read/write ...
> [ ok ]
> * Setting hostname to moria ...
> [ ok ]
> * Calculating module dependencies ...
> * System.map not found - unable to check symbols
> [ ok ]
> * Checking all filesystems ...
> /boot: clean, 45/8032 files, 9889/32098 blocks
> /1: clean, 237777/768544 files, 880666/1536215 blocks
> /dev/hda12: clean, 35/131616 files, 4220/263056 blocks
> /dev/hdb1: clean, 14439/3842720 files, 4020444/7679062 blocks
> /dev/hdb4: clean, 62419/4374528 files, 2600814/8747392 blocks
> /dev/hda13: clean, 66726/1284224 files, 802063/2568384 blocks
> /: clean, 4035/513024 files, 40118/1024143 blocks
> /dev/hda11: clean, 141207/780288 files, 1043596/1560305 blocks (check in
> 2 mounts) /dev/hda10: clean, 2559/788704 files, 971368/1574362 blocks
> [ ok ]
> * Mounting local filesystems ...
> [ ok ]
> * Mounting USB device filesystem (usbfs) ...
> [ ok ]
> * Activating (possibly) more swap ...
> [ ok ]
> * Setting system clock using the hardware clock [UTC] ...
> [ ok ]
> * Configuring kernel parameters ...
> [ ok ]
> * Updating environment ...
> [ ok ]
> * Cleaning /var/lock, /var/run ...
> [ ok ]
> * Cleaning /tmp directory ...
> [ ok ]
> * Coldplugging input devices ...
> [ ok ]
> * Coldplugging isapnp devices ...
> [ ok ]
> What about everything from "Coldplugging pnp devices ..." to the end
> (net, local, etc.) ?
> Is this normal?
> --
> Jorge Almeida
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-10 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 13:39 [gentoo-user] ...startup information on screen Fredrik Lundgren
2006-02-06 14:13 ` Neil Bothwick
2006-02-06 17:28 ` [gentoo-user] " Harry Putnam
2006-02-06 17:33 ` Harry Putnam
2006-02-06 20:34 ` Neil Bothwick
2006-02-06 21:13 ` Peter Ruskin
2006-02-10 9:09 ` [gentoo-user] " Jorge Almeida
2006-02-10 9:32 ` Robert Crawford [this message]
2006-02-10 10:46 ` Michael Kintzios
2006-02-10 17:04 ` Robert Crawford
2006-02-06 14:18 ` Michael Kintzios
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=200602100432.01351.flacycads@cox.net \
--to=flacycads@cox.net \
--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