From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udevd boot messages
Date: Thu, 24 May 2012 07:55:13 +0700 [thread overview]
Message-ID: <CAA2qdGWxM1Qc_Zdhgq2uhY6GDHXW4TC0UeCfMZX=f0we==hWHQ@mail.gmail.com> (raw)
In-Reply-To: <20120524001132.323a8581@khamul.example.com>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
On May 24, 2012 5:19 AM, "Alan McKinnon" <alan.mckinnon@gmail.com> wrote:
>
> On Wed, 23 May 2012 22:54:23 +0100
> Markos Chandras <hwoarang@gentoo.org> wrote:
>
[znip]
> > 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 haven't opened a bug myself, mostly because I've never been bitten
> by this. My Gentoo servers run stable so I've always known from this
> list and other places when something requiring a reboot is coming down
> the line.
>
+1
I love this list :-)
In my previous place, I have one 'experimental' server which gets updated
before all others. It's the 'designated fall guy'.
Which reminds me of Project Management 101: What's the first thing you must
do before embarking on a project? Answer: Designate a fall guy and prepare
implicating evidences. ;-)
> I agree, a news item is the perfect solution. Having portage do it will
> be highly cumbersome, it will require some kind of new magic flag in
> ebuilds that portage must parse. All that work for something that
> doesn't happen often? Nah, it'll never fly.
>
Also a heartfelt +1 for this.
That said, I'm going to repost this 'news' to the Gentoo-server list,
unless someone beats me to it.
Rgds,
[-- Attachment #2: Type: text/html, Size: 1853 bytes --]
next prev parent reply other threads:[~2012-05-24 0:57 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 [this message]
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='CAA2qdGWxM1Qc_Zdhgq2uhY6GDHXW4TC0UeCfMZX=f0we==hWHQ@mail.gmail.com' \
--to=pandu@poluan.info \
--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