[Bug 620434] New: kernel parameters are not kept on kernel updates
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c0 Summary: kernel parameters are not kept on kernel updates Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: estellnb@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 It is a real annoyance that user defined kernel parameters which are ment to be kept permanently are lost on every kernel update. With os11.2 I had to patch the resume= parameter on every kernel update (because it was always lost) and often could not suspend to disk because I simply forgot about it seeking for the error in a totally different place and thus wasting lots of precious time. This time with os11.3 I have to set the nomodeset parameter, have remebered wrong about it (as modeset or modset=0) and thus another time wasted huge amounts of time. The bug does not seem to serious but it provides a true utterly annoying hazard. Please fix this before the release of os11.3! It should not be a great deal, at least to keep all parameters behind the final runlevel stating (5 or 3, usually). The parameters there can only having been entered by a user. Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Bootloader AssignedTo|kernel-maintainers@forge.pr |jsrain@novell.com |ovo.novell.com | QAContact|qa@suse.de |jsrain@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c1 Leonardo Chiquitto <lchiquitto@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |lchiquitto@novell.com InfoProvider| |estellnb@gmail.com --- Comment #1 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-08 13:17:10 UTC --- Elmar, how are you setting the custom boot parameters? Are you editing /boot/grub/menu.lst directly? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c2 --- Comment #2 from Elmar Stellnberger <estellnb@gmail.com> 2010-07-09 11:10:20 UTC --- Yes, I have set them directly. This is often the only way to do it. Just imagine that X does not start and that you can not use Yast to edit the boot loader. Besides this many people will prefer editing menu.lst directly because this is more simple and straight forward than clicking through a deeply branched GUI. In a minimal chroot environment to be booed by Xen (this is just another important use case) you will not install YaST either. Either way; please set up a method to detect changes to menu.lst!! If the data to generate menu.lst is stored somewhere in /etc/sysconfig this is for the better because then you can easily detect manual changes to menu.lst. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c3 Elmar Stellnberger <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|estellnb@gmail.com | --- Comment #3 from Elmar Stellnberger <estellnb@gmail.com> 2010-07-09 11:10:38 UTC --- . -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c4 Leonardo Chiquitto <lchiquitto@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |estellnb@gmail.com --- Comment #4 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-09 11:28:18 UTC --- Elmar, please check /etc/sysconfig/bootloader. You can add the custom parameters to $DEFAULT_APPEND and/or $XEN_KERNEL_APPEND. This file is always used when generating /boot/grub/menu.lst, so the parameters will be kept even when you update or install a new kernel. Please confirm if this resolves the problem for you. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c5 Elmar Stellnberger <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|estellnb@gmail.com | --- Comment #5 from Elmar Stellnberger <estellnb@gmail.com> 2010-07-10 09:40:06 UTC --- No, it was not added to $DEFAULT_APPEND. Now it is. I assume that it will work now (I will inform you for the case it really should not). Nonetheless please add something like # # *** do not edit this file *** # ... bootloader configuration ... has to be done in /etc/sysconfig/bootloader # I believe it has to be as clear as this. 99% will overlook the hidden comment about /etc/sysconfig/bootloader otherwise. (There are always tons of useless comments in config file instead of having a good man page about them so usually no one pays attention to comments as long as they are not marked as important in some way. You may also make the file read only if you believe that to be useful.) .- An annoyance for users new to Suse! Please resolve this - and be it just by an adequately visible comment. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c6 --- Comment #6 from Elmar Stellnberger <estellnb@gmail.com> 2010-07-10 09:40:21 UTC --- No, it was not added to $DEFAULT_APPEND. Now it is. I assume that it will work now (I will inform you for the case it really should not). Nonetheless please add something like # # *** do not edit this file *** # ... bootloader configuration ... has to be done in /etc/sysconfig/bootloader # I believe it has to be as clear as this. 99% will overlook the hidden comment about /etc/sysconfig/bootloader otherwise. (There are always tons of useless comments in config file instead of having a good man page about them so usually no one pays attention to comments as long as they are not marked as important in some way. You may also make the file read only if you believe that to be useful.) .- An annoyance for users new to Suse! Please resolve this - and be it just by an adequately visible comment. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |jreidinger@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c7 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #7 from Josef Reidinger <jreidinger@novell.com> 2010-07-12 10:07:02 UTC --- Hi, I already add to 11.3 information to header. It now adds to the top of menu.lst this line: # Modified by YaST2. Last modification on Po lis 23 08:22:13 CET 2009 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader so I think it is already solved for 11.3. If you find such comment inadequate then please reopen this bug with proposal of better message. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c8 Robin Knapp <robin.knapp@ts.fujitsu.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |robin.knapp@ts.fujitsu.com Resolution|FIXED | --- Comment #8 from Robin Knapp <robin.knapp@ts.fujitsu.com> 2010-07-14 13:31:41 CEST --- Just tested it, but... if I update /etc/sysconfig/bootloader - nothing happens. Running update-bootloader --refresh - nothing happens. I have to either update a kernel to add these options or edit both /etc/sysconfig/bootloader AND /boot/grub/menu.lst which is suboptimal. So either don't remove custom automatically, try to detect them: if it's different from what's defined in /etc/sysconfig/bootloader, find out custom options and add them with the new kernel. Or provide a command to update the bootloader. Or use yast But this is not a good solution - people cried for years that you can only configure your system using yast; editing configuration files will break your system. This has become much better recently, but now it returns in a very critical place: the bootloader. So do we really want to return to "use yast or die"? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c9 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |estellnb@gmail.com --- Comment #9 from Josef Reidinger <jreidinger@novell.com> 2010-07-14 11:45:33 UTC --- (In reply to comment #8)
Just tested it, but... if I update /etc/sysconfig/bootloader - nothing happens. Running update-bootloader --refresh - nothing happens.
Of course, refresh is just to install bootloader to its location. It doesn't change configuration.
I have to either update a kernel to add these options or edit both /etc/sysconfig/bootloader AND /boot/grub/menu.lst which is suboptimal.
So either don't remove custom automatically, try to detect them: if it's different from what's defined in /etc/sysconfig/bootloader, find out custom options and add them with the new kernel.
/etc/sysconfig/bootloader is parameters for newly installed kernels. /boot/grub/menu.lst is actual settings. I detect custom settings, but if defined variables in sysconfig I use it. It is because we want clear solution for customer, because in past sometime happen that when customer has different kernel favors with different options and we use bad parameters for newly added kernel, so we use solution where is clear which parameters is used for new kernels.
Or provide a command to update the bootloader.
tool to edit bootloader is yast. Pbl is library, so you can create own tool using it. It is opensource.
Or use yast
But this is not a good solution - people cried for years that you can only configure your system using yast; editing configuration files will break your system. This has become much better recently, but now it returns in a very critical place: the bootloader.
So do we really want to return to "use yast or die"?
It is not "use yast or die". It is edit menu.lst for current kernels and edit /etc/sysconfig/bootloader for newly installed kernels ( e.g. ubuntu has both in one file and it is horrible mess, so we have two files ) None solution is the best one, always there is some users which complain. I hope that current solution is flexible and text in menu.lst should help user to know what is needed to edit to preserve settings after adding new kernel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c10 --- Comment #10 from Robin Knapp <robin.knapp@ts.fujitsu.com> 2010-07-14 14:08:20 CEST --- Ah, now I got it, misunderstood the comment in /boot/grub/menu.lst (even though it's clear). But to prevent some surprises for users who changed these option in menu.lst for ages this should be mentioned in the release notes. For example there's a part for KMS which says:
To set this permanently, add it to the kernel command line in /boot/grub/menu.lst.
Which will cause trouble after the first kernel update -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c11 Elmar Stellnberger <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|estellnb@gmail.com | --- Comment #11 from Elmar Stellnberger <estellnb@gmail.com> 2010-07-30 17:59:47 UTC --- Everything clear, isn`t it? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c12 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |ke@novell.com --- Comment #12 from Josef Reidinger <jreidinger@novell.com> 2010-08-16 07:05:25 UTC --- Karl - is possible to mention fix it in documentation? (see comment #10) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c13 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@novell.com InfoProvider|ke@novell.com |fs@novell.com --- Comment #13 from Karl Eichwalder <ke@novell.com> 2010-08-16 13:59:52 UTC --- I think it is already documented in the manuals (grub.xml) and there is no need to mention it in the release notes again. Or shall we do something else, Frank. please? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c14 --- Comment #14 from Robin Knapp <robin.knapp@ts.fujitsu.com> 2010-08-16 16:45:48 CEST --- I just looked into the documentation - it's quite clear. But I do not read the *whole* documentation everytime I upgrade and as this change affects booting (which is critical), therefore it should be mentioned in the release notes (IMHO) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c15 --- Comment #15 from Josef Reidinger <jreidinger@novell.com> 2010-10-04 13:28:42 UTC --- Just my 2c: I think that mention in menu.lst is enough, because release notes should contain important information which can block usage of opensuse or greatly change usage. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c16 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #16 from Felix Miata <mrmazda@earthlink.net> 2010-10-04 17:05:45 UTC --- FWIW, I habitually change menu.lst manually, as I run several multiboot systems with Factory, and for Factory I _always_ want showopts before root= on kernel line. I can find no way to have /etc/sysconfig/bootloader do that for me. Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c17 --- Comment #17 from Josef Reidinger <jreidinger@novell.com> 2010-10-05 12:11:41 UTC --- (In reply to comment #16)
FWIW, I habitually change menu.lst manually, as I run several multiboot systems with Factory, and for Factory I _always_ want showopts before root= on kernel line. I can find no way to have /etc/sysconfig/bootloader do that for me.
Sorry, but this is not possible. order of elements is hardcoded and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do. Of course if you have special requirements you can disable automatic change of boot menu and do it manually. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c18 --- Comment #18 from Felix Miata <mrmazda@earthlink.net> 2010-10-05 14:11:21 UTC --- (In reply to comment #17)
order of elements is hardcoded
Where and why?
and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
In Factory, sometimes it doesn't work and some experimenting is necessary to get a boot and find out why. e.g. for a long while, root=LABEL= syntax was not working, and still might not be in certain cases. Also, modern root=/dev/disk* syntax makes most kernel lines are longer than the text editor screen is wide (wrapping makes more confusion), which means also /dev/disk entries are too long for human brains to remember for manual typing. And, sometimes troubleshooting requires /dev/sdX# syntax. When dropping back to text mode to edit cmdline and mistake is made, grub doesn't recover nicely, and reboot to restart Grub is often required to retry. So, showopts before root= in gfxmenu is nice facility.
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do.
Again, hardcoded where? It seems to me during installation select list could also have additional option to make vga=normal not result on default kernel cmdline made by perl-Bootloader. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c19 --- Comment #19 from Josef Reidinger <jreidinger@novell.com> 2010-10-05 14:22:58 UTC --- (In reply to comment #18)
(In reply to comment #17)
order of elements is hardcoded
Where and why?
In perl-bootloader which add new sections to boot menu. And reason is to contain all parts from sysconfig and hard coded one is better then random :) Of course it is possible to have option which allow change of order, but noone yet find it useful. If you think it is useful please add it to features.opensuse.org and if there is enough positive responses I can do it.
and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
In Factory, sometimes it doesn't work and some experimenting is necessary to get a boot and find out why. e.g. for a long while, root=LABEL= syntax was not working, and still might not be in certain cases. Also, modern root=/dev/disk* syntax makes most kernel lines are longer than the text editor screen is wide (wrapping makes more confusion), which means also /dev/disk entries are too long for human brains to remember for manual typing. And, sometimes troubleshooting requires /dev/sdX# syntax. When dropping back to text mode to edit cmdline and mistake is made, grub doesn't recover nicely, and reboot to restart Grub is often required to retry. So, showopts before root= in gfxmenu is nice facility.
Yes, but it is quite specific case, I think common user doesn't find much benefit to have line which contain very long root before remaining parameters like nomodeset which is more useful to him.
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do.
Again, hardcoded where? It seems to me during installation select list could also have additional option to make vga=normal not result on default kernel cmdline made by perl-Bootloader.
Yes, it sounds reasonable. Could you please open separate bug report to easier track as it is out of context of this bug report? Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c20 --- Comment #20 from Felix Miata <mrmazda@earthlink.net> 2010-10-06 01:06:39 UTC --- (In reply to comment #19)
If you think it is useful please add it to features.opensuse.org and if there is enough positive responses I can do it.
https://features.opensuse.org/310673
Could you please open separate bug report to easier track as it is out of context of this bug report? Thanks
https://bugzilla.novell.com/show_bug.cgi?id=643984 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c21 Elmar Stellnberger <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|fs@novell.com | --- Comment #21 from Elmar Stellnberger <estellnb@gmail.com> 2010-11-15 19:43:24 UTC --- Open a different report for enhanced customization of kernel command line? That could be a feature request although I believe it is a too specialized issue for a public poll. The other side of the medal appears more like a bug an can therefore not be placed usefully on features.opensuse.org, I believe. Wouldn`t it really be a job that could be done with bounded effort to detect manual menu.lst changes to leave this entries simply in place eventually changing the kernel release number on updates? What is the script responsible for creating new menu.lsts?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c22 --- Comment #22 from Josef Reidinger <jreidinger@novell.com> 2010-11-16 08:39:28 UTC --- (In reply to comment #21)
Open a different report for enhanced customization of kernel command line? That could be a feature request although I believe it is a too specialized issue for a public poll. The other side of the medal appears more like a bug an can therefore not be placed usefully on features.opensuse.org, I believe. Wouldn`t it really be a job that could be done with bounded effort to detect manual menu.lst changes to leave this entries simply in place eventually changing the kernel release number on updates? What is the script responsible for creating new menu.lsts??
Hi, in general problem is that each additional customization of kernel line make tool more and more "expert" like as it require more advanced knowledge. So features helps to manage which is still in scope of tool and what is out of scope. It is not so easy with changing booting menu, as GRUB allow many options and e.g. it allow different parameters for different kernels. If you have just one kernel and want to have same parameters you can simple disable autoadapting (set LOADER_TYPE in /etc/sysconfig/bootloader to 'none' and set your in menu section kernel and initrd as symlinks). Reason why it is not so simple is two. If you have more kernel with different flavors, then it is not so easy to detect which one is correct. The second one is also important. If you change flavor of kernel ( so e.g. from default to desktop) and remove old one, then it is not ensure, that new one is installed before old one, so in one moment there could be no section in menu.lst and I need to get somewhere parameters and this is why it is introduced /boot/sysconfig/bootloader, which store it and it is always clear what is used during upgrade of kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434 https://bugzilla.novell.com/show_bug.cgi?id=620434#c23 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #23 from Josef Reidinger <jreidinger@novell.com> 2010-12-03 16:54:23 UTC --- I think that everything is clear there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com