From owner-freebsd-audit Tue Nov 30 14:19:34 1999 Delivered-To: freebsd-audit@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 5A63814C97; Tue, 30 Nov 1999 14:19:30 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Wed, 1 Dec 1999 09:12:02 +1100 Content-return: prohibited Date: Wed, 1 Dec 1999 09:19:18 +1100 From: Peter Jeremy Subject: Re: cvs commit: src/sys/i386/conf files.i386 src/sys/kern kern_fork.c src/sys/libkern arc4random.c src/sys/sys libkern.h In-reply-to: <89015.943945313@zippy.cdrom.com> To: arch@FreeBSD.ORG, audit@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Dec1.091202est.40330@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <89015.943945313@zippy.cdrom.com> Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-30 18:01:53 +1100, Jordan K. Hubbard wrote: >> This would fall under my preferred policy, which you didn't quote, namely >> "turn on everything which doesn't have a negative impact, and providing > >Not being able to predict pids (for useful purposes) would fall under >the definition of "negative impact" for a number of admins. I agree. Digital UNIX uses something like random PID generation and I find it a PITA. Sequential PID allocation makes it much easier to get a feeling for what is going on (and in what order). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message