From: "james palmer" <james@biobuf.link>
To: "9front mailing list" <9front@9front.org>
Subject: Re: [9front] cfs(4)
Date: Sat, 13 Feb 2021 00:30:00 +0000 [thread overview]
Message-ID: <f2475cf8-bc38-43ea-9ea0-7cef2d1f795c@www.fastmail.com> (raw)
In-Reply-To: <E45D2C90-5C45-4857-898C-0B97EA01FBD9@gmail.com>
Quoth meta.jxy@gmail.com:
> What is that ramdisk provides that ramfs does not?
> Is there any 9p protocol not implemented properly?
iirc ramfs dynamically allocates data for its files.
data that is all 0 is not stored in memory.
ramdisk reserves a section of memory and presents it as a disk device.
cfs seems to assume the ramfs file is of 0 size.
> Like I said, putting it in plan9.ini seems to work,
> but I can't figure out why running it manually does not.
> What am I supposed to do?
you are running it with -d. this enables debugging and keeps in in the foreground. it is not hung, it is waiting for a 9p connection.
next prev parent reply other threads:[~2021-02-13 0:36 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
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 [this message]
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=f2475cf8-bc38-43ea-9ea0-7cef2d1f795c@www.fastmail.com \
--to=james@biobuf.link \
--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).