From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Modifying FS (hjfs)
Date: Fri, 22 Jan 2021 15:49:53 -0800 [thread overview]
Message-ID: <CAHwi9bx3U+96AAFQtfKEG2i5U1mhhvaSHmn81=bqWGTB51ogPw@mail.gmail.com> (raw)
In-Reply-To: <20210122142211.58c69ee0@gmx.de>
> * creating cwfs there and using that, as above (seems as strange as the
> last)?
I set up for example a 256 GB microSD card as a (very slow...) cwfs,
by looking at how /sys/lib/dist/mkfile generates the pi release imgs,
and the scripts in /bin/inst
next prev parent reply other threads:[~2021-01-23 0:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 13:22 Eckard Brauer
2021-01-22 13:45 ` hiro
2021-01-22 16:24 ` Eckard Brauer
2021-01-22 16:56 ` Romano
2021-01-22 17:38 ` Eckard Brauer
2021-01-22 18:10 ` Romano
2021-01-22 18:42 ` [9front] Modifying FS (hjfs) (pi wifi) Steve Simon
2021-01-22 19:32 ` Lyndon Nerenberg
2021-01-23 14:24 ` cinap_lenrek
2021-01-22 23:49 ` Eli Cohen [this message]
2021-01-23 12:50 ` [9front] Modifying FS (hjfs) Eckard Brauer
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='CAHwi9bx3U+96AAFQtfKEG2i5U1mhhvaSHmn81=bqWGTB51ogPw@mail.gmail.com' \
--to=echoline@gmail.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).