9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.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: Sun,  2 Sep 2018 10:03:08 -0700	[thread overview]
Message-ID: <D2CBCC24-9B42-4EBF-B6AC-B6F48F65F27D@bitblocks.com> (raw)
In-Reply-To: <CAJQ9t7iBcRg-FPH7Kr5nGX+uA=ZF+4tknb_9qqDyyX4i1KXnjw@mail.gmail.com>



> On Sep 2, 2018, at 2:25 AM, Lucio De Re <lucio.dere@gmail.com> wrote:
> 
> (GIT is the main reason for my begging here: I "pull" the latest Go to
> my workstation, then "archive" to Plan 9 (fossil). But fossil is slow,
> too slow to compete even with cross-compiling to plan9_386. Part of
> the problem is needing to flush the "archive" target in case bits have
> been removed and "export" does not delete them on the target - that
> works well, though, with fresh releases, like go1.11, of late. To be
> honest, I have the slack to use Plan 9 on a low-powered
> server/workstation combination and even cross-produce Linux-64
> executables for production; but building the Go distribution isn't
> really worth the trouble - I make a special effort to do that, not
> often enough.)

I now run 9front on FreeBSD under bhyve on a 10 year old
athlon64 machine. Initially I cross compiled go but now a native
compile doesn’t take all that long, using a previously compiled
Go as the bootstrap compiler. I’m using 9front’s new filesystem,
not fossil.

The “dgit” program (Dave McFarlane, with assists from Chris
McGee) works well enough now for “go get” or “git pull”.

I too want a unified filesystem that all my machines feed off of but
so far I have not found a solution. Local file systems are still faster.



  reply	other threads:[~2018-09-02 17:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2018-09-02 13:33 cinap_lenrek
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=D2CBCC24-9B42-4EBF-B6AC-B6F48F65F27D@bitblocks.com \
    --to=bakul@bitblocks.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).