public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Marineau <mike@marineau.org>
Cc: Alan Stern <stern@rowland.harvard.edu>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_UEVENT_HELPER default
Date: Tue, 24 Jun 2014 14:33:10 -0400	[thread overview]
Message-ID: <20140624183310.GA4955@kroah.com> (raw)
In-Reply-To: <CAHW-aUfJedVUkYxxD-GSNaQg+FvXDXGW9Q9HaTknBeGZMF9REA@mail.gmail.com>

On Tue, Jun 24, 2014 at 11:30:05AM -0700, Michael Marineau wrote:
> On Jun 24, 2014 11:23 AM, "Alan Stern" <stern@rowland.harvard.edu> wrote:
> >
> > Michael and Greg:
> >
> > The help text for CONFIG_UEVENT_HELPER says (among other things):
> >
> >           This should not be used today, because usual systems create
> >           many events at bootup or device discovery in a very short time
> >           frame.
> >
> > If it shouldn't be used, why does it default to 'y'?
> >
> > Alan Stern
> >
> 
> To introduce the option but not change the default behavior. (yet?) I don't
> really have an opinion one way or the other, I just defaulted to being
> conservative.

Yes, being conservative is good as turning this off with older systems
(like the pathological Fedora 3 system that some kernel developers still
use for testing), would result in a non-booting box.  So if you know
that your system is "new enough", it's safe to turn off, but if you have
a doubt, leave it on to be safe.

thanks,

greg k-h

  parent reply	other threads:[~2014-06-24 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:23 CONFIG_UEVENT_HELPER default Alan Stern
     [not found] ` <CAHW-aUfJedVUkYxxD-GSNaQg+FvXDXGW9Q9HaTknBeGZMF9REA@mail.gmail.com>
2014-06-24 18:33   ` Greg KH [this message]
2014-06-24 19:55     ` Andy Lutomirski
2014-06-24 22:35       ` Ken Moffat
2014-07-03 21:24         ` Ken Moffat

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=20140624183310.GA4955@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@marineau.org \
    --cc=stern@rowland.harvard.edu \
    /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