From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] cwfs and hjfs
Date: Wed, 27 Aug 2014 09:57:20 +0900 [thread overview]
Message-ID: <bbea514b2df0ce6d9d2c759ec688ee1d@saturn.jitaku.localdomain> (raw)
In-Reply-To: <4d70f8b91dbc85a44c6106251cb98ec8@xx230.inri>
Thanks sl
> than hjfs with it's 4KB blocks and single partition. At 4GB you may run out
> of space fairly quickly after rebuilding the system and periodic dumps are
> taken into account.
Now I got why 9front people use hjfs instead of cwfs for 9pi.
> It also seems unlikely that file system speed is really your bottleneck. I used
> the rpi tcp booted (no local disk access after boot) and experienced similar
> problems. The USB ethernet seems to tax the system severely: when the network
> was active I routinely experienced dropouts in typing on my USB keyboard. This
> could also be related to voltage.
Yes, when I use root from tcp, many things got better.
Richard's rpi has the option of ipconfig='....' in cmdline.txt,
but 9front-9pi doesn't. I had to use termrc.local to setup ipconfig line.
This means two versions have some diference in the firmware?
> For what it's worth, the cat-v.org sites run on hjfs (at ramnode.com, KVM
> backed by an SSD).
The reason why I tried 9front-rpi instead of original one is that I cannot cpu
from the original to our 9ront cpu machine. This is neccessary to read pdf
files on the 9pi terminal.☺
Kenji
next prev parent reply other threads:[~2014-08-27 0:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 16:03 sl
2014-08-26 16:34 ` hiro
2014-08-27 1:01 ` kokamoto
2014-08-27 1:07 ` kokamoto
2014-08-27 0:57 ` kokamoto [this message]
2014-08-27 1:26 ` kokamoto
2014-08-27 6:30 ` kokamoto
2014-08-27 7:03 ` cinap_lenrek
2014-08-27 9:46 ` kokamoto
2014-08-27 10:10 ` cinap_lenrek
2014-08-27 23:37 ` kokamoto
2014-08-28 8:27 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2014-08-25 3:33 kokamoto
2014-08-25 8:32 ` [9front] " dante
2014-08-25 23:20 ` kokamoto
2014-08-26 6:35 ` kokamoto
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=bbea514b2df0ce6d9d2c759ec688ee1d@saturn.jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--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).