From: "Jay F. Shachter" <jay@m5.chicago.il.us>
To: 9front@9front.org
Subject: [9front] Followup: Hjfs Installation Fails With Infinitely-Repeated "file does not exist" Messages
Date: Wed, 26 Jul 2023 19:34:51 -0500 (EDT) [thread overview]
Message-ID: <16904180910.DB58e.90726@lsd.chicago.il.us> (raw)
Followup to my posting of a few minutes ago:
One thing that I had not yet tried, was to re-install and select the
"experimental" hjfs filesystem. Don't even try doing that, because it
will break your heart. The installation fails at a very early stage,
with infinitely-repeated messages of
% mount -c /srv/hjfs.newfs /n/newfs
mount: can't open /srv/hjfs.newfs: '/srv/hjfs.newfs' file does not exist
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"
next reply other threads:[~2023-07-27 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 0:34 Jay F. Shachter [this message]
2023-07-27 0:44 ` Jacob Moody
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=16904180910.DB58e.90726@lsd.chicago.il.us \
--to=jay@m5.chicago.il.us \
--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).