Re: [9fans] Isnt it time we have the next bay area meeting?
>> it has been a long time since we met. >> >> any plans to have our next Plan9 Bay Area Users Group Meeting? > > The sooner the better, I hope! agreed :) nkl
Re: [9fans] Isnt it time we have the next bay area meeting?
On Sun, 2008-06-01 at 15:03 -0700, Tharaneedharan Vilwanathan wrote: > hi, > > it has been a long time since we met. > > any plans to have our next Plan9 Bay Area Users Group Meeting? The sooner the better, I hope! Thanks, Roman.
Re: [9fans] gsoc.cat-v.org links/pages lost
On Tue, May 27, 2008 at 09:12:05AM +, prem wrote: > Hi guys, > does anyone know why links under http://gsoc.cat-v.org/people/nwf/ (or > any links under http://gsoc.cat-v.org) does not really work ? > Are there any mirrors of this site ? > I was actually looking for the dynld.txt and paper-strategy-plus.pdf If it's not already back up, I can certainly provide you with a copy. Any particular interest or just looking? --nwf; pgpPNcGQrP3jH.pgp Description: PGP signature
[9fans] Isnt it time we have the next bay area meeting?
hi, it has been a long time since we met. any plans to have our next Plan9 Bay Area Users Group Meeting? thanks dharani
Re: [9fans] plan9port: tcp servers
On Sun, Jun 1, 2008 at 10:41 AM, erik quanstrom <[EMAIL PROTECTED]> wrote: > > if dial strings are written with / and not ! >/net/tcp/bell-labs.com/http, > an appropriately constructed namespace could > allow the "correct" fileserver to pass judgement. > Why include the tcp path element? Name resolution should be able to determine the best network path to the service. -eric
Re: [9fans] plan9port: tcp servers
the fact that dial strings live in their own parallel universe has always seemed un-plan 9-ish to me. > network addresses and files are different kinds of names. > mixing them would introduce ambiguities, like what > if i have a file name 'tcp!bell-labs.com!http'. we don't have this problem with devices, due to convention. if we didn't have an implicit /net, i don't think your example would lead to any confusion. /net/tcp!bell-labs.com!http is pretty clearly not a normal file. on the other hand, making dial strings special, cuts the namespace out of how network names are constructed. you can't create a special case in networking with bind(1). > also there was no obvious error response if you > dial "a!b!c!d!e". is it a malformed address? > not if a file name a!b!c!d!e exists. but in general, yes. if dial strings are written with / and not ! /net/tcp/bell-labs.com/http, an appropriately constructed namespace could allow the "correct" fileserver to pass judgement. - erik
Re: [9fans] crosstool fails on gentoo
* Yann E. MORIN <[EMAIL PROTECTED]> wrote: > On Wednesday 28 May 2008 18:52:14 Lance Spaulding wrote: > > I'm trying to use crosstool-ng to build an ARM toolchain but if fails > > with the following error message: > > [ALL ]*** [Gentoo] sanity check failed! *** > > [ALL ]*** libtool.m4 and ltmain.sh have a version mismatch! *** > > [ALL ]*** (libtool.m4 = 1.5.23b, ltmain.sh = "1.5.24 Debian 1.5.24-1") > > *** > > This was already reported a few days ago: > http://sourceware.org/ml/crossgcc/2008-05/msg00080.html > > > It looks like several people have ran into this error on gentoo but I > > haven't been able to find a solution anywhere (and got no replies to > > this question in the gentoo forums). Anyone have a fix for this? > > As suggested by Enrico in that message: "we should recreate the > autotools+libtool > stuff before compiling." Right, manually running autoreconf -fi && libtoolize on the already uncompressed tree fixed it for me. Of course this manual hack is ugly, it should be done automatically after decompression. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ -
Re: [9fans] plan9port: tcp servers
> BTW: I've now mounted an vacfs from Midnight Command :)
> But when trying to overwrite, it causes mc to hang. Could it be
> that vacfs drops certain messages instead of returning an
> appropriate error ?
you can run
verbose9pserve=2 vacfs ...
and you will get a lot of debugging messages on standard error.
among other things, you'll get a trace of all the 9p traffic,
and you can check whether this is true. i doubt very much
that vacfs is dropping messages, since it is a single-threaded
server with a simple
for(;;){
read request
response = handle(request);
write response
}
loop.
>> i had considered not requiring the unix! once,
>> but i decided against it.
>
> That would be fine, why did you decied against ?
network addresses and files are different kinds of names.
mixing them would introduce ambiguities, like what
if i have a file name 'tcp!bell-labs.com!http'.
also there was no obvious error response if you
dial "a!b!c!d!e". is it a malformed address?
not if a file name a!b!c!d!e exists. but in general, yes.
russ
Re: [9fans] plan9port: tcp servers
* Russ Cox <[EMAIL PROTECTED]> wrote: > > seems like dial() doesn't accept socket path names. > > I'll have a look if I can fix this ... > > sorry, that should be > > 9pserve -c unix!`namespace`/acme tcp!*!12345 yep, already found it out. Seems to work fine. BTW: I've now mounted an vacfs from Midnight Command :) But when trying to overwrite, it causes mc to hang. Could it be that vacfs drops certain messages instead of returning an appropriate error ? > i had considered not requiring the unix! once, > but i decided against it. That would be fine, why did you decied against ? cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ -
Re: [9fans] cut word out of a line with regexp
> How do I cut a word out of a line with sed? The word end with a '_'. I > don't know, how to match word boundaries. I need "sample" > out of a sample_ line. that blanks in the char class brackets are [ \t] (space and tab) you could expand the chars that can be part of a word, e.g. 0-9 cpuc% cat | sed 's/(^|[ ]+)[A-Za-z][A-Za-z_]*_([]+|$)/ /g' this is a test_ this test_ is another test_ this case too test_test shouldn't get deleted multiple test_ should also test_ work this is a this is another this case too test_test shouldn't get deleted multiple should also work
Re: [9fans] cut word out of a line with regexp
> How do I cut a word out of a line with sed? The word end with a '_'. I > don't know, how to match word boundaries. I need "sample" > out of a sample_ line. you can match word characters instead. sed 's/[^ ]+_ / /' sed 's/[a-zA-Z0-9_]+_([^a-zA-Z0-9_])/\1/' russ
Re: [9fans] plan9port: tcp servers
> seems like dial() doesn't accept socket path names. > I'll have a look if I can fix this ... sorry, that should be 9pserve -c unix!`namespace`/acme tcp!*!12345 i had considered not requiring the unix! once, but i decided against it. russ
[9fans] cut word out of a line with regexp
Moin! How do I cut a word out of a line with sed? The word end with a '_'. I don't know, how to match word boundaries. I need "sample" out of a sample_ line. Many thanks Matthias
Re: [9fans] plan9port: tcp servers
* Russ Cox <[EMAIL PROTECTED]> wrote:
Hi,
> If you were to add a -c option to 9pserve
> to make it connect to a network address instead of
> using stdin/stdout, then you could use 9pserve
> to redirect the Unix postings onto TCP.
>
> ARGBEGIN{
> ...
> case 'c':
> if((fd = dial(EARGF(usage()), nil, nil, nil)) < 0)
> sysfatal("dial %s: %r");
> dup(fd, 0);
> dup(fd, 1);
> if(fd > 1)
> close(fd);
> break;
> ...
> }ARGEND
>
> Then you could run something like
>
> 9pserve -c `namespace`/acme tcp!*!12345
this doesn't work - gives: malformed address.
seems like dial() doesn't accept socket path names.
I'll have a look if I can fix this ...
cu
--
-
Enrico Weigelt== metux IT service - http://www.metux.de/
-
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
-
Re: [9fans] /dev/audio format (was: read/write offset hack)
mime type of x-iaf was used successfully. On 6/1/08, Enrico Weigelt <[EMAIL PROTECTED]> wrote: > * Bruce Ellis <[EMAIL PROTECTED]> wrote: > > Hi, > > > There was also the Inferno Audio File format which was rather fb > > like.The file began with text lines describing the stuff and then > > after a\n\n the rest was data. > > Interesting idea. > We could also use something like HTTP or mail headers - easy to > understand for many people :) > > Maybe an advanced audio server could even directly understand > mimetypes ? ,-O > > BTW: some weeks ago, I started hacking on an 9P'ed pulseaudio. > It will be configurable completely via 9P and also support > audio I/O via 9P. But I'm still looking for a suitable interface. > > The audio interface should be capable of completely replacing > other common interfaces (in GNU world), so eg. understand > all hw-supported formats, realtime-capable, etc. > > Once this works, I intend to rewrite certain client libs for > other audio servers (pulse, esd, arts, ...) to go through > that new 9P interface. > > > Suggestions appreciated :) > > > cu > -- > -- > Enrico Weigelt, metux IT service -- http://www.metux.de/ > > cellphone: +49 174 7066481 email: [EMAIL PROTECTED] skype: nekrad666 > -- > Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme > -- > >
Re: [9fans] /dev/audio format (was: read/write offset hack)
* Bruce Ellis <[EMAIL PROTECTED]> wrote: Hi, > There was also the Inferno Audio File format which was rather fb > like.The file began with text lines describing the stuff and then > after a\n\n the rest was data. Interesting idea. We could also use something like HTTP or mail headers - easy to understand for many people :) Maybe an advanced audio server could even directly understand mimetypes ? ,-O BTW: some weeks ago, I started hacking on an 9P'ed pulseaudio. It will be configurable completely via 9P and also support audio I/O via 9P. But I'm still looking for a suitable interface. The audio interface should be capable of completely replacing other common interfaces (in GNU world), so eg. understand all hw-supported formats, realtime-capable, etc. Once this works, I intend to rewrite certain client libs for other audio servers (pulse, esd, arts, ...) to go through that new 9P interface. Suggestions appreciated :) cu -- -- Enrico Weigelt, metux IT service -- http://www.metux.de/ cellphone: +49 174 7066481 email: [EMAIL PROTECTED] skype: nekrad666 -- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme --
