From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] suggestion for a domestic 9front fs
Date: Sat, 03 Jul 2021 21:55:58 -0700 [thread overview]
Message-ID: <751AB701E501497C357EA0A134B326B7@smtp.pobox.com> (raw)
In-Reply-To: <F40864C0CA5FCF8FF6F78B0427532C0B@felloff.net>
Quoting cinap_lenrek@felloff.net:
> > A domestic 9front fileserver can be anything from a RPI, to a racked
> > server, including a laptop in a closet, or a virtual machine.
>
> i'd like to challenge that. raspberry pi's are anything BUT a good
> fileservers. for one, it has no sata nor pcie slot for nvme.
> so you'r limited to usb.
>
> the only raspberry pi with a not completely useless usb implementation
> is the pi4 (also the only model that has a built in ethernet mac instead
> of some horrible usb contraption).
>
> the raspberry pi is a machine with lots of compromises.
> really, it is a graphics card with a arm processor on the side.
>
> and imho it is not really worth it spending alot of money working around
> its limitations with adding expensive external gadgets that will add up
> to more than the machine itself.
>
> especially usb disk adapters can cause you problems...
What cinap wrote has been my experience. I wanted to get onto some
real hardware, and thought the pi4 would be a good start. I did learn
quite a bit and still have 9front running on it, but I came up against
two things that I really wanted to use it for that currently aren't
available on 9front:
* wifi support
* virtualization
Wifi I think is supported in rmiller's port, but then you don't get
the benefit of a lot more software (if you're not running separate
cpu/auth/fs).
prev parent reply other threads:[~2021-07-04 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 13:47 Maurizio Boriani
2021-06-29 16:46 ` Lorenzo Bivens
2021-06-29 17:50 ` Stanley Lieber
2021-06-29 18:41 ` Lorenzo Bivens
2021-07-01 10:20 ` Maurizio Boriani
2021-07-01 16:19 ` cinap_lenrek
2021-07-04 4:55 ` unobe [this message]
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=751AB701E501497C357EA0A134B326B7@smtp.pobox.com \
--to=unobe@cpan.org \
--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).