From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gentoo as NAS
Date: Mon, 8 Feb 2021 00:59:24 +0100 [thread overview]
Message-ID: <YCB+3L+EX6N6dQ6/@kern> (raw)
In-Reply-To: <985250a2f96fc5242d21eeb53b5b45fd7329533f.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Am Fri, Feb 05, 2021 at 10:43:39AM -0600 schrieb Matt Connell (Gmail):
> On Fri, 2021-02-05 at 09:36 +0000, Michael wrote:
> > Wouldn't a binary distro, potentially purpose built as a NAS and/or HTPC
> > offering, make more sense? I don't see what advantage the maintenance burden
> > of a Gentoo system has to offer in this use case, other than repurposing with
> > little effort an existing Gentoo installation. :-/
>
> Running Gentoo on my home server makes the maintenance burden *lower*
> for me because I can use all the same tools I'm used to. Besides,
> portage is the pinnacle of package managers IMHO. Using a GNU+Linux
> system without USE flags and such feels like I'm stuck in a hallway,
> with someone else's idea of how software should be configured and
> deployed.
Coincidentally, my NAS is the only Gentoo system left in my menagerie. The
install base is much smaller than on a desktop, which keeps the package
graph to a manageable size (and with, it portage churning time). Every few
months I fire it up to store new movies or grab old ones to watch, and I do
a system update at the same time. That way I won’t lose all of my Gentoo-foo
over time.
I built it in a small cube-format server case and a server-grade mITX board,
and maxed it out with four drives, 6 TB each, plus a small system SSD. They
are used in a raid Z2 data pool, on top of LUKS-encrypted block devices.
This is out of pure paranoia in case I need to send a drive in for warranty.
Currently, I don’t use the system for anything else but media library. For
24/7 services I have a raspi. The power bill just isn’t worth it.
--
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.
Team work:
Everyone does what he wants, nobody does what he should, and all play along.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-02-07 23:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 18:04 [gentoo-user] Gentoo as NAS Raphael MD
2021-02-04 22:05 ` Michael Jones
2021-02-04 22:16 ` Neil Bothwick
2021-02-04 23:56 ` [gentoo-user] " Grant Edwards
2021-02-05 0:36 ` Michael Jones
2021-02-05 0:53 ` Grant Edwards
2021-02-05 1:06 ` Grant Edwards
2021-02-05 2:29 ` Scott Ellis
2021-02-05 3:34 ` Matt Connell (Gmail)
2021-02-05 9:36 ` Michael
2021-02-05 16:01 ` Grant Edwards
2021-02-05 16:43 ` Matt Connell (Gmail)
2021-02-07 23:59 ` Frank Steinmetzger [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=YCB+3L+EX6N6dQ6/@kern \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.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