Displaying 4 results from an estimated 4 matches for "mani386".
Did you mean:
magni86
2014 Dec 05
2
vesamenu back to text before booting
...; Please do.
Okay, MediaWiki syntax docs follow. Note I have tested those
only a bit, and not within the vesamenu context, but if mboot.c32
resets to text mode, all will be fine.
------------------------------------------------------------------
=== MirBSD ===
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?...
2014 Dec 05
0
vesamenu back to text before booting
> 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
2014 Dec 05
0
vesamenu back to text before booting
...s follow. Note I have tested those
> only a bit, and not within the vesamenu context, but if mboot.c32
> resets to text mode, all will be fine.
>
> ------------------------------------------------------------------
>
> === MirBSD ===
>
> 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
> &quo...
2014 Dec 05
8
vesamenu back to text before booting
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