Re: [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late)

[Rich Freeman <rich0@gentoo.org>]

On Fri, Jan 25, 2013 at 4:19 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Wed, Jan 23, 2013 at 2:14 PM, Samuli Suominen <ssuominen@gentoo.org> wrote:
>> please review this news item, seems we need one after all
>
> Here's a crazy idea: can we patch our kernel to let "make oldconfig"
> default CONFIG_DEVTMPFS to true? Or better yet, request that this is
> changed upstream?

I could see making that the default if there is no .config file
present and a new one is being created, and perhaps upstream would
support that since udev is popular.  However, make oldconfig is
usually used when you have a .config file and you just want to update
it.  In that case I don't think we should be changing settings - what
if a user doesn't want this set?  They'd have to remember to manually
unset it every single time they compile a new kernel, as we'd be
"helpfully" changing it back.

Not everybody uses udev.

Somebody already brought this up, but the main thing users need is
notice for changes like this, and warnings.  By all means mention in
the warnings that their systems will be unbootable.  And by all means
let's cut down on spurious elog traffic otherwise.

Oh, here's another thought - when elog traffic gets sent out as email
can the subject line be changed based on the most serious message in
the log?  That is, can a log-only email be distinguished from one that
has a warning in it?

Rich