public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] See bootup/poweroff screen?
Date: Thu, 5 Mar 2015 10:00:07 +0000	[thread overview]
Message-ID: <20150305100007.0ff79dd6@digimed.co.uk> (raw)
In-Reply-To: <54F81F07.1030704@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

On Thu, 05 Mar 2015 03:16:55 -0600, Dale wrote:

> > Of course it wasn't. Warnings about /var not being writeable are not
> > going to be written to /var.

> Yea, it won't catch everything.  This is sort of designed for that point
> where one log stops and the other hasn't started yet.  This is usually
> where dmesg stops and syslog and friends hasn't yet started.  Of course,
> if /var isn't mounted, well, it has no where to go.
> 
> Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
> it supposed to store it in memory until /var is mounted and then dump
> it?

The combination of dracut and systemd means it all goes in the journal.
The journal is kept in memory and then flushed to disk later in the boot
process.

journalctl is rather neat, being able to search both dmesg and system
logs in one go, and apply various search criteria, is far more flexible
than the alternatives.


-- 
Neil Bothwick

WWW: World Wide Wait

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-03-05 10:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  2:58 [gentoo-user] See bootup/poweroff screen? German
2015-03-05  4:44 ` Adam Carter
2015-03-05  6:17 ` Dale
2015-03-05  8:08   ` German
2015-03-05  8:25     ` Neil Bothwick
2015-03-05  9:16       ` Dale
2015-03-05 10:00         ` Neil Bothwick [this message]
2015-03-05 12:01         ` covici
2015-03-05 13:19           ` Dale
2015-03-05 14:38             ` Rich Freeman
2015-03-05 17:08               ` Neil Bothwick
2015-03-05 17:13                 ` Rich Freeman
2015-03-06  1:13         ` Fernando Rodriguez

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=20150305100007.0ff79dd6@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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