From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] robust heterogenous home file server?
Date: Thu, 9 Aug 2007 15:58:43 +0200 [thread overview]
Message-ID: <200708091358.l79Dwha23305@zamenhof.cs.utwente.nl> (raw)
I'm finally producing data at home that I care about (DSLR, shooting RAW)
so I'm wondering how to construct a robust file server that allows
heterogenous access (windows, mac, linux, plan9), is affordable,
low-power, ideally low noise, low-maintenance (I like kenf) and preferably
can be built with little effort using of-the-shelf items.
robustness being the main criterion.
I've been looking at coraids products but they seem a bit high-endish...
something like that but then 'smaller' might be nice.
I'm unsure about plugging usb-drives into wireless access points
(what is apple's bonjour? open in any way?)
any thoughts, experiences? (does, don'ts?)
Axel.
next reply other threads:[~2007-08-09 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 13:58 Axel Belinfante [this message]
2007-08-09 14:10 ` Gabriel Diaz
2007-08-09 14:27 ` erik quanstrom
2007-08-09 15:38 ` Gabriel Diaz
2007-08-09 17:02 ` Lucio De Re
2007-08-09 17:20 ` erik quanstrom
2007-08-09 17:38 ` Lucio De Re
2007-08-09 17:42 ` erik quanstrom
2007-08-09 17:48 ` Lucio De Re
2007-08-09 14:26 ` Abhey Shah
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=200708091358.l79Dwha23305@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/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).