[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 17:12 --- This is still valid. Every upgrade that I have performed does not change the linux menu entry but adds the latest kernel as an entry but does NOT set that new entry as default. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 17:32 --- Are you sure of this? I don't know if it applies to upgrade, but this is what happens in Cooker when the kernel changes: the new kernel package installs itself as /boot/vmlinuz-version. It also creates a symlink to itself as /boot/vmlinuz, removing the previous /boot/vmlinuz symlink which was to the previous installed version. The corresponding thing happens for /boot/initrd-version and /usr/src/linux-version: they create symlinks to /boot/initrd and /usr/src/linux . Thus the top entry in lilo.conf doesn't ever need to change, because it simply points at the symlinks, which are updated by the kernel .RPM. The link added at the bottom of lilo.conf points not to the symlinks but to the actual files, so that when you do multiple upgrades (as Cooker users do) all the kernels remain available from the boot menu (if you run Cooker for a while and don't prune lilo.conf yourself, you end up with a list of previous kernels as long as your arm at the bottom of lilo.conf). So the fact that the linux entry isn't changing doesn't mean that it's not referring to a new kernel. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 18:00 --- Do the generic entries for vmlinuz and initrd point to the new kernel? When I upgrade the kernel on my computer, the symlinks for vmlinuz, initrd.img and system.map are set as the defaults. When I upgrade, they are always pointed to the new kernel and an entry is made in lilo.conf for the old kernel. This way, I never have to change the default entry, it automatically points to the newer kernel. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 18:26 --- I can verify that this is the case. I will will install RC2 cds and then do a network upgrade and double check. This maybe a stupid bug on my part --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 19:06 --- Upgraded from RC2 to todays cooker and it worked as it should have... closing bug... --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
[Cooker] [Bug 1988] [Installation] Upgrade path did not upgrade kernel
http://qa.mandrakesoft.com/show_bug.cgi?id=1988 --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 01:01 --- When doing network upgrade, this is still an issue... --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Using the network.img, I downloaded the RC1 version of MDK and used the Upgrade path. This did not upgrade the kernel. However, there was a lilo entry for the new kernel, so I am using that and defaulting to that entry.
