From: david larsson <david.larsson@selfhosted.xyz>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org,
Help-Guix <help-guix-bounces+someone=selfhosted.xyz@gnu.org>
Subject: Re: NAS hardware recommendations
Date: Wed, 09 Dec 2020 17:46:27 +0100 [thread overview]
Message-ID: <bce71c605f441a0411b0f73166161550@selfhosted.xyz> (raw)
In-Reply-To: <87im9cgutb.fsf@ambrevar.xyz>
On 2020-12-08 16:51, Pierre Neidhardt wrote:
> Hi Guix!
>
> Has anyone had luck installing Guix on a NAS?
> If so, which one?
>
> If not, which NAS hardware would you recommend?
> I'm looking for
>
> - something as open as possible;
> - 3-4 bays;
> - lowest consumption possible;
> - Btrfs support.
>
> Any tips?
>
> Cheers!
Ive always wanted a GnuBee which is very open. Idle power is 11.64 W.
There is both a 3.5" and 2.5" version - it has a MIPS processor though.
Also, I don't know if you can actually still order them anywhere:
https://www.crowdsupply.com/gnubee/personal-cloud-1
Guix has some old support for installing on MIPS:
https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00500.html
Otherwise, the very open Vikings D8, has 6 SATA 300mb/s slots, but
perhaps not really what you are looking for and it's pretty expensive.
https://store.vikings.net/libre-friendly-hardware/d8ryf
Best regards,
David
next prev parent reply other threads:[~2020-12-09 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 15:51 NAS hardware recommendations Pierre Neidhardt
2020-12-09 16:46 ` david larsson [this message]
2020-12-10 10:47 ` zloster
2020-12-10 14:43 ` Pierre Neidhardt
2020-12-11 15:32 ` zloster
2020-12-12 17:26 ` Pierre Neidhardt
2020-12-12 19:21 ` Efraim Flashner
2020-12-12 19:51 ` Pierre Neidhardt
2020-12-13 6:37 ` Efraim Flashner
2020-12-15 16:38 ` zloster
2020-12-19 10:21 ` Pierre Neidhardt
2020-12-20 10:26 ` Dr. Arne Babenhauserheide
2020-12-10 11:53 ` zimoun
2020-12-10 14:41 ` Pierre Neidhardt
2020-12-10 20:57 ` david larsson
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=bce71c605f441a0411b0f73166161550@selfhosted.xyz \
--to=david.larsson@selfhosted.xyz \
--cc=help-guix-bounces+someone=selfhosted.xyz@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.