public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  homemade nas setup
Date: Fri, 30 Jan 2009 12:56:48 +0100	[thread overview]
Message-ID: <4982EB00.2010309@smash-net.org> (raw)
In-Reply-To: <87y6wtlksy.fsf@newsguy.com>

Harry Putnam schrieb:
> A few I can think of are space and noise.. but having never been
> around our run a nas setup... I'm not sure if that is really true.
>
> Anyway, a few thoughts on what I might be running into doing it myself,
> or missing compared to storebought.  Maybe maintenance
> considerations.. or whatever, would be welcome.
>
>   

I am running my old AthlonXP system with 2 gig ram, a minimal
installation on a small extra disk, 3 disks for data as raid 5 and some
crypto, as a home nas. The system is build from spare parts except the
data disks and a small sata controller, which i had to buy. The old
miditower resides in a lumber-room under a shelf. So noise and space is
no problem. Of course you could build such a system in a smaller case.

The system only runs nfs, samba and a cups server. I do not use some
fancy guis or anything like that. So settings have to be made in the
config files manualy, except the cupsd which brings a web gui. Maybe
that is something some people would miss. But i do not think a gentoo
user would care.

As maintainence i do ,beside the regular emerge --sync and updates, a
raidcheck every weekend, but that can be cronjobed of course.

One point i feel mentionable is scalability. You buy a home nas with two
disks and you are stuck with that two disks because the case can not
handle more than that. Your do-it-yourself nas can do that.
It is a point of personal liking i think. I mean, you buy a home nas
click 5 minutes in the gui an you are done. Selfmade nas needs
understanding of the system, setting the whole thing up and some
configfile changes every now and then.

Regards
Norman



  parent reply	other threads:[~2009-01-30 11:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  0:06 [gentoo-user] homemade nas setup Harry Putnam
2009-01-30  0:44 ` Matt Harrison
2009-01-31  1:29   ` [gentoo-user] " Harry Putnam
2009-01-31  8:36     ` Matt Harrison
2009-01-31 15:37       ` Harry Putnam
2009-01-31 16:05         ` Matt Harrison
2009-01-30 10:43 ` [gentoo-user] " Peter Humphrey
2009-01-30 18:30   ` [gentoo-user] " Harry Putnam
2009-01-31 11:39     ` Peter Humphrey
2009-01-30 11:56 ` Norman Rieß [this message]
2009-01-30 12:05   ` [gentoo-user] " Neil Bothwick
2009-01-30 18:33   ` [gentoo-user] " Harry Putnam
2009-01-30 22:48     ` Norman Rieß
2009-01-30 23:24       ` Harry Putnam
2009-01-31 11:22         ` Norman Rieß
2009-01-30 23:39     ` Stroller
2009-01-30 23:00 ` [gentoo-user] " Stroller

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=4982EB00.2010309@smash-net.org \
    --to=norman@smash-net.org \
    --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