Re: 712/60 bootp/dhcp network boot problem
On Fri, Feb 11, 2005 at 06:15:31PM -0600, Larry Crouch wrote:
> Hello,
>
> Hope this is the right list.
I think you might have better luck at debian-hppa@lists.debian.org
Frank
>
> My problem is that I'm having difficulty getting my 712/60 computer to boot over the network.
> The boxes (I have 2) boot fine from their internal hard-drive.
>
> Here's the setup: windows 2000 (192.168.1.2) acting as a proxy for my dial-up.
> hp4 (192.168.1.4) and hp5 (192.168.1.5) are HP 712/60 workstations with 128Mb and 64 MB of memory respectively. Each 712 has a 1 GB hard drive.
>
> First of all, arp -a sees IPs and MAC addresses, ping works fine, smbclient on the 712s sees the windows shares and the windows computer sees the 712s shares, apache, mysql, php works on all machines - in other words all computers are booting and working.
>
> I initially loaded the boxes by loading bootp/dhcp on my windows 2000 computer.
> I'd rather not use the windows computer for booting this time.
>
> Using dselect I have downloaded and installed various packages very successfully. dselect/apt uses the windows proxy.
>
> I loaded dhcp and bootp packages.
> Here is the relavant inetd.conf file:
>
> tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /boot
> bootps dgram udp wait root /usr/sbin/bootpd bootpd bootptab
>
> Here is the bootptab file:
>
> .default:\
> :hd=/boot:bf=lifimage:\
> :sm=255.255.255.0:\
> :td=/boot:\
> :bs=21692:
> hp5:ip=192.168.1.5:ha=0800099359c6:tc=.default:
> hp4:ip=192.168.1.4:ha=0800099359a2:tc=.default:
>
>
> In the /boot directory I have the lifimage file which is 11,106,304 bytes (21,692 for the length parameter).
>
>
>
> Larry
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
Reply to: