Subject: Re: The daily insecurity output
To: Sam Carleton <email@example.com>
From: Jim Bernard <firstname.lastname@example.org>
Date: 07/24/2001 07:43:56
On Mon, Jul 23, 2001 at 11:23:33PM -0400, Sam Carleton wrote:
> In the "The daily insecurity output" I have been informed that:
> Checking special files and directories.
> missing: ./etc/mk.conf
> I looked at the man pages on mk.conf, I don't have /usr/pkgsrc on my
> system, thus I don't have /usr/pkgsrc/mk/mk.conf.example
> What should I do? Do I REALLY need this file? If so, what should be in
> the file?
No, you don't need the file---it just provides a way to set make variables
to override defaults. If you are bothered by the message from the security
script, just create an empty file. If you want to read about the purpose
of the file and see system-related variables you can set, type "man mk.conf".
Package-related variables are discussed in "man packages" and mk.conf.example,
which you can easily download via
without having to grab all of pkgsrc. Of course, setting package variables
won't be of any interest to you if you're not building packages via pkgsrc.