From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Terminal Problem
Date: Mon, 16 Apr 2001 22:43:15 +0100 [thread overview]
Message-ID: <20010416214557.509F819A14@mail.cse.psu.edu> (raw)
>>Thanks but i dont think that is what im looking for.
>>What we have is this:
>>NO DHCP, NO TFTP services.
well, then booting ether0 won't work unless something else
on the network provides those services. given that you've got
at least one cpu server to act as authentication server, why not
have it boot the terminals as well? in which case, it will need
to run those servers (just uncomment the lines in cpurc).
you do need the files on the fileserver in /386 that you want
the terminals to run. cd /sys/src/9/pc; mk 'CONF=pc' install; mk 'CONF=pcdisk' install
next reply other threads:[~2001-04-16 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 21:43 forsyth [this message]
2001-04-17 14:40 ` Dave Iafrate - CSCI/F1997
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 14:52 forsyth
2001-04-17 15:02 ` Dave Iafrate - CSCI/F1997
2001-04-16 18:12 forsyth
2001-04-16 18:19 ` Dave Iafrate - CSCI/F1997
2001-04-16 18:02 Dave Iafrate - CSCI/F1997
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=20010416214557.509F819A14@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).