From: Frans Pop <elendil@planet.nl>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev in kernel source?
Date: Sun, 25 Oct 2009 20:33:40 +0100 [thread overview]
Message-ID: <200910252033.41218.elendil@planet.nl> (raw)
In-Reply-To: <200910252004.21546.Martin@lichtvoll.de>
(For the kernel mailing lists it is customary to reply-to-all. Due to the
very high volume on linux-kernel it's otherwise easy to miss replies.)
Martin Steigerwald wrote:
> And there is another issue: AFAIK distributors handle at least parts of
> the udev configuration including rules.
Exactly. Those "plug-in" rules installed by other packages can quite easily
conflict or overlap with a new version of udev.
For an example of how a udev update can break other programs, see
http://bugs.debian.org/545801.
> Maybe its more about the discoverability of such issue: I don't look into
> the boot log / syslog every day. ;)
Give logcheck a try. I run it on most of my systems, including my laptop.
> Hopefully upward incompatible changes in SysFS could be avoided in the
> future.
I wouldn't want to bet on that ;-)
Cheers,
FJP
next prev parent reply other threads:[~2009-10-25 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 17:33 Martin Steigerwald
2009-10-25 18:30 ` Frans Pop
2009-10-25 19:04 ` Martin Steigerwald
2009-10-25 19:33 ` Frans Pop [this message]
2009-10-25 22:37 ` Ben Nizette
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=200910252033.41218.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=Martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome