Networking change causes distribution headaches

Posted Oct 29, 2008 8:24 UTC (Wed) by rvfh (guest, #31018)
In reply to: Networking change causes distribution headaches by ncm
Parent article: Networking change causes distribution headaches

The procps package with the fix will depend on a kernel with version greater or equal to the fixed one. Simple.

Networking change causes distribution headaches

Posted Oct 29, 2008 11:25 UTC (Wed) by mjg59 (subscriber, #23239) [Link] (2 responses)

It can't do that, since users may be using unpackaged kernels. Also, the Ubuntu kernel packaging system results in a different package name per version (it's the only way to handle parallel installation on Debian-style systems) so you can only depend on a single specific kernel version.

Networking change causes distribution headaches

Posted Oct 29, 2008 16:30 UTC (Wed) by jzbiciak (guest, #5246) [Link] (1 responses)

If only there were a filesystem that allowed the kernel to export information to user space, such as what kernel version was currently running... ;-)

Seriously, why can't procps look at /proc/version and presume that 2.6.27 is broken, but any other version (including 2.6.27.1). As long as it's looking very specifically for the broken version's version string there, it should work ok.

Sure, if someone installs a broken kernel with a different string, then the workaround won't kick in, but I don't really see a problem with that. If you're installing your own kernel rather than sticking to vendor kernels, then you're signing up to own a bit more of the problem yourself, don't ya think?

Networking change causes distribution headaches

Posted Oct 29, 2008 18:21 UTC (Wed) by jzbiciak (guest, #5246) [Link]

Seriously, why can't procps look at /proc/version and presume that 2.6.27 is broken, but not any other version (including 2.6.27.1)

oops. :-) Fixed that.