From owner-freebsd-hackers  Mon Oct 14 20:17:50 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA20717
          for hackers-outgoing; Mon, 14 Oct 1996 20:17:50 -0700 (PDT)
Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA20711;
          Mon, 14 Oct 1996 20:17:33 -0700 (PDT)
Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id XAA12967; Mon, 14 Oct 1996 23:16:44 -0400 (EDT)
Date: Mon, 14 Oct 1996 23:16:40 -0400 (EDT)
From: Gary Roberts <wangel@wgrobez1.remote.louisville.edu>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: current@freebsd.org, hackers@freebsd.org
Subject: Re: -current stable again?
In-Reply-To: <Pine.NEB.3.95.961014172417.3543q-100000@mail.cdsnet.net>
Message-ID: <Pine.NEB.3.95.961014231539.12960A-100000@wgrobez1.remote.louisville.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 14 Oct 1996, Jaye Mathisen wrote:

> 
> 
> I have held off on upgrading because of the recent problems reported by
> Karl and others, but -current seems suspiciously quiet after Saturday.  Is
> it safe to use?
> 
> 
I tried updating pppd to pppd2.3b or whatever, but it broke my kernel
tree.  I ended up running a sup to update, everything seems ok, however I
did recieve alot of Warning messages from gcc while compiling a new
kernel.

Gary Roberts 
System Admin. -- Altered Reality.
http://136.165.243.183 -- Main User Pages