Re: Bug#502729: and the mysterious freebsd-utils package
On Wed, Jan 07, 2009 at 09:34:18AM +0100, Petr Salinger wrote:
It looks like we (GNU/kFreeBSD) have to create better wrapper
around native /lib/freebsd/sysctl.
The current one does not accept file name for "-p",
it always uses /etc/sysctl.conf and the possibly specified filename
treats as variable to set.
Is that the right way? I'm a little worried that one package's init file
(procps) is calling anothers program (freebsd-utils). The whole point of
procps' init file is to start its sysctl. I already conditionally remove
sysctl and its man page so in a way it makes sense to remove the init
file if sysctl goes away and then let the other package deal with init
files for *its* sysctl.
It really makes sense. Sysctl should come from freebsd-utils package and
therefore also init files. The init script should be addopted by
freebsd-utils, with similar behaviour, i.e. on start set variables
from /etc/sysctl.d/*.conf and /etc/sysctl.conf.
As current init script from procps does not work with current sysctl
wrapper from freebsd-utils, it should not do any harm to just remove it
from procps on GNU/kFreeBSD. Please remove all sysctl related things
from procps on GNU/kFreeBSD.