Re: [9fans] 9vx, kproc and *double sleep*
On Sun, Jun 13, 2010 at 11:03 AM, Philippe Anel wrote: > I tried with adding : > > while (p->mach) > sched_yield(); > > > at the end of sched.c:^runproc(), before the return. > > It seems to work well. > > What do you think ? Not sure I understand all the implications but I'll try anything at this point :-) I'm trying now with -O3 back on. The -O3 was a red herring. ron
Re: [9fans] 9vx, kproc and *double sleep*
If anyone can help me with some valgrind patches we can see if valgrind can be useful. Charles, I am really puzzled about your ubuntu experience. Oh, wait, can you set LANG=C and try again? Or is it? BTW when you get the immediate explosion does a window even ever come up or does it die before that? ron
Re: [9fans] naming conventions
> I can run "9 9term", but what happens when you run something like "9vx -u > glenda -r /some/very/long/path/" and then run "!9vx" the next time to rerun > the last command starting with ? It probably runs the 9'th command in the > history. Sorry I was not clear. I consider this a minor his is a minor > nit, the real problem is the journal editors and assumptions of the search > engines. the rc history mechanism doesn't suffer from this. it's a simple patch to and uses an external program "-p" and an rc function "-". essentially, i ripped off byron's rip off of v10 "=". - erik
Re: [9fans] naming conventions
On Mon, 14 Jun 2010 21:10:38 +, hiro <23h...@googlemail.com> wrote: > I tried running 9 9term in bash and had no problems. > Perhaps you haven't set up your $PATH correctly? I can run "9 9term", but what happens when you run something like "9vx -u glenda -r /some/very/long/path/" and then run "!9vx" the next time to rerun the last command starting with ? It probably runs the 9'th command in the history. Sorry I was not clear. I consider this a minor his is a minor nit, the real problem is the journal editors and assumptions of the search engines. EBo --
Re: [9fans] naming conventions
I tried running 9 9term in bash and had no problems. Perhaps you haven't set up your $PATH correctly?
Re: [9fans] 9vx, kproc and *double sleep*
Charles, Can you please give us stack information with gdb ? Phil; On Mon, 2010-06-14 at 20:15 +0100, Charles Forsyth wrote: > it's interesting that neither of philippe's changes, > however justified, make any visible difference > to 9vx on my ubuntu 10.04LTS system: 9vx still > fails almost immediately. that's consistent with > 9vx behaving itself as well as on any other platform > until i changed the linux and/or ubuntu version. > i'll see if i can brave gdb some more to find out. >
Re: [9fans] 9vx, kproc and *double sleep*
it's interesting that neither of philippe's changes, however justified, make any visible difference to 9vx on my ubuntu 10.04LTS system: 9vx still fails almost immediately. that's consistent with 9vx behaving itself as well as on any other platform until i changed the linux and/or ubuntu version. i'll see if i can brave gdb some more to find out.
Re: [9fans] Printing via lpdaemon(1)
This is what mine has (default):
if(/sys/lib/lp/bin/lpscratch){
exec /$cputype/bin/aux/lpdaemon >>[2] `{cat
/env/LPSCRATCH}^/log/lpdaemonl
}
In any case, I set the environment variable
through /cfg/sounine/cpustart just to make
sure, as well as in the service file, but to
no avail.
ak
On Mon, Jun 14, 2010 at 5:58 AM, erik quanstrom wrote:
>> On Sun, Jun 13, 2010 at 7:19 PM, erik quanstrom
>> wrote:
>> > have you set $LPSCRATCH?
>>
>>
>> No; I thought it was supposed to be set by /sys/lib/lp/bin/lpscratch?
>
> i don't see that being run from /rc/bin/service/!tcp515.
>
> - erik
>
>
Re: [9fans] naming conventions
Would a phonetic morphology à la the ceePlusPlus of wiki would suffice for our lexically challenged friends?
Re: [9fans] naming conventions
On Mon, Jun 14, 2010 at 8:47 AM, EBo wrote: > >> your shell is broken. [0-9] are perfectly valid anywhere in a unix file >> name. > > does bash completion work for you on *anything*? Or does it get confused > thinking that you are specifying a previous command (!### in the history)? > Yes, a file/script named [0-9]* is valid, but still breaks things. Maybe > there is some trick to get around it that I do not knwo about, but the big > issues where those that the editor raised. > > EBo -- For what it's worth, ksh on OpenBSD handles completion on 9* files just fine. -sl
Re: [9fans] naming conventions
> does bash completion work for you on *anything*? that's a purely theoretical question. i use rc. - erik
Re: [9fans] naming conventions
> your shell is broken. [0-9] are perfectly valid anywhere in a unix file > name. does bash completion work for you on *anything*? Or does it get confused thinking that you are specifying a previous command (!### in the history)? Yes, a file/script named [0-9]* is valid, but still breaks things. Maybe there is some trick to get around it that I do not knwo about, but the big issues where those that the editor raised. EBo --
Re: [9fans] unknown error message
On 14 Jun 2010, at 03:46, erik quanstrom wrote: plan 9 is fairly unique in that it's a system one can reasonablly hope to understand by reading the source. that's it? really, that's it. Plan 9 has given me a feeling about computing I haven't had since my 8- bit days. So refreshing! Somewhat pointless post, I know, but I had to write something positive after my last mail to a certain other list. -- Complexity is not a function of the number of features. Some features exist only because complexity was _removed_ from the underlying system.
Re: [9fans] naming conventions
> I've been catching a little flack off and on about the Plan 9's naming > convention of adding a '9' in front of program names. I've also noticed > that using emulators, on the linux side, prefixing a 9 breaks history > utilization functionality in most of the shells I use. your shell is broken. [0-9] are perfectly valid anywhere in a unix file name. - erik
Re: [9fans] Printing via lpdaemon(1)
> On Sun, Jun 13, 2010 at 7:19 PM, erik quanstrom > wrote: > > have you set $LPSCRATCH? > > > No; I thought it was supposed to be set by /sys/lib/lp/bin/lpscratch? i don't see that being run from /rc/bin/service/!tcp515. - erik
Re: [9fans] naming conventions
>Is it more reasonable in this case to name the executive vx32 instead of >9vx since it is a plan 9 emulator for linux? not really, because vx32 is the library, and 9vx is just one sample application. (there are others.)
Re: [9fans] unknown error message
Yes, it can be easier in a sense that you sometimes get the explanation that you would not have gotten in a obvious manner by reading the code. If I don't need the answer to the issue right away, and if I want to work on something else in the meanwhile, it can be better to wait and see what you wise guys come up with, rather that going head first and grok the whole context where the piece of code is. Especially if I'm unfamiliar with that part of the code. Yes, it's a form of lazyness, but not just for the sake of being lazy ;) Mathieu --- Begin Message --- > Thanks, that's what I was curious about. shoulda grepped but figured > one of you would know off the top of your head. :) is posting to 9fans now easier than grep? probablly not. recently i've been working with a few non-plan 9 guys, and the ones that take the time to look at the system are at first appalled by the simplicity. that's it? really, that's it. i've learned to ignore that. inevitably, a question similar to this thread comes up. how to i find xyz. i get xyz error message. well, g xyz /sys/src. that's it? really, that's it. i think the complexity of most systems can knock one of one's rhythm and forget that it can be as appalingly simple as grep. plan 9 is fairly unique in that it's a system one can reasonablly hope to understand by reading the source. that's it? really, that's it. - erik --- End Message ---
[9fans] naming conventions
I do not mean to feed any trolls with this one, but I need to know how people what some of this addressed in the future. I've been catching a little flack off and on about the Plan 9's naming convention of adding a '9' in front of program names. I've also noticed that using emulators, on the linux side, prefixing a 9 breaks history utilization functionality in most of the shells I use. For immediate discussion, the 9vx executable is part of the vx32 source. Is it more reasonable in this case to name the executive vx32 instead of 9vx since it is a plan 9 emulator for linux? As a note, the flack I've been getting is not just about aesthetics. When the editor of one of the journals I will likely want to publish in says "good god, do not name it that. Starting a proper name or the title of a paper with a numeral will break some search engines and cataloging utilities..." I see this a potential problem. EBo --
