This one time, at band camp, Marco d'Itri said: > On Feb 10, Sven Luther <[EMAIL PROTECTED]> wrote: > > > We need something which upgrades seamlessly, and the above solution is not > > acceptable for the etch release, as has been said already in the past. > This would be nice, but so far nobody has been able to design anything > better, myself included.
[...] > > Is it not possible to have a newer udev which is not removing the older > > udev, > > so you have both installed, and the older udev will work with older kernels > > and the newer udev will work with newer kernels ? > I do not believe that this would be possible, at least for the general > case, because the version of udev in stable is almost a different > program with different interfaces with other system components. In this case, does itmake any sense to treat the two versions of udev similarly to how we treat library transitions? I.e., rename the new udev to udev-$min-kernel-ver or something? (the name is ugly, but you get the idea). The upgrade path won't be perfect, but it will have the benefit of leaving the user with their current kernel + current udev at the end, at which point they will need to install the newer udev and newer kernel and reboot. Just a thought, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
