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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 25 Oct 2009 19:30:35 +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?

Martin Steigerwald wrote:
> Would that qualify as a reason to put it there and have make-kpkg / make
> deb / make rpm spit out a udev package as well?

How would that help?

It will result in udev more frequently being incompatible with user space. 
It also will increase the chance of failure if you switch between older 
and newer kernel versions.

IMO udev should primarily ensure compatibility with user space. The kernel 
should provide sufficient backwards compatibility to support older udev 
versions.

Sure, there will be cut-off points (one of which you seem to have hit 
here), but in general it's a lot easier to ensure a kernel is compatible 
with your current version of udev than ensuring random upstream versions 
of udev are compatible with your userland (especially if you're running 
the stable version of a distro).

Just my take on this issue.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ