Subject: Diskless systems
To: None <port-i386@netbsd.org>
From: Mark Randelhoff <MarkR@cat.co.za>
List: port-i386
Date: 09/01/1999 09:10:41
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_001_01BEF449.1F96FBA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=A0
Hi
I am trying to setup a diskless 1.4 i386 system using a 3COM
3C905C-TX-M,=20
with a lanworks bootware rom.=A0 I have installed a bootp server, and
enabled=20
TFTP but the response from the ROM is :
"File transfer error, image file too large for low memory".
=A0
Has anyone had experience with setting up a diskless system on a PC?
=A0
Am I following the correct approach?
=A0
The smallest kernel I have managed to generate is about 890K, with
bootp, nfs support, ide,=20
keyboard and wscons support. Does this seem about right?
=A0
Is there a utility which will allow me to break up a kernel into =
smaller
loadable portions for the=20
bootrom? Apparently linux use something like this.
=A0
Kind regards
Mark
=A0

------ =_NextPart_001_01BEF449.1F96FBA0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">



<META content='"MSHTML 4.72.3110.7"' name=GENERATOR>
</HEAD>
<BODY bgColor=#c0c0c0>
<DIV>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2>Hi</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>I am 
trying to setup a diskless 1.4 i386 system using a 3COM 3C905C-TX-M, 
</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>with a 
lanworks bootware rom.&nbsp; I have installed a bootp server, and enabled 
</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>TFTP 
but the response from the ROM is :</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2>&quot;File transfer error, image file too large for low 
memory&quot;.</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>Has 
anyone had experience with setting up a diskless system on a 
PC?</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>Am I 
following the correct approach?</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>The 
smallest kernel I have managed to generate is about 890K, with bootp, nfs 
support, ide, </FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2>keyboard and wscons support. Does this seem about 
right?</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>Is 
there a utility which will allow me to break up a kernel into smaller loadable 
portions for the </FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2>bootrom? Apparently linux use something like this.</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial size=2>Kind 
regards</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN><SPAN class=900415006-01091999><FONT color=#000000 
face=Arial size=2>Mark</FONT></SPAN></DIV>
<DIV><SPAN class=900415006-01091999><FONT color=#000000 face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

------ =_NextPart_001_01BEF449.1F96FBA0--