From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Greg KH <greg@kroah.com>, Michael Marineau <mike@marineau.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org
Subject: Re: CONFIG_UEVENT_HELPER default
Date: Thu, 3 Jul 2014 22:24:11 +0100 [thread overview]
Message-ID: <20140703212411.GB23074@milliways> (raw)
In-Reply-To: <20140624223509.GA21551@milliways>
On Tue, Jun 24, 2014 at 11:35:09PM +0100, Ken Moffat wrote:
> On Tue, Jun 24, 2014 at 12:55:26PM -0700, Andy Lutomirski wrote:
> > On 06/24/2014 11:33 AM, Greg KH wrote:
> > > 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:
> > >>>
[ snipping most of this ]
> (i.) I got the option with 'make oldconfig' and, after reading the
> help, made a decision. But, in the absence of other problems, and
> if the help text is correct, it looks as if a kernel built after
> accepting the default 'Y' here with recent userspace might grind to
> a halt after "successfully" booting? That sounds slightly better
> than "fails to boot", but only slightly. Maybe the problem needs
> a lot of modules, or is it something like "it will hang for a minute,
> then boot" ?
>
> (ii.) I understand that people continue to use ancient userspace,
> and for that the 'Y' option is needed. Using ancient userspace is
> a worthwhile thing for _somebody_ to try. But where is the line
> between "you need to enable this" and "enabling this might be a
> really bad idea" ? Maybe a specific version of udev ?
>
Now that I have managed to boot -rc3, with the default 'Y' on a
recent system (linuxfromscratch from May), it appears to work fine.
So, the text implies that bad things might happen, but so far I have
not seen them. I'll stop caring.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
prev parent reply other threads:[~2014-07-03 21:24 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
2014-06-24 19:55 ` Andy Lutomirski
2014-06-24 22:35 ` Ken Moffat
2014-07-03 21:24 ` Ken Moffat [this message]
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=20140703212411.GB23074@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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