On Sat, 2003-10-11 at 00:03, Cameron Mac Millan wrote:
> >> bootp()/tftproot/tftpboot.img
> No server for /tftproot/tftpboot.img.
> Your netaddr environment variable may be set incorrectly, or
> the net may be too busy for a connection to be made.
> Unable to execute bootp()/tftproot/tftpboot.img
I unset netaddr.
And using debian's DHCPd, I had this in my config:
...
range dynamic-bootp 192.168.1.200 192.168.1.250;
...
host johnson {
hardware ethernet 08:00:69:09:55:7c;
fixed-address 192.168.1.107;
}
...
There were also some values that had to be inserted into the /proc
filesystem on the DHCP server. For the record I'm also using atftpd.
`bootp()/tftpboot/tftpboot.img` then worked fine.
However, something to note, putting the tftpboot.img file into a
sub-directory of /tftpboot caused random timeout errors some 75% of the
time, I cannot offer an explaination for that.
One other thing you need to be aware of. Your HDDs are going to need an
SGI disklabel on them before you can fdisk them appropriately. Newer
versions of fdisk and parted can do this, however I seem to recall the
version in tftpboot.img is not new enough. There is also an IRIX tool to
mark disks with the SGI disklabel, but I forget it's name.
--davyd
--
http://davyd.ucc.asn.au/
PGP Fingerprint <http://davyd.ucc.asn.au/pgp>
08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA
Attachment:
signature.asc
Description: This is a digitally signed message part