OK, so there's a general consensus about *when* to run `plumber`:
Run early. Run often, as needed.
Now I'm wondering about *where* to run `plumber`.
On Windows, I've done stuff like this before:
$env:PASS = 'p9qemu-demo'; drawterm.exe -h 127.0.0.1 -a 127.0.0.1
-u glenda -c 'plumber; rio' &
And that works fine.
I run 9front.
These are the steps I take
to make a stock-9front install
accept drawterm connections:
https://github.com/dharmatech/9front-notes/blob/main/docs/allow-drawterm.md
As you can see from there, I put this in `plan9.ini`:
service=cpu
Well, `/usr/glenda/lib/profile` doesn't run `plumber` for the `cpu` case:
bind -a $home/bin/rc /bin
bind -a $home/bin/$cputype /bin
if(! syscall create /tmp/xxx 1 0666 >[2]/dev/null)
ramfs # in case we're running off a cd
font=/lib/font/bit/vga/unicode.font
switch($service){
case terminal
if(! webcookies >[2]/dev/null)
webcookies -f /tmp/webcookies
webfs
plumber
echo -n accelerated > '#m/mousectl'
echo -n 'res 3' > '#m/mousectl'
prompt=('term% ' ' ')
fn term%{ $* }
rio -i riostart
case cpu
bind /mnt/term/dev/cons /dev/cons
bind -q /mnt/term/dev/consctl /dev/consctl
>[2] /dev/null {
cp /dev/sysname /mnt/term/dev/label
if(test -s /mnt/term/env/wsys)
wsys=/mnt/term^`{cat /mnt/term/env/wsys}
}
bind -a /mnt/term/dev /dev
prompt=('cpu% ' ' ')
fn cpu%{ $* }
case con
prompt=('cpu% ' ' ')
}
It does run it for the `terminal` case.
So I *could* just throw another call to `plumber` in
`/usr/glenda/lib/profile` somewhere.
But I'm wondering, is that the suggested place to put it?
What do y'all do?
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tb77bce4699e6922a-Mf9443c8d64a6f95ba5a6439c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
