maybe the plan9-theme-for-unix projects have a solution?
if you have a patch that isnt too disruptive (removing troff
doesnt count) i'd be willing to commit it but i'm not undergoing
the work to puzzle arround with macosx problems.
--
cinap
thats a good one. this is not a problem with the repository. this
is a problem with this troff compontent assuming a case sensitive
filesystem. i cant fix it without changing troff. also, this isnt
the only case. i can't for example check out on windows because
we have /bin/aux and aux is a special
Quoting Yoann Padioleau :
Hi cinap,
Would it be possible to change a bit the 9front mercurial repository so that
it can work on MacOS filesystem.
I get some:
abort: case-folding collision between
sys/lib/troff/font/devutf/charlib/lH and
sys/lib/troff/font/devutf/charlib/LH
when hg pull;
On Mon, 09 Jun 2014 17:15:39 PDT "Brian L. Stuart"
wrote:
> > With the trick I am talking about, there is nothing to stop
> > you from connecting to N different remote ventis.=A0 In effect
> > your local (by that I mean under your control, not necessarily
> > on the same machine) venti can be tre
while you'r at it. take a look at 9front imageattach() code.
it allows the chan attached to the image to be released when the
image is not in use. this avoids all these chans and mounts
being kept arround until the image is reclaimed. the problem
is worked arround in iostats by killing the filesyst
On Mon Jun 9 04:25:00 EDT 2014, charles.fors...@gmail.com wrote:
> On 8 June 2014 19:37, Charles Forsyth wrote:
>
> > On 8 June 2014 19:15, erik quanstrom wrote:
> >
> >> i think it is in the image cache, but .ref >1.
> >
> >
> > but in that case it will still not pio, but make a local writabl
On Tue, Jun 10, 2014, at 02:07 AM, erik quanstrom wrote:
> On Mon Jun 9 21:02:01 EDT 2014, p...@fb.com wrote:
> > Hi cinap,
> >
> > Would it be possible to change a bit the 9front mercurial repository so that
> > it can work on MacOS filesystem.
> >
> > I get some:
> > abort: case-folding colli
On Mon Jun 9 21:02:01 EDT 2014, p...@fb.com wrote:
> Hi cinap,
>
> Would it be possible to change a bit the 9front mercurial repository so that
> it can work on MacOS filesystem.
>
> I get some:
> abort: case-folding collision between sys/lib/troff/font/devutf/charlib/lH
> and sys/lib/troff/fo
Hi cinap,
Would it be possible to change a bit the 9front mercurial repository so that
it can work on MacOS filesystem.
I get some:
abort: case-folding collision between sys/lib/troff/font/devutf/charlib/lH and
sys/lib/troff/font/devutf/charlib/LH
when hg pull; hg update.
I can understand the
> With the trick I am talking about, there is nothing to stop
> you from connecting to N different remote ventis. In effect
> your local (by that I mean under your control, not necessarily
> on the same machine) venti can be treated as just a buffer!
I took a look at some things along those line
On Mon, 09 Jun 2014 18:22:26 EDT erik quanstrom wrote:
> > Over the weekend I was playing with fossil and "copied" my
> > fossil partition using its last score, swapped the two disks
> > (under virtualbox) and rebooted. df now shows 1MB in use! So
> > if you init fossil from the score of an exist
> Over the weekend I was playing with fossil and "copied" my
> fossil partition using its last score, swapped the two disks
> (under virtualbox) and rebooted. df now shows 1MB in use! So
> if you init fossil from the score of an existing installation,
> you can make do with a lot less space -- onl
On Mon, 09 Jun 2014 17:25:51 EDT erik quanstrom wrote:
> On Mon Jun 9 17:13:09 EDT 2014, lyn...@orthanc.ca wrote:
>
> >
> > On Jun 9, 2014, at 1:21 PM, Riddler wrote:
> >
> > > It was brought about mainly because the wiki states that sources only
> > > uses ~512MB for fossil.
> >
> > I suspe
On Mon Jun 9 17:13:09 EDT 2014, lyn...@orthanc.ca wrote:
>
> On Jun 9, 2014, at 1:21 PM, Riddler wrote:
>
> > It was brought about mainly because the wiki states that sources only
> > uses ~512MB for fossil.
>
> I suspect that's wildly out of date.
a basic install requires about 512mb, which
On Jun 9, 2014, at 1:21 PM, Riddler wrote:
> It was brought about mainly because the wiki states that sources only
> uses ~512MB for fossil.
I suspect that's wildly out of date.
signature.asc
Description: Message signed with OpenPGP using GPGMail
hello, mischief here.
it is 'in the works'. there's some bugs to be squashed.
i'm using the legacy virtio interface. it doesn't perform very great
right now, usually slower than igbe, but that may not matter if you
can't get igbe at all. it also seems to crash on old (meaning, 1.0)
qemu. i've bee
> why bother optimizing this? fossil is going to be <1% of the disk even
> if you make it silly huge.
64GB was just a number that seemed like it should accommodate pretty
much anything I could need.
As Steve points out fossil won't do any caching of often used files so
I'll probably cut it in hal
> Why would you want to make the fossil partition that small?
>
> I would keep it at least twice as large as the largest file
> I'd ever want to create.
I was not actually planning on making it that small, I was just
curious as to how fossil would react.
It was brought about mainly because the wik
Cool! is there a virtio ethernet driver in the works for 9front?
anyone know what flavor is mischief's version?
-Skip
On Fri, Jun 6, 2014 at 5:16 PM, wrote:
> DONE, now beer.
>
>
> http://code.google.com/p/plan9front/source/detail?r=2f51489d42116c85159dc1649ab82cec9a766542
>
> --
> cinap
>
>
> On 8 June 2014 19:37, Charles Forsyth wrote:
>
> > On 8 June 2014 19:15, erik quanstrom wrote:
> >
> >> i think it is in the image cache, but .ref >1.
> >
> >
> > but in that case it will still not pio, but make a local writable copy.
>
>
> in fact ref > 1 is the copy-on-write case and in a
if you setup an auth+fs+cpu machine, then you can tftp boot the pi(s); it
is just as fast.
On Mon, Jun 9, 2014 at 12:40 AM, Yoann Padioleau wrote:
> Hi,
>
> I have a raspberry pi :) but I've found it incredibly convenient to have
> an emulator
> to test things. The development iterative loop is
On 8 June 2014 19:37, Charles Forsyth wrote:
> On 8 June 2014 19:15, erik quanstrom wrote:
>
>> i think it is in the image cache, but .ref >1.
>
>
> but in that case it will still not pio, but make a local writable copy.
in fact ref > 1 is the copy-on-write case and in a sense the usual one,
w
On 9 June 2014 08:40, Yoann Padioleau wrote:
> I think I've found a possible situation where we call two times free on
> the same pointer.
> in sysexec() there is essentially
>
the only correct way to write these is not to rely on nil values or not,
but immediately after the allocation, include
Hi,
I think I've found a possible situation where we call two times free on the
same pointer.
in sysexec() there is essentially
sysexec(...) {
…
if(waserror()){
free(file0);
free(elem);
nexterror();
}
for(;;){
Hi,
I have a raspberry pi :) but I've found it incredibly convenient to have an
emulator
to test things. The development iterative loop is far faster when you can
cross-compile
from your pc and test directly on your pc. Then once it works you can deploy
and test on the real machine. Anyway, I un
25 matches
Mail list logo
