Re: [9fans] 9front on raspberry pi

[Chris McGee]

Apologies Richard for misspelling your last name.

Chris

> On Nov 1, 2016, at 9:35 PM, Chris McGee  wrote:
> 
> Hi All,
> 
> I have released an experimental 9front raspberry pi image that I use for my 
> cluster.
> https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
> 
> Highlights:
> -Latest 9front release 2016-10-27
> -Merged in Richard Millar’s kernel from a couple of months ago
> -Retains 9front GPIO filesystem structure
> -Link local ipv4 address on boot (low likelihood of collisions)
> -Discovery of other nodes using multicast DNS through the ‘find9p’ command
> -9fs mount other nodes on the network
> -Go 1.7.3
> -Git script (works with github and google source repos)
> 
> Cheers,
> Chris

Re: [9fans] Fossil+Venti system memory requirements to be aware of?

[Steven Stallion]

Hi Jim,

It's important to point out that the arena size does not have to match
the size of an arenas file. In my case, I do something similar where I
use 2GB for an arena but keep my arenas files at 2GB (I don't have
much use for keeping multiple arena files).

More indexes help to an extent. My fs isn't under exceptionally heavy
load, but I've found that 2 seem to work out nicely for my
configuration.

Steve

On Wed, Nov 2, 2016 at 1:44 PM, James A. Robinson  wrote:
> On Wed, Oct 19, 2016 at 9:47 AM Steven Stallion  wrote:
>> In short, start small and grow as needed. For reference, when I ran
>> Coraid's fs based on 64-bit Ken's (WORM only, no dedupe) in RWC
>> (based on the main fs in Athens). Over the course of a few years
>> the entire WORM grew to around 35GB. This was for a couple dozen
>> people working full time. I believe I had the LUN configured to
>> something rather large at the time - around 12TB. All wasted space.
>
> Hi,
>
> So if you were setting up a new filesystem for the same group, and
> were using venti, would you be using the default 500 mb arena size
> (meaning 70+ arenas), or would you be sizing them at a larger size,
> like 1 gb, 2 gb, etc?
>
> The "setting up venti" page indicates that multiple small disks
> help with performance on venti due to using more indexes, but I
> can't tell if that translates to more partitions (e.g., 1 RAID 1+0
> disk split into multiple smaller partitions, and divvied up into
> isectX and arenaX drives).  I guess it probably comes down to
> how well (or poorly) the underlying disk array performs at random
> read/write ops.
>
> I see that AWS S3 allows for up to 5 gb in a single PUT, or 5 tb
> using multipart streams, and am thinking that using 1 to 5 gb
> arenas might make sense as a more modern "sized for for easy
> offline backup" default.
>
> Jim
>

Re: [9fans] Fossil+Venti system memory requirements to be aware of?

[James A. Robinson]

On Wed, Oct 19, 2016 at 9:47 AM Steven Stallion  wrote:
> In short, start small and grow as needed. For reference, when I ran
> Coraid's fs based on 64-bit Ken's (WORM only, no dedupe) in RWC
> (based on the main fs in Athens). Over the course of a few years
> the entire WORM grew to around 35GB. This was for a couple dozen
> people working full time. I believe I had the LUN configured to
> something rather large at the time - around 12TB. All wasted space.

Hi,

So if you were setting up a new filesystem for the same group, and
were using venti, would you be using the default 500 mb arena size
(meaning 70+ arenas), or would you be sizing them at a larger size,
like 1 gb, 2 gb, etc?

The "setting up venti" page indicates that multiple small disks
help with performance on venti due to using more indexes, but I
can't tell if that translates to more partitions (e.g., 1 RAID 1+0
disk split into multiple smaller partitions, and divvied up into
isectX and arenaX drives).  I guess it probably comes down to
how well (or poorly) the underlying disk array performs at random
read/write ops.

I see that AWS S3 allows for up to 5 gb in a single PUT, or 5 tb
using multipart streams, and am thinking that using 1 to 5 gb
arenas might make sense as a more modern "sized for for easy
offline backup" default.

Jim

Re: [9fans] 9front on raspberry pi

[Steve Simon]

Hi all,

anyone seen some strange TLS issues (when talking to windows boxen).

tlsClient: devtls expected ver=301, saw (len=19232) type=2a ver=204f '* 
OK ����'

This is running Richard millers raspberry kernel so no 9front encryption fixes.
maybe my TLS needs to be taught more smarts?

-Steve

Re: [9fans] 9front on raspberry pi

[Chris McGee]

Thanks,

I'm thinking that could be related to USB problem making the mouse jump around.

Chris

> On Nov 2, 2016, at 8:05 AM, arisawa  wrote:
> 
> hello Chris,
> 
>> 2016/11/02 20:17、Chris McGee  のメール：
>> 
>> What's wrong with the large display?
> 
> the display size is 1920x1200.
> when I try to resize a window, the mouse cursor flips and it is difficult to 
> resize.
> 
> 

Re: [9fans] 9front on raspberry pi

[arisawa]

hello Chris,

> 2016/11/02 20:17、Chris McGee  のメール：
> 
> What's wrong with the large display?

the display size is 1920x1200.
when I try to resize a window, the mouse cursor flips and it is difficult to 
resize.

Re: [9fans] 9front on raspberry pi

[Chris McGee]

> but something weird.
> term% mount -a '#G' /dev
> mount: can’t open '#G': permission denied
> I don’t know the reason.

Maybe you want to use bind instead?

> 
> using large display is frustrating...
> my portable HDMI display of 1280x800 works fine.
> 

What's wrong with the large display?

Re: [9fans] 9front on raspberry pi

[arisawa]

sorry 

> mount -a '#G' /dev
shoud be
bind -a '#G' /dev

> 2016/11/02 19:47、arisawa  のメール：
> 
> hi steve
> 
>> 2016/11/02 16:57、Steve Simon  のメール：
>> 
>> can you tell me what the gpio file system looks like
> 
> try
>   ls -l '#G'
> them you will find some files such as
>   #G/gpio/CE0
>   #G/gpio/CE1
>   #G/gpio/GPI00
>   #G/gpio/GPI01
>   ...
>   #G/gpio/ctl
>   #G/gpio/event
> but something weird.
> term% mount -a '#G' /dev
> mount: can’t open '#G': permission denied
> I don’t know the reason.
> 
> I haven’t tried GPIO nor mDNS yet, sorry.
> 
> using large display is frustrating...
> my portable HDMI display of 1280x800 works fine.
> 
> 

Re: [9fans] 9front on raspberry pi

[Chris McGee]

The GPIO doesn't have a manual page as far as I know. The implementation came 
from what is in 9front mainline and is in #G. I agree that it would be good to 
have a manual page for it there.

mDNS is running as bcast9p process and is written in Go. It's based on a Go 
library and uses udp multicast support for plan 9 that is only in latest git 
master branch, slated for Go 1.8.

Go SDK in this image is 1.7.3 though. It should be reasonably stable.

Chris

> On Nov 2, 2016, at 3:57 AM, Steve Simon  wrote:
> 
> hi,
> 
> this is interesting.
> 
> can you tell me what the gpio file system looks like (pointer to man page?). 
> also, is the mDNS client the go one discussed recently or a c implementation?
> 
> i have never go'ed and have been thinking about writing a upnp renderer for 
> plan9 for years...
> 
> -Steve
> 
> 
>> On 2 Nov 2016, at 07:48, arisawa  wrote:
>> 
>> I’ve tried both pi1 and pi2.
>> both devices successfully boot up.
>> 
>> my impression only in primitive usage is:
>> pi2 is fine. thanks Chris!
>> pi1 is a bit unsteady on usb device. usb keyboard is sometimes accidentally 
>> detached.
>> 
>> 
>>> 2016/11/02 14:05、arisawa  のメール：
>>> 
>>> thanks, i will try.
>>> 
>>> is this for pi1 or pi2 or both?
>>> 
 2016/11/02 10:35、Chris McGee  のメール：
 
 Hi All,
 
 I have released an experimental 9front raspberry pi image that I use for 
 my cluster.
 https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
 
 Highlights:
 -Latest 9front release 2016-10-27
 -Merged in Richard Millar’s kernel from a couple of months ago
 -Retains 9front GPIO filesystem structure
 -Link local ipv4 address on boot (low likelihood of collisions)
 -Discovery of other nodes using multicast DNS through the ‘find9p’ command
 -9fs mount other nodes on the network
 -Go 1.7.3
 -Git script (works with github and google source repos)
 
 Cheers,
 Chris
>>> 
>>> 
>> 
> 
> 

Re: [9fans] 9front on raspberry pi

[Chris McGee]

Thanks for trying it out. Can you raise a github issue with any error messages 
or data that I can use to try to fix the problem?

I understand that Richard's kernel that I used should work with Pi 1, 2 and 
zero. I have tried it with a Pi 1 B+ and Pi 2 B.

Sent from my iPhone
> On Nov 2, 2016, at 3:48 AM, arisawa  wrote:
> 
> I’ve tried both pi1 and pi2.
> both devices successfully boot up.
> 
> my impression only in primitive usage is:
> pi2 is fine. thanks Chris!
> pi1 is a bit unsteady on usb device. usb keyboard is sometimes accidentally 
> detached.
> 
> 
>> 2016/11/02 14:05、arisawa  のメール：
>> 
>> thanks, i will try.
>> 
>> is this for pi1 or pi2 or both?
>> 
>>> 2016/11/02 10:35、Chris McGee  のメール：
>>> 
>>> Hi All,
>>> 
>>> I have released an experimental 9front raspberry pi image that I use for my 
>>> cluster.
>>> https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
>>> 
>>> Highlights:
>>> -Latest 9front release 2016-10-27
>>> -Merged in Richard Millar’s kernel from a couple of months ago
>>> -Retains 9front GPIO filesystem structure
>>> -Link local ipv4 address on boot (low likelihood of collisions)
>>> -Discovery of other nodes using multicast DNS through the ‘find9p’ command
>>> -9fs mount other nodes on the network
>>> -Go 1.7.3
>>> -Git script (works with github and google source repos)
>>> 
>>> Cheers,
>>> Chris
>> 
>> 
> 
> 

Re: [9fans] 9front on raspberry pi

[arisawa]

hi steve

> 2016/11/02 16:57、Steve Simon  のメール：
> 
> can you tell me what the gpio file system looks like

try
ls -l '#G'
them you will find some files such as
#G/gpio/CE0
#G/gpio/CE1
#G/gpio/GPI00
#G/gpio/GPI01
...
#G/gpio/ctl
#G/gpio/event
but something weird.
term% mount -a '#G' /dev
mount: can’t open '#G': permission denied
I don’t know the reason.

I haven’t tried GPIO nor mDNS yet, sorry.

using large display is frustrating...
my portable HDMI display of 1280x800 works fine.

Re: [9fans] 9front on raspberry pi

[Steve Simon]

hi,

this is interesting.

can you tell me what the gpio file system looks like (pointer to man page?). 
also, is the mDNS client the go one discussed recently or a c implementation?

i have never go'ed and have been thinking about writing a upnp renderer for 
plan9 for years...

-Steve


> On 2 Nov 2016, at 07:48, arisawa  wrote:
> 
> I’ve tried both pi1 and pi2.
> both devices successfully boot up.
> 
> my impression only in primitive usage is:
> pi2 is fine. thanks Chris!
> pi1 is a bit unsteady on usb device. usb keyboard is sometimes accidentally 
> detached.
> 
> 
>> 2016/11/02 14:05、arisawa  のメール：
>> 
>> thanks, i will try.
>> 
>> is this for pi1 or pi2 or both?
>> 
>>> 2016/11/02 10:35、Chris McGee  のメール：
>>> 
>>> Hi All,
>>> 
>>> I have released an experimental 9front raspberry pi image that I use for my 
>>> cluster.
>>> https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
>>> 
>>> Highlights:
>>> -Latest 9front release 2016-10-27
>>> -Merged in Richard Millar’s kernel from a couple of months ago
>>> -Retains 9front GPIO filesystem structure
>>> -Link local ipv4 address on boot (low likelihood of collisions)
>>> -Discovery of other nodes using multicast DNS through the ‘find9p’ command
>>> -9fs mount other nodes on the network
>>> -Go 1.7.3
>>> -Git script (works with github and google source repos)
>>> 
>>> Cheers,
>>> Chris
>> 
>> 
> 

Re: [9fans] 9front on raspberry pi

[arisawa]

I’ve tried both pi1 and pi2.
both devices successfully boot up.

my impression only in primitive usage is:
pi2 is fine. thanks Chris!
pi1 is a bit unsteady on usb device. usb keyboard is sometimes accidentally 
detached.


> 2016/11/02 14:05、arisawa  のメール：
> 
> thanks, i will try.
> 
> is this for pi1 or pi2 or both?
> 
>> 2016/11/02 10:35、Chris McGee  のメール：
>> 
>> Hi All,
>> 
>> I have released an experimental 9front raspberry pi image that I use for my 
>> cluster.
>> https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
>> 
>> Highlights:
>> -Latest 9front release 2016-10-27
>> -Merged in Richard Millar’s kernel from a couple of months ago
>> -Retains 9front GPIO filesystem structure
>> -Link local ipv4 address on boot (low likelihood of collisions)
>> -Discovery of other nodes using multicast DNS through the ‘find9p’ command
>> -9fs mount other nodes on the network
>> -Go 1.7.3
>> -Git script (works with github and google source repos)
>> 
>> Cheers,
>> Chris
> 
>