9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fazlul Shahriar <fshahriar@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] authoritative source for u9fs?
Date: Fri, 22 Jan 2021 03:20:03 -0500	[thread overview]
Message-ID: <CAA2CNPbtUhGbqdn+J_T8nuBNMt_fsMn3eAnW_iXYpm14=sqYAg@mail.gmail.com> (raw)
In-Reply-To: <20210122.010137.1211309442562667039.dworkin@weaselfish.com>

Actually, I only know of one u9fs that is being maintained:
https://bitbucket.org/plan9-from-bell-labs/u9fs/src/master/
I think most of the others you may find on github are (outdated)
mirror of this one.

On Fri, Jan 22, 2021 at 3:02 AM Dworkin Muller <dlm-9fans@weaselfish.com> wrote:
> 
> My initial installation/playing with Plan 9 was, surprisingly enough,
> using the basic Plan 9 ISO from 9p.io.  That image (and the resulting
> installed system's /sys/src) has a handful of useful interoperability
> bits to run on Unix, including u9fs.  Now I've working with 9front,
> which is being less frustrating in at least a few respects.  However,
> it no longer has those Unix-related bits.  Doing a web search for
> "u9fs server" comes up with a lot of different places claiming to have
> it, but they don't appear to all have exactly the same thing, and I'm
> generally reluctant to use a package from other than its true home or
> a mirror listed at said true home.
> 
> Thus, the question is, what is considered to be the location of the
> source for u9fs?
> 
> I have a funny feeling the answer's going to be ``well, it depends on
> which variant of u9fs you want''.... :-)
> 
> Thanks.
> 
> Dworkin

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tee2220301f2a891c-Mce5f51c865d65f16cb30bb66
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-01-22  8:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  8:01 Dworkin Muller
2021-01-22  8:20 ` Fazlul Shahriar [this message]
2021-01-22  9:15   ` Dworkin Muller
2021-01-22  9:36     ` Steve Simon
2021-01-24 23:30     ` Charles Forsyth
2021-01-24 23:34       ` Charles Forsyth
2021-01-25  0:10         ` Lyndon Nerenberg
2021-01-25  0:14           ` Charles Forsyth
2021-01-25  6:33           ` ori
2021-01-25  5:10       ` Lucio De Re
2021-01-25  5:52         ` Dworkin Muller
2021-01-27 16:23         ` Ethan Gardener
2021-01-27 18:49           ` Lucio De Re

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='CAA2CNPbtUhGbqdn+J_T8nuBNMt_fsMn3eAnW_iXYpm14=sqYAg@mail.gmail.com' \
    --to=fshahriar@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).