Re: [9fans] Duff's rc paper: Why awk?

2013-06-11 Thread Rudolf Sykora
> plan 9 sed reads a second line before quitting (note the "def" in the example
> below); sed does not work.

Is there any good reason for this difference between plan9 and gnu behaviour?

Thanks!
Ruda



[9fans] plumb rule for include files in different directories

2013-06-11 Thread Bence Fábián
i work on a project and i'd like to be able to plumb #includes right

source files are in $path-to-project/source/$subsystem/src/
includes are in either $path-to-project/source/$subsystem/intf/
or $path-to-project/intf/$subsystem/intf/

it's quite chaothic

i'm trying (at the end of rules) with something like

type is text
wdir matches '(/path-to-project/.*)/src/.*'
arg isdir $1
data matches '([a-zA-Z¡-￿0-9]+\.h)('$addr')?'
arg isfile $dir/intf/$1
data set $file
attr add addr=$3
plumb to edit
plumb client window $editor

but it doesn't seem to work

Does anyone experimented with this (and managed to solve it)?


Re: [9fans] plumb rule for include files in different directories

2013-06-11 Thread Steve Simon
I do somthing similar, though my solution is rather crufty.

I connect linux box using ssh from plan9, I also have a sftpfs
session from plan9 mounted at /n/linux

I have my own script called make on a which runs /bin/make and
pipes the output through sed. sed rewrites the absolute paths
(I have to use cmake which always uses absolute paths) into
plan9 relative paths so they can be plumbed. e.g.

/home/steve/work/xxx/yyy/fred.cpp
gets rewritten as
/n/linux/home/steve/work/xxx/yyy/fred.cpp

I also use conswdir(1) and a cd function in rc (on linux) to ensure 
my plan9 /dev/wdir is kept in sync with linux. This allows me to plumb files
in the current dir or dirs relative to it.

I warned you it was crufty.

-Steve



Re: [9fans] Duff's rc paper: Why awk?

2013-06-11 Thread markus schnalke
[2013-06-11 14:24] Rudolf Sykora 
> > plan 9 sed reads a second line before quitting (note the "def" in the 
> > example
> > below); sed does not work.

Erik, thanks for the explanation.

However, the man page states:

q   Quit. Branch to the end of the script. Do not start a new cycle.

Thus, this is a bit odd.


> Is there any good reason for this difference between plan9 and gnu behaviour?

It looks a bit like the bug described in the man page, although input is read
from the terminal, not from a pipe.

http://plan9.bell-labs.com/magic/man2html/1/sed


meillo



[9fans] Step by step Acme/Mail with plan9ports in Mac OS X Setup

2013-06-11 Thread Brian Vito
Has anyone prepared a step-by-step guide to setting up plan9port's
Acme Mail in Mac OS X? Everything I can find in the archives is
incomplete in some way and I haven't been able to figure out how to
set things up. I am using lavabit mail (and could use either POP or
IMAP, whichever is easier). Thanks very much.



Re: [9fans] plumb rule for include files in different directories

2013-06-11 Thread Richard Miller
If you're using acme, the Incl command might be useful.




Re: [9fans] Win starting rc?

2013-06-11 Thread marius eriksen
On Jun 11, 2013, at 4:09 PM, Brian Vito  wrote:

> Is there a way to have Acme's Win command start an rc session rather
> than bash? Also, is it possible to set the bash prompt to PS1=": {\w}
> %; " if bash is started by Win? Thanks again.

export SHELL=rc

For the latter, you might find it useful to make PS1 conditional on $TERM.



[9fans] Win starting rc?

2013-06-11 Thread Brian Vito
Is there a way to have Acme's Win command start an rc session rather
than bash? Also, is it possible to set the bash prompt to PS1=": {\w}
%; " if bash is started by Win? Thanks again.



Re: [9fans] plumb rule for include files in different directories

2013-06-11 Thread Bence Fábián
i missed Incl.
thank you


2013/6/11 Richard Miller <9f...@hamnavoe.com>

> If you're using acme, the Incl command might be useful.
>
>
>


Re: [9fans] Win starting rc?

2013-06-11 Thread Matthew Veety
On Jun 11, 2013, at 16:09, Brian Vito  wrote:

> Is there a way to have Acme's Win command start an rc session rather
> than bash? Also, is it possible to set the bash prompt to PS1=": {\w}
> %; " if bash is started by Win? Thanks again.
> 

Bash was ported to plan 9?



Re: [9fans] Step by step Acme/Mail with plan9ports in Mac OS X Setup

2013-06-11 Thread Rudolf Sykora
On 11 June 2013 18:09, Brian Vito  wrote:
> Has anyone prepared a step-by-step guide to setting up plan9port's
> Acme Mail in Mac OS X? Everything I can find in the archives is
> incomplete in some way and I haven't been able to figure out how to
> set things up. I am using lavabit mail (and could use either POP or
> IMAP, whichever is easier). Thanks very much.
>

I do not know about Mac. But following are my notes about what I should do
when installing slackware and want to use p9p's acme Mail together with my
gmail account accessed via imap.
If that can help...
(I use secstore to keep my passwords, but this should not make
a difference.)
note:
My machine has the name 'perseus'.
I guess also something like
127.0.0.1   localhost
127.0.0.1   perseus
must be in /etc/hosts.
Finally, 'rudas.dom' near the end can probably be whatever you like. I do not
know what that is really good for.

Ruda

#mailing using p9p Mail in acme
#have a 9mail script in bin with
mailfs -t imap.gmail.com
sudo /usr/sbin/stunnel3 -c -d 12345 -r smtp.gmail.com:465
#do what's in $PLAN9/mail/README
#then remove upas/vf from the pipeline in mail/lib/qmail
#(was the cause of the .suspect being attached to mails;
#according to the plan9 mailing list it is no longer used)
#add keys like
key proto=pass role=client server=perseus service=smtp user=rudolf.sykora@gmail.
com !password?
key proto=pass role=client server=imap.gmail.com service=imap user=rudolf.sykora
 !password?
#to factotum (... secstore)
#1st line in 9mail (above) should now be enough so that
#acme's 9 Mail -s could read email
#2nd line thereof should arrange things for sending an email, which
#can be tested with eg
$PLAN9/bin/upas/smtp -ai 'tcp!perseus!12345' rudolf.syk...@gmail.com
rudolf.syk...@cern.ch 

Re: [9fans] Win starting rc?

2013-06-11 Thread dexen deVries
On Tuesday 11 of June 2013 13:06:15 Matthew Veety wrote:
> On Jun 11, 2013, at 16:09, Brian Vito  wrote:
> > Is there a way to have Acme's Win command start an rc session rather
> > than bash? Also, is it possible to set the bash prompt to PS1=": {\w}
> > %; " if bash is started by Win? Thanks again.
> 
> Bash was ported to plan 9? 

the other way around: http://swtch.com/plan9port/


also p9p mk defaults to bash , so it's good to set MKSHELL=rc on top of 
mkfiles.


-- 
dexen deVries

[[[↓][→]]]

I have seen the Great Pretender and he is not what he seems.




Re: [9fans] Win starting rc?

2013-06-11 Thread Matthew Veety
On Jun 11, 2013, at 16:33, dexen deVries  wrote:

>> Bash was ported to plan 9?
> 
> the other way around: http://swtch.com/plan9port/

Shit, I'm really dumb sometimes.



[9fans] PBSR...EI

2013-06-11 Thread trebol
Hello,
The new 9atom iso fails for me the same.  But if you finish manually the
installation formatting and preparing the 9fat partition, the system boots right
(just as erik said).  Also, the annoying "cpu0:spurious interrupt" kernel 
message 
is gone (with the iso's 9pcf and with a 9pccpuf compiled by me), so I spouse
the problem is in 9pccd. 

This is the linux's lspci output:
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/8251 PCI bridge 
[K8M890/K8T800/K8T890 South]
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller 
(rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge 
[KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 
AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address 
Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM 
Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] 
(rev a1) 

Maybe this can be of any use for erik and the people working in 9load and Plan 
9's kernel.
For now that is the only thing I can do, test and report... I hope in the 
future to be of more help.

When I have time I will try installing Plan 9 in the other machine that fails 
with PBSR...
(an old PentiumIII).

Regards,
trebol.



Re: [9fans] PBSR...EI

2013-06-11 Thread erik quanstrom
> Maybe this can be of any use for erik and the people working in 9load
> and Plan 9's kernel.  For now that is the only thing I can do, test
> and report...  I hope in the future to be of more help.

ah, so the issue is that 9load (on the default install cd) and the
non-mp kernel 9pccd have some sort of malfunction.  i'm glad you
tracked this down.

there is also the 9atom.nboot cd which uses iplpxe and not 9load.
there have been reports of issues with this install method, but it
might be worth a shot.  this install should support usb.

also,
> This is the linux's lspci output: 00:00.0 Host bridge: VIA
for future reference, pci(8) output is preferred if plan 9 is
already booting.  :-)

- erik



[9fans] /dev/draw/new and /dev/draw/n/ctl

2013-06-11 Thread Jeremy Jackins
from draw(3):

"Each client of the device connects by opening /dev/draw/new and
reading 12 strings, each 11 characters wide followed by a blank: the
connection number (n), the image id (q.v.)  of the display image
(always zero), the channel format of the image, the min.x, min.y,
max.x, and max.y of the display image, and the min.x, min.y, max.x,
and max.y of the clipping rectangle."

After acknowledging that there are 12 strings, it only describes 11.
What is the number that comes between the channel format and min.x?



Re: [9fans] /dev/draw/new and /dev/draw/n/ctl

2013-06-11 Thread Federico G. Benavento
it's "repl", meaning that if it's non zero the image gets replicated when
used as source.
a better explanation can be found in draw(2).


On Wed, Jun 12, 2013 at 12:56 AM, Jeremy Jackins wrote:

> from draw(3):
>
> "Each client of the device connects by opening /dev/draw/new and
> reading 12 strings, each 11 characters wide followed by a blank: the
> connection number (n), the image id (q.v.)  of the display image
> (always zero), the channel format of the image, the min.x, min.y,
> max.x, and max.y of the display image, and the min.x, min.y, max.x,
> and max.y of the clipping rectangle."
>
> After acknowledging that there are 12 strings, it only describes 11.
> What is the number that comes between the channel format and min.x?
>
>


-- 
Federico G. Benavento


Re: [9fans] PBSR...EI

2013-06-11 Thread lucio
> ah, so the issue is that 9load (on the default install cd) and the
> non-mp kernel 9pccd have some sort of malfunction.  i'm glad you
> tracked this down.

Yes, I noted a similar message:

PBS...EI

(unless my memory fails me) even using the Bell Labs release on
VMware, so I reverted to the most recent bootable disk I could find.

I don't know when the problem started, it's been a long time since a
booted from a CD.

++L




Re: [9fans] PBSR...EI

2013-06-11 Thread erik quanstrom
> Yes, I noted a similar message:
> 
>   PBS...EI
> 
> (unless my memory fails me) even using the Bell Labs release on
> VMware, so I reverted to the most recent bootable disk I could find.
> 
> I don't know when the problem started, it's been a long time since a
> booted from a CD.

totally seperate issue.  i've only seen the 9atom issue with via chipsets.

- erik