From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: [9front] Re: [9front] reform hjfs file creation broken in current release and after
Date: Tue, 04 Jul 2023 16:24:08 -0400 [thread overview]
Message-ID: <19324C57-6024-44E1-9F78-F5564055B6BB@stanleylieber.com> (raw)
In-Reply-To: <11915E3A5BF56A2E9E17F4E72C0117E9@ftrv.se>
On July 4, 2023 3:46:13 PM EDT, "Sigrid Solveig Haflínudóttir" <sigrid@ftrv.se> wrote:
>I tried hjfs built with 7c with the last change to it (the C compiler) reverted and it seems to work fine. *With* it, hjfs can't properly initialize the filesystem - it's empty, not even /adm/users is there. I think that would explain the error. I will ping cinap as soon as he's on IRC.
>
this might have been easily overlooked if everybody was working with fully installed systems on cwfs. i started with the stock reform live image (hjfs) from the current release, and it booted fine, but no new files could be created.
next: after rebuilding the kernel with current sources, ether0=type=iwl in plan9.ini seems to have no effect. firmware iwn-6005 is located, loaded, and recognized with no errors, but ether0 is still the built-in ethernet. i'll try again once i have the whole system fully updated.
sl
next prev parent reply other threads:[~2023-07-04 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 4:51 Stanley Lieber
2023-07-04 13:26 ` Sigrid Solveig Haflínudóttir
2023-07-04 19:07 ` sl
2023-07-04 19:46 ` Sigrid Solveig Haflínudóttir
2023-07-04 20:18 ` [9front] " Stanley Lieber
2023-07-04 20:24 ` Stanley Lieber [this message]
2023-07-04 21:13 ` cinap_lenrek
2023-07-04 21:30 ` sl
2023-07-05 0:02 ` cinap_lenrek
2023-07-05 2:26 ` sl
2023-07-05 10:57 ` cinap_lenrek
2023-07-05 11:21 ` cinap_lenrek
2023-07-05 14:05 ` [9front] " Stanley Lieber
2023-07-06 7:05 ` cinap_lenrek
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=19324C57-6024-44E1-9F78-F5564055B6BB@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).