search for: ldbsd

...irBSD === The MirBSD [https://www.mirbsd.org/mani386/boot.8 second-stage bootloader] acts as faux MultiBoot ?OS kernel?. It can either load the boot.cfg file and the kernel from disc, or have them passed as faux MultiBoot ?OS modules?. In SYSLINUX scenarios, the bootloader is commonly renamed as ?ldbsd.com?, although upstream places it under ?/boot? normally. ==== just the bootloader ==== <pre> LABEL mirbsd KERNEL mboot.c32 APPEND /ldbsd.com </pre> ==== bootloader, config, and kernel ==== <pre> LABEL mirbsd KERNEL mboot.c32 APPEND /ldbsd.com --- /boot.cfg --- /bsd &l...

> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), > > The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. > It can then use disc access (not PXE), or you can pass it the "real" > kernel, but

...oot.8 second-stage > bootloader] acts as faux MultiBoot "OS kernel". It can either > load the boot.cfg file and the kernel from disc, or have them > passed as faux MultiBoot "OS modules". > > In SYSLINUX scenarios, the bootloader is commonly renamed as > "ldbsd.com", although upstream places it under "/boot" normally. > > ==== just the bootloader ==== > > <pre> > LABEL mirbsd > KERNEL mboot.c32 > APPEND /ldbsd.com > </pre> > > ==== bootloader, config, and kernel ==== > > <pre> &g...

...taller/jessie/i386/linux matches Binary file ./debian-installer/wheezy/amd64/linux matches Binary file ./debian-installer/wheezy/i386/linux matches It does not switch back to text mode when chaining to https://www.mirbsd.org/MirOS/current/i386/boot renamed to "pxebsd.0" (used to be "ldbsd.com" before you dropped COMBOOT support). bye, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG Bonn) ? USt-ID (VAT): DE122264941 Gesch?ftsf?hrer: Dr. Stefan Barth, Kai Ebenrett, Boris Ess...

On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot

Hi, I still have the question: when I have an environment that uses vesamenu, for example on PXE, how do I configure it so that, for some of the menu entries, it switches back to the text mode (03h) before handing off to the next bootloader / kernel? Thanks, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228

On 12/02/2014 06:48 AM, Thorsten Glaser wrote: > Hi, > > I still have the question: when I have an environment that uses > vesamenu, for example on PXE, how do I configure it so that, for > some of the menu entries, it switches back to the text mode (03h) > before handing off to the next bootloader / kernel? > This is the default unless the "quiet" option is set.

...matches >Binary file ./debian-installer/wheezy/amd64/linux matches >Binary file ./debian-installer/wheezy/i386/linux matches > >It does not switch back to text mode when chaining to >https://www.mirbsd.org/MirOS/current/i386/boot renamed >to "pxebsd.0" (used to be "ldbsd.com" before you dropped >COMBOOT support). > >bye, >//mirabilos -- Sent from my mobile phone. Please pardon brevity and lack of formatting.

...Tue, 2 Dec 2014, H. Peter Anvin wrote: > > > This is the default unless the "quiet" option is set. > > Hmm. > It does not switch back to text mode when chaining to > https://www.mirbsd.org/MirOS/current/i386/boot renamed > to "pxebsd.0" (used to be "ldbsd.com" before you dropped > COMBOOT support). Please inline your entire configuration file. --Gene