From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] 9P or better file services for multiple platforms
Date: Sun, 2 Sep 2018 18:44:00 +0100 [thread overview]
Message-ID: <1535910240.3778367.1494266984.4C7B2E47@webmail.messagingengine.com> (raw)
In-Reply-To: <CAJQ9t7gZN9pwtyzzzgq2hwLYKPsuMtKWPbf3Swzq2FBCwKYPhw@mail.gmail.com>
I had a thought pertaining to the original topic.
On Sat, Sep 1, 2018, at 6:21 AM, Lucio De Re wrote:
> The question, then, is what file service will satisfy these needs,
> including access control, automatic backup as provided by default
> under Plan 9, etc. I am not very fond of Linux's propensity to need
> daily upgrades, but Plan 9 has quirks of its own, which I would be
> hard pressed to enumerate here, but we are all aware of.
>
> If I could run the file server on a modern (or even an ancient)
> version of NetBSD, I'd be even happier as NetBSD is the Unix flavour I
> highly favour. But that is a bonus, not an essential.
Regarding the automatic backup, FreeBSD's UFS (the default filesystem) provides snapshots much like CWFS's dump. I think you can enable it for the whole filesystem with a mount option, but if not, I think it's quite easy to set up anyway.
FreeBSD has ZFS too, which of course offers snapshots, but it has so many options that I found it a bit too much. It seems well documented and the interface seems reasonable for the feature set, but it's a big feature set. I have a habit of trying to understand and use too much at once, I guess.
next prev parent reply other threads:[~2018-09-02 17:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 5:21 Lucio De Re
2018-09-01 10:29 ` Rui Carmo
2018-09-01 13:33 ` Lucio De Re
2018-09-01 14:03 ` Emery Hemingway
2018-09-01 14:33 ` Lucio De Re
2018-09-01 14:49 ` Lucio De Re
2018-09-01 18:00 ` Joseph Stewart
2018-09-02 11:14 ` Lucio De Re
2018-09-02 11:24 ` hiro
2018-09-02 11:30 ` hiro
2018-09-02 12:01 ` Lucio De Re
2018-09-02 12:16 ` hiro
2018-09-02 12:22 ` hiro
2018-09-02 17:51 ` Lucio De Re
2018-09-02 18:00 ` hiro
2018-09-02 18:07 ` hiro
2018-09-02 11:43 ` Lucio De Re
2018-09-02 11:48 ` Lucio De Re
2018-09-02 12:07 ` hiro
2018-09-03 4:03 ` Lucio De Re
2018-09-01 18:32 ` Ethan Gardener
2018-09-01 20:33 ` hiro
2018-09-02 11:22 ` Lucio De Re
2018-09-02 11:25 ` Lucio De Re
2018-09-02 11:32 ` hiro
2018-09-02 17:44 ` Ethan Gardener [this message]
2018-09-02 18:02 ` Lucio De Re
2018-09-02 18:19 ` Ethan Gardener
2018-09-02 18:24 ` Lucio De Re
2018-09-02 18:55 ` Ethan Gardener
2018-09-02 17:47 ` Skip Tavakkolian
2018-09-02 17:55 ` Lucio De Re
2018-09-02 18:09 ` Lucio De Re
2018-09-02 23:22 ` Kurt H Maier
2018-09-03 3:22 ` Lucio De Re
[not found] <600987589.2057147.1535842278571.ref@mail.yahoo.com>
2018-09-01 22:51 ` Brian L. Stuart
2018-09-02 9:25 ` Lucio De Re
2018-09-02 17:03 ` Bakul Shah
2018-09-02 13:33 cinap_lenrek
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=1535910240.3778367.1494266984.4C7B2E47@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).