9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "qwx via 9fans" <9fans@9fans.net>
To: 9fans@9fans.net
Subject: Re: [9fans] I did bad things and 9front won't boot
Date: Thu, 21 Dec 2023 03:47:29 +0100	[thread overview]
Message-ID: <76887205CF95524760D1F01C9684C89A@migadu.com> (raw)
In-Reply-To: <C8EAAA67-95BE-4B81-8CE8-4F45989BCEA4@o5r.ca>

On Thu Dec 21 02:54:25 +0100 2023, o@o5r.ca wrote:
> Hello, 
> I seem to have done incredibly stupid things to my 9front instance and now on boot I get "panic: unknown keyword in config block: <some character>", followed by a "mount: sys: write on closed pipe pc=0x2008c6" and "mount /srv/boot /root: mount 185: sys: write on closed pipe pc=0x2008c6”.

What stupid things did you do to break it?

> Is there a way for me to rewrite the config block to sensible defaults by dropping into a shell and/or using a usb drive w/ 9front on it (as if doing an install) to just backstep whatever terrible thing I performed accidentally?
> Thanks,
> Olivier

Yes, see fqa 9.2.5 [1].  See also fsconfig(8) [2].  What you enter
here depends on your setup.

You may want to subscribe to the 9front mailing list [3] and ask
9front-specific questions there to get better help.


[1] http://fqa.9front.org/fqa9.html#9.2.5
[2] http://man.9front.org/8/fsconfig
[3] http://fqa.9front.org/fqa2.html#2.2

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T110553196be52532-M0b37e672735d00be2ed8c677
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-12-21  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  1:52 o
2023-12-21  2:47 ` qwx via 9fans [this message]
2023-12-21  2:56 ` ori
2023-12-21 11:00   ` Olivier Tremblay

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76887205CF95524760D1F01C9684C89A@migadu.com \
    --to=9fans@9fans.net \


* 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).