Re: LiveCD bootloader

Re: LiveCD bootloader

[Tom Davies]

[-- Attachment #1: Type: text/plain, Size: 549 bytes --]

Hi :)

Are we talking about a bootloader that can be used inside a customised Cd? Could 
grub2 be installed to hard-drive and dynamically include a menu item for LiveCd 
if it found an Ubuntu or other distros CD in the cd/dvd-drive?  I am not sure 
the complexity would be worth it?  If it could be done in some simple way then 
could it also boot iso files found in a specific location?  Again i am more 
curious about people's thoughts rather than thinking we really need this level 
of functionality.

Regards from
Tom :)



      

[-- Attachment #2: Type: text/html, Size: 769 bytes --]

Re: LiveCD bootloader

[Teresa e Junior]

On Thu, 9 Sep 2010 10:34:22 +0000 (GMT)
Tom Davies <tomdavies04@yahoo.co.uk> wrote:

> Hi :)

Hi, Sorry for taking so long to answer!

> Are we talking about a bootloader that can be used inside a
> customised Cd?

We were talking about the bootloader that calls the live system, like
the one for choosing a Language in Ubuntu LiveCDs.

> Could grub2 be installed to hard-drive and dynamically
> include a menu item for LiveCd if it found an Ubuntu or other distros
> CD in the cd/dvd-drive?  I am not sure the complexity would be worth
> it?

I think loading a CD if found is a BIOS duty.

> If it could be done in some simple way then could it also boot
> iso files found in a specific location?  Again i am more curious
> about people's thoughts rather than thinking we really need this
> level of functionality.
> 
> Regards from
> Tom :)

This is already possible, see http://mgerards.net/blog/?p=16

See you!
Teresa e Junior

LiveCD bootloader

[Teresa e Junior]

Hello, GRUB developers!

I'm fighting to replace isolinux with GRUB2 in the Live System I'm
about to release. I already got the CD to boot with GRUB2, generating
the ISO with grub-mkrescue. I think there must be some smarter way to
do this, but I can't find out.

But due to some features I need (not the eyecandy), I noticed the CD
only boots without gfx support (which is the most important for me).

I already tried using --modules="linux ext2 fshelp ls boot pc coreui vbe
png jpeg gettext gfxmode" without any success. Tried some burg-mkisofs
and xorriso commands, but I believe I miss something. Typing
`configfile /grub.cfg' won't help either.

Your help will be very appreciated, for we've been struggling for not
a few hours!

Teresa e Junior

Re: LiveCD bootloader

[Brendan Trotter]

Hi,

On Wed, Sep 8, 2010 at 12:12 PM, Teresa e Junior
<teresaejunior@gmail.com> wrote:
> But due to some features I need (not the eyecandy), I noticed the CD
> only boots without gfx support (which is the most important for me).

You can't really safely use graphics support in a Live-CD anyway.

GRUB and Linux use "video mode numbers" to request a video mode. These
video mode numbers can be different for different video cards. Early
versions of VBE did define some standard mode numbers, but these
became obsolete in VBE version 2.0 (back in 1994). Software written
after 1994 shouldn't rely on these obsolete video mode numbers. For
example, if you're lucky mode 0x118 might be 1024*768 with 24-BPP, but
nothing guarantees that anymore, and it could easily be any other
video mode. There's also no guarantee that the the video card supports
the video mode (e.g. a lot of video cards only support 32-BPP video
modes and don't support any 24-BPP video modes; and some only support
24-BPP video modes and not 32-BPP video modes; and the same is true
for 15-BPP vs. 16-BPP).

Finally, even if you're lucky and VBE does support the video mode (and
it's the right one, not something else); there's no guarantee that the
monitor also supports the video mode (neither VBE nor GRUB nor Linux
bother the check the monitors EDID information to make sure). This can
be worse than "user can't see anything. For some (very old) "VGA only"
monitors exceeding the monitor's maximum timing frequencies can cause
the monitor to blow up (but these are quite rare now, for obvious
reasons). I've also heard rumours that for some LCDs built into
cheaper notebook type devices, exceeding the screen's maximum timing
frequencies can cause permanent damage.

Basically, the entire thing only works when the user tells GRUB/Linux
which video mode to use (and then it's the user's fault if they choose
something that doesn't work). It fails for a Live-CD which is meant to
work "as is" and isn't pre-configured by the user.

The only "least likely to fail" option would be to use standard VGA
video modes instead - e..g mode 0x12 (320*200*256 colours) or mode
0x13 (640*480*16 colours). These mode numbers are "guaranteed" (by VGA
compatibility) to be what you asked for, and are also "guaranteed" to
work with the monitor (by VGA compatibility for older monitors and by
VESA's "Safe Mode Timing" specification for newer monitors).
Unfortunately they also suck - very low resolution and/or poor colour
depth.

Of course, I'm not saying that you can't unsafely use graphics support
in a Live-CD - I'm sure plenty of people have done worse.



Cheers,

Brendan

Re: LiveCD bootloader

[Brendan Trotter]

Hi,

On Wed, Sep 8, 2010 at 2:39 PM, Brendan Trotter <btrotter@gmail.com> wrote:
> GRUB and Linux use "video mode numbers" to request a video mode. These
> video mode numbers can be different for different video cards. Early
> versions of VBE did define some standard mode numbers, but these
> became obsolete in VBE version 2.0 (back in 1994). Software written
> after 1994 shouldn't rely on these obsolete video mode numbers. For
> example, if you're lucky mode 0x118 might be 1024*768 with 24-BPP, but
> nothing guarantees that anymore, and it could easily be any other
> video mode. There's also no guarantee that the the video card supports
> the video mode (e.g. a lot of video cards only support 32-BPP video
> modes and don't support any 24-BPP video modes; and some only support
> 24-BPP video modes and not 32-BPP video modes; and the same is true
> for 15-BPP vs. 16-BPP).

My apologies.

It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
"standard video mode numbers" anymore. Except for problems caused by
video modes that are supported by the video card but not supported by
the monitor; it's mostly only a problem with Linux itself now.


Cheers,

Brendan

Re: LiveCD bootloader

[Robert Millan]

2010/9/8, Brendan Trotter <btrotter@gmail.com>:
> My apologies.
>
> It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
> "standard video mode numbers" anymore. Except for problems caused by
> video modes that are supported by the video card but not supported by
> the monitor; it's mostly only a problem with Linux itself now.

Not with Linux either, just "set gfxpayload=keep" and GRUB will preserve
video mode when giving control to Linux.

-- 
Robert Millan

Re: LiveCD bootloader

[Teresa e Junior]

On Wed, 8 Sep 2010 14:54:25 +0930
Brendan Trotter <btrotter@gmail.com> wrote:

> Hi,
> 
> On Wed, Sep 8, 2010 at 2:39 PM, Brendan Trotter <btrotter@gmail.com>
> wrote:
> > GRUB and Linux use "video mode numbers" to request a video mode.
> > These video mode numbers can be different for different video
> > cards. Early versions of VBE did define some standard mode numbers,
> > but these became obsolete in VBE version 2.0 (back in 1994).
> > Software written after 1994 shouldn't rely on these obsolete video
> > mode numbers. For example, if you're lucky mode 0x118 might be
> > 1024*768 with 24-BPP, but nothing guarantees that anymore, and it
> > could easily be any other video mode. There's also no guarantee
> > that the the video card supports the video mode (e.g. a lot of
> > video cards only support 32-BPP video modes and don't support any
> > 24-BPP video modes; and some only support 24-BPP video modes and
> > not 32-BPP video modes; and the same is true for 15-BPP vs. 16-BPP).
> 
> My apologies.
> 
> It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
> "standard video mode numbers" anymore. Except for problems caused by
> video modes that are supported by the video card but not supported by
> the monitor; it's mostly only a problem with Linux itself now.
> 
> 
> Cheers,
> 
> Brendan
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel

Thanks! We have to set 640x480 as default anyway...

Re: LiveCD bootloader

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 09/09/10 00:47, Teresa e Junior wrote:
> On Wed, 8 Sep 2010 14:54:25 +0930
> Brendan Trotter<btrotter@gmail.com>  wrote:
>
>    
>> Hi,
>>
>> On Wed, Sep 8, 2010 at 2:39 PM, Brendan Trotter<btrotter@gmail.com>
>> wrote:
>>      
>>> GRUB and Linux use "video mode numbers" to request a video mode.
>>> These video mode numbers can be different for different video
>>> cards. Early versions of VBE did define some standard mode numbers,
>>> but these became obsolete in VBE version 2.0 (back in 1994).
>>> Software written after 1994 shouldn't rely on these obsolete video
>>> mode numbers. For example, if you're lucky mode 0x118 might be
>>> 1024*768 with 24-BPP, but nothing guarantees that anymore, and it
>>> could easily be any other video mode. There's also no guarantee
>>> that the the video card supports the video mode (e.g. a lot of
>>> video cards only support 32-BPP video modes and don't support any
>>> 24-BPP video modes; and some only support 24-BPP video modes and
>>> not 32-BPP video modes; and the same is true for 15-BPP vs. 16-BPP).
>>>        
>> My apologies.
>>
>> It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
>> "standard video mode numbers" anymore. Except for problems caused by
>> video modes that are supported by the video card but not supported by
>> the monitor; it's mostly only a problem with Linux itself now.
>>
>>
>> Cheers,
>>
>> Brendan
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>      
> Thanks! We have to set 640x480 as default anyway...
>
>    
You can specify multiple comma-separated possibilities in order of 
priorities
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>    


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

Re: LiveCD bootloader

[Teresa e Junior]

On Thu, 09 Sep 2010 00:52:27 +0200
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> wrote:

> On 09/09/10 00:47, Teresa e Junior wrote:
> > On Wed, 8 Sep 2010 14:54:25 +0930
> > Brendan Trotter<btrotter@gmail.com>  wrote:
> >
> >    
> >> Hi,
> >>
> >> On Wed, Sep 8, 2010 at 2:39 PM, Brendan Trotter<btrotter@gmail.com>
> >> wrote:
> >>      
> >>> GRUB and Linux use "video mode numbers" to request a video mode.
> >>> These video mode numbers can be different for different video
> >>> cards. Early versions of VBE did define some standard mode
> >>> numbers, but these became obsolete in VBE version 2.0 (back in
> >>> 1994). Software written after 1994 shouldn't rely on these
> >>> obsolete video mode numbers. For example, if you're lucky mode
> >>> 0x118 might be 1024*768 with 24-BPP, but nothing guarantees that
> >>> anymore, and it could easily be any other video mode. There's
> >>> also no guarantee that the the video card supports the video mode
> >>> (e.g. a lot of video cards only support 32-BPP video modes and
> >>> don't support any 24-BPP video modes; and some only support
> >>> 24-BPP video modes and not 32-BPP video modes; and the same is
> >>> true for 15-BPP vs. 16-BPP). 
> >> My apologies.
> >>
> >> It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
> >> "standard video mode numbers" anymore. Except for problems caused
> >> by video modes that are supported by the video card but not
> >> supported by the monitor; it's mostly only a problem with Linux
> >> itself now.
> >>
> >>
> >> Cheers,
> >>
> >> Brendan
> >>
> >> _______________________________________________
> >> Grub-devel mailing list
> >> Grub-devel@gnu.org
> >> http://lists.gnu.org/mailman/listinfo/grub-devel
> >>      
> > Thanks! We have to set 640x480 as default anyway...
> >
> >    
> You can specify multiple comma-separated possibilities in order of 
> priorities
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
> >    
> 
> 

Hello, Vladimir!

What do you mean with that? Let us suppose, I set:

GRUB_GFXMODE=1280x800,1024x768,640x480

and if the hardware supports the first, it will use the first, and so
forth?

Thank you!
Teresa e Junior

Re: LiveCD bootloader

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 09/09/10 01:00, Teresa e Junior wrote:
> On Thu, 09 Sep 2010 00:52:27 +0200
> Vladimir 'φ-coder/phcoder' Serbinenko<phcoder@gmail.com>  wrote:
>
>    
>> On 09/09/10 00:47, Teresa e Junior wrote:
>>      
>>> On Wed, 8 Sep 2010 14:54:25 +0930
>>> Brendan Trotter<btrotter@gmail.com>   wrote:
>>>
>>>
>>>        
>>>> Hi,
>>>>
>>>> On Wed, Sep 8, 2010 at 2:39 PM, Brendan Trotter<btrotter@gmail.com>
>>>> wrote:
>>>>
>>>>          
>>>>> GRUB and Linux use "video mode numbers" to request a video mode.
>>>>> These video mode numbers can be different for different video
>>>>> cards. Early versions of VBE did define some standard mode
>>>>> numbers, but these became obsolete in VBE version 2.0 (back in
>>>>> 1994). Software written after 1994 shouldn't rely on these
>>>>> obsolete video mode numbers. For example, if you're lucky mode
>>>>> 0x118 might be 1024*768 with 24-BPP, but nothing guarantees that
>>>>> anymore, and it could easily be any other video mode. There's
>>>>> also no guarantee that the the video card supports the video mode
>>>>> (e.g. a lot of video cards only support 32-BPP video modes and
>>>>> don't support any 24-BPP video modes; and some only support
>>>>> 24-BPP video modes and not 32-BPP video modes; and the same is
>>>>> true for 15-BPP vs. 16-BPP).
>>>>>            
>>>> My apologies.
>>>>
>>>> It seems GRUB2 has improved a lot, and doesn't rely on the obsolete
>>>> "standard video mode numbers" anymore. Except for problems caused
>>>> by video modes that are supported by the video card but not
>>>> supported by the monitor; it's mostly only a problem with Linux
>>>> itself now.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Brendan
>>>>
>>>> _______________________________________________
>>>> Grub-devel mailing list
>>>> Grub-devel@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>>>
>>>>          
>>> Thanks! We have to set 640x480 as default anyway...
>>>
>>>
>>>        
>> You can specify multiple comma-separated possibilities in order of
>> priorities
>>      
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>>
>>>        
>>
>>      
> Hello, Vladimir!
>
> What do you mean with that? Let us suppose, I set:
>
> GRUB_GFXMODE=1280x800,1024x768,640x480
>
> and if the hardware supports the first, it will use the first, and so
> forth?
>
>    
yes
> Thank you!
> Teresa e Junior
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>    


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

Re: LiveCD bootloader

[Teresa e Junior]

On Thu, 09 Sep 2010 01:29:09 +0200
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> wrote:

> yes

Thanks again!

Re: LiveCD bootloader

[Brendan Trotter]

Hi,

On Thu, Sep 9, 2010 at 8:30 AM, Teresa e Junior <teresaejunior@gmail.com> wrote:
> What do you mean with that? Let us suppose, I set:
>
> GRUB_GFXMODE=1280x800,1024x768,640x480
>
> and if the hardware supports the first, it will use the first, and so
> forth?

Not all of my previous assumptions were obsolete (and this time I
checked the source code for GRUB2 to make sure).

If the video card and software supports the first video mode then GRUB
will use the first video mode; regardless of whether or not the
monitor itself supports the video mode.

This means that: for the monitors I have here; for the newest 3 (LCD)
monitors you'll get 1280x800 and it will work fine (although probably
a little blurry due to not using the native resolution of any of the
monitor's); for the largest CRT you'll probably get a squashed image
that might still be readable (within the monitors maximum frequency,
but unsupported aspect ratio); for the next CRT you'll get a black
screen with an error message from the on screen display; for the next
2 CRTs you'll get an unreadable (flickering/rolling) mess; and for the
last monitor (a very old CRT) you'll probably cause permanent damage.


Cheers,

Brendan

Re: LiveCD bootloader

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 09/09/10 03:33, Brendan Trotter wrote:
> Hi,
>
> On Thu, Sep 9, 2010 at 8:30 AM, Teresa e Junior<teresaejunior@gmail.com>  wrote:
>    
>> What do you mean with that? Let us suppose, I set:
>>
>> GRUB_GFXMODE=1280x800,1024x768,640x480
>>
>> and if the hardware supports the first, it will use the first, and so
>> forth?
>>      
> Not all of my previous assumptions were obsolete (and this time I
> checked the source code for GRUB2 to make sure).
>
> If the video card and software supports the first video mode then GRUB
> will use the first video mode; regardless of whether or not the
> monitor itself supports the video mode.
>    
GRUB uses VBE on real hardware (I have some intelfb code but it's not 
functional yet), in this case it's VBE responsibility to verify monitor 
capabilities. Even having EDID without knowing the card characteristics 
you can't really check it since card itself may perform 
post-transformations like stretching or splitting the image among monitors.
> This means that: for the monitors I have here; for the newest 3 (LCD)
> monitors you'll get 1280x800 and it will work fine (although probably
> a little blurry due to not using the native resolution of any of the
> monitor's); for the largest CRT you'll probably get a squashed image
> that might still be readable (within the monitors maximum frequency,
> but unsupported aspect ratio); for the next CRT you'll get a black
> screen with an error message from the on screen display; for the next
> 2 CRTs you'll get an unreadable (flickering/rolling) mess; and for the
> last monitor (a very old CRT) you'll probably cause permanent damage.
>
>
> Cheers,
>
> Brendan
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>    


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

Re: LiveCD bootloader

[Robert Millan]

2010/9/8, Teresa e Junior <teresaejunior@gmail.com>:
> But due to some features I need (not the eyecandy), I noticed the CD
> only boots without gfx support (which is the most important for me).

You need to write a grub.cfg for that.  Check this one as an example
and adjust to your liking:

http://svn.debian.org/viewsvn/d-i/trunk/installer/build/boot/kfreebsd/grub-kfreebsd-cdrom.cfg?revision=64460&view=markup

-- 
Robert Millan

Re: LiveCD bootloader

[Teresa e Junior]

On Wed, 8 Sep 2010 10:36:35 +0200
Robert Millan <rmh@gnu.org> wrote:

> 2010/9/8, Teresa e Junior <teresaejunior@gmail.com>:
> > But due to some features I need (not the eyecandy), I noticed the CD
> > only boots without gfx support (which is the most important for me).
> 
> You need to write a grub.cfg for that.  Check this one as an example
> and adjust to your liking:
> 
> http://svn.debian.org/viewsvn/d-i/trunk/installer/build/boot/kfreebsd/grub-kfreebsd-cdrom.cfg?revision=64460&view=markup
> 

Thanks, from it I can see some mistakes I committed!

Re: LiveCD bootloader

[Andreas Born]

Hi,

we're building our LiveCD with Grub2. You can have a look at the config 
files we use/generate here: 
http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/livegrub2/
The other live stuff in general is here: 
http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/
For the buildscript look here (scroll towards the end for the grub2 
related stuff): 
http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/build-salixlive.sh?revision=1638

There are some issues though:
  - Black border displayed around the initial splash screen (maybe fixed 
in trunk, haven't read so on the maillist)
  - Starting Grub2 fails on my pretty new desktop (the only such report 
as far as I'm concerned)
  - Graphics are pretty slow

Andreas

Am 08.09.2010 04:42, schrieb Teresa e Junior:
> Hello, GRUB developers!
>
> I'm fighting to replace isolinux with GRUB2 in the Live System I'm
> about to release. I already got the CD to boot with GRUB2, generating
> the ISO with grub-mkrescue. I think there must be some smarter way to
> do this, but I can't find out.
>
> But due to some features I need (not the eyecandy), I noticed the CD
> only boots without gfx support (which is the most important for me).
>
> I already tried using --modules="linux ext2 fshelp ls boot pc coreui vbe
> png jpeg gettext gfxmode" without any success. Tried some burg-mkisofs
> and xorriso commands, but I believe I miss something. Typing
> `configfile /grub.cfg' won't help either.
>
> Your help will be very appreciated, for we've been struggling for not
> a few hours!
>
> Teresa e Junior
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>    

Re: LiveCD bootloader

[Colin Watson]

On Wed, Sep 08, 2010 at 05:28:07PM +0200, Andreas Born wrote:
> There are some issues though:
>  - Black border displayed around the initial splash screen (maybe fixed  
> in trunk, haven't read so on the maillist)

Not fixed.  See:

  http://lists.gnu.org/archive/html/grub-devel/2010-07/msg00057.html

>  - Starting Grub2 fails on my pretty new desktop (the only such report  
> as far as I'm concerned)

Fails how?

>  - Graphics are pretty slow

Might be related to:

  http://lists.gnu.org/archive/html/grub-devel/2010-06/msg00129.html

-- 
Colin Watson                                       [cjwatson@ubuntu.com]

Re: LiveCD bootloader

[Teresa e Junior]

On Wed, 08 Sep 2010 17:28:07 +0200
Andreas Born <futur.andy@googlemail.com> wrote:

> Hi,
> 
> we're building our LiveCD with Grub2. You can have a look at the
> config files we use/generate here: 
> http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/livegrub2/
> The other live stuff in general is here: 
> http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/
> For the buildscript look here (scroll towards the end for the grub2 
> related stuff): 
> http://salix.svn.sourceforge.net/viewvc/salix/salix-live/trunk/build-salixlive.sh?revision=1638
> 
> There are some issues though:
>   - Black border displayed around the initial splash screen (maybe
> fixed in trunk, haven't read so on the maillist)
>   - Starting Grub2 fails on my pretty new desktop (the only such
> report as far as I'm concerned)
>   - Graphics are pretty slow
> 
> Andreas
> 
> Am 08.09.2010 04:42, schrieb Teresa e Junior:
> > Hello, GRUB developers!
> >
> > I'm fighting to replace isolinux with GRUB2 in the Live System I'm
> > about to release. I already got the CD to boot with GRUB2,
> > generating the ISO with grub-mkrescue. I think there must be some
> > smarter way to do this, but I can't find out.
> >
> > But due to some features I need (not the eyecandy), I noticed the CD
> > only boots without gfx support (which is the most important for me).
> >
> > I already tried using --modules="linux ext2 fshelp ls boot pc
> > coreui vbe png jpeg gettext gfxmode" without any success. Tried
> > some burg-mkisofs and xorriso commands, but I believe I miss
> > something. Typing `configfile /grub.cfg' won't help either.
> >
> > Your help will be very appreciated, for we've been struggling for
> > not a few hours!
> >
> > Teresa e Junior
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >    
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel

Thank you, very helpful!