From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16198 invoked from network); 14 Jan 2022 11:50:25 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 14 Jan 2022 11:50:25 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Fri Jan 14 06:45:39 -0500 2022 Message-ID: Date: Fri, 14 Jan 2022 12:45:29 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: anonymous shared shader framework extension persistence-aware frontend Subject: Re: [9front] Reply-To: 9front@9front.org Precedence: bulk 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