Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Mar 1998 19:04:16 -0800 (PST)
From:      "William R. Somsky" <wrsomsky@halcyon.com>
To:        andrsn@andrsn.stanford.edu (Annelise Anderson)
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE.
Message-ID:  <199803150304.TAA00508.gramarye.wrsomsky@halcyon.com>
In-Reply-To: <Pine.BSF.3.96.980314171206.19968D-100000@andrsn.stanford.edu> from Annelise Anderson at "Mar 14, 98 05:25:03 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> From: Annelise Anderson <andrsn@andrsn.stanford.edu>
> 
> I think I'm trying to say that the information on *how to get* the
> latest errata and any special build instructions (or whatever) needs
> to arrive with the goods; one can't expect people to pick up this
> information in some other place--on some newsgroup or mailing list.
> 
> At least, I think this has the best chance of reducing the repetitive
> questions.
> 
> For the cdrom sets, the brochure that goes in the package should 
> have a little note that says something about getting information
> that became available after the cd's were made.  This can be a
> standard location, e.g., the location of the errata.txt file on
> the web site or WC CDROM for a particular release.
> 
> For sources obtained with cvsup, a README file that ends up in the
> one directory that has to be visited (/usr/src) that either provides
> information or directs the reader to information is all that's needed.
> 
> Annelise

I'll second this.

I'm running a home machine and a couple at work with 2.2.5-stable
-- excuse me, it's 2.2.6-beta now -- and I'm trying to follow
the -stable mailing list, but there's enough there that one can
easily miss something.  It would be nice if there was a web-page
and/or ftp-file that contained a summary of current errata, need-to-know
and don't-forget information, and even just useful notes, that
contained the current state of needed information.  I mean, the
mailing list is good for ongoing discussions about things, but its
just not very good as a reference.  _I'd_ use such a page.  I'm
trying to be a knowledgeble -stable user, but inevitably, something
will go by in a discussion that I don't particularly pay attention
to at the time, and then I get bitten by it later.  At that point,
there's not much I can do other that post a "didn't somebody say
something about" message -- the mailing list archives aren't really
very useful for this, even if you can figure out a seach to pick
the messages relevant to the topic in questions, you get all the
messages, the initial problem reports, the side comments,
the why didn't we do this before, I thought we did, Linux did
it long ago, NetBSD hasn't done it yet, yadda, yadda, yadda,
along with the actual answer, if there is one.  If we had such
a "current notes" page, I know I'd use it.  Now, I won't promise
I'd always read it before doing a make world -- I'm not that diciplined --
but then I'd have a first place to look for info when something went wrong.
And if it were well advertized, others would know to look there as well.

(Sorry, I'm rambling... I'll take my medication now... *gulp*... ahh...)

So, to make a long story short -- (too late) -- I think that a well
advertized "current notes and errata" page for each of the branches
(-release, -stable, -current) would be very useful.

________________________________________________________________________
William R. Somsky                                   wrsomsky@halcyon.com
Physicist, Baritone, Guitarist           http://www.halcyon.com/wrsomsky

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803150304.TAA00508.gramarye.wrsomsky>