9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] MBR; Boot Arguments
Date: Fri, 28 Jul 2023 00:07:14 -0500	[thread overview]
Message-ID: <8807ea01-47b6-085f-9ffb-9657a2431130@posixcafe.org> (raw)
In-Reply-To: <16905130930.52F6E.13899@lsd.chicago.il.us>

On 7/27/23 21:58, Jay F. Shachter wrote:
> 
> Centuries ago, Nostradamus predicted that Jacob Moody would write on Thu Jul 27 16:53:52 2023:
> 
>>
>> 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.
>> But in your previous mails you mentioned installing 9front in MBR
>> mode.
>>
> 
> It is an MBR-partitioned disk.  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.
> 
>>
>> Can you give me an entire explanation of how your disk is
>> configured?
>>
> 
> 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).  FreeDOS 1.3 resides on the third primary
> slice because it is practically impossible to get FreeDOS to work
> anywhere but on a primary slice.  Everything else resides on logical
> slices within the extended slice.  The two Linux systems reside on a
> single logical slice, which constitutes a volume group from which
> Linux logical volumes can be carved out.  The other operating systems
> each occupies a separate logical slice.  9front is on slice #14.  The
> MBR boots Linux GRUB.  There is also a backup copy of the Linux GRUB
> MBR on slice #10.  There is a backup copy of the Solaris GRUB MBR on
> slice #13.
> 
> 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.  I am bypassing the 9front
> bootloader; GRUB is booting /9pc64 directly.  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=glenda
> option that keeps me from having to type Enter to confirm that I am
> glenda)?  Thank you in advance for any and all replies.
> 
>                         Jay F. Shachter
>                         6424 North Whipple Street
>                         Chicago IL  60645-4111
>                                 (1-773)7613784   landline
>                                 (1-410)9964737   GoogleVoice
>                                 jay@m5.chicago.il.us
>                                 http://m5.chicago.il.us
> 
>                         "Quidquid latine dictum sit, altum videtur"
> 


For non prompted booting you can change 'bootargs' to 'nobootprompt'.
If you also add a 'user=glenda', that will prevent it from asking you
for that as well.

      parent reply	other threads:[~2023-07-28  5:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  2:58 Jay F. Shachter
2023-07-28  3:18 ` B. Atticus Grobe
2023-07-28  3:42   ` qwx
2023-07-28 10:58     ` grobe0ba
2023-07-28  3:21 ` Stanley Lieber
2023-07-28  5:07 ` Jacob Moody [this message]

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=8807ea01-47b6-085f-9ffb-9657a2431130@posixcafe.org \
    --to=moody@posixcafe.org \
    --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).