On Mon, Oct 20, 2008 at 07:35:45PM +0200, Ludovic Brenta wrote: > By your reasoning, /etc/init.d/procps should not call sysctl on any > architecture or kernel, then. I think that's fair enough; we should > arrange for whatever package provides sysctl to call it in an init > script. sysctl comes from procps, except for FreeBSD. So where it does come from procps then it should provide the init script, where it doesn't, it shouldn't.
> Also, the FreeBSD documentation describes /etc/sysctl.conf quite > extensively and a search for FreeBSD kernel configuration variables > inevitably points at /etc/sysctl.conf. I suggest that package > maintainers coordinate a strategy to ensure /etc/sysctl.conf works out > of the box on all systems. I completely agree with you. The first step would of been the other maintainers actually making me aware there was another sysctl. We could of avoided this whole problem that way. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 http://www.enc.com.au/ csmall at : enc.com.au http://www.debian.org/ Debian GNU/Linux, software should be Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
