From owner-freebsd-current  Sun Sep 10 09:58:40 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id JAA06595
          for current-outgoing; Sun, 10 Sep 1995 09:58:40 -0700
Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA06566
          for <freebsd-current@freebsd.org>; Sun, 10 Sep 1995 09:58:37 -0700
Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4)
	id AA18401; Sun, 10 Sep 1995 12:58:31 -0400
Received: by borg.ess.harris.com (4.1/SMI-4.1)
	id AA01584; Sun, 10 Sep 95 12:55:55 EDT
Date: Sun, 10 Sep 95 12:55:55 EDT
From: jleppek@suw2k.ess.harris.com (James Leppek)
Message-Id: <9509101655.AA01584@borg.ess.harris.com>
To: faulkner@mpd.tandem.com
Subject: Re: sig 11
Cc: freebsd-current@freebsd.org
Sender: current-owner@freebsd.org
Precedence: bulk

I agree, I do not think anyone here is complaining, just trying
to pass along information to help isolate the problem or just
identify that there is a real one. while I wish I had the time
to be a more active "core" member, the best I can be is part of
the "informal" test organization and porting apps as time permits
for local folks running stable. I try to keep up with the 
cvs msgs and do a rebuild weekly or when I see a "try this" type
message to provide stability feedback or help confirm that lone
message that comes in that says "my system crashed" and the first
reponses are "must be your hardware". I know I have avoided swapping
drives/cards/SIMMS because of the many folks running current who
can send at least a confirmation message that says "I saw
something like that to, thought it was just me".
Isn't this what "current" folks are supposed to be doing?

Hmmm, just saw a message that says more VOP changes coming :-)

Jim Leppek

> From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 12:37:24 1995
> From: faulkner@mpd.tandem.com (Boyd Faulkner)
> Subject: Re: sig 11
> To: jdl@chromatic.com
> Date: Sun, 10 Sep 1995 11:30:01 -0500 (CDT)
> Cc: jc@irbs.com, freebsd-current@freebsd.org
> X-Mailer: ELM [version 2.4 PL17]
> Content-Type> : > text> 
> Sender: current-owner@freebsd.org
> 
> > 
> > John Capo scribbled:
> > > These kinds of problems are all part of running -current.  Current
> > > is a development tree and is quite often broken for one reason or
> > > another.  Like the docs say, "The bleeding edge".
> > > 
> > > Sounds like you should be running -stable rather than -current.
> > 
> > Hmmm.  Is the problem here that people always think they want
> > to be running "the latest release" and they equate that to
> > the "current" system and get it wrong?  Should we maybe rename
> > the -current as like, -development, -devel, -bleed or something?
> > To make it *really* obvious.  I mean, I had to actually *read*
> > FAQ to find this out... :-)
> > 
> > jdl
> > 
> Let's not.  I don't think I could stand to watch my box come up and say
> 
> FreeBSD bleeds.  :-)
> 
> One simply must give rope to allow people to hang themselves, else, they will
> weave their own.
> 
> -- 
> _______________________________________________________________________
> 
>  Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner
> _______________________________________________________________________
>