On 01/21/2013 04:16 PM, Bruce Ferrell wrote:

...

Very interesting systemd thread: http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/8165

On 01/21/2013 11:00 AM, Felix Miata wrote: perhaps the dead end is systemd with it's "my way or the highway" ways... Just sayin'

That's called making design decisions, and taking the bootloader out of the picture when UEFI is available is exactly the correct path to take. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday 2013-01-21 21:22, Greg KH wrote:

On Mon, Jan 21, 2013 at 02:00:46PM -0500, Felix Miata wrote:

...

Very interesting systemd thread: http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/8165

For UEFI systems, yes, grub2 is not needed and I would never recommend it, use something simpler and easier like gummiboot or syslinux (once it gets UEFI support.)

For all other systems (and those are a lot of them), sure use grub2.

So - presuming I understand the thread at gmane right - if you move a disk between a non-EFI and EFI system, you suddenly get screwed over by a systemd that suddenly starts automounting EFI instead of your traditional /dev/sda1 onto /boot? Great outlook... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday 2013-01-21 23:18, Greg KH wrote:

On Mon, Jan 21, 2013 at 11:04:22PM +0100, Jan Engelhardt wrote:

...

On Monday 2013-01-21 21:22, Greg KH wrote:

...

On Mon, Jan 21, 2013 at 02:00:46PM -0500, Felix Miata wrote:

...

Very interesting systemd thread: http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/8165

For UEFI systems, yes, grub2 is not needed and I would never recommend it, use something simpler and easier like gummiboot or syslinux (once it gets UEFI support.)

For all other systems (and those are a lot of them), sure use grub2.

So - presuming I understand the thread at gmane right - if you move a disk between a non-EFI and EFI system, you suddenly get screwed over by a systemd that suddenly starts automounting EFI instead of your traditional /dev/sda1 onto /boot?

Huh? You do that with grub2 and you have the same issues, you can't expect to move a EFI bootloader-marked disk to a non-EFI system and expect it to boot properly, no bootloader can handle that, sorry.

Was just looking at the non-EFI -> EFI direction, since EFI should hopefully boot in the classic mode via a bootloader like grub. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Mon, 21 Jan 2013 14:18:56 -0800 Greg KH пишет:

On Mon, Jan 21, 2013 at 11:04:22PM +0100, Jan Engelhardt wrote:

...

On Monday 2013-01-21 21:22, Greg KH wrote:

...

On Mon, Jan 21, 2013 at 02:00:46PM -0500, Felix Miata wrote:

...

Very interesting systemd thread: http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/8165

For UEFI systems, yes, grub2 is not needed and I would never recommend it, use something simpler and easier like gummiboot or syslinux (once it gets UEFI support.)

For all other systems (and those are a lot of them), sure use grub2.

So - presuming I understand the thread at gmane right - if you move a disk between a non-EFI and EFI system, you suddenly get screwed over by a systemd that suddenly starts automounting EFI instead of your traditional /dev/sda1 onto /boot?

Huh? You do that with grub2 and you have the same issues, you can't expect to move a EFI bootloader-marked disk to a non-EFI system and expect it to boot properly, no bootloader can handle that, sorry.

Of course I can. Moreover, I can use the *same* bootloader configuration for *both* cases and transparently switch between UEFI and Legacy BIOS boot. I will need to install both bootloader on this disk, sure. How do you do it with direct UEFI kernel boot? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 22/01/13 13:31, Greg KH escribió:

So are you suggesting that openSUSE install two different bootloaders on all systems, and keep them in sync with the installed kernel versions, just for the extreemly rare case when someone wants to take their boot disk out of one machine and put it into another one?

Have fun adding that feature :)

This ideas are part of this mentality that we must support half a dozen ways to do things, all of which end half implemented/working and then complain when they dont work. As this is a "new" feature for "new installs" on "new hardware" it is the perfect time to cut down the number of possible supported scenarios to the bare minimum considering the most common cases only and focus on getting stuff working great under that constrains. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 22/01/13 14:50, Ken Schneider - openSUSE escribió:

So, to hell with all of the current hardware owners out there, you are on your own going forward.

Again, please read what I've said. stop putting words in my fingers. I didnt say a word about existing hardware or installations, that's a completely separate issue. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Jan 22, 2013 at 10:45:45AM +0400, Andrey Borzenkov wrote:

В Mon, 21 Jan 2013 14:18:56 -0800 Greg KH пишет:

...

On Mon, Jan 21, 2013 at 11:04:22PM +0100, Jan Engelhardt wrote:

...

On Monday 2013-01-21 21:22, Greg KH wrote:

...

On Mon, Jan 21, 2013 at 02:00:46PM -0500, Felix Miata wrote:

...

Very interesting systemd thread: http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/8165

For UEFI systems, yes, grub2 is not needed and I would never recommend it, use something simpler and easier like gummiboot or syslinux (once it gets UEFI support.)

For all other systems (and those are a lot of them), sure use grub2.

So - presuming I understand the thread at gmane right - if you move a disk between a non-EFI and EFI system, you suddenly get screwed over by a systemd that suddenly starts automounting EFI instead of your traditional /dev/sda1 onto /boot?

Huh? You do that with grub2 and you have the same issues, you can't expect to move a EFI bootloader-marked disk to a non-EFI system and expect it to boot properly, no bootloader can handle that, sorry.

Of course I can. Moreover, I can use the *same* bootloader configuration for *both* cases and transparently switch between UEFI and Legacy BIOS boot.

So are you suggesting that openSUSE install two different bootloaders on all systems, and keep them in sync with the installed kernel versions, just for the extreemly rare case when someone wants to take their boot disk out of one machine and put it into another one? Have fun adding that feature :) good luck, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Tue, 22 Jan 2013 05:29:46 -0500 Felix Miata пишет:

On 2013-01-22 10:22 (GMT+0100) Hans Witvliet composed:

...

Limitations of grub-legacy are a real PITA.

As are the complications of Grub2.

grub2 requires knowledge of a single command - grub2-install. I do not call this overly complicated.

...

Some (btrfs, encrypted boot) were solved by grub2. Obviously grub2 isn't the holy grail and things like EFI pose additional challenges

...

It would be advisable to spend more time on getting grub2 fully acceptable

I can install and maintain Grub Legacy without any need for scripts, or looking up how to do what I need to do with it. Grub2 is so much more complicated than. and inconsistent with, Grub Legacy, it's hard to imagine "fully acceptable" ever coming to pass except for those who have never had working familiarity with Grub Legacy.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 22/01/13 22:18, Felix Miata wrote:

On 2013-01-22 14:47 (GMT+0400) Andrey Borzenkov composed:

...

Tue, 22 Jan 2013 05:29:46 -0500 Felix Miata composed:

...

...

On 2013-01-22 10:22 (GMT+0100) Hans Witvliet composed:

...

...

...

Limitations of grub-legacy are a real PITA.

...

...

As are the complications of Grub2.

...

grub2 requires knowledge of a single command - grub2-install. I do not call this overly complicated.

You over-simplify.

Due to the significant differences between Grub Legacy and Grub2, to become competent in the use of grub2-install may require unlearning grub-install.

On multiboot systems, mixing the two is a can of worms.

Grub Legacy can be maintained and used through its shell and thus without mounting the target and without dependence on config files scattered in disparate locations. To me who already knows Grub Legacy and has no need for features it lacks, this is an overwhelming advantage. It's good enough to carry me until such point as I need EFI loading kernels and initrds directly, making Grub2, depending on POV, either stillborn, or dead end.

Felix, I have been knocking my head against the brick wall trying to understand how I can install multiple OSs with grub/grub2, and have used very, VERY, bad language directed at whoever came up with the concept of grub2! I have sent this person to the lowest level of the lowest sub-basement of hell after I was stupid enough to believe the blurb that grub2 was the future and used it when I installed oS 12.2 :-( . In trying to understand grub2 I came across this: http://www.linuxidentity.com/us/down/articles/LSK_multi_distro_install_US.pd... and the comment by Hans above re using the single command "grub2-install" made me read the above pdf again. And again.....and again....and again..... (Whoever wrote that pdf article appears to have had it edited, or something, and it is not a smooth flowing article but possibly a combination of 2 separate versions of the article melded together.) I am now starting to work out what is necessary to be done to harness grub2. I am at a point now where tomorrow I will attempt to perform what that pdf describes has to be done to be able to install and boot multiple OSs using grub2. Using grub2 sounds like a piece of cake. But then, everything is easy when you know what you are doing, right? :-) Tomorrow then is D-DAY! BC -- Using openSUSE 12.2 x86_64 KDE 4.10.0 & kernel 3.7.4-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 29/01/13 17:27, Felix Miata wrote:

On 2013-01-29 17:14 (GMT+1100) Basil Chupin composed:

...

I have been knocking my head against the brick wall trying to understand how I can install multiple OSs with grub/grub2, and have used very, VERY, bad language directed at whoever came up with the concept of grub2!

...

I have sent this person to the lowest level of the lowest sub-basement of hell after I was stupid enough to believe the blurb that grub2 was the future and used it when I installed oS 12.2 :-( .

...

In trying to understand grub2 I came across this:

...

http://www.linuxidentity.com/us/down/articles/LSK_multi_distro_install_US.pd...

...

and the comment by Hans above re using the single command "grub2-install" made me read the above pdf again. And again.....and again....and again.....

...

(Whoever wrote that pdf article appears to have had it edited, or something, and it is not a smooth flowing article but possibly a combination of 2 separate versions of the article melded together.)

...

I am now starting to work out what is necessary to be done to harness grub2.

...

I am at a point now where tomorrow I will attempt to perform what that pdf describes has to be done to be able to install and boot multiple OSs using grub2.

...

Using grub2 sounds like a piece of cake.

...

But then, everything is easy when you know what you are doing, right? :-)

...

Tomorrow then is D-DAY!

Take a look at https://www.mageia.org/pipermail/mageia-dev/2013-January/022146.html and its thread before you start your D-day. It really does look at least theoretically simple; at least, if you aren't already intimately familiar with Grub Legacy, and you stick to the Grub2 scripts instead of doing it the old fashioned way as I do with Grub Legacy. Other than out of curiosity, I really have no use to spend time with Grub2.

Thanks for the link above. I shall look at it ASAP (after dinner which is getting close to being served). The only trouble is is that grub legacy is no longer supported, and the antagonism to switch to grub from grub legacy is sounding very much like the situation where people were (still are) arguing about KDE3 versus KDE4. BC -- Using openSUSE 12.2 x86_64 KDE 4.10.0 & kernel 3.7.4-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2013-01-29 17:49 (GMT+1100) Basil Chupin composed:

...

The only trouble is is that grub legacy is no longer supported, and the

I see "no longer supported" as applied to Grub Legacy as no more than an excuse to switch to something more bloated and complicated just to provide a few growingly necessary features lacking from Grub Legacy. It's well known what it's limitations are. It needs no more development, so no more "support" beyond simply providing the same rpm and yast module as that for the past half decade or more. As an only bootloader option at installation time it's dead, but it's not ready to discard.

...

antagonism to switch to grub from grub legacy is sounding very much like the situation where people were (still are) arguing about KDE3 versus KDE4.

To me the parallel is quite striking. KDE3 and Grub Legacy both give me what I need without bloat or mutated or replaced paradigms. I agree that the value of GRUB2 is way,way overated. I have never seen an example of a useful scriipt. For openSUSE on a mulltiboot system - ev en with a boot manager - GRUB legacy does a ar better job of installing in the right partition, particularly in a extended volume. If openSUSE completely abandomed GRUB in favor of GRU2 (you can still select GRUB legacy during installation) as Fedora has I'm going to have to try using a CD ro install a bootloader What's the main

On 01/29/2013 02:02 AM, Felix Miata wrote: point of a bootloader anyway? It'st is to start the boot process in a few seconds. I use LILO ato boot Debian. Works iin a ftrfs root. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

and the comment by Hans above re using the single command "grub2-install" made me read the above pdf again. And again.....and again....and again.....

I have boxes and vms multibooting with separate linuxes, linux+windows, linux+different windowses, and even some linux/BSD combination and they all work "out of the box" with grub2, not even needing to hand-edit any files. We should stop this now, it is not very related to releasing the next openSUSE version. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh пишет:

First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.

If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:

grub2-mkconfig -o /boot/grub2/grub.cfg

On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Tue, 29 Jan 2013 13:25:48 -0500 Patrick Shanahan пишет:

* Andrey Borzenkov [01-29-13 13:03]:

...

В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh пишет:

...

First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.

If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:

grub2-mkconfig -o /boot/grub2/grub.cfg

On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig.

so cp /boot/grub2/grub.cfg /boot/grub2/custom.cfg and edit custom.cfg?

No copy, just edit.

if custom.cfg exists, is it used instead of grub.cfg or in addition to?

In addition to. custom.cfg is included into grub.cfg at runtime.

in editing "40_custom" it must be necessary to copy and alter "entire" sections of grub.cfg as "40_custom" appears to merely add lines to the "bottom" of grub.cfg. ie: its format/usage is not well explained, aics.

info grub2, Configuration - Simple Configuration. Did you read it?

I tried to add "video=1600x1200-32" to grub.cfg kernel parameters line via 40_custom and it only added a single line at the bottom of grub.cfg and had *no* effect.

There is "Additional kernel command line parameters" in YaST2 bootloader configuration (loosely translation back to English). Does it not work if you add it there?

thus far, usage/adaptation of grub2 as in unix text configuration files seem to be quite illogical and convoluted.

grub2.cfg is not unix text configuration file. It is script that is interpreted at runtime. grub-mkconfig is a convenience layer which automatically generates this script. Use of it is not mandatory and I have seen several projects that claim to do better job in maintaining grub.cfg.

I somehow after using grub2-mkconfig realized unwanted/unusable addiitons to the kernel parameters line in grub.cfg and could find *no* reference for correcting. On a "stab-in-the-dark" edited /etc/default/grub.old and was able to removed the unwanted chars from the grub.cfg kernel param lines. This is definitely *not* intuitive, expected, logical or documented (that I could find).

Let's be fair. Use of grub-mkconfig is documented well enough.

grub2 "may be a good thing" but is a mess to the unknowing w/o very good documentation and that requirement does not exist. This point is a *major* failure.

What exactly do you need to customize that is not documented? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 01/29/2013 03:09 PM, Roman Bysh wrote:

On Tue 29 Jan 2013 02:20:32 PM EST, Andrey Borzenkov wrote:

...

В Tue, 29 Jan 2013 13:25:48 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [01-29-13 13:03]:

...

В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh пишет:

...

First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.

If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:

grub2-mkconfig -o /boot/grub2/grub.cfg

On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig.

so cp /boot/grub2/grub.cfg /boot/grub2/custom.cfg and edit custom.cfg?

No copy, just edit.

...

if custom.cfg exists, is it used instead of grub.cfg or in addition to?

In addition to. custom.cfg is included into grub.cfg at runtime.

...

in editing "40_custom" it must be necessary to copy and alter "entire" sections of grub.cfg as "40_custom" appears to merely add lines to the "bottom" of grub.cfg. ie: its format/usage is not well explained, aics.

info grub2, Configuration - Simple Configuration. Did you read it?

...

I tried to add "video=1600x1200-32" to grub.cfg kernel parameters line via 40_custom and it only added a single line at the bottom of grub.cfg and had *no* effect.

There is "Additional kernel command line parameters" in YaST2 bootloader configuration (loosely translation back to English). Does it not work if you add it there?

...

thus far, usage/adaptation of grub2 as in unix text configuration files seem to be quite illogical and convoluted.

grub2.cfg is not unix text configuration file. It is script that is interpreted at runtime. grub-mkconfig is a convenience layer which automatically generates this script. Use of it is not mandatory and I have seen several projects that claim to do better job in maintaining grub.cfg.

...

I somehow after using grub2-mkconfig realized unwanted/unusable addiitons to the kernel parameters line in grub.cfg and could find *no* reference for correcting. On a "stab-in-the-dark" edited /etc/default/grub.old and was able to removed the unwanted chars from the grub.cfg kernel param lines. This is definitely *not* intuitive, expected, logical or documented (that I could find).

Let's be fair. Use of grub-mkconfig is documented well enough.

...

What exactly do you need to customize that is not documented?

I didn't know about "custom.cfg" even after dealing with the people at Bugzilla. They said that I had to use 40_custom for custom wording.

*And* editing existing entries. Any good examples of custom.cfg integration to grub.cfg? Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Andrey Borzenkov [01-29-13 14:22]:

В Tue, 29 Jan 2013 13:25:48 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [01-29-13 13:03]:

...

В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh пишет:

...

First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.

If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:

grub2-mkconfig -o /boot/grub2/grub.cfg

On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig.

so cp /boot/grub2/grub.cfg /boot/grub2/custom.cfg and edit custom.cfg?

No copy, just edit.

If I *create* custom.cfg, ie: touch ./custom.cfg, it is an empty file. Remember I am not expert with grub2. What do I edit?

...

if custom.cfg exists, is it used instead of grub.cfg or in addition to?

In addition to. custom.cfg is included into grub.cfg at runtime.

So "melded together" or added at the end of or ...

...

in editing "40_custom" it must be necessary to copy and alter "entire" sections of grub.cfg as "40_custom" appears to merely add lines to the "bottom" of grub.cfg. ie: its format/usage is not well explained, aics.

info grub2, Configuration - Simple Configuration. Did you read it?

Ah, some enlightenment. No, I had not.

...

I tried to add "video=1600x1200-32" to grub.cfg kernel parameters line via 40_custom and it only added a single line at the bottom of grub.cfg and had *no* effect.

There is "Additional kernel command line parameters" in YaST2 bootloader configuration (loosely translation back to English). Does it not work if you add it there?

It was yast that added unwanted chars to the kernel parameter line and would not remove them. I have since correct it by editing "grub.old" but that was a *lucky* guess. Perhaps I was too focused on the video parameter list that I didn't try, think of, using the parameters line. Forgive my frustration.

...

thus far, usage/adaptation of grub2 as in unix text configuration files seem to be quite illogical and convoluted.

grub2.cfg is not unix text configuration file. It is script that is interpreted at runtime. grub-mkconfig is a convenience layer which automatically generates this script. Use of it is not mandatory and I have seen several projects that claim to do better job in maintaining grub.cfg.

...

I somehow after using grub2-mkconfig realized unwanted/unusable addiitons to the kernel parameters line in grub.cfg and could find *no* reference for correcting. On a "stab-in-the-dark" edited /etc/default/grub.old and was able to removed the unwanted chars from the grub.cfg kernel param lines. This is definitely *not* intuitive, expected, logical or documented (that I could find).

Let's be fair. Use of grub-mkconfig is documented well enough.

I am not disillusioned with grub-mkconfig, it takes a formated list of variables and their parameters and formats it for use in booting, ie: provides grub.cfg I was not *blaming* grub-mkconfig, rather I believe yast deformed the kernel parameters line with, iirc, "24-bit" and another partial string beginning with "(".

...

grub2 "may be a good thing" but is a mess to the unknowing w/o very good documentation and that requirement does not exist. This point is a *major* failure.

What exactly do you need to customize that is not documented?

Perhaps I view too narrowly the useage as I wanted to add "video=1600x1200x32" to the kernel parameters using the drop-down table offered in "yast bootloader" but could never get the system to boot to that video mode. Indeed, yast does not offer "video=" but "vga=". So I tried to add by 40_custom, which did add the string to grub.cfg (at the bottom). Which also did not work and I now surmise that some other variable needed to be set to that string, instead. I may appear to not be "open minded" about this but I am more confused than anything. I have no problem using grub2 for my systems, but do have a problem *understanding* it's configuration. And thank-you for taking the time to help. I am sure others that see this discussion that are also confused will also benefit. I also was paying more attention to on-line documentation than that within my own system, shame on me. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Tue, 29 Jan 2013 18:07:47 -0500 Patrick Shanahan пишет:

* Andrey Borzenkov [01-29-13 14:22]:

...

В Tue, 29 Jan 2013 13:25:48 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [01-29-13 13:03]:

...

В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh пишет:

...

First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.

If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:

grub2-mkconfig -o /boot/grub2/grub.cfg

On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig.

so cp /boot/grub2/grub.cfg /boot/grub2/custom.cfg and edit custom.cfg?

No copy, just edit.

If I *create* custom.cfg, ie: touch ./custom.cfg, it is an empty file. Remember I am not expert with grub2. What do I edit?

...

...

if custom.cfg exists, is it used instead of grub.cfg or in addition to?

In addition to. custom.cfg is included into grub.cfg at runtime.

So "melded together" or added at the end of or ...

...

...

in editing "40_custom" it must be necessary to copy and alter "entire" sections of grub.cfg as "40_custom" appears to merely add lines to the "bottom" of grub.cfg. ie: its format/usage is not well explained, aics.

info grub2, Configuration - Simple Configuration. Did you read it?

Ah, some enlightenment. No, I had not.

...

...

I tried to add "video=1600x1200-32" to grub.cfg kernel parameters line via 40_custom and it only added a single line at the bottom of grub.cfg and had *no* effect.

There is "Additional kernel command line parameters" in YaST2 bootloader configuration (loosely translation back to English). Does it not work if you add it there?

It was yast that added unwanted chars to the kernel parameter line and would not remove them.

And bug report number is ...?

I was not *blaming* grub-mkconfig, rather I believe yast deformed the kernel parameters line with, iirc, "24-bit" and another partial string beginning with "(".

...

...

grub2 "may be a good thing" but is a mess to the unknowing w/o very good documentation and that requirement does not exist. This point is a *major* failure.

What exactly do you need to customize that is not documented?

Perhaps I view too narrowly the useage as I wanted to add "video=1600x1200x32" to the kernel parameters using the drop-down table offered in "yast bootloader" but could never get the system to boot to that video mode. Indeed, yast does not offer "video=" but "vga=".

But that's YaST2, not grub2, you are talking about.

So I tried to add by 40_custom, which did add the string to grub.cfg (at the bottom).

No, it won't work this way. You juts need to add it to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. 40_custom is for adding verbatim *code* to grub.cfg, not for customizing grub-mkconfig. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org