Advertisement
Interested in hardware, diags, validation, Linux, C, ARM, Microcode and low level programming and blazing networks?
| |||||||||||||
|
| |||||||||||||
Networking change causes distribution headachesNetworking change causes distribution headachesPosted Oct 29, 2008 5:27 UTC (Wed) by ncm (subscriber, #165)In reply to: Networking change causes distribution headaches by jordip Parent article: Networking change causes distribution headaches
How will the procps workaround ever be removed, once a fixed kernel is installed? I.e., how does procps know what kernels might be on the system, and need it? Is the workaround a script that will test the running kernel's version, and operate only for known-broken kernels?
(Log in to post comments)
Networking change causes distribution headaches Posted Oct 29, 2008 8:24 UTC (Wed) by rvfh (subscriber, #31018) [Link]
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]
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 (✭ supporter ✭, #5246) [Link]
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 (✭ supporter ✭, #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.
Networking change causes distribution headaches Posted Oct 29, 2008 12:40 UTC (Wed) by nix (subscriber, #2304) [Link]
The workaround is a one-line sysctl.conf addition.
Networking change causes distribution headaches Posted Oct 29, 2008 18:42 UTC (Wed) by ncm (subscriber, #165) [Link]
So it appears there's no clean way to phase out the workaround.
|
|
||||||||||||