From: Phillip Stanley-Marbell <narteh@ece.rutgers.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] upas, cron and CPU servers
Date: Wed, 21 Jun 2000 23:12:09 -0400 [thread overview]
Message-ID: <Pine.SOL.4.10.10006212310510.18516-100000@brainstorm.rutgers.edu> (raw)
I successfully set up a CPU server, though I still need to tweak some
configs. Here are some notes and questions:
(1) When you first boot up a CPU server after recompiling the cpu server
kernel, and are prompted for hostdomain, DON'T just hit <return> !!!
(2) /sys/cron/upas -- owned by 'sys' in default config, should be owned by
upas ??
(3) /sys/log/cron is absent -- auth/cron tries to append to it and starts
gavoreeting bloody murder.
(4) start.xxx says to do
for (i in '#m' '#i' '#S' '#t')
bind -a $i /dev >/dev/null >[2]/dev/null
saying "... if you leave out '#m', rio will not start...", but rio won't
start anyway, since cpurc has no calls to aux/mouse and aux/vga. Right ?
Anyway, adding aux/mouse and aux/vga -l your.vga.size seems to do it.
-
pip
reply other threads:[~2000-06-22 3:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.SOL.4.10.10006212310510.18516-100000@brainstorm.rutgers.edu \
--to=narteh@ece.rutgers.edu \
--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).