Re: [9fans] Terminal Problem

Re: [9fans] Terminal Problem

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 149 bytes --]

if you say mk 'CONF=xyz' it creates 9xyz and mk 'CONF=xyz' install copies that to /386/9xyz
so mk 'CONF=pccpu'  is needed to create /386/9pccpu.


[-- Attachment #2: Type: message/rfc822, Size: 2129 bytes --]

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: Tue, 17 Apr 2001 10:40:54 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0104171039100.18551-100000@jupiter.scs.ryerson.ca>

On Mon, 16 Apr 2001 forsyth@caldo.demon.co.uk wrote:

> Date: Mon, 16 Apr 2001 22:43:15 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu

> 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
>
which one is which here?
do i mk 'CONF=pc' install and move it to /386/9pc ??
and then do mk 'CONF=pcdisk' install and move to 9pccpu ???

im now using dhcp so here goes...

Re: [9fans] Terminal Problem

[Dave Iafrate - CSCI/F1997]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 536 bytes --]

thanks just got that..

i compiled the pc no problem but when i do the pcdisk we get an
insufficient memory fault???

what the heck is this?
On Tue, 17 Apr 2001 forsyth@caldo.demon.co.uk wrote:

> Date: Tue, 17 Apr 2001 15:52:29 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] Terminal Problem
>
> if you say mk 'CONF=xyz' it creates 9xyz and mk 'CONF=xyz' install copies that to /386/9xyz
> so mk 'CONF=pccpu'  is needed to create /386/9pccpu.
>
>

[-- Attachment #2: Type: MESSAGE/RFC822, Size: 2129 bytes --]

Received: from tele-punt-22.mail.demon.net ([194.217.242.7]) by lavoro; Tue Apr 17 15:44:47 BST 2001
Received: from punt-2.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk
          id 987518609:20:10243:2; Tue, 17 Apr 2001 14:43:29 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-2.mail.demon.net
           id aa2009612; 17 Apr 2001 14:43 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id 1751819A45; Tue, 17 Apr 2001 10:42:12 -0400 (EDT)
Received: from jupiter.scs.ryerson.ca (unknown [141.117.150.31])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 8422919A00
	for <9fans@cse.psu.edu>; Tue, 17 Apr 2001 10:41:09 -0400 (EDT)
Received: (from localhost user: 'diafrate', uid#26582)
	by jupiter.scs.ryerson.ca with ESMTP id <S446851AbRDQOky>;
	Tue, 17 Apr 2001 10:40:54 -0400
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
In-Reply-To: <20010416214557.509F819A14@mail.cse.psu.edu>
Message-ID: <Pine.GSO.4.21.0104171039100.18551-100000@jupiter.scs.ryerson.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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: Tue, 17 Apr 2001 10:40:54 -0400 (EDT)

On Mon, 16 Apr 2001 forsyth@caldo.demon.co.uk wrote:

> Date: Mon, 16 Apr 2001 22:43:15 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu

> 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
>
which one is which here?
do i mk 'CONF=pc' install and move it to /386/9pc ??
and then do mk 'CONF=pcdisk' install and move to 9pccpu ???

im now using dhcp so here goes...



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: Tue, 17 Apr 2001 10:40:54 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0104171039100.18551-100000@jupiter.scs.ryerson.ca>

On Mon, 16 Apr 2001 forsyth@caldo.demon.co.uk wrote:

> Date: Mon, 16 Apr 2001 22:43:15 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu

> 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
>
which one is which here?
do i mk 'CONF=pc' install and move it to /386/9pc ??
and then do mk 'CONF=pcdisk' install and move to 9pccpu ???

im now using dhcp so here goes...

Re: [9fans] Terminal Problem

[Dave Iafrate - CSCI/F1997]

On Mon, 16 Apr 2001 forsyth@caldo.demon.co.uk wrote:

> Date: Mon, 16 Apr 2001 22:43:15 +0100
> From: forsyth@caldo.demon.co.uk
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu

> 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
>
which one is which here?
do i mk 'CONF=pc' install and move it to /386/9pc ??
and then do mk 'CONF=pcdisk' install and move to 9pccpu ???

im now using dhcp so here goes...

Re: [9fans] Terminal Problem

[forsyth]

>>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

Re: [9fans] Terminal Problem

[Dave Iafrate - CSCI/F1997]

[-- 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

Re: [9fans] Terminal Problem

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

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 --]

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

[9fans] Terminal Problem

[Dave Iafrate - CSCI/F1997]

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