From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] Building a new Plan 9 system.
Date: Thu, 1 Oct 1998 10:29:48 +0100 [thread overview]
Message-ID: <19981001092948.4ZEWeG69RUghlOe7wn23muT3_Uvn7BOnkp05maOYea8@z> (raw)
>>I was interested to read the comments that the CPU server and terminal
>>server don't need hard drives. I was wondering how hard it is to then
>>use the terminal to install the file server software? But in any case,
a little more elaboration might be helpful.
i was trying to remember how the 4 diskette set was organised.
using that, i suppose you would need to unpack the diskettes into a dos
partition somewhere to provide the environment to make the file
server boot diskette and unload the CDROM.
with your configuration, i'd probably have booted the cpu server
as a terminal for initial installation and left the `real' terminal
discless. (i'll discuss that in a moment.) once you've got a file
server loaded, the terminals can indeed be discless.
connect it to the network, make an entry in /lib/ndb/local, and boot.
(you can also boot, then make the entry in /lib/ndb/local if you
load the kernel from floppy not over the network.)
contrary to what i said before, it can be (marginally) helpful to have a disc
on the cpu server because the nvram partition lives there,
making reboots a little more automatic (though i still don't bother).
you can also use it for local paging space.
a disc on the terminal could be used for dual-boot
with windows or linux if you need them, for paging space for plan9, for the
cache file system if you're using the cable modem to a system
at work, or for local kfs storage.
i still prefer to have discless terminals when i can,
partly because it demonstrates that the network computer was easily
but more usefully anticipated by plan9's arrangement;
it is slightly cheaper to build a new terminal or server(though not by as much as it once did);
one less thing is needed when recycling cast-off 486 machines as utility cpu servers
or cheap terminals;
but mainly because there is less noise.
when i nevertheless need a disc on a terminal for windows/linux/xBSD dual boot,
or for experiment (eg, with scsi cards), and the drive supports it,
i set spindowntime in plan9.ini (for eide drives)
or use scuzz (for scsi drives) to have the system shut down the drive.
my terminal at home has indeed got a drive
next reply other threads:[~1998-10-01 9:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-01 9:29 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-10-05 13:59 G.David
1998-10-05 7:46 Nigel
1998-10-01 9:40 forsyth
1998-10-01 9:02 forsyth
1998-09-30 23:06 James
1998-09-26 10:00 forsyth
1998-09-26 9:39 forsyth
1998-09-26 3:43 Scott
1998-09-26 3:36 Scott
1998-09-26 2:17 James
1998-09-25 8:59 miller
1998-09-25 6:04 James
1998-09-24 1:37 forsyth
1998-09-21 12:03 jmk
1998-09-21 8:24 Scott
1998-09-21 7:38 James
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=19981001092948.4ZEWeG69RUghlOe7wn23muT3_Uvn7BOnkp05maOYea8@z \
--to=forsyth@caldo.demon.co.uk \
/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).