9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Julius Schmidt <aiju@phicode.de>
To: 9front <9front@googlegroups.com>
Subject: Re: Problem during install
Date: Thu, 21 Jul 2011 10:34:49 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1107211026450.32694@localhost> (raw)
In-Reply-To: <6a9f9e5b-3d64-41ee-926f-f8924ec528a5@q5g2000yqj.googlegroups.com>

> What is for 9front the difference between a terminal and a cpu
> installation (this s asked during installation)
A (standalone) terminal is just a single standalone machine.
A CPU server is a machine where users log in and work on.
Read /sys/doc/9.ps ;)

> After install and a new boot, I can only log in as Glenda? Is Glenda
> root?
Yes, you can only log in as Glenda.
See http://code.google.com/p/plan9front/wiki/admin for creating more
users.

No, Glenda is not root, the concept of a superuser is foreign to Plan 9.
All direct hardware access is restricted to the so-called hostowner.
On terminals the hostowner is whoever logged in.
On CPU servers the hostowner is specified as a configuration option, the
default is glenda.
There are two groups, sys and adm, which define users with elevated
privileges.
Users in sys may change system files and users in adm may change
authentication data.
(This is just because sys is the group of all system files and adm is
the group of /adm)

aiju

  reply	other threads:[~2011-07-21  8:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  6:42 neo67
2011-07-20  7:08 ` neo67
2011-07-20  7:54   ` cinap_lenrek
2011-07-20  8:55     ` neo67
2011-07-20 10:11       ` cinap_lenrek
2011-07-21  6:49     ` neo67
2011-07-21  8:34       ` Julius Schmidt [this message]
2011-07-21 11:03         ` neo67
2011-07-21 11:46           ` Julius Schmidt
2011-07-21 12:09             ` neo67

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=alpine.LNX.2.00.1107211026450.32694@localhost \
    --to=aiju@phicode.de \
    --cc=9front@googlegroups.com \
    /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).