[oi-dev] FLAG DAY: Provide loader menu additions for boot image.

[Toomas Soome]

> On 4. nov 2016, at 14:07, Aurélien Larcher <aurelien.larcher at gmail.com> wrote:
> 
> 
> 
> On Fri, Nov 4, 2016 at 12:47 PM, Toomas Soome <tsoome at me.com <mailto:tsoome at me.com>> wrote:
> 
> > On 4. nov 2016, at 11:53, Jean-Pierre André <jean-pierre.andre at wanadoo.fr <mailto:jean-pierre.andre at wanadoo.fr>> wrote:
> >
> > Toomas Soome wrote:
> >>
> >> Support for specifying loader configuration on installation media was added to distribution constructror.
> >>
> >> This support consists several components.
> >>
> >> 1. loader configuration script for distribution manifest:
> >
> > I do not see information about which file systems are supported
> > by the loader.
> >
> > Is dual (triple) booting on Windows (ntfs) and Linux (ext2)
> > supported by the loader (or planned to be supported) ?
> >
> > Jean-Pierre
> >
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
> > https://openindiana.org/mailman/listinfo/oi-dev <https://openindiana.org/mailman/listinfo/oi-dev>
> 
> 
> I forgot to add; for dual boot *menu* entry, all you need is to set chain_disk=“devicename:”, for example in file /boot/conf.d/chainload  - if the variable chain_disk is set, the menu entry will appear. In case of distro constructor, this will be done in /boot/loader.rc.local on installer image. However, we do not install this file to disk (if you will look into it, you can figure out, why;).
> 
> Could we compile the info on the Wiki somehow, or if you have a pointer at hand?
>  

Sure, just someone needs to write it down… Also, there are manuals waiting for helping hand in source tree - reviewing and updating manuals is great way to get knowledge and to start to contribute. This is not Sun/Oracle any more - if people wont contribute, nothing will happen.

rgds,
toomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20161104/a41e81a8/attachment-0005.html>