From owner-freebsd-doc Fri Mar 13 21:34:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14430 for freebsd-doc-outgoing; Fri, 13 Mar 1998 21:34:38 -0800 (PST) (envelope-from owner-freebsd-doc@FreeBSD.ORG) Received: from northwest.com (root@port32.northwest.com [204.119.42.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14423 for ; Fri, 13 Mar 1998 21:34:31 -0800 (PST) (envelope-from stevemw@northwest.com) Received: from fuji (stevemw@localhost [127.0.0.1]) by northwest.com (8.8.8/8.8.7) with ESMTP id VAA00861; Fri, 13 Mar 1998 21:33:02 -0800 (PST) (envelope-from stevemw@fuji) Message-Id: <199803140533.VAA00861@northwest.com> To: Doug White cc: "Jordan K. Hubbard" , Aleksey Zvyagin , freebsd-doc@FreeBSD.ORG Subject: Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE. In-reply-to: Your message of "Fri, 13 Mar 1998 19:31:44 PST." Date: Fri, 13 Mar 1998 21:33:02 -0800 From: Stephen Wynne Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , 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