> When detecting a 2.4 kernel is > running, udev instaklls itself, but in disabled form. When detecting the sarge > 2.6.8 kernel, udev refuses to install, and if you already had part of gnome > upgraded, you are left with a mess.
Why all this fuss about using debconf? Can't it just treat 2.6.8 the same as 2.4? I.e., when detecting linux 2.6.8 is running, udev installs itself, but in disabled form. Also note that if the debconf question defaults to "no", you're gratuitously breaking install path for users whose debconf priority is too high. -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
