[9fans] Filesystem scheme for Web-Access ?
Hi folks, I'm currently thinking about moving out mozilla's web access handling (http + friends) to some 9p server to make moz's structure some reasonable bit simpler and make performance tweaking easier (w/ the current structure it's nearly impossible to find bootlenecks and blocking situations). This server should also handle the whole caching issue, ssl, connection pooling, etc. What do you think about this idea ? How should that fs be structured ? 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/ -
[9fans] inotify / waiting for events on 9p
Hi folks, I'm currently thinking about event notifications via 9p. An simple way would be just reading from some file, and this read operation will sleep until some event occours. The question is: how long can that operation sleep ? Is there any timeout ? 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] simplicity
On 9/16/07, Francisco J Ballesteros [EMAIL PROTECTED] wrote: Any other suggestion? ELF prelinking (on, e.g., FC7) how to take a bad decision and make it worse ron
Re: [9fans] simplicity
oh, yeah, the utf8 example is great. abiword use to be fast. before internationalization. Now it is so slow as to be totally useless. ron
Re: [9fans] inotify / waiting for events on 9p
I'm currently thinking about event notifications via 9p. An simple way would be just reading from some file, and this read operation will sleep until some event occours. The question is: how long can that operation sleep ? Is there any timeout ? neither 9p nor the plan 9 kernel nor unix system calls have read timeouts. particular filesystems like nfs might. - erik
Re: [9fans] inotify / waiting for events on 9p
On 9/17/07, Enrico Weigelt [EMAIL PROTECTED] wrote: The question is: how long can that operation sleep ? Is there any timeout ? totally depends on what's at the other end. Also, it can always return with no event having happened -- think remote system died. So, in general, plan for a failure. ron
Re: [9fans] Filesystem scheme for Web-Access ?
webfs(4) On 9/17/07, Enrico Weigelt [EMAIL PROTECTED] wrote: Hi folks, I'm currently thinking about moving out mozilla's web access handling (http + friends) to some 9p server to make moz's structure some reasonable bit simpler and make performance tweaking easier (w/ the current structure it's nearly impossible to find bootlenecks and blocking situations). This server should also handle the whole caching issue, ssl, connection pooling, etc. What do you think about this idea ? How should that fs be structured ? 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/ -
[9fans] new venti qemu / hang after sync...
Hello! Some guy at IRC installed current iso with fossil+venti on qemu. The first boot into the new installed system works, but on the 2nd boot time venti hangs with: conf...httpd tcp!127.1!8000...init...sync... I installed it today and could reproduce the problem. Tried running Plan9 from live cd to see whats happening gets the same problem: ip/ipconfig venti/venti -d -L -c /dev/sdC0/arenas -a 'tcp!*!17034' -h 'tcp!*!8000' conf...httpd tcp!127.1!8000...init...sync... ... And then looking at the logs shows: (sorry, removed timestamps because i typed this manualy) hget 'http://10.0.2.15:8000/log?log=all' | htmlfmt proc main: kick icache work icachewritecoord: start proc icachewritecoord: icachewritecoord kick dcache work flushproc: start proc flushproc: build t=131 proc flushproc: writeblocks t=991 proc flushproc: writeblocks.1 t=1632 proc flushproc: writeblocks.2 t=2296 proc flushproc: writeblocks.3 t=2944 proc flushproc: undirty.4 t=3564 work flushproc: finish proc icachewritecoord: kick dcache proc icachewritecoord: icachewritecoord kicked dcache proc icachewritecoord: icachewritecoord start flush proc icachewritecoord: icachedirty enter proc icachewritecoord: icachedirty exit proc icachewritecoord: icachewritecoord sleep proc main: kick icache ...the stuff repeats again... The log fills all the time... All processes alive none broken. Starting venti with the -r option seems to work without such problems. (because syncindex() is not called?) Any suggestions what I should to to debug this problem further? Would be interesting to know if this happens on qemu only... cinap_lenrek
Re: [9fans] simplicity
Francisco J Ballesteros wrote: the slides are a buch of programs. In fact, I use a terminal to compile and run programs from the 9.intro.pdf book. ... By the way, I've been reading through that book in my spare time, and it's a pretty good resource.
Re: [9fans] simplicity
erik quanstrom wrote: i think the devolution of gnu grep is quite instructive. ... it gets to the heart of why plan9's invention and use (thank's rob, ken) of utf-8 is so great. If the problem is that Gnu grep converts any non-8-bit character set to wchar_t (the equivalent of Plan 9 rune), then it's not really a fair criticism of the software. The conversion approach handles a wide variety of character encoding scheme, whereas grepping the encodings directly (the fast approach) doesn't work well for many non-UTF-8 encodings.
Re: [9fans] simplicity
Steve Simon wrote: Top of my over-complex list would be configure. My experience with configure is that it seldom selects the compiler I wanted to use, for some reason preferring the Gnu software even though the conventional Unix versions work at least as well for the purpose.
Re: [9fans] simplicity
erik quanstrom wrote: i think the devolution of gnu grep is quite instructive. ... it gets to the heart of why plan9's invention and use (thank's rob, ken) of utf-8 is so great. If the problem is that Gnu grep converts any non-8-bit character set to wchar_t (the equivalent of Plan 9 rune), then it's not really a fair criticism of the software. The conversion approach handles a wide variety of character encoding scheme, whereas grepping the encodings directly (the fast approach) doesn't work well for many non-UTF-8 encodings. performance may suck, but that's just a symptom of a bigger problem. wchar_t is not the equivalent of Rune. Rune is always utf-8. wchar_t can be whatever. this is not a feature. it is a bug. suppose Linux user a and user b grep the same text file for the same string. results will depend on the users' locales. contrast plan 9. any two users grepping the same file for the same string will get the same results. in either case a character set conversion might be necessary to match the locale. but in the plan 9 case, one conversion will fix things for any plan 9 user. in the Linux case, there is no conversion that will fix things for any Linux user. - erik p.s. gnu grep does special-cases utf-8 and avoids wchar_t conversions
[9fans] Qemu tip for saving all that retyping
If you boot plan9 in qemu like this : qemu $otheroptions -serial stdio you can do this : term% echo hello console where qemu started /dev/eia0 term% cat /dev/eia0 back at ya term% which is how I did the term%s in this email :) -- matt lawless [EMAIL PROTECTED] -- http://www.fastmail.fm - A fast, anti-spam email service.
Re: [9fans] Qemu tip for saving all that retyping
many thanks for the tip! :-) cinap_lenrek ---BeginMessage--- If you boot plan9 in qemu like this : qemu $otheroptions -serial stdio you can do this : term% echo hello console where qemu started /dev/eia0 term% cat /dev/eia0 back at ya term% which is how I did the term%s in this email :) -- matt lawless [EMAIL PROTECTED] -- http://www.fastmail.fm - A fast, anti-spam email service.---End Message---
Re: [9fans] simplicity
In my experience, the one thing that really gets Plan 9 across to people is the telco server. That's an example of something that you can't nicely do in Unix, and that exhibits power and elegance as a consequence of a few basic design choices.
