hola,

I think most of your question has been already answered, but anyways

On 6/7/07, Frank Lenaerts <[EMAIL PROTECTED]> wrote:
Hi,

After installing Plan 9 on a standalone machine, adding a user,
configuring the network, wandering around a bit, reading some
manpages, ... I have a few questions for which I didn't find an
answer. They seem stupid, so I might have missed some important
documentation. If so, just point me to the docs, if not, an
explanation is welcome;-)


welcome to Plan 9!


- Is there something like "su" to let me be someone else in another
  window?

why do you want to be someone else? isn't good enough being yourself? ;)

- Can I somehow lock the screen?


the screen lock prg the guys mentioned is at /n/sources/patch/sorry/robs-bits/

- I noticed that users glenda, adm and none don't have a password (by
  default). These users can however change the timezone, reboot the
  machine, ...

password to access the machine you just booted?
of course you can run rob's lock prg in your termrc, but what would be
the point,
stopping your children from playing with Plan 9?, but that could be a great
learning experience for them :)

- What is the purpose of the different users like (a) glenda (seems to
  be hostowner, can create users, etc.), (b) adm, (c) none?

  [*] is part of the sys group but could not change /rc/bin/termrc
  because he couldn't write to /tmp (no profile like a normal user
  binding /tmp to /home/tmp; I suppose he can do this interactively)


you didn't run /sys/lib/newuser after you created your user, that's why
you didn't get a $home/lib/profile that binds $home/tmp over /tmp


- Is there something like virtual consoles to allow e.g.  several
  users to login simultaneously and each starting a graphical
  environment?

you'd better make your machine into a cpu/auth server or allow drawterming
to it.

- Is there something like a plain "mount" command, just to see all
  bindings?

ns(1)


cu,

cu == means "butt" in some weird latin language

have a good day

--
Federico G. Benavento

Reply via email to