-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15 Aug 2002, Adam Williamson wrote:
> Something interesting just came up in the IRC channel. I noticed that > kernel packages are currently named as follows: > > kernel-W.X.Y.Zmdk > > (e.g. kernel-2.4.19.3mdk) > > but kernel-source packages are named: > > kernel-source-W.X.Y-Zmdk > > (e.g. kernel-source-2.4.19-3mdk) > > the practical upshot of this is that when you do urpmi --auto-select > after a new kernel release, kernel-source will be automatically updated > to the new kernel version, but your kernel itself won't be. You have to > urpmi the new kernel manually. > > Surely this is bad? It leaves you with a source tree and an actual > kernel which don't match, which could mess some things up (the nvidia > drivers spring to mind as an example.) Is there a reason for this? > I'm not certain this is such a bad thing, when installing another source version, the sources go in the /usr/src/linux-x.y.zz directory, and a simlink to the current kernel version is created into /usr/src/linux. Similar situation with the vmlinuz, intird, etc when installing a new kernel (plus it gets added to the lilo config -- gotta remember to run lilo after each -- otherwise bombs on my install of 8.2) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1cjTUACgkQUMkt1ZRwL1PSmQCgnsyEkV9OYXofKSXi4uckqt30 rVcAoK/UXm6OAT5iw278/1qP4jGpXCy1 =545e -----END PGP SIGNATURE-----
