From: Dave Iafrate - CSCI/F1997 <diafrate@scs.ryerson.ca>
To: forsyth@caldo.demon.co.uk
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] Terminal Problem
Date: Mon, 16 Apr 2001 14:19:47 -0400 [thread overview]
Message-ID: <Pine.GSO.4.21.0104161417140.9857-110000@jupiter.scs.ryerson.ca> (raw)
In-Reply-To: <20010416181444.BBA20199FA@mail.cse.psu.edu>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1684 bytes --]
Thanks but i dont think that is what im looking for.
What we have is this:
NO DHCP, NO TFTP services.
The fileserver is up and the cpu server is booting locally(sdC0)
all i need to do is connect the terminals and another cpu server.
I started using the "Customizing a Fileserver" description but this
has not worked.
Id rather boot both with a floppy, how do i do this, i think my ndb is
fine currently since the fileserver is connecting fine.
On Mon, 16 Apr 2001 forsyth@caldo.demon.co.uk wrote:
> Date: Mon, 16 Apr 2001 19:12:00 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] Terminal Problem
>
> the root can come from the file server -- answer il to root from ... -- but the file server itself doesn't
> boot terminals using bootp/tftpd. that's done by a cpu server running ip/dhcpd and ip/tftpd.
> see the commented-out lines in /rc/bin/cpurc.
> furthermore the terminals need to be set for booting in /lib/ndb (eg, /lib/ndb/local),
> for instance
>
> ip=200.1.1.46 ether=00a0cc3cd489 sys=vivido
> dom=vivido.vitanuova.com
> bootf=/386/9pc
> proto=il
>
> the ether= and bootf= are needed for booting; proto=il is needed to cause the
> terminal once booted to use il for other services (such as cpu).
> if ip/dhcpd is running on a cpu server, you can look at /sys/log/ipboot
> to track its actions.
>
> for the above entry to work, the /lib/ndb/local also should have fs= and auth=
> entries at the subnet or network level. (you can include them per terminal, but
> that's normally done only if they need to be different from the default configuration.)
>
>
[-- Attachment #2: Type: MESSAGE/RFC822, Size: 1737 bytes --]
Received: from tele-punt-22.mail.demon.net ([194.217.242.7]) by lavoro; Mon Apr 16 18:59:54 BST 2001
Received: from punt-2.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk
id 987444282:20:19601:0; Mon, 16 Apr 2001 18:04:42 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-2.mail.demon.net
id aa2019420; 16 Apr 2001 18:04 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id C0D0019A08; Mon, 16 Apr 2001 14:04:11 -0400 (EDT)
Received: from jupiter.scs.ryerson.ca (unknown [141.117.150.31])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1E1A5199E4
for <9fans@cse.psu.edu>; Mon, 16 Apr 2001 14:03:07 -0400 (EDT)
Received: (from localhost user: 'diafrate', uid#26582)
by jupiter.scs.ryerson.ca with ESMTP id <S446801AbRDPSC6>;
Mon, 16 Apr 2001 14:02:58 -0400
From: Dave Iafrate - CSCI/F1997 <diafrate@scs.ryerson.ca>
To: 9fans@cse.psu.edu
Message-ID: <Pine.GSO.4.21.0104161401140.7609-100000@jupiter.scs.ryerson.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [9fans] Terminal Problem
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Mon, 16 Apr 2001 14:02:58 -0400 (EDT)
We seem to have a problem with out terminal setup. Bootp times out when
we try to boot from ether0. Do we have to compile a kernel for
this. We're booting from a floppy trying to boot from the file server.
Thanks in advance
From: Dave Iafrate - CSCI/F1997 <diafrate@scs.ryerson.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] Terminal Problem
Date: Mon, 16 Apr 2001 14:02:58 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0104161401140.7609-100000@jupiter.scs.ryerson.ca>
We seem to have a problem with out terminal setup. Bootp times out when
we try to boot from ether0. Do we have to compile a kernel for
this. We're booting from a floppy trying to boot from the file server.
Thanks in advance
next prev parent reply other threads:[~2001-04-16 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 18:12 forsyth
2001-04-16 18:19 ` Dave Iafrate - CSCI/F1997 [this message]
-- 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 21:43 forsyth
2001-04-17 14:40 ` 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=Pine.GSO.4.21.0104161417140.9857-110000@jupiter.scs.ryerson.ca \
--to=diafrate@scs.ryerson.ca \
--cc=9fans@cse.psu.edu \
--cc=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).