From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bakul Shah Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Sun, 2 Sep 2018 10:03:08 -0700 Message-Id: References: <600987589.2057147.1535842278571.ref@mail.yahoo.com> <600987589.2057147.1535842278571@mail.yahoo.com> In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] 9P or better file services for multiple platforms Topicbox-Message-UUID: e021fee0-ead9-11e9-9d60-3106f5b1d025 > On Sep 2, 2018, at 2:25 AM, Lucio De Re wrote: >=20 > (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=E2=80=99t take all that long, using a previously compiled Go as the bootstrap compiler. I=E2=80=99m using 9front=E2=80=99s new filesys= tem, not fossil. The =E2=80=9Cdgit=E2=80=9D program (Dave McFarlane, with assists from Chris McGee) works well enough now for =E2=80=9Cgo get=E2=80=9D or =E2=80=9Cgit pu= ll=E2=80=9D. 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.=