From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Cc: Markos Chandras <hwoarang@gentoo.org>
Subject: Re: [gentoo-user] udevd boot messages
Date: Thu, 24 May 2012 05:35:26 -0400 [thread overview]
Message-ID: <4FBE00DE.3050306@libertytrek.org> (raw)
In-Reply-To: <4FBD55D1.9000508@gentoo.org>
On 2012-05-23 5:25 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 05/23/2012 05:24 PM, Tanstaafl wrote:
>> *Especially* for servers, there really, REALLY needs to be a way to see
>> this kind of warning BEFORE updating... ie, the warning should be
>> printed to the screen during an 'emerge -pvuDN world' or something, so I
>> know that a reboot will be required for this update.
>> </pet-peeve>
> This kind of messages are also printed at the end of -uDNav world so if
> you scroll your screen up you can see all the warning/log messages from
> every package that you have updated. Also, these kind of messages are
> logged in/var/log/portage/
Ummm... yes, I know that, I get my elogs via email...
You must have missed the words 'BEFORE updating' above... I put BEFORE
in caps, not sure what else I could have done to make it more plain... ;)
next prev parent reply other threads:[~2012-05-24 9:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 9:15 [gentoo-user] udevd boot messages Jacques Montier
2012-05-21 14:27 ` Michael Hampicke
2012-05-21 15:41 ` [solved] " Jacques Montier
2012-05-21 21:00 ` Markos Chandras
2012-05-23 16:24 ` Tanstaafl
2012-05-23 16:49 ` Alex Schuster
2012-05-23 17:18 ` Tanstaafl
2012-05-23 21:25 ` Markos Chandras
2012-05-23 21:47 ` Alan McKinnon
2012-05-23 21:54 ` Markos Chandras
2012-05-23 22:11 ` Alan McKinnon
2012-05-24 0:55 ` Pandu Poluan
2012-05-24 9:45 ` Tanstaafl
2012-05-24 9:35 ` Tanstaafl [this message]
2012-05-24 23:24 ` Michael Mol
2012-05-25 11:17 ` Tanstaafl
2012-05-25 20:13 ` pk
2012-05-25 23:52 ` Peter Humphrey
2012-05-26 8:36 ` pk
2012-05-26 9:34 ` Peter Humphrey
2012-05-26 9:37 ` Markos Chandras
2012-05-26 12:48 ` Peter Humphrey
2012-05-26 2:10 ` Michael Mol
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=4FBE00DE.3050306@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=hwoarang@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