Under plan9 the user who boots a machine has rights to its filesystem,
so unless you are accessing a remote plan9 file server which is running
an auth server I doubt your problems are to do with administration rights.
Somtimes plan9 will produce slightly misleading error messages, permission
denied might be saying the OS will not allow you to do what you wanted
because it doesn't make sense.
What I suspect is that you didn't chmod your startup (riostart) script
to make it executable?
If this isn't the problem can you cut and paste the exact command that produced
the permission denied error?
I have attached my startup script for interest, it lives in my
$home/bin/rc/startup
(other script names are available).
-Steve
#!/bin/rc
rfork e
scr=(`{cat /dev/draw/new >[2]/dev/null || status=''})
height=$scr(12)
y1=`{echo 'int(' $height '*' 0.12 ')' | hoc}
y2=`{echo 'int(' $height '*' 0.3 ')' | hoc}
y3=`{echo 'int(' $height '*' 0.7 ')' | hoc}
width=$scr(11)
x1=`{echo 'int(' $width '*' 0.1 ')' | hoc}
x2=`{echo $x1 + 1 | hoc}
x3=`{echo 'int(' $x2 + '(' $width '*' 0.5 '))' | hoc}
x4=`{echo $x3 + 1 | hoc}
x6=`{echo $width - $y1 | hoc}
x5=`{echo $x6 - 1 | hoc}
x7=`{echo $width - 1 | hoc}
if(~ $service terminal)
auth/fgui &
if(~ $service terminal && ! ~ $#cpu 0)
window -r 0 0 $x1 $y1 stats -lmei $sysname $cpu
if not
window -r 0 0 $x1 $y1 stats -lmei
window -r $x2 0 $x3 $y1 faces -i
if(cat /dev/volume >[2] /dev/null)
window -r $x4 0 $x5 $y1 audio/tuner
window -r $x6 0 $x7 $y1 clock
window -r $x2 $y2 $x3 $y3 logwin
