9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lloyd M Caldwell <lmc@xmission.com>
To: 9fans@cse.psu.edu, lmc@xmission.com
Subject: [9fans] really basic (stupid) questions, re: beginning sys admin.
Date: Sat, 21 Oct 2006 12:08:08 -0600	[thread overview]
Message-ID: <453A6208.7090108@xmission.com> (raw)

Hello,

This is fairly long so tia if you choose to continue reading.

I have used, administered and programmed Un*x's for many years, this 
seems to be more of a hinderance then help.

To prove how stupid I am, it took me 3 weeks to figure out how to enter 
text into sam. If you invoke 'sam file.txt' you see nothing of the file 
and all the typing in sam's control window results in nothing. Maybe if 
sam had used the same "new window" icon as rio, I might have figured out 
more quickly that you must make a new window inside an existing window 
to actually see the text file contents.  This, despite having read of 
the recursive rio capability and seeing the figures in Rob Pike's paper 
on sam. Acme is too much of a commitment, besides the initial glenda 
login acme window message says there are two columns and my systems 
glenda,acme window has three columns.

My system is installed from cdrom, release 4, march 23rd, fossil+venti.

Q1) how to "logout" of the fossil+venti console? In my experience, open 
console access to servers is bad (insecure).  Even though it is stated 
numerous places that there is no "root" account.  Apparently physical 
access to the console IS "root"?

Q2) It is stated that you can't run both an authentication server and a 
file server on the same node so how do I get the 'factotum' stuff going 
on a standalone file-server/terminal/cpu-server (the cdrom installed 
system)?

Q3) I have made a new user, how would I set this new user's (and 
glenda's) password?  Again on the standalone cdrom installed system.

Q4) on Un*x, after entering a man page command I can search for a 
specific word with /word in a terminal emulator window. How do I perform 
the same thing in a rio/rc window (please don't answer "use acme")?

Q5) rebooting seems to be the main method to re-configure the system or 
ones access rights.  In Un*x logging in/out and using su and 
kill/restart allowed one to choose the role and modify the system 
configuration without rebooting (I have a system running with uptime 
over 3 years). Is rebooting the method for performing these tasks?  This 
seems rather draconian (imo).

Any help is greatly appreciated.

tia
regards
Lloyd M Caldwell
lmc@xmission.com

ps: i have an ac97 audio driver written and working on a via-epia 
motherboard? anyone interested in trying this?


             reply	other threads:[~2006-10-21 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 18:08 Lloyd M Caldwell [this message]
2006-10-21 18:26 ` andrey mirtchovski
2006-10-21 18:32 ` andrey mirtchovski
2006-10-22 15:26   ` erik quanstrom
2006-10-22 15:46     ` andrey mirtchovski
2006-10-21 18:39 ` Sascha Retzki
2006-10-21 19:25 ` Steve Simon
2006-10-22 15:07 ` erik quanstrom

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=453A6208.7090108@xmission.com \
    --to=lmc@xmission.com \
    --cc=9fans@cse.psu.edu \
    /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).