From owner-freebsd-stable Wed Jun 5 15:09:59 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA09795 for stable-outgoing; Wed, 5 Jun 1996 15:09:59 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA09789 for ; Wed, 5 Jun 1996 15:09:57 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA23546; Wed, 5 Jun 1996 16:09:48 -0600 Date: Wed, 5 Jun 1996 16:09:48 -0600 From: Nate Williams Message-Id: <199606052209.QAA23546@rocky.sri.MT.net> To: Joao Carlos Mendes Luis Cc: nate@sri.MT.net (Nate Williams), jkh@time.cdrom.com, stable@freebsd.org Subject: Re: Mega-Commit cleanups In-Reply-To: <199606052206.TAA26623@mailhost.coppe.ufrj.br> References: <199606052008.OAA23006@rocky.sri.MT.net> <199606052206.TAA26623@mailhost.coppe.ufrj.br> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > // OK. Do you want to bring in 'newsyslog(8)' into -stable, or roll back > // the changes which require them? > > May you please explain me what's the problem with newsyslog ? I'm > using 2.1.0R and brought in the newsyslog from -current. It's working > perfectly for my needs. Because it's by definition 'new' software that's un-necessary. It *could* (doubtful) have some bug in it or security flaw that causes the system to be less -stable, so it stays out of stable until someone is willing to bring it in and stand in the line of fire. I'm not willing to do that, but if I got Jordan's permission I wouldn't have been responsible for anything bad that occurred because of it. :) Nate