From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: 9front@9front.org
Subject: Re: [9front] Re: 9front Boots Into "No Config" -- The Most Bizarre Error; Bypassing The Bootloader
Date: Thu, 27 Jul 2023 17:26:32 -0500 [thread overview]
Message-ID: <893ab0e4-ff59-6caa-5d9d-80154c025364@tcp80.org> (raw)
In-Reply-To: <16904938490.a94c1A.9077@lsd.chicago.il.us>
On 7/27/23 16:37, Jay F. Shachter wrote:
...
> The one thing I have not yet been able to do is eliminate the bootargs
> prompt. I want to invoke /9pc64 in such a way that it is told
> everything it needs to know in advance, and doesn't have to ask me
> anything. As you can tell from the kernel arguments in my GRUB
> menuitem, I tried to do that with the bootargs= argument, but it's
> not working, it still asks me to tell it the bootargs. How do I
> eliminate the bootargs prompt when I boot 9front? Thank you in
> advance for any and all replies.
man plan9.ini
as moody said, try this on a drive that isn't filled with stuff.
or run it in a vm. minus a (now patched) issue with hjfs in the
installer that has already been mentioned, the installer does the right
thing for a "supported" installation.
all these other hoops you're failing to jump through are of your own
invention. there is a reason no one does single-drive multiboot like
this, because it is not actually a supported configuration for any OS,
just one of those things that can _sometimes_ be made to work.
on the other hand, 9front and most modern operating systems run just
fine under qemu, virtualbox, vmware, vmd, and probably even hyperv and
don't require all of this ridiculous crap. 15 (or more?)
partitions/slices? this is just stupid. do stupid things, get stupid
results.
prev parent reply other threads:[~2023-07-27 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 21:37 Jay F. Shachter
2023-07-27 21:53 ` Jacob Moody
2023-07-27 22:26 ` B. Atticus Grobe [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=893ab0e4-ff59-6caa-5d9d-80154c025364@tcp80.org \
--to=grobe0ba@tcp80.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).