-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/29/2012 09:11 AM, Marcus Meissner wrote:

On Fri, Jun 29, 2012 at 01:34:37AM +0200, Hans Witvliet wrote:

...

Hi all,

today i received a message that grub-2.0 is finally released. I lost track counting how may years they needed for it ;-)

Obviously this version can not be included into 12.2, much too late for that now.

...

From what i learned from the grub2-list, last couple of weeks quite a number of changes finally made it. So will grub2.0 be in a update after the 12.2 release, or will it be 12.3?

It was checked into 12.2 already.

Heretic you are. Neither of maintainers think this is a good idea :). thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP7VovAAoJEL0lsQQGtHBJiwgP/1jOnjQ9NIGxIm204atxKQns Lyux9Q6y9+nTFyBFgF2G8euz+95+icvUEgoPrbih+MboOKu/iNOsX8t1GRCngcNO DCFwNIv7xuw7oPOhFeaB+tfX1PCfa75donMbObhcK6q9I/DqZjHbeojU1lxI/2rv AgdJWomBLBNuHdDv/1pbYXn+Th5syxjgo8dH0jU4nTZoNeGTAL/HMeXmnzl6I9GM BptOkz8ZfnE1YiQHmnhc77rEv8KPlesJsQ8GWTH5RVNa7JTPQMHwfp4oRwobkpng qqIhMskrPSwkYX/Aa8i4d+9XKMyf6o4wIVX/bwQuEq4ZXYh4afXgNyDeSSUnWzqu HF9bXZKeFF6sCUEXFN0/m808eo6glUkFJxqyx61X0s+t1LdMYfXk57n6UW3S9Q+N Ko+4JzJoHwggSXJkwL/bgFO+RBxEkNFCoPaN/WvDpqrVGPCheDm90R8XKLjKjhWj RJmTZwZnIvGackJCq9xUmnG1/Lup+L+ve/nvCd0dT9X+FYj0C8he4asrgEUM2fgX pkJZVgS46UuVIDTo5n/xMRFbP409kI4L+kta7y/xqvehv4TmqiHqkU7ToawEztBW vycU88UNEQ+KJEDiTQLJKQrYfAo5OFMCrMM4o4CW3aAtOFBBZxtNE+gi3FmFLG5f bE/Ec/H/+h5oN8oq3yVr =VP1G -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 29.06.2012 09:34, Jiri Slaby wrote:

On 06/29/2012 09:33 AM, Jiri Slaby wrote:

...

Heretic you are. Neither of maintainers think this is a good idea :).

Too early for me now, heroic I meant :D.

As grub2 is most likely *the* change of 12.2 and bootloaders tend to get a lot of testing, I decided out of the mood at 6am when playing a puzzle with my daughter that I want to take *that* risk :) But if you say it's not a good idea - it would have been nice to include that in your submit request message. And grub2 is easy to revert. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Actual GRUB2 released has to be better than the buggy pre-releases I've been dealing with. I'm still using the Fedora 17 GRUB2 to manage booting on my machines because of all the bugs in openSUSE 12.2 GRUB2. On Fri, Jun 29, 2012 at 1:11 AM, Stephan Kulow wrote:

On 29.06.2012 09:34, Jiri Slaby wrote:

...

On 06/29/2012 09:33 AM, Jiri Slaby wrote:

...

Heretic you are. Neither of maintainers think this is a good idea :).

Too early for me now, heroic I meant :D.

As grub2 is most likely *the* change of 12.2 and bootloaders tend to get a lot of testing, I decided out of the mood at 6am when playing a puzzle with my daughter that I want to take *that* risk :)

But if you say it's not a good idea - it would have been nice to include that in your submit request message. And grub2 is easy to revert.

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

-- Twitter: http://twitter.com/znmeb Computational Journalism Server http://j.mp/compjournoserver Data is the new coal - abundant, dirty and difficult to mine. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 01-07-12 12:37, Sid Boyce schreef:

I'm just curious as I have 4 running 12.2 Beta2 boxes all using grub2 and just running openSUSE. What are these problems and are you dual booting? I can't see any specifics just that it's "rubbish" so I'd like to know if there is a potential pitfall awaiting. Regards Sid. Hmm, I can't boot 12.2 after the last upgrade of grub2; see my post of 29-06 on this list. I would call that a problem... My gear as a whole is dual boot (12.1 and 12.2), but each system boot from a separate disk, which I have to choose at bios start. Regards, Jogchum

On 01/07/12 04:53, M. Edward (Ed) Borasky wrote:

...

Actual GRUB2 released has to be better than the buggy pre-releases I've been dealing with. I'm still using the Fedora 17 GRUB2 to manage booting on my machines because of all the bugs in openSUSE 12.2 GRUB2.

On Fri, Jun 29, 2012 at 1:11 AM, Stephan Kulow wrote:

...

...

On 06/29/2012 09:33 AM, Jiri Slaby wrote:

...

Heretic you are. Neither of maintainers think this is a good idea :). Too early for me now, heroic I meant :D. As grub2 is most likely *the* change of 12.2 and bootloaders tend to get a lot of testing, I decided out of the mood at 6am when playing a

On 29.06.2012 09:34, Jiri Slaby wrote: puzzle with my daughter that I want to take *that* risk :)

But if you say it's not a good idea - it would have been nice to include that in your submit request message. And grub2 is easy to revert.

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

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

Hi to all I've a question. GRUB2 after ugrade of kernel at a new release, not refresh the list at the start-up, why? Thanks Maury -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I apologize, but i'm new user from linux world. Exactly i don't know how obtain a file bug report. I know only what i've seen on my screen when i've restarted my PC after the last kernel upgrade. Are installed GRUB and GRUB2. On screen during start up, is a normaly presents 3 options by boot loader config. the 1st and the 2nd are the normal GRUB, the 3rd is for GRUB2. Well, when i've clicked on the 3rd option, on the GRUB2 screen, i've seen that the option 1 & 2 aren't refreshed how in GRUB line on boot loader config, remain the last configuration on screen and when i want to use 1 of 2 options, obviously does not start the system and appeared a command line where it says, " file not found". This is all i can say at regards of the bug. Maury Il 03/07/2012 15.01, Andreas Jaeger ha scritto:

On Tuesday, July 03, 2012 14:56:01 maury63ts wrote:

...

Hi to all

I've a question.

GRUB2 after ugrade of kernel at a new release, not refresh the list at the start-up, why? It should - if not, please file a bugreport,

Andreas

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

Thanks Martin It's very complicated for me your solution. I've supposed that, if i write on these factory discussion team, perhaps the developed factory guys, would seek a solution. I was wrong, and frankly, is too complicated to perform too many steps just to a bug. I think that there is no desire to upgrade to RC1 where, to go to the bathroom, I need to ask permission. I'm sorry. Maury Il 03/07/2012 16.45, Martin Schlander ha scritto:

Tirsdag den 3. juli 2012 16:37:47 maury63ts skrev:

...

I apologize, but i'm new user from linux world. Exactly i don't know how obtain a file bug report. http://en.opensuse.org/openSUSE:Submitting_bug_reports

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

2012/7/3 maury63ts :

I apologize, but i'm new user from linux world. Exactly i don't know how obtain a file bug report. I know only what i've seen on my screen when i've restarted my PC after the last kernel upgrade.

Are installed GRUB and GRUB2. On screen during start up, is a normaly presents 3 options by boot loader config. the 1st and the 2nd are the normal GRUB, the 3rd is for GRUB2.

The third entry is added by installed grub2 package. It's intended for user to test grub2 running without actually installing them. You still use grub not grub2.

Well, when i've clicked on the 3rd option, on the GRUB2 screen, i've seen that the option 1 & 2 aren't refreshed how in GRUB line on boot loader config, remain the last configuration on screen and when i want to use 1 of 2 options, obviously does not start the system and appeared a command line where it says, " file not found".

Because your current bootloader is grub, during kernel update perl bootloader will only update the current config in use, that is grub's config. So grub2 is totally unaffected and you need update it manually. There's a similar bug report to this issue. https://bugzilla.novell.com/show_bug.cgi?id=763578 Andreas, how do you think we remove this feature? We can't call grub2-mkconfig for user in bnc#763578's case because it would lead regression to this bug: https://bugzilla.novell.com/show_bug.cgi?id=768063 And this keep people think about this is a bug if we can't offer a sane grub2 config for them to work. :( Thanks, Michael

This is all i can say at regards of the bug.

Maury

Il 03/07/2012 15.01, Andreas Jaeger ha scritto:

...

On Tuesday, July 03, 2012 14:56:01 maury63ts wrote:

...

Hi to all

I've a question.

GRUB2 after ugrade of kernel at a new release, not refresh the list at the start-up, why?

It should - if not, please file a bugreport,

Andreas

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

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

2012/7/5 Andreas Jaeger :

On Thursday, July 05, 2012 14:21:23 Michael Chang wrote:

...

2012/7/3 maury63ts : [snip]

What about enhancing /etc/sysconfig/bootloader to accept a list of bootloaders?

The question is there's no such case in real that we need to manage multipule installed bootloader configs at the same time. The change is huge and intrusive .. not just a enhance but a completely new feature and we don't know about how to implement it correctly .. :(

Or allow a manual invocation of perl-bootloader with an option like -- grub or --grub2 to write the specific configuration?

This will be have problem, in this case grub2 haven't been configured and thus perl-bootloader would fail due to it's not "initialized" ..

But IMO this is a transition problem: People don't trust grub2, want to play with it - and thus install them beside each other. Perhaps it's enough to document this scenario a bit more?

Maybe we could consider again in 12.3, or when we have more confidence on grub2. Thanks, Michael

Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

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

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

2012/7/5 Neil Rickert :

On Tue, 03 Jul 2012 14:56:01 +0200 maury63ts wrote:

...

GRUB2 after ugrade of kernel at a new release, not refresh the list at the start-up, why?

A comment on this.

On one of my machines, I have both 12.1 installed (using legacy grub), and 12.2 installed using grub2. The grub2 menu includes entries for booting either system.

(1) After a kernel update for 12.1, the grub2 menu still lists the old kernel for 12.1, so the grub2 menu entries cannot boot 12.1

Yes.

(2) After a kernel update for 12.2, the grub2 menu was updated for the correct kernel for 12.2. That would probably have also updated the 12.1 entries, except that 12.1 is in an encrypted LVM and not fully visible to 12.2, so the entries were instead dropped.

Yes.

I am not sure, but I suspect that Maury is talking about (1) rather than about (2). In that case, I don't see it as a bug.

Personally, I have added an entry to the grub2 menu that chainloads legacy grub to boot 12.1. So the problem in (1) is not a problem for me.

Personal opinion: I think grub2 commits the sin of doing too much. It would have been better to chainload to other installs, instead of directly booting the kernels.

I agree with you on chainloading is better than directly booting kernel in general, But the problem comes from how to deal with different install scenarios and that's complicated. There's no general rule to know what partition's bootsector is used and we could leverage it in chainloading to desired place. It's a wild open. For example a distribution may install it's loader to extended partition and /boot on logical partiton (/dev/sda5). This is quite common scenario I think. In this case chainloading /dev/sda5 simply fails. Also we cannot predict chainloading that extended partition would lead us to where ... So, directly booting kernel is not perfect but somehow it is predictable by utilities. And manually configure your chainload partitions to satisfy your needs. Don't trust machines, they are always dumb. :) Thanks, Michael

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

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

On Fri, 2012-06-29 at 09:11 +0200, Marcus Meissner wrote:

On Fri, Jun 29, 2012 at 01:34:37AM +0200, Hans Witvliet wrote:

...

Hi all,

today i received a message that grub-2.0 is finally released. I lost track counting how may years they needed for it ;-)

Obviously this version can not be included into 12.2, much too late for that now.

...

From what i learned from the grub2-list, last couple of weeks quite a number of changes finally made it. So will grub2.0 be in a update after the 12.2 release, or will it be 12.3?

It was checked into 12.2 already.

From feature point-of-view: wonderful, thanks a lot!!

From project/product P.O.V: lets say.. daring. I mean, even on the grub-M.L. _they_ were complaining about the amount of last-minute changes.

Looks like your team has been working around the clock ;-) Tnx, hans. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org