9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "\"Rodolfo \\\"kix\\\" Garci­a\"" <kix@kix.es>
To: 9fans@cse.psu.edu
Subject: [9fans] CPU Server
Date: Sun, 23 Dec 2007 00:12:07 +0100	[thread overview]
Message-ID: <476D99C7.6050101@kix.es> (raw)

Hi,

the page Configuring_a_Standalone_CPU_Server is not correct and the 
people can have problems to configure a CPU Server. Examples:

1 - - -

"cd /cfg; mkdir $sysname; dircp example $sysname
(...)
At the end of cpurc.local ..."

The cpurc.local is only in /bin, not in /cfg/example/

2 - - -

'cat /dev/drivers' will list the available devices. In this case we have 
m (mouse), i (draw), S (sd - disk), and t (uart - serial); if you get 
errors about /dev/realmode, include P in this list:

for (i in m i S t)
    bind -a '#'^$i /dev >/dev/null >[2=1]

Is OK, but ... why is not it in the file like in /bin/termrc?

3 - - -

Uncomment the two lines indicated in cpurc to enable the authentication 
functions:

# auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null >[2=1]
# auth/cron >>/sys/log/cron >[2=1] &

This lines are not in the /cfg/$sysname/cpurc file

4 - - -

Add these lines to /cfg/$sysname/cpustart

The cpustart file do not exists

 - - -

Thanks.


             reply	other threads:[~2007-12-22 23:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 23:12 "Rodolfo \"kix\" Garci­a" [this message]
2007-12-22 23:15 ` Iruata Souza
2007-12-23  3:13 ` John Soros
2007-12-23  3:35   ` erik quanstrom
2007-12-27 16:16     ` "Rodolfo \"kix\" Garci­a"
  -- strict thread matches above, loose matches on Subject: below --
2007-12-28  3:09 Joshua Wood
2007-08-15 22:13 Rodolfo (kix)
2007-08-16  1:26 ` geoff
2007-08-16 13:18   ` rob
2007-08-16 13:29     ` erik quanstrom
2004-02-07  0:24 [9fans] cpu server vdharani
2004-02-06 22:50 ` Jim Choate
2004-02-07  3:41   ` Bruce Ellis
2004-02-07 14:48     ` Jim Choate
2004-02-07 15:21       ` Bruce Ellis
2004-02-07 16:05         ` Jim Choate
2004-02-07 19:54           ` Charles Forsyth
2004-02-07 22:26             ` a
2004-02-07 23:16               ` andrey mirtchovski
2004-02-09 17:47                 ` rog
2004-02-09 18:19                   ` andrey mirtchovski
2004-02-09 18:43                     ` rog
2004-02-09 18:49                       ` andrey mirtchovski
2004-02-09 18:49                     ` rog
2004-02-09 18:50                       ` andrey mirtchovski
2004-02-09 19:32                     ` 9nut
2004-02-09 18:44                       ` andrey mirtchovski
2004-02-10  1:38                     ` Kenji Okamoto
2004-02-10  1:40                       ` David Presotto
2004-02-10  1:50                       ` boyd, rounin
2004-02-10  1:11                         ` andrey mirtchovski
2004-02-10  3:03                           ` Lyndon Nerenberg
2004-02-10  5:00                           ` Geoff Collyer
2004-02-11  3:14                             ` Jack Johnson
2004-02-08  1:04               ` Taj Khattra
2004-02-08  1:20             ` Jim Choate
2004-02-08  2:56               ` Bruce Ellis
2004-02-08  2:40           ` Bruce Ellis
2004-02-07  8:18   ` andrey mirtchovski
2004-02-07 11:12     ` Bruce Ellis
2004-02-07 11:33     ` a
2004-02-07 13:30     ` boyd, rounin
2004-02-07 13:38     ` boyd, rounin
2004-02-07 14:51     ` Jim Choate
1998-07-13 15:46 [9fans] CPU Server Franklin

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=476D99C7.6050101@kix.es \
    --to=kix@kix.es \
    --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).