From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Wed, 22 Oct 2008 17:02:25 +0000 Subject: Re: Report: Threaded udevd Message-Id: <20081022170225.GA23609@bongo.bofh.it> MIME-Version: 1 Content-Type: multipart/mixed; boundary="5mCyUwZo2JvN/JJP" List-Id: References: <48FF3458.6030909@tuffmail.co.uk> In-Reply-To: <48FF3458.6030909@tuffmail.co.uk> To: linux-hotplug@vger.kernel.org --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Oct 22, Greg KH wrote: > > > I see no problem with depending on the very latest kernels; using a > > > latest udev version goes hand-in-hand with using a latest kernel. > > I do, since this tends to badly mess upgrades... > How? Can't you just specify a minimum kernel version in your packaging > system for the latest version of udev? That's what we do for other > distros... The problem is handling upgrades between two different major revisions of a distribution. e.g. Debian 3.1 shipped udev 56 and kernel 2.6.8, while Debian 4.0 shipped udev 105 and kernel 2.6.18. udev 105 did not work with kernel 2.6.18 and udev 56 did not work with kernel 2.6.8, so the udev installation script had to jump hoops to not start the new udev, make sure that a suitable updated kernel was installed at the same time and recommend the administrator to reboot ASAP. And if for some reason the new kernel does not work, the user will be left with a mostly broken (no working udev) system. This is why I would really really like to see kernel 2.6.26 supported by udev for the next few years. --=20 ciao, Marco --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkj/XKEACgkQFGfw2OHuP7ENnACfVdDPRp+lqnEjfeZn4NJVkBr2 1YEAnjDcj/PeQfCc7lKHfymt6QZPVrnN =T9V+ -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP--