I have a multikernel-system, which uses a Vanilla-kernel at the moment. IMO YOU should only do a kernel-update, when a SuSE-kernel is running. Al
Urgh, I'm running SuSE 8.1 on a "root-server" at an ISP where also a vanilla kernel runs. If the "new" automatic update from YOU will kick this kernel I (and many others like me) may run in trouble, because all needed features are linked staticly in this kernel... :-/ The ethernet-driver is also static. So I don't know what will happen, if YOU replaces it with the module-oriented SuSE-Kernel. ...yes I know: just don't select the kernel-packet, but I bet many people just use the automatic mode... On Donnerstag, 19. Juni 2003 14:19, Al Bogner wrote:
I have a multikernel-system, which uses a Vanilla-kernel at the moment. IMO YOU should only do a kernel-update, when a SuSE-kernel is running.
-- Eat, sleep and go running, David Huecking. Encrypted eMail welcome! GnuPG/ PGP-Key: 0x57809216. Fingerprint: 3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216
On Thursday 19 June 2003 15:04, David Huecking wrote:
...yes I know: just don't select the kernel-packet, but I bet many people just use the automatic mode...
I hope SuSE will correct this ASAP. Also with a manual update you could forget to deactivate it. Maybe you don't forget it with the 1st update, but with th n-th update you will, for sure. Al
On Thu, Jun 19, 2003 at 03:04:38PM +0200, David Huecking wrote:
Urgh, I'm running SuSE 8.1 on a "root-server" at an ISP where also a vanilla kernel runs. If the "new" automatic update from YOU will kick this kernel I (and many others like me) may run in trouble, because all needed features are linked staticly in this kernel... :-/ The ethernet-driver is also static. So I don't know what will happen, if YOU replaces it with the module-oriented SuSE-Kernel. ...yes I know: just don't select the kernel-packet, but I bet many people just use the automatic mode...
If you use an individual kernel, you should better install it under a different name. If you did so, an upgrade cannot hurt you. This problem is not kernel-specific. Everytime you replace any file from the installation with an individual one, your replacement will be killed by an update. This is one reason, you should use /usr/local for applications you built on your own, and for the same reason you should use a different name for a kernel you built on your own. Robert -- Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
On Thursday 19 June 2003 22:53, Robert Schiele wrote:
If you use an individual kernel, you should better install it under a different name. If you did so, an upgrade cannot hurt you.
Nevertheless YOU suggests an update, which doesn't make sense IMO. The name of my kernel is vmlinuz-2.4.21-rc7-grsec, but the original vmlinuz is also in /boot. Shouldn't it be easy to check the kernel version as a basis for the update? Al
On Thursday 19 June 2003 23:58, Al Bogner wrote:
Nevertheless YOU suggests an update, which doesn't make sense IMO. The name of my kernel is vmlinuz-2.4.21-rc7-grsec, but the original vmlinuz is also in /boot.
Shouldn't it be easy to check the kernel version as a basis for the update?
YOU does check the kernel version, but not in the way you expect it to. It does check in the RPM database what version is installed and based on that decides whether an update is needed. If you didn't create a RPM package and installed that, according to the RPM database you still have the old version and an update should be performed. As long as you build RPM packages for any updates you want to perform, you can even install them via YaST and YOU will have no problem handling those. If you don't want to do that, you should refrain from using YOU and YaST as well. Best regards, Arjen -- 51 N 25' 05.1" - 05 E 29' 14.1" Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
On Fre, 20 Jun 2003, Arjen de Korte wrote:
As long as you build RPM packages for any updates you want to perform, you can even install them via YaST and YOU will have no problem handling those. If you don't want to do that, you should refrain from using YOU and YaST as well.
I disagree. SuSE has support for /boot/vmlinuz and /boot/vmlinuz.shipped. The YOU update should only update /boot/vmlinuz.shipped if /boot/vmlinuz is modified. -- Dirk
On 06/20/2003 06:37 AM, Dirk Mueller wrote:
I disagree. SuSE has support for /boot/vmlinuz and /boot/vmlinuz.shipped. The YOU update should only update /boot/vmlinuz.shipped if /boot/vmlinuz is modified.
But vmlinuz.shipped uses modules from the SAME kernel, so if that kernel is changed/ replaced, BOTH have to be updated, or failsafe boot will no longer work. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
As long as you build RPM packages for any updates you want to perform, you can even install them via YaST and YOU will have no problem handling those. If you don't want to do that, you should refrain from using YOU and YaST as well.
I disagree. SuSE has support for /boot/vmlinuz and /boot/vmlinuz.shipped. The YOU update should only update /boot/vmlinuz.shipped if /boot/vmlinuz is modified.
I disagree. If you have modified your (installed) kernel _package_, you can't complain that YOU overwrites it. If you are using a vanilla kernel, then deinstall the SuSE rpm kernel package: rpm -e `rpm -qf /boot/vmlinuz` ...and you're safe. I'm afraid that there is no other way to fix this. Roman.
* Arjen de Korte wrote on Fri, Jun 20, 2003 at 00:09 +0200:
On Thursday 19 June 2003 23:58, Al Bogner wrote:
Shouldn't it be easy to check the kernel version as a basis for the update?
YOU does check the kernel version, but not in the way you expect it to. It does check in the RPM database what version is installed and based on that decides whether an update is needed. If you didn't create a RPM package and installed that, according to the RPM database you still have the old version and an update should be performed.
Yeah, in a RPM system a clean update is by RPM. If you don't use kernel RPMs you can use some "ginstall" dummy-RPMs.
As long as you build RPM packages for any updates you want to perform, you can even install them via YaST and YOU will have no problem handling those. If you don't want to do that, you should refrain from using YOU and YaST as well.
Isn't it sufficient to have a kernel-version-whateverid in /boot or such? the kernel itself will not be overwritten (otherwise you made it to provoke also a name clash by using SuSE-Names like vmlinuz, well, but this is a bug easy to solve :-) ). Is lilo.conf modified? I don't think so. So even if lilo is run, the "linux-bak" or whatever may boot a new kernel, but your default should still boot your kernel. So I don't see what SuSE could fix here. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
participants (8)
-
Al Bogner -
Arjen de Korte -
David Huecking -
Dirk Mueller -
Joe Morris (NTM) -
Robert Schiele -
Roman Drahtmueller -
Steffen Dettmer