[9fans] [kenfs] the mercurial repo problem

[Akshat Kumar]

Ah, sorry to double-post, but in order
to get this working, one must:

mkdir repo
hg init repo
cd repo; hg pull -u https://...
echo '[paths]
default = https://...' > .hg/hgrc

Because it is forbidden to directly
clone on a non-empty directory
(an lnfs mounted dir contains a
.longnames index file).


ak

On Thu, Feb 2, 2012 at 3:56 AM, Akshat Kumar

This is a problem perhaps two of us
have on Plan 9 (hi Erik): mercurial
repositories contain files with long
names and/or spaces.
I realised that `lnfs' is a neat solution
to this problem (though you have to
remember to run it each time you're
in the repo) for the time-being. In
particular, it doesn't hog up ram (the
way ramfs does... :), and it doesn't
rely on the repo .hg dir already being
there (the way hgfs does), which is
what usually contains the long names.
And we can use `unlnfs' to export.
Just for future reference -- I noticed that
this didn't come up when we last discussed
this issue.
As always -
BUGS
         This exists only to shame us into getting a real long name
         file server working.
(Yeah, yeah - fossilheads can SUCK EGGS :-)
Best,
ak

[erik quanstrom]

This is a problem perhaps two of us
have on Plan 9 (hi Erik): mercurial
repositories contain files with long
names and/or spaces.

coraid run's ken's file server. so a fair percentage
of plan 9 users run on that rather than fossil.

- erik