Is there a "quick" and "stable" way to mount a 9p exported
file-system on an OSX host? (By "quick way" I mean something which
doesn't imply compiling; and by "safe" something that others can
recommend as not crashing the system...)
Obviously I've found the following:
* https://code
On Tue, Mar 20, 2012 at 14:32, Dan Cross wrote:
> 9P itself is not a stream-oriented
> protocol, nor is it what one would generally call, 'transport
> technology.'
I would beg to differ on this subject... Because a lot of tools in
the Plan9 environment expose their facilities as 9p file syst
On Fri, Mar 16, 2012 at 19:36, Russ Cox wrote:
> On Fri, Mar 16, 2012 at 7:40 AM, Ciprian Dorin Craciun
> wrote:
>> Why was I puzzled: because as a non Plan9 user / developer, I
>> usually think of the underlaying transport technology (be it sockets
>> or 9p) as a
Hello all!
I'm reading through the nice `factotum` paper [1], and the section
describing the `rpc` file behaviour (section "2.6. Factotum
transactions") states:
Programs authenticate with factotum by writing a request to the rpc
file and reading back the reply; this sequence is calle
On Tue, Jan 18, 2011 at 18:28, Russ Cox wrote:
>> But the above statement is true unless you have about 367 targets
>> (for quite a small project -- only 2 tiny and 1 larger Erlang
>> applications), which when built takes about 45 seconds (with
>> NPROC=16), and the second time (without touchin
On Mon, Jan 17, 2011 at 20:36, Bakul Shah wrote:
> On Mon, 17 Jan 2011 11:56:22 EST erik quanstrom
> wrote:
>> > strace tells you what system calls were made and when. To
>> > find out which functions use most time, compile with -pg and
>> > look at the gprof output once done. That 14 seconds
On Mon, Jan 17, 2011 at 20:36, Bakul Shah wrote:
> On Mon, 17 Jan 2011 11:56:22 EST erik quanstrom
> wrote:
>> > strace tells you what system calls were made and when. To
>> > find out which functions use most time, compile with -pg and
>> > look at the gprof output once done. That 14 seconds
On Mon, Jan 17, 2011 at 17:53, Robert Raschke wrote:
>
> On Mon, Jan 17, 2011 at 3:33 PM, Ciprian Dorin Craciun
> wrote:
>>
>> On Mon, Jan 17, 2011 at 17:00, Robert Raschke
>> wrote:
>> > Your email also doesn't explain why you cannot generate a &qu
On Mon, Jan 17, 2011 at 18:02, andrey mirtchovski wrote:
> something else to try if you're on a multiprocessor system: set $NPROC
> to a value > 1 and see how this affects the runtime in the 14-second
> case. your dependency tree may be very deep, but parallelizable.
I've tried that, either N
;m not able to
fix this I'll have to resort back to make...) :(
> But it's cool to see someone else who uses Erlang and RabbitMQ hanging out
> on this list. :-)
>
> Robby
Glad to see another erlanger. :)
Ciprian.
> On Mon, Jan 17, 2011 at 2:47 PM, Ciprian Dorin C
On Mon, Jan 17, 2011 at 16:47, Ciprian Dorin Craciun
wrote:
> Hello all!
>
> Sorry for interrupting again, but I've stumbled on an `mk` issue...
>
> I've written a little Scheme application that generates `mk`
> scripts for building Erlang applications. (See
On Mon, Jan 17, 2011 at 16:59, erik quanstrom wrote:
>> Any ideas what could cause this?
>
> have you tried profiling mk?
>
> - erik
In fact I tried to `strace -f -T` it and it seems that in the
first second or so it `stats` all the files that exist, and then it
just waits 14 seconds comp
On Fri, Jan 7, 2011 at 12:40, Henning Schild
wrote:
> On Fri, 7 Jan 2011 10:51:56 +0100
> Ciprian Dorin Craciun wrote:
>
>> :) I've kind of feared that this is the reason... :)
>>
>> But still how do people handle the issue?
>
>
> I guess in most
On Fri, Jan 7, 2011 at 11:25, erik quanstrom wrote:
> the code has its reasons. from mk.c:/^outofdate
>
> /*
> * Treat equal times as out-of-date.
> * It's a race, and the safer option is to do
> * extra building rather than not enoug
Hello all!
I've played today with mk (from plan9ports), and I thin I've
stumbled upon the following issue: if both the build of a prerequisite
and the target itself is less than a second (the same second), then mk
believes it must remake the target when invoked a second time.
See belo
Hello all!
In what follows I would like to ask for your comments regarding a
9p file server that exports a file system with a (message) queue
semantics. (My major interest here is more about the actual semantic
itself, and less about the implementation details. But all comments
are welcome
Hy there! (I'm quite new to the whole Plan 9 and 9P, so please
bare with me if I'm asking stupid or well known questions.) :)
Today I've introduced myself to the 9P protocol, and I've found it
very interesting. (I've reached it from the XCPU project.)
(And I must say that, in Linux, it
On Mon, Dec 14, 2009 at 6:14 PM, erik quanstrom wrote:
>> One for example (I think it is a bug, but maybe in the semantics
>> you've described it's not):
>> * again if we're using `-e`, and inside a function we write `fn
>> dosomething { echo 1 ; false ; echo 2 ; return 0 ; }`
>> * if
On Mon, Dec 14, 2009 at 4:08 PM, erik quanstrom wrote:
>> Unfortunately after playing a little bit more with rc, and trying
>> it's syntax and semantics to the limit, I've also found other nasty
>> bugs (some of which I've fixed, other I was not able to do so)...
>
> what nasty bugs? could yo
On Mon, Dec 14, 2009 at 11:49 AM, weakish wrote:
> On Dec 6, 3:54Â pm, ciprian.crac...@gmail.com (Ciprian Dorin, Craciun)
> wrote:
>
>> Â Â Now I'm trying to contribute back to the community, and I've sent
>> an email to Tig Goodwin (at t...@star.le.ac.uk), which
On Sun, Dec 6, 2009 at 1:36 PM, Charles Forsyth wrote:
>> * who is maintaining the UNIX port of rc shell? (is it still
>>Tig?) (if so what's the email address?)
>
> if it's Byron Rakitzis' rc, it's not a `port' to UNIX of Plan 9's rc,
> but an independent implementation, with differences in th
Hello all!
I'm a new (1 week) user of the rc shell (I want to migrate from
the Sh/Bash and their offsprings to rc after a lot of pain and misery
with them). :) And so far I like the rc look-and-feel (by look I mean
syntax and by feel I mean semantics.) as their quite minimal and with
just
22 matches
Mail list logo
