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 modules, which are made available as a pseudo-filesystem inside that loader.> If so: http://www.syslinux.org/wiki/index.php/Mboot.c32I?m not permitted to edit either that page or its talk page. Do I submit the content addition here, then? 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 Esser, Alexander Steeg
> 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 modules, > which are made available as a pseudo-filesystem inside that loader. > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > I?m not permitted to edit either that page or its talk page. > Do I submit the content addition here, then?Please do. Alternatively (or, even better), you could send a link to original documentation about your boot loader. About additional possibilities, there are 2 KERNEL-like directives for boot sectors files (IIRC, valid for SYSLINUX only, but I could be misremembering): LABEL asbootsector BS yourbootsectorfile LABEL as_doslike_bootsector BSS yourbootsetorfile Similarly, chain.c32 also accepts bs/bss options. For example: LABEL chain_to_bs_in_same_boot_partition COM32 chain.c32 APPEND boot bs=yourbootsectorfile There are additional options for chain.c32 (see the 2 wiki pages about it). Regards, Ady.
Geert Stappers
2014-Dec-05 10:31 UTC
[syslinux] updating the wiki WAS: vesamenu back to text before booting
On Fri, Dec 05, 2014 at 10:16:10AM +0100, Thorsten Glaser wrote:> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > I???m not permitted to edit either that page or its talk page. > Do I submit the content addition here, then?Euh, yes, that is an option. Hereby I volunteer for updating the wiki with updates that get to this mailinglist. This should allow other people in the Syslinux project to make the Syslinux wiki a wiki that resists spam. Groeten Geert Stappers -- Leven en laten leven
On Fri, 5 Dec 2014, Ady wrote:> > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I?m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > 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? 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 </pre> ==== example with differently named kernel === (editorial note: bsd4grml actually uses a boot.cfg file, too) <pre> LABEL bsd4grml KERNEL /boot/isolinux/mboot.c32 APPEND /boot/addons/bsd4grml/ldbsd.com set image bsd4me.rd`set timeout 5 --- /boot/addons/bsd4grml/bsd.rd </pre> ------------------------------------------------------------------> Alternatively (or, even better), you could send a link to > original documentation about your boot loader.*ahem* does CVSweb to the sources count? ;-) Well, I?ve gone back to the above and put a link to its manpage, although that will be way too high-level and user-oriented for this?> About additional possibilities, there are 2 KERNEL-like directives for > boot sectors files (IIRC, valid for SYSLINUX only, but I could beOK, that would work too, but these files would need to be produced first. (Not working within PXE, and tricky within ISO, and even more so within EXT.) Probably easier to write a .c32 that loads the second-stage loader to the right address and jumps there the same way the native bootsector does. 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 Esser, Alexander Steeg
> On Fri, Dec 05, 2014 at 10:16:10AM +0100, Thorsten Glaser wrote: > > On Fri, 5 Dec 2014, Gene Cumm wrote: > > > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I???m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > Euh, yes, that is an option. > > > Hereby I volunteer for updating the wiki with updates > that get to this mailinglist. > > This should allow other people in the Syslinux project > to make the Syslinux wiki a wiki that resists spam. > > > Groeten > Geert Stappers > -- > Leven en laten leven > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >Adding information to the Syslinux wiki regarding a specific OS (or regarding any project other than The Syslinux Project) usually also generates problems. The FreeBSD info is one example of such problematic cases. The boot loader used to work in a certain way (e.g. compatible with mboot), but later versions of FreeBSD are using a different bootloader. The newer versions seem to be incompatible with mboot, and there is no original updated documentation about it. So users keep blaming Syslinux ("it fails", "it doesn't work") and/or its documentation ("someone claims to have had success one time, but there is no source for such claim, no version is mentioned, no mention of the specific boot options being used..."), and wasting time (not just their's, but also answering again and again about it) trying (and failing) to boot newer versions of FreeBSD with mboot.c32. Posting additional examples in the mboot.c32 wiki page _might_ be useful, but it is certainly much more useful to post a link to original documentation. When the relevant boot loader changes and the original documentation changes, then users can find it, instead of (inadequately) expecting the mboot.c32 wiki page to be permanently up-to-date about other projects. Regards, Ady.
On Fri, Dec 5, 2014 at 4:16 AM, Thorsten Glaser <t.glaser at tarent.de> wrote:> 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.Good.> It can then use disc access (not PXE), or you can pass it the ?real? > kernel, but also e.g. configuration files, as Multiboot modules, > which are made available as a pseudo-filesystem inside that loader.This should then make it universal (not specific to a particular variant/file system).>> If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > I?m not permitted to edit either that page or its talk page. > Do I submit the content addition here, then?1) I was showing the name of and instructions for mboot.c32 such that hopefully we could work out a MirOS-specific example(s) (which I think I'd rather see in both places and you already did). 2) New users don't have edit (thought there was a notice during signup that existed at some point ) and you need a wikiadmin (done). -- -Gene
On 12/05/2014 01:16 AM, Thorsten Glaser wrote:> > I?m not permitted to edit either that page or its talk page. > Do I submit the content addition here, then? >Let us know your wiki handle, so we can give it edit privileges. It is an antispam measure. -hpa
On Wed, Dec 10, 2014 at 12:34:53PM -0800, H. Peter Anvin wrote:> On 12/05/2014 01:16 AM, Thorsten Glaser wrote: > > > > I???m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > > > Let us know your wiki handle, so we can give it edit privileges. It is > an antispam measure. > > -hpa >Gene allready took care of it. Information from http://www.syslinux.org/wiki/index.php/Special:Log/rights 14:18, 5 December 2014 GeneC (Talk | contribs) changed group membership for User:Mirabilos from (none) to editor (human) Groeten Geert Stappers -- Leven en laten leven
On Fri, Dec 05, 2014 at 11:31:51AM +0100, Geert Stappers wrote:> On Fri, Dec 05, 2014 at 10:16:10AM +0100, Thorsten Glaser wrote: > > On Fri, 5 Dec 2014, Gene Cumm wrote: > > > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I???m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > Euh, yes, that is an option. > > > Hereby I volunteer for updating the wiki with updates > that get to this mailinglist.The procedure in http://www.syslinux.org/archives/2014-December/022903.html * register wiki user * name your wiki account and ask for edit permission * edit the wiki your self worked better. Use that approach.> This should allow other people in the Syslinux project > to make the Syslinux wiki a wiki that resists spam.A mediawiki that I co-maintain has require_once "$IP/extensions/ConfirmEdit/Asirra.php"; in LocalSettings.php Groeten Geert Stappers -- Leven en laten leven ------------- volgend deel ------------ Een niet-tekst bijlage is gescrubt... Naam: signature.asc Type: application/pgp-signature Grootte: 836 bytes Omschrijving: Digital signature URL : <http://www.zytor.com/pipermail/syslinux/attachments/20150102/cb078b47/attachment.sig>