Date: Fri, 13 Mar 1998 21:33:02 -0800 From: Stephen Wynne <stevemw@northwest.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Aleksey Zvyagin <zal@rest.ru>, freebsd-doc@FreeBSD.ORG Subject: Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE. Message-ID: <199803140533.VAA00861@northwest.com> In-Reply-To: Your message of "Fri, 13 Mar 1998 19:31:44 PST." <Pine.BSF.3.96.980313193002.19404U-100000@gdi.uoregon.edu>
index | next in thread | previous in thread | raw e-mail
In message <Pine.BSF.3.96.980313193002.19404U-100000@gdi.uoregon.edu>,
Doug White writes:
Speaking of FAQ, it may be useful to do some preemptive customer support
and add a FAQ question for it [the new slice bits].
Oh, and regarding cvs-up documentation in general, I think that
a strong pointer in /usr/src/README to
http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html
(which is actually referenced from http://www.freebsd.org/docs.html) would
be *very* useful. I had already begun my first cvsup by the time I found
this. (I was lucky to have picked most of the right things to do already,
and the defaults worked out nicely for me.)
Why is this so obvious? Becase the unsuspecting but intuitive user
will just drop into /usr/src and want to know what to do in 15
easy steps. That's not easy to do with the 2.2.5 files :-)
Also, the tutorial could point to the latest warnings about each
release. I had to get subscribed to freebsd-latest to start getting
an idea what was really happening, and I think this isn't exactly
what the average user wants to do.
Instead of asking users to subscribe to freebsd-stable@freebsd.org,
perhaps a continually-updated webpage with issues raised there would
be better. Maybe this would take too much time for the engineers involved
with maintaining the release. In that case, I apologize and retract
my suggestion.
And I think there should be a default cvsup file in /usr/src that
lets people stay on *-stable with comments that contain a cron(8)
script that people can cut and paste to begin using.
One final suggestion: we need better information about how long it
will take us to do various CVS operations. Perhaps cvsup could
be modified to provide this, or estimates for 28.8, 56k, and T1
speeds in a table of operations could be provided. I know this
is a FAQ from spending some time on EFNet's #java IRC channel.
My reaction to the FreeBSD documentation is more or less ``it's all there,
but finding it is non-intuitive sometimes.'' If I sound like I'm
complaining, I'm not. I'm very happy, in fact. I've been around long
enough to know that FreeBSD is a superbly organized effort.
Regards,
Steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803140533.VAA00861>