From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udevd boot messages
Date: Thu, 24 May 2012 05:45:18 -0400 [thread overview]
Message-ID: <4FBE032E.1070501@libertytrek.org> (raw)
In-Reply-To: <4FBD5C8F.5040705@gentoo.org>
On 2012-05-23 5:54 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 05/23/2012 10:47 PM, Alan McKinnon wrote:
>> Tanstaafl wants to know if a reboot*will* be required*before* he does
>> the update. What you are describing tells him that after the update
>> completes when it is already too late.
>>
>> I face the same issue at work. We have a change policy requiring 14
>> days advance notice of any change affecting service. If I do a routine
>> world update then have to log an emergency change for an unexpected
>> reboot, the change manager will have my nuts for breakfast.
>>
>> If it happens more than once, I'd be having a really unusual
>> conversation with the CTO which probably ends with him standing behind
>> me watching while I migrate every single box that isn't RHEL6 (all 200
>> of them) over to RHEL6 where I*do* have exact knowledge in advance of
>> the impact of a change.
> Did either of you ever open a bug about this or even discuss it in the
> gentoo-dev mailing list? What you say sounds like a valid concern to me
> but unless you express your needs to maintainers, nothing is ever going
> to happen. However, in this particular case, yes a news item would be
> the ideal solution.
I didn't discuss it on the dev list (I'm not a dev), but I did ask a
question about this, but it was more general in nature (how to get
ewarn/einfo during --pretend):
http://forums.gentoo.org/viewtopic.php?p=5930125#5930125
As a result of that thread, I then opened this bug which was
subsequently closed:
https://bugs.gentoo.org/show_bug.cgi?id=281248
next prev parent reply other threads:[~2012-05-24 9:47 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 [this message]
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=4FBE032E.1070501@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