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=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31153 invoked from network); 28 Jul 2023 03:24:34 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 28 Jul 2023 03:24:34 -0000 Received: from gaff.inri.net ([168.235.71.243]) by 9front; Thu Jul 27 23:21:30 -0400 2023 Received: from [127.0.0.1] ([107.115.206.129]) by gaff; Thu Jul 27 23:21:30 -0400 2023 Date: Thu, 27 Jul 2023 23:21:27 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <16905130930.52F6E.13899@lsd.chicago.il.us> References: <16905130930.52F6E.13899@lsd.chicago.il.us> Message-ID: <24404049-B55D-4481-B5B6-2BD581237735@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extensible private ORM out-scaling method Subject: Re: [9front] MBR; Boot Arguments Reply-To: 9front@9front.org Precedence: bulk On July 27, 2023 10:58:13 PM EDT, "Jay F=2E Shachter" wrote: > >Centuries ago, Nostradamus predicted that Jacob Moody would write on Thu = Jul 27 16:53:52 2023: > >>=20 >> Are you using an EFI partition table or an MBR? I assume you must be >> using EFI if you are dealing in more then 4 partitions on a disk=2E >> But in your previous mails you mentioned installing 9front in MBR >> mode=2E >>=20 > >It is an MBR-partitioned disk=2E I think -- and please correct me if I >am wrong -- that the entire concept of a boot flag on a disk slice is >inapplicable to GPT-partitioned disks=2E > >> >> Can you give me an entire explanation of how your disk is >> configured? >>=20 > >Windows 10 occupies the first two primary slices (when I got the >computer, Windows 10 had colonized all three primary slices, but I >liberated the third one)=2E FreeDOS 1=2E3 resides on the third primary >slice because it is practically impossible to get FreeDOS to work >anywhere but on a primary slice=2E Everything else resides on logical >slices within the extended slice=2E The two Linux systems reside on a >single logical slice, which constitutes a volume group from which >Linux logical volumes can be carved out=2E The other operating systems >each occupies a separate logical slice=2E 9front is on slice #14=2E The >MBR boots Linux GRUB=2E There is also a backup copy of the Linux GRUB >MBR on slice #10=2E There is a backup copy of the Solaris GRUB MBR on >slice #13=2E > >But the question of disk layout -- the entire question of why the >9front bootloader cannot find anything in the 9fat filesystem when >primary slice #1 is flagged as bootable -- is now a question only of >intellectual, but not practical, interest=2E I am bypassing the 9front >bootloader; GRUB is booting /9pc64 directly=2E The remaining question, >which I hope someone on this mailing list can answer, is: What >argument can I pass to /9pc64 that will tell it the bootfile, so that >I don't have to type the Enter key whenever I boot 9front to confirm >that I want to use local!/dev/sdE0/fs (similar to the user=3Dglenda >option that keeps me from having to type Enter to confirm that I am >glenda)? Thank you in advance for any and all replies=2E > > Jay F=2E Shachter > 6424 North Whipple Street > Chicago IL 60645-4111 > (1-773)7613784 landline > (1-410)9964737 GoogleVoice > jay@m5=2Echicago=2Eil=2Eus > http://m5=2Echicago=2Eil=2Eus > > "Quidquid latine dictum sit, altum videtur" > > the leading slash in front of pc64 is not needed when you're trying to loa= d the kernel off the 9fat partition=2E conversely, for pxe booting you'd ne= ed to provide the full path=2E al