On Tue, 19 Jun 2012 12:49:13 -0400 Roman Bysh <rbtc1@rogers.com> wrote:

On Tue 19 Jun 2012 12:39:23 PM EDT, Josef Reidinger wrote:

...

On Tue, 19 Jun 2012 12:22:57 -0400 Roman Bysh<rbtc1@rogers.com> wrote:

...

Hello all,

Is there a plan to expand the Yast Boot Loader using Grub2? We would like to edit the /boot/Grub2/grub.cfg file.

The same way that we were able to edit /boot/grub/menu.lst.

Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293

Hi, I don't expect it (but I am not maintaner anymore). Grub2 think that you should not touch such file and this file is not easy to parse. It is own scripting language that is generated by set of grub2 config generators. If you are interested I can point you to some documentation. Josef

Yes. I would be interested.

What about providing a kcm-grub module? We just want the ability to edit the text label.

Well, if it is just limited subset of configuration options it is possible. My sources are: http://www.gnu.org/software/grub/manual/grub.html#Configuration ( official manual with described set of possible changes ) https://help.ubuntu.com/community/Grub2 (user perspective side of configuration) http://en.gentoo-wiki.com/wiki/Grub2 (more geek side, contain also changes to generators ) Just note that grub2 change quite lot in configurain area, when I write mail with possibility for yast2 module for it there is almost none options that can be easily write. Now there is a lot of options and it is quite funny, that it is quite similar to /etc/sysconfig/bootloader that we already have for old grub and do automatic generation from it like grub2 :) Josef

-- Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293

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

2012/6/19 Freigeist <m4ng4n@gmx.de>:

Am 19.06.2012 18:22, schrieb Roman Bysh:

...

Hello all,

Is there a plan to expand the Yast Boot Loader using Grub2? We would like to edit the /boot/Grub2/grub.cfg file.

The same way that we were able to edit /boot/grub/menu.lst.

Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293

What about this one?

http://kde-apps.org/content/show.php?content=139643

Thanks. Very interesting, but...... Do You see at the bottom of this page? Doesn't install in openSuSE 12.2/Factory.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 19 Jun 2012 19:44:17 -0300 Juan Erbes <jerbes@gmail.com> wrote:

2012/6/19 Freigeist <m4ng4n@gmx.de>:

...

Am 19.06.2012 18:22, schrieb Roman Bysh:

...

Hello all,

Is there a plan to expand the Yast Boot Loader using Grub2? We would like to edit the /boot/Grub2/grub.cfg file.

The same way that we were able to edit /boot/grub/menu.lst.

Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293

What about this one?

http://kde-apps.org/content/show.php?content=139643

Thanks.

Very interesting, but......

Do You see at the bottom of this page?

Doesn't install in openSuSE 12.2/Factory.... Hi That comment was on version 0.5.5 it's at 0.5.8 now

Looks like it changed in factory..... https://build.opensuse.org/package/binaries?arch=x86_64&package=PackageKit&p... It looks like with some updating the package has been rebuilt..... https://build.opensuse.org/package/files?package=kcm-grub2&project=home%3Aks... Doesn't seem to show a dependence on libpackagekit-qt.so.14 https://build.opensuse.org/package/binary?arch=x86_64&filename=kcm-grub2-0.5... -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.31-0.9-default up 2 days 4:59, 5 users, load average: 0.33, 0.40, 0.40 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 19 Jun 2012 21:17:51 -0300 Juan Erbes <jerbes@gmail.com> wrote:

2012/6/19 Malcolm <malcolm_lewis@bellsouth.net>:

...

On Tue, 19 Jun 2012 19:44:17 -0300 Juan Erbes <jerbes@gmail.com> wrote:

...

2012/6/19 Freigeist <m4ng4n@gmx.de>:

...

Am 19.06.2012 18:22, schrieb Roman Bysh:

...

Hello all,

Is there a plan to expand the Yast Boot Loader using Grub2? We would like to edit the /boot/Grub2/grub.cfg file.

The same way that we were able to edit /boot/grub/menu.lst.

Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293

What about this one?

http://kde-apps.org/content/show.php?content=139643

Thanks.

Very interesting, but......

Do You see at the bottom of this page?

Doesn't install in openSuSE 12.2/Factory.... Hi That comment was on version 0.5.5 it's at 0.5.8 now

Looks like it changed in factory..... https://build.opensuse.org/package/binaries?arch=x86_64&package=PackageKit&p...

It looks like with some updating the package  has been rebuilt..... https://build.opensuse.org/package/files?package=kcm-grub2&project=home%3Aks...

Doesn't seem to show a dependence on libpackagekit-qt.so.14 https://build.opensuse.org/package/binary?arch=x86_64&filename=kcm-grub2-0.5...

I installed it, and the only dependency required was libMagick++5: libMagick++.so.5()(64bit)

The packege I installed is: kcm-grub2-0.5.8-96.1.x86_64.rpm

But as user, it dont opens. I do'nt know how to use it.

Regards, Juan

Hi I would imagine it needs to run as the root user.... It should be part of the control center? http://ksmanis.wordpress.com/projects/grub2-editor/ Note, I'm a GNOME user..... -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.31-0.9-default up 2 days 5:42, 5 users, load average: 0.51, 0.41, 0.37 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Josef Reidinger wrote:

[...] Yes, this way is possible to write grub2 part of yast2 bootloader. But it doesn't edit grub.cfg. It edits /etc/default/grub from which is generated grub.cfg (so don't have full control for all configuration, just subset that grub2 developer decide that you can modify). Grub2 allows even bigger configuration changes, but it contain changes in generators and it is really tricky part.

That's retarded. Back to the yast1 days of shell script generated config files? I thought we try to get of SuSEconfig and now we are introducing a mechanism like SuSEconfig for the boot loader. What's the killer feature of grub2 that's worth swallowing the bitter pill of giving up sane yast support? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012/06/20 09:14 (GMT+0200) Ludwig Nussel composed:

What's the killer feature of grub2 that's worth swallowing the bitter pill of giving up sane yast support?

UEFI & installation to RAID are the ones I remember, but I think there's at least one other. Even though Grub Legacy has had no upstream for years, it doesn't really need maintaining, and should be kept as first option for those who don't need features it doesn't support. I've been reading the Grub support list for years, and installing *buntu on occasion in part to see how it works, and often fails. I see a shameful parallel between Grub 2 and KDE 4.x. Grub 2 is a complicated mess that shouldn't be foisted upon those who don't need what Grub Legacy lacks, at least, not yet. Let's get past the similarly troublesome systemd-init conversion first at least. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 6/20/2012 3:14 AM, Ludwig Nussel wrote:

Josef Reidinger wrote:

...

[...] Yes, this way is possible to write grub2 part of yast2 bootloader. But it doesn't edit grub.cfg. It edits /etc/default/grub from which is generated grub.cfg (so don't have full control for all configuration, just subset that grub2 developer decide that you can modify). Grub2 allows even bigger configuration changes, but it contain changes in generators and it is really tricky part.

That's retarded. Back to the yast1 days of shell script generated config files? I thought we try to get of SuSEconfig and now we are introducing a mechanism like SuSEconfig for the boot loader. What's the killer feature of grub2 that's worth swallowing the bitter pill of giving up sane yast support?

cu Ludwig

That aspect of grub2 is the way grub2 works. It's not a suse or opensuse decision. I hate it too but the upstream grub developers say it's the only sane way for them to support the wild and dynamic range of boot scenarios that exist today. I agree that the needs of bootloaders are crazy today vs in the past. But even if I were to agree that the bootloader needed an interpreted scripting language to provide the flexibility and run-time adaptability required today, I don't see why it has to be a new from-scratch one that no one knows, instead of being something standard that already exists, or at least a subset or superset. For example, as obscure as the freebsd bootloader is, it's at least a standard language, forth. You may or may not like forth as a language for most jobs, but it's been around a long time and it's syntax and methodologies have been documented a lot and it is at least used in a few other places and is useful for some other situations, so learning it isn't a _total_ waste of your time. Learning the grub2 syntax is _only_ good for grub2. Who the heck is ever going to ever get comfortable at that for casual infrequent yet commonly desired edits? I can't do the simplest little thing in grub2 without careful googling and hoping to hell I can find someone elses example that works. The average person will not be able to make common edits, only grub experts will. That's not a desirable design to me no matter what the other benefits. I also like that: The bootloader goes from config files (lilo, grub1) to scripting language (grub2), at the same time init goes from scripts (sysv) to config files (systemd). Can they both be right about the best way to do the job in the future? Is there anything about those two different jobs that really results in this setup being the sanest? I don't think so. I think one or the other approach is saner and applies to both jobs. I think the scripting approach is ultimately more useful so I'm all for grub2 going dynamic, but I just wish it was some standard language that is not a waste of time to learn, and arrange things so that the main config doesn't necessarily require an expert scripter to make common changes. You can write the most complex script and have a section, or a whole separate include-file, that just has basic variable definitions anyone can safely edit. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thursday 2012-06-21 02:00, Roman Bysh wrote:

It's a shame that openSUSE's Yast has not been able to completely integrate Grub2 the same way that they have done with Grub1.

At the same time, it's rather strange no developer with a distro background has yet produced a bootloader that meets the "requirement" of being easy to configure automatically. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org