9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] "init: starting /bin/rc" repeats endlessly when I boot a computer installed from 9front-9931.amd64.iso
Date: Fri, 21 Jul 2023 09:50:49 +0200	[thread overview]
Message-ID: <CAC7E5A897BA7570C98EB913CCC796DD@wopr.sciops.net> (raw)
In-Reply-To: <16899169930.eD0eB387.99539@lsd.chicago.il.us>

Hi,

I'm not sure I understand what you did in the second part of your
email, you were trying to reinstall 9front by booting the usb or cd
and that failed?

> [...] I type Enter again and then see:
> 
>    current fs is "main"
>    10 uids read, 3 groups used
>    63-bit cwfs as of Sun Jun 25 10:07:41 2023
>            last boot Thu Jul 20 20:54:23 2023
> 
>    init: starting /bin/rc
> 
>    init: starting /bin/rc
> 
>    init: starting /bin/rc
> 
>    init: starting /bin/rc
> 
>    init: starting /bin/rc
> 
>    init: starting /bin/rc
> 
> repeated endlessly.

For the first part, no, 5gb is not enough if you use cwfs, which by
default splits the partition into 3 slices for cache, worm and other.
Read the documentation on cwfs to know why.  I suspect a borked
installation just because of this.  Either use 10gb or more or switch
to hjfs.  Even 10gb isn't a lot, the worm will fill up quickly.


> I then see something being counted very quickly, then I see
> 
>     Plan 9
> 
> and then a bunch of other stuff that flies off the screen, culminating
> in the list of devices that you saw earlier, and then:
> 
>     bootargs is (tcp, tls, il, local!device)[local!/dev/sdE1/data]

For the second part, look at bootargs: you have local!/dev/sdE1/data
selected by default, which corresponds to the dvd drive.  Make sure
that the right entry is specified, if the usb drive is inserted, you
should have a /dev/sdU…/data in the list and you should set bootargs
to local!/dev/sdU…/data if it isn't set automatically.  I figure the
I/O read error you get is just because it can't read anything there.

Hope this helps,

Cheers,
qwx

  reply	other threads:[~2023-07-21  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  5:23 Jay F. Shachter
2023-07-21  7:50 ` qwx [this message]
2023-07-21 15:11   ` Jay F. Shachter
2023-07-21 15:20     ` Jacob Moody
2023-07-21 15:30     ` Dave Woodman

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=CAC7E5A897BA7570C98EB913CCC796DD@wopr.sciops.net \
    --to=qwx@sciops.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).