I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
thanks that worked.
On Thu, 2004-07-15 at 12:26 -0400, ne... wrote:
On Jul 15, 2004 at 11:17, Doug Maurer in a soothing rage wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Yes. Edit your grub.conf and change the default kernel.
N.Emile...
On Jul 15, 2004 at 11:17, Doug Maurer in a soothing rage wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Yes. Edit your grub.conf and change the default kernel.
N.Emile...
Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
I think that's a feature, not a bug! I use synaptic instead of up2date, on FC1, but it works the same way. (Or the kernel RPMs do it as a postinstall action -- DIIK) I always go for a couple of boots, selecting the new kernel manually, before I update the grub default to the new kernel. Cheers, Gordon Keehn
On Thu, 2004-07-15 at 10:17, Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Others told you to manually edit grub.conf.
If you use yum instead of up2date it will automatically make the new kernel the default.
Your choice of which you prefer.
On Thu, Jul 15, 2004 at 11:17:41AM -0400, Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
--
I would use yum to update. It does the right thing. You can configure up2date to use yum.
Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Though editing /etc/grub.conf with an editor and changing the default= line to match up to wherever your new kernel is located to would be the way to change it.
Also, if all goes well with the new kernel, uninstall the older kernel and see if the new kernel becomes default.
And my favorite way.
up2date system-config-boot
Then under the menu, choose system settings > bootloader (Enter password) and select the new kernel with the simple GUI interface.
Though this is a limited featured program, it is great for default settings and for adjusting the timeout, in a short amount of time and limited keystrokes.
Jim
On Thu, Jul 15, 2004 at 02:39:55PM -0500, Jeff Vian wrote:
On Thu, 2004-07-15 at 10:17, Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Others told you to manually edit grub.conf.
If you use yum instead of up2date it will automatically make the new kernel the default.
Your choice of which you prefer.
I got the same answer when I asked the same question about 2 weeks ago. But if yum does the right thing, and up2date did the right thing in FC1, might the up2date behaviour in FC2 qualify as a bug?
I think it is very confusing this way, and potentially dangerous; people may believe they are running the latest kernels when they are not.
David
On Fri, 2004-07-16 at 05:41, David Jansen wrote:
On Thu, Jul 15, 2004 at 02:39:55PM -0500, Jeff Vian wrote:
On Thu, 2004-07-15 at 10:17, Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Others told you to manually edit grub.conf.
If you use yum instead of up2date it will automatically make the new kernel the default.
Your choice of which you prefer.
I got the same answer when I asked the same question about 2 weeks ago. But if yum does the right thing, and up2date did the right thing in FC1, might the up2date behaviour in FC2 qualify as a bug?
I think it is very confusing this way, and potentially dangerous; people may believe they are running the latest kernels when they are not.
David
I agree it may be a bit disconcerting. Some people seem to prefer up2date and its behavior over that of yum. I personally see no problem with having both behaviors available because we don't all fit the same mold.
AFAICT, if people do not know which kernel they are booting they are either blind (cant see the menu when booting) or don't care (never look at the screen anyway). They also would have to NEVER run uname in order to remain ignorant of which kernel is in use.
In any case, ignoring the kernel in use is their choice and I hardly feel it is up to me to force one or the other behavior on the tools used.
YMMV
Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
I am running FC2 as well, and I noticed that up2date did not set the new kernel as default, but if you look in your gnome menu -> system settings -> bootloader, there is a GUI program that lets you select default kernel without editing any text.
On Fri, 2004-07-16 at 06:41, David Jansen wrote:
On Thu, Jul 15, 2004 at 02:39:55PM -0500, Jeff Vian wrote:
On Thu, 2004-07-15 at 10:17, Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
Others told you to manually edit grub.conf.
If you use yum instead of up2date it will automatically make the new kernel the default.
Your choice of which you prefer.
I got the same answer when I asked the same question about 2 weeks ago. But if yum does the right thing, and up2date did the right thing in FC1, might the up2date behaviour in FC2 qualify as a bug?
I think it is very confusing this way, and potentially dangerous; people may believe they are running the latest kernels when they are not.
David
I am not in a position to test this fully....
On my RHEL 3 ES system, my manual running of up2date is definitely updating the grub.conf to make the new kernel the default one.
So why then is Fedora Core's up2date not.....
I did have access to the /etc/sysconfig/rhn/up2date files on both systems and am noticing an extra line in the one on the RHEL 3 system. It is: noBootLoader=0
Unfortunately I cannot test to see if the addition of this one line might adjust FC2 to (let me say this delicately) "properly update" the default= line in grub.conf to point to the new kernel.
Anyone have an idea?
--Rob
On Fri, 2004-07-16 at 09:38, Andrew Konosky wrote:
Doug Maurer wrote:
I've noticed since FC2 and now fc3 test1, that when I run up2date and it has a new kernel that after rebooting the machine it still defaults to the original installed kernel. Its doing it on two machines I have FC2 and FC3test1 on. Anyone else experience this, know of a fix?
I am running FC2 as well, and I noticed that up2date did not set the new kernel as default, but if you look in your gnome menu -> system settings -> bootloader, there is a GUI program that lets you select default kernel without editing any text.
"YOU" are not editing the text. The app is doing it for you. Same net effect.
-
akonstam＠trinity.edu -
Andrew Konosky -
David Jansen -
Doug Maurer -
Gordon Keehn -
Jeff Vian -
Jim Cornette -
ne... -
Robert Locke