From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udevd boot messages
Date: Wed, 23 May 2012 13:18:33 -0400 [thread overview]
Message-ID: <4FBD1BE9.9050703@libertytrek.org> (raw)
In-Reply-To: <20120523184907.01cb6c5a@weird.wonkology.org>
On 2012-05-23 12:49 PM, Alex Schuster <wonko@wonkology.org> wrote:
> Tanstaafl writes:
>
>> *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>
>
> Indeed! I think eselect news read should show this, at least.
That would work for me... anytime I saw an update for system critical
stuff (like baselayout or udev or openrc) I'd be sure to check things...
As it stands, I'm now very glad for my self imposed policy of waiting a
few days for critical things like this...
next prev parent reply other threads:[~2012-05-23 17:20 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 [this message]
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
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=4FBD1BE9.9050703@libertytrek.org \
--to=tanstaafl@libertytrek.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