From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cfs(4)
Date: Thu, 11 Feb 2021 21:16:10 -0600 [thread overview]
Message-ID: <724AD21E-05BF-4ECD-B92B-3AF191CC77C2@gmail.com> (raw)
In-Reply-To: <6af5b5ea-c6d5-40f6-a22d-eb3b9f93f123@www.fastmail.com>
> On Feb 10, 2021, at 9:27 AM, james palmer <james@biobuf.link> wrote:
>
> Quoth sl@stanleylieber.com:
>> i'd like to document setting up cfs in the fqa. some questions:
>>
>> - can it use a file on fat volume, or a fat volume itself
> i'd guess that this would work fine seeing as it just takes a file as an argument.
>
>> - if not, what are the steps for creating a minimum viable cfs partition
> cfs will format the partition it is given. i use this to run cfs on a ramdisk.
I can't get it to work.
; ramfs
; dd -if /dev/zero -of /tmp/cache -bs 1m -count 32
32+0 records in
32+0 records out
; {cfs -s -dS -f /tmp/cache </srv/office &} | echo 0 >/srv/office.c
; dinit: bsize 0x0<= 0
formatting disk
formatting inodes
; mount /srv/office.c /mnt/office.c
<-client: Tversion tag 65535 msize 8216 version '9P2000'
->server: Tversion tag 65535 msize 8216 version '9P2000'
cfs: sendmsg
mount: sys: write on closed pipe pc=0x2008c6
directly use -F also does not work for me.
; dd -if /dev/zero -of /tmp/cache -bs 1m -count 32
32+0 records in
32+0 records out
; cfs -F /srv/office -dknS -f /tmp/cache /mnt/office.c
dinit: bsize 0x0<= 0
formatting disk
formatting inodes
<-client: Tversion tag 65535 msize 8216 version '9P2000'
->server: Tversion tag 65535 msize 8216 version '9P2000'
cfs: sendmsg
it seems to stuck there.
>
>> - how does cfs= in plan9.ini interact with tls booting
> works fine for me. i enter my secstore password, cfs is run, then init runs /bin/rc.
putting the line in plan9.ini seems to work for tls boot.
next prev parent reply other threads:[~2021-02-12 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 15:51 Stanley Lieber
2021-02-10 15:27 ` james palmer
2021-02-12 3:16 ` Xiao-Yong Jin [this message]
2021-02-12 7:30 ` Silas McCroskey
2021-02-12 8:34 ` james palmer
2021-02-12 19:50 ` Xiao-Yong Jin
2021-02-13 0:30 ` james palmer
2021-02-13 2:35 ` Xiao-Yong Jin
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=724AD21E-05BF-4ECD-B92B-3AF191CC77C2@gmail.com \
--to=meta.jxy@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).