linux-kernel - Re: udev in kernel source?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200910252033.41218.elendil@planet.nl>
Date:	Sun, 25 Oct 2009 20:33:40 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Martin Steigerwald <Martin@...htvoll.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: udev in kernel source?

(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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/