From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front]
Date: Fri, 14 Jan 2022 12:45:29 +0100 [thread overview]
Message-ID: <DBEFB879C02ADBF72E9DBA6C2481D369@felloff.net> (raw)
In-Reply-To: <CD2B63B7FCBEF6C0ECC64BAFF6980663@gmail.com>
it is supporting the multiboot standard.
any multiboot capable bootloader (grub, coreboot, qemu,
syslinux, linux kexec) can start our kernel file directly,
the plan9.ini is (optionally) passed as a "module"
(like initrd).
this is done by having a second entry point in the kernel
dedicated for multiboot, which also handles things like
getting the framebuffer configuration and memory map from
multiboot parameters and converting them into internal
plan9.ini format.
9boot and /dev/reboot (yes, you can start a plan9 kernel
from a plan9 kernel) enter the kernel thru the classical
a.out entry point.
--
cinap
next prev parent reply other threads:[~2022-01-14 11:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 8:44 [9front] thinktankworkspaces
2022-01-10 10:21 ` [9front] sirjofri
2022-01-10 17:25 ` [9front] thinktankworkspaces
2022-01-10 23:33 ` [9front] sirjofri
2022-01-12 1:16 ` [9front] thinktankworkspaces
2022-01-12 8:30 ` [9front] sirjofri
2022-01-12 9:29 ` [9front] Eckard Brauer
2022-01-12 13:09 ` [9front] sirjofri
2022-01-12 13:40 ` [9front] hiro
2022-01-12 14:59 ` [9front] thinktankworkspaces
2022-01-12 16:56 ` [9front] hiro
2022-01-14 11:45 ` cinap_lenrek [this message]
2022-01-12 14:40 ` [9front] thinktankworkspaces
2022-01-12 14:18 ` [9front] Stanley Lieber
2022-01-12 15:04 ` [9front] thinktankworkspaces
2022-01-10 12:10 ` [9front] mkf
-- strict thread matches above, loose matches on Subject: below --
2022-06-22 12:28 [9front] roy niang
2022-06-22 12:32 ` [9front] stefncb
2021-09-16 22:17 [9front] Drew Fargo
2021-08-24 19:25 [9front] Jonas
2021-06-09 14:33 [9front] adr
2021-03-31 16:32 [9front] cinap_lenrek
2021-04-01 18:33 ` [9front] Romano
2021-04-01 18:54 ` [9front] Romano
2021-04-01 19:03 ` [9front] cinap_lenrek
2021-04-01 23:16 ` [9front] Romano
2021-04-02 14:31 ` [9front] cinap_lenrek
2021-04-02 18:31 ` [9front] cinap_lenrek
2021-04-03 0:41 ` [9front] Romano
2021-04-02 21:24 ` [9front] Romano
2021-04-02 21:54 ` [9front] cinap_lenrek
2021-01-22 16:32 [9front] Марко М. Костић
2021-01-22 23:41 ` [9front] Tanami Muller
2021-01-23 0:29 ` [9front] Stuart Morrow
2021-01-23 13:38 ` [9front] Thaddeus Woskowiak
2021-01-23 14:12 ` [9front] hiro
2018-08-20 19:42 [9front] umbraticus
2018-08-20 12:11 [9front] Alex Musolino
2018-06-06 12:30 Stanislav Paskalev
2018-06-06 15:50 ` [9front] Kurt H Maier
2018-02-17 4:53 [9front] kokamoto
2016-12-28 23:31 sl
2016-12-28 23:33 ` [9front] cinap_lenrek
2015-10-02 11:43 Holger Sebert
2015-10-02 14:32 ` [9front] Kurt H Maier
2015-10-04 21:18 ` [9front] Stanley Lieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBEFB879C02ADBF72E9DBA6C2481D369@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).