-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2007-12-05 at 14:37 -0500, Richard Creighton wrote:
Shortly after rebooting, the updater said it had a security patch on the
new .13 kernel and (I know, I should know better than to trust anything
by now), it was small, a patch and I said, go ahead, it isn't installing
a new kernel, just requires a reboot to load it into memory after the
update.....Yeah, right!....
Patch or no patch, a kernel patch replaces the whole kernel, even if only
a small part of it actually changes.
It not only ate my GRUB configuration files
and replaced them, it also destroyed (by erasure) all of the other linux
kernels in /boot, their syms AND all of the modules AND sources in /lib
for those versions!!!!! Dammitalltohellanyway!!!!
All the kernels with different version numbers that the one it was
replacing? It should only replace the previous kernel, no more. If it
removes other kernels, open a bugzilla.
And, if you say you had compiled your own kernel, that one would not be
touched - provided you compiled it with a different name. Furthermore,
once you give the kernel a name (inside the make), the /lib/modules/ tree
receives also a different name, and that one is not replaced:
1505880 Nov 22 22:21 /boot/vmlinuz-2.6.22.12-0.1-cer <-- mine
1559220 Nov 12 04:13 /boot/vmlinuz-2.6.22.12-0.1-cer.old <-- mine, old
1593968 Nov 7 17:09 /boot/vmlinuz-2.6.22.12-0.1-default <-- theirs
Only "theirs" is replaced. Plus:
/lib/modules/2.6.22.12-0.1-cer/ <=== mine
/lib/modules/2.6.22.12-0.1-default/
/lib/modules/2.6.22.12-0.1-debug/
/lib/modules/2.6.22.12-0.1-xen/
/lib/modules/2.6.22.12-0.1-xenpae/
Those I have named your kernel, prior to compile, mind! are not replaced
by Yast. They don't belong to any rpm, thus they are not touched.
The sources, yes, that would be lost unless I copied them over. That is
known.
But yes, for something as important as a kernel, it should ask. But I
think you can go into YOU (never, ever, do an automatic update) and select
the previous kernel to be maintained - but... no, as it has the same rpm
name, the option is not given. You can't.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFHVwLvtTMYHG2NR9URAr6jAJ9hpzL0ZGxPsUSpk3AmoDCH/yYoMwCgkYG7
0K09hp35c8RTelJ/ErbTWk0=
=4Xya
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
