Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Aug 1999 14:38:25 +0200 (MET DST)
From:      Nick Hibma <nick.hibma@jrc.it>
To:        Fernando Schapachnik <fpscha@via-net-works.net.ar>
Cc:        hoek@FreeBSD.ORG, fpscha@sminter.com.ar, freebsd-bugs@FreeBSD.ORG
Subject:   Re: kern/10387: 2.2.7 hangs when trying to write on defective HD with no messages
Message-ID:  <Pine.GSO.3.95q.990823143017.27688x-100000@elect8>
In-Reply-To: <199908231228.JAA06139@ns1.sminter.com.ar>

next in thread | previous in thread | raw e-mail | index | archive | help

For the record:

FreeBSD comes in three different versions:

x.y-RELEASE	(tagged as RELEASE_x_y)
x.y-STABLE	(tagged as RELENG_3)
(x+1)-CURRENT	(tagged as HEAD)


RELEASE is the version as it comes off the CD. Releases we have had so
far are 3.0, 3.1 and 3.2, and 3.3 is coming on the 15th of september.

When mistakes are detected in the RELEASES these are corrected in the
STABLE version. The STABLE version is a sliding version as it is the
name for the most recent version since RELEASE. You can fetch it through
using CVSUP or ftp (see handbook).

RELEASE is simply a STABLE version at a certain timestamp (so Jordan can
have his fun, annoy everybody by blocking access to the repo and act
like he is in charge of everything, and then try and prove it and give
away CD's for free at conferences :-) 

And then there is CURRENT. Don't use it, unless you know what you are
doing and are willing to spend the odd half hour once in a while to fix
someones else mistakes in trying something new.


To answer your question: It will be in stable. If someone says he has
committed the change to STABLE you should be able to update your sources
using cvsup a day later and have an updated version, solving your
problem.


Nick


On Mon, 23 Aug 1999, Fernando Schapachnik wrote:

 > This feels my soul with happiness! :)
 > 
 > How can I know in  which version of -stable will it be commited?
 > 
 > Thanks!
 > 
 > En un mensaje anterior, hoek@FreeBSD.org escribió:
 > > Synopsis: 2.2.7 hangs when trying to write on defective HD with no messages
 > > 
 > > State-Changed-From-To: open->closed
 > > State-Changed-By: hoek
 > > State-Changed-When: Sat Aug 21 21:39:47 PDT 1999
 > > State-Changed-Why: 
 > > This has been fixed in FreeBSD-current (and -stable??).  I don't expect
 > > it to be merged all the way back to 2.2-stable.  However, you may be
 > > able to distill the necessary incantations and test them and submit
 > > them for inclusion.  I don't believe it would be a worthwhile exercise,
 > > however, since a HD failure is generally (hopefully) a one (or few-)
 > > time occurrence.
 > > 
 > 
 > 
 > 
 > 
 > Fernando P. Schapachnik
 > Administración de la red
 > VIA Net Works Argentina SA
 > Diagonal Roque Sáenz Peña 971, 4º y 5º piso.
 > 1035 - Capital Federal, Argentina. 
 > (54-11) 4323-3333
 > http://www.via-net-works.net.ar
 > 
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 > 
 > 

-- 
ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95q.990823143017.27688x-100000>