9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P or better file services for multiple platforms
Date: Sat,  1 Sep 2018 16:33:04 +0200	[thread overview]
Message-ID: <CAJQ9t7iWn2bhixQs7Z2JoCSOpZjEc9zZbOhrj5QoBLY6jejq8w@mail.gmail.com> (raw)
In-Reply-To: <02f5fc7d-bf68-4f91-ab82-6b79d6cebe99@posteo.net>

On 9/1/18, Emery Hemingway <ehmry@posteo.net> wrote:
> I don't think you can find better than u9fs for unix.
>
I tend to use that as a norm, but the backing Plan 9 server is kind of
in the wrong "key". OK for Plan 9, but too slow for Linux. Still, that
sounds like a warning that better that u9fs is not out there.

> I've tried to use diod once or twice, but it is some weird overengineered
> linux shit.
>
I quickly built it and deployed it on my Linux Mint (32-bit, 1.18.1 or
some such), and it builds OK, skips a lot of tests, but fails none. As
"root" the tests jam, that can't be good.

Trying it out, it fails to find "attach" and there is no clue where
that should come from. It did strike me as complex, but if it serves
an NFS filesystem, that is probably adequate.

I'll wait to pass judgement for after I have it actually serving
anything at all.

Thanks for your comments, in any case.

Lucio.

PS: I suppose the Plan 9 problem is that it is too many different
things to too many different people and it has yet to find one niche
purpose that it serves better than any other OS. It's a sad destiny,
really sad.



  reply	other threads:[~2018-09-01 14:33 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 [this message]
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
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=CAJQ9t7iWn2bhixQs7Z2JoCSOpZjEc9zZbOhrj5QoBLY6jejq8w@mail.gmail.com \
    --to=lucio.dere@gmail.com \
    --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).