9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Adventures of a home user
Date: Tue, 21 Apr 2009 08:06:37 -0400	[thread overview]
Message-ID: <b817308890c73bbdb1166dfbcc4efcdd@quanstro.net> (raw)
In-Reply-To: <ea634cc80904202055q6dac2182h8edb1d980e1d2c66@mail.gmail.com>

>
> - and how to change to a different user without rebooting.

there are two answers to this question, depending on if you
have a cpu server or a terminal
* terminal.  don't do that.  the plan 9 model is that you really
own the hardware and the terminal is not intended to be
multi-user.  so you do need to reboot to change users.

(okay, i realize that you can start a bunch of services on a
terminal and approximate a cpu server, and if you are logged
in as an acceptable hostowner according to the auth server,
things might work out.  but that's not part of the standard
model.)

* cpu server.  the hostowner is fixed at boot.  if you have
the credentials for any user you can cpu(1) in as that user.

i'm speculating on the design of the auth system.  i wasn't
there so i could be wrong.  but in order to have a terminal
that many people could log into would require either
(a) killing off the original factotum on logout and changing
eve back to bootes or something.  and beware the 1001 places
that stash eve somewhere.
(b) the terminal running as the auth server's eve, requiring
that the auth server's key be present when the terminal boots.
since the user really owns a terminals hardware, this couldn't
be very secure unless the administator typed in the password
on every boot.

- erik



  reply	other threads:[~2009-04-21 12:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  1:01 Jim Habegger
2009-04-19  1:05 ` john
2009-04-19  1:08 ` erik quanstrom
2009-04-19 10:15 ` yy
2009-04-19 14:16 ` Jim Habegger
2009-04-19 14:34   ` erik quanstrom
2009-04-19 14:43   ` Anthony Sorace
2009-04-19 15:37   ` Jim Habegger
2009-04-20 10:42     ` Balwinder S Dheeman
2009-04-21  7:55       ` Jim Habegger
2009-04-21 22:03         ` blstuart
2009-04-20  5:01 ` Jim Habegger
2009-04-20  5:13   ` andrey mirtchovski
2009-04-20  5:38     ` André Günther
2009-04-20  5:22   ` Federico G. Benavento
2009-04-20  7:14 ` Jim Habegger
2009-04-21  3:38 ` Jim Habegger
2009-04-21  5:14   ` john
2009-04-21  7:05   ` Federico G. Benavento
2009-04-21  3:52 ` Jim Habegger
2009-04-21  3:55   ` Jim Habegger
2009-04-21 12:06     ` erik quanstrom [this message]
2009-04-21 22:13       ` blstuart
2009-04-21  6:02 ` Jim Habegger
2009-04-21  6:31   ` Anthony Sorace
2009-04-21  6:59     ` Jim Habegger
2009-04-21  9:10 ` Jim Habegger
2009-04-21 11:26   ` erik quanstrom
2009-04-21 15:26   ` john
2009-04-21 15:34     ` erik quanstrom
2009-04-21 20:01 ` Jim Habegger
2009-04-21 21:28   ` Karin Willers
2009-04-21 22:23   ` blstuart
2009-04-22  0:29     ` john
2009-04-22  1:07       ` Jim Habegger
2009-04-23  9:12 ` Jim Habegger
2009-04-23 10:23   ` Eris Discordia
2009-04-23 15:55     ` maht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b817308890c73bbdb1166dfbcc4efcdd@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).