hi,
quick question.
snarf doesnt work properly in plan9 on vmware fusion 2.0 for mac. from what
i found this seems to be a known issue. is there any fix available?
any help appreciated.
thanks
dharani
On Thu, Dec 25, 2008 at 1:55 AM, erik quanstrom wrote:
>> Ah sorry I had confused the various tests I did: the case where I
>> actually have this problem is if
>> I call the function acme itself, ie if I do
>> fn acme { acme -f /lib/font/bit/fixed/unicode.8x13.font }
>>
>> If I call it acmef or wh
> I surely hope the festive mood of the season will protect me from being
> ostracized for asking this, but is there any chance to map Plan9
> development practices to some of the established ways of source
> code management? I mostly long for things like being able to browse
> Plan9 history with a
Mostly off-topic, but the newly released linux 2.6.28 talks about the
"Nokia phonet protocol". Google "helpfully" returns all sorts of
things with "phone" in it as a match to "phonet", making it a bit hard
to find more detailed protocol documentation. Anyone have a pointer to
anything more definiti
perhaps Russ's most excellent search engine helps? I know nothing
of this phonet of which you speak so I honestly don't know if this
is of any use.
http://www.google.com/codesearch?hl=en&lr=&q=phonet+nokia&sbtn=Search
-Steve
I agree with erik, given 9fs dump I have no need for SCM,
however the return of the /n/sources/extra/changes would be
wonderful.
For the couple of years the guys at the labs where keeping one
up to date I found it very interesting and, I think I learnt
a lot. It also helped me to feel more envolve
i highly recommend rsc's excellent search engine also.
> perhaps Russ's most excellent search engine helps? I know nothing
> of this phonet of which you speak so I honestly don't know if this
> is of any use.
>
> http://www.google.com/codesearch?hl=en&lr=&q=phonet+nokia&sbtn=Search
>
> -Steve
On Dec 24, 2008, at 10:40 PM, erik quanstrom wrote:
Is there any preferred way to get changelogs / diffs these days?
yesterday -d ...
when i'm especially curious or anxious.
But yesterday won't work in a more lightweight environment (such as
9vx) will it?
exactly the same as plan 9 does.
a
> True, but I'd really like to NOT have any extra software running and
> still have and ability to do replica/* and yesterday under 9vx.
I'm only vaguely familiar with 9vx, so there I can't speak, but you
can certainly do replica/* as it is a user-level tool and as for
yesterday, you can apply it
depends what you mean by "extra". if that means "outside 9vx", then
yes; if it means "besides what 9vx uses by default", no.
yesterday(1) relies on having dump-style snapshots. 9vx, as shipped,
gets its root file system from #Z, which doesn't have snapshots.
erik offered some suggestions for host
> using fossil for your root, instead of #Z, will obviously cost you the
> benefits of #Z - namely, the pass-through transparency. if your
> primary interest is for replica/*, though, you might consider the
> direction i've been headed: root from fossil, but import $home or /usr
> from #Z.
That's
11 matches
Mail list logo
