From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat,  6 Dec 2014 23:25:09 -0800
To: 9fans@9fans.net
Message-ID: <808dc99f6576d2e2a5c55906ab133b34@lilly.quanstro.net>
In-Reply-To: <1417929610.3339668.199764105.54122796@webmail.messagingengine.com>
References: <1417446698.1746961.197334701.394E4D52@webmail.messagingengine.com>
	<48AC91DA-BAA7-4419-BCDC-7E1D05D96065@9srv.net>
	<1417929610.3339668.199764105.54122796@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] golang on 9atom
Topicbox-Message-UUID: 3588acd6-ead9-11e9-9d60-3106f5b1d025

On Sat Dec  6 21:18:18 PST 2014, ram@rkrishnan.org wrote:
> On Wed, Dec 3, 2014, at 06:21 PM, Anthony Sorace wrote:
> > The error is what it says: the file name (rather than the full path) is
> > too long for your file server. It sounds like you're running kfs, which
> > is the oldest and most restricted of our general purpose options.
> > Long-term, I suggest migrating, although if you're on a single-system
> > setup and already have data you care about, that can be a pain. In the
> > short-term, check out lnfs(4) to get around this issue.
>
> Thank you. Didn't know about lnfs and the kfs limitations. I wonder, why
> then is the kfs, the default for 9atom. I see a fossil option while
> installation as an experimental option. Will try that out.

one is expected to use the initial install to provision
a well-configured system.  the intial install can also serve
as a rescue image.  it's not intended as a long term solution.
i use ken's file server.

- erik