Subject: Re: Okay, I give up...
To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
From: William Duke <wduke@cogeco.ca>
List: port-mac68k
Date: 10/30/2005 14:58:28
> From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
> Date: Sun, 30 Oct 2005 21:03:14 +0200
> To: William Duke <wduke@cogeco.ca>
> Cc: <port-mac68k@NetBSD.org>
> Subject: Re: Okay, I give up...
> 
> At 13:08 Uhr -0500 30.10.2005, William Duke wrote:
>> You're right.   The bottom line is that it *will* work. I just have to be
>> a little more patient and figure out why it isn't working. Then I have to
>> make the corrective actions.
> 
> That's the right spirit!  ;)
> 
>> Okay, I'm running DHCP on my router so I'm assuming that I'll have to
>> disable DHCP service on my router in order to use it on a BSD machine. You
>> can't run two different DHCP servers on the same subnet, right?
> 
> Right. Or rather, the servers won't mind, but the clients will show
> interesting behaviour.
> 
>> Now, I've read that the bootp daemon will not run while dhcp is running,
>> does this mean the dhcp daemon on the server machine?   Or do I have to
>> completely disable dhcp on the entire network?
> 
> The ISC dhcpd that ships with NetBSD does both dhcp and bootp. So, it's a
> one-stop solution.
> 
>> I think that I could be having a problem there because I've been using dhcp
>> to configure the tcp/ip settings for my Mac OS running computers. I just
>> never had any reason to manually configure the tcp/ip settings on my mac os
>> machines before.
> 
> In the dhcpd.conf, either link ip addresses to the ethernet MAC address of
> the machine, or set up an ip range for unregistered clients. The latter
> will most likely emulate your router's behaviour.
> 
>> So, would you suggest that I manually configure my Mac OS machines and
>> disable dhcp on my router?   Also, for my boot server, which do you prefer,
>> bootp or dhcp?
> 
> That depends on the clients' needs. dhcpd, as I said, can do both.
> 
>> I am having one rather persistent problem with the hn: line in my
>> etc/bootparams file.
> 
> What client wants the bootparamd?
> 
> hauke

The Indy wants the bootparamd.   When I type "boot" from the Indy's prom
prompt, it finds the server and initiates the request, but there's a problem
with the bootparams file.   The LCIII console says something about syntax on
the hn: entry and halts.   The Indy then times out and reports that the
server was either too busy or that the connection was refused.

Basically, the Indy recognizes that the server exists and attempts to
connect to the LCIII.   The LCIII recognizes that the Indy is attempting to
negotiate and looks at the bootparams file.   It appears that the LCIII is
finding the entry for the indy in the bootparams file but is having trouble
with the syntax on the line that designates the boolean hostname assignment.
Everything stops at that point.

I'll give it another try when the sun goes down and I don't have to contend
with the glare on my crt's.

Regards,

William