From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <dcv90ps0tmt3179h9o0nitvg.1371953513705@email.android.com>
Date: Sun, 23 Jun 2013 15:19:10 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <21898635-2AC3-49BD-92CD-8FC19A0CF090@ar.aichi-u.ac.jp>
References: <dcv90ps0tmt3179h9o0nitvg.1371953513705@email.android.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] long filenames in cwfs
Topicbox-Message-UUID: 6725e00c-ead8-11e9-9d60-3106f5b1d025

thank you erik.

I forgot the existence of lnfs.
I will try your lnfs.

On 2013/06/23, at 11:11, Erik Quanstrom <quanstro@quanstro.net> wrote:

> Lnfs works fine.  Since fses vary in max length I modified it to take =
a max length parameter.  See the atom man pages.
>=20
> - erik
>=20
>=20
> arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>=20
>> Hello,
>>=20
>> importing files from outer world (mainly OSX or Win),  we are =
sometimes obliged to handle=20
>> long filenames.
>> fossil is no problem.
>> cwfs has limit of name length that is insufficient to handle these =
long names.
>> any idea?
>>=20
>> Kenji Arisawa
>>=20
>>=20
>>=20