Re: Blacklistd Issues - Problem Identified

> On Apr 18, 2023, at 11:46, Norman Gray <gray@nxg.name> wrote:
> 
> 
> Doug, hello.
> 
> On 18 Apr 2023, at 19:18, Doug Hardie wrote:
> 
>> Quick answers as I have to leave very soon.
>> 
>> Blacklistd source is in /usr/src/contrib/blacklistd/bin
>> 
>> Apply the patch there.
>> 
>> To recompile it go to /usr/src/usr.sbin/blacklistd and do the make there.
> 
> Aha!  Thanks.  The stock version builds OK, so ... onward to step 2!
> 
>> To find the new execuitable go to /usr/obj/usr/src/amd64.amd64/usr.sbin/blacklistd and put the blacklistd there into /usr/libexec
> 
> In my install, the products end up in the same directory, rather than in /usr/obj.  I could presumably tweak that (MAKEOBJDIRPREFIX in the environment?), but will forbear to do so for the moment.
> 
> I note Michael's point about the config file format.  I do remember looking in the blacklistd source before, trying to understand how it was parsed (or indeed mis-parsed), and I recall that the parsing was a bit... magic.

I have never seen make build a system component in the source tree.  However, I have only used i386 and amd64 so it's possible some of the other architectures build things differently.  

I had to use blacklistd's debug setting to find out how it was working.  Then I played computer and walked through the code.  Very time consuming, but successful.

-- Doug