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] Re: Udev-197 :  4  show-stoppers
Date: Wed, 23 Jan 2013 09:05:05 +0000	[thread overview]
Message-ID: <20130123090505.6bae09af@digimed.co.uk> (raw)
In-Reply-To: <50FF9F5F.90204@hanft.de>

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

On Wed, 23 Jan 2013 09:29:19 +0100, Matthias Hanft wrote:

> > This got me too.  Now there's a discussion in -dev about making config
> > warnings fatal.  
> 
> Good idea, but as I updated udev yesterday on one of my Gentoo systems,
> in the usual after-update messages there was a line in red, telling me
> "You don't have CONFIG_DEVTMPFS enabled. udev will not start." So it's
> not really a surprise, is it? Hence, I built a new kernel *before*
> rebooting :-)

That's fine if you see the message, which you should, and the system
does not suffer an unplanned reboot, which it shouldn't. But leaving a
system in a state that won't reboot following a crash or power failure is
not particularly clever, making the warnings fatal sounds a safe default
to me. As this is Gentoo there will always be a way to turn the airbags
off and even disable the brakes :)


-- 
Neil Bothwick

Some cause happiness wherever they go. Others whenever they go.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-01-23  9:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20  8:51 [gentoo-user] Udev-197 : 4 show-stoppers Philip Webb
2013-01-20  9:12 ` Canek Peláez Valdés
2013-01-20  9:52   ` Neil Bothwick
2013-01-20 10:11     ` Canek Peláez Valdés
2013-01-21  9:18       ` Neil Bothwick
2013-01-20  9:29 ` victor romanchuk
2013-01-20 23:44   ` [gentoo-user] " walt
2013-01-21  0:17     ` Dale
2013-01-21  0:56       ` Bruce Hill
2013-01-21  3:28         ` Dale
2013-01-21  9:33         ` Neil Bothwick
2013-01-21  5:47       ` Walter Dnes
2013-01-21  9:57       ` Alan McKinnon
2013-01-21 19:36         ` Dale
2013-01-22  0:38           ` Alan McKinnon
2013-01-22  4:06           ` Walter Dnes
2013-01-22  6:02             ` Pandu Poluan
2013-01-22  6:03             ` Dale
2013-01-21  7:46   ` [gentoo-user] Udev-197 show-stoppers : SOLVED Philip Webb
2013-01-20 16:57 ` [gentoo-user] Udev-197 : 4 show-stoppers Peter Humphrey
2013-01-23  2:41   ` [gentoo-user] " »Q«
2013-01-23  8:29     ` Matthias Hanft
2013-01-23  9:05       ` Neil Bothwick [this message]
2013-01-23 11:10     ` Thanasis
2013-01-23 11:18       ` Thanasis
2013-01-23 15:45       ` Alan McKinnon
2013-01-23 20:10         ` »Q«
2013-01-24  2:20           ` Peter Humphrey
2013-01-24  7:40           ` Alan McKinnon
     [not found] <ktYUV-5CD-1@gated-at.bofh.it>
     [not found] ` <ku6ps-6zt-3@gated-at.bofh.it>
     [not found]   ` <kuYzw-7xl-11@gated-at.bofh.it>
     [not found]     ` <kv3Sy-5SS-11@gated-at.bofh.it>
     [not found]       ` <kv4vh-6Je-25@gated-at.bofh.it>
2013-01-23 11:06         ` Gregory Shearman
2013-01-23 22:19           ` Neil Bothwick
2013-01-24  1:41           ` Peter Humphrey
2013-01-25  6:51           ` Daniel Wagener

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=20130123090505.6bae09af@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