Bug 20398

Summary: Tracking STABLE instructions should explicitly state you need src-all for STABLE
Product: Documentation Reporter: jeffblaine <jeffblaine>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description jeffblaine 2000-08-04 15:00:01 UTC
In the Handbook, under advanced topics, the docs on tracking -STABLE
do not mention that you _must_ CVS update src-all.  There is only a
pointer to a stable-cvsupfile, inside of which it is not clear at
all what you _have_ to do to track STABLE (and maybe other branches?).

The stable-cvsupfile leads one to believe that there are choices,
yet when wanting to track STABLE, there are not (that I can tell).
It's src-all or nothing.

How-To-Repeat: Try to upgrade your 4.0-RELEASE machine's kernel to 4.0-STABLE by
only CVS updating from src-sys.  It doesn't work.
Comment 1 jim 2000-08-04 22:59:22 UTC
On Fri, 04 Aug 2000 at 06:54:00 -0700, jeffblaine@mediaone.net wrote:
> >Number:         20398
> >Category:       docs
> >Synopsis:       Tracking STABLE instructions should explicitly state you need src-all for STABLE
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-doc
> >State:          open

[snip..]

> >Description:
> In the Handbook, under advanced topics, the docs on tracking -STABLE
> do not mention that you _must_ CVS update src-all.  There is only a
> pointer to a stable-cvsupfile, inside of which it is not clear at
> all what you _have_ to do to track STABLE (and maybe other branches?).
> 
> The stable-cvsupfile leads one to believe that there are choices,
> yet when wanting to track STABLE, there are not (that I can tell).
> It's src-all or nothing.
> >How-To-Repeat:
> Try to upgrade your 4.0-RELEASE machine's kernel to 4.0-STABLE by
> only CVS updating from src-sys.  It doesn't work.

That's part of your problem right there.  You don't update to -STABLE by
just upgrading your kernel.  You build world which is explained in the
handbook.  At any rate, here's a proposed patch for the stable-supfile.
Comments are appreciated.

Index: stable-supfile
===================================================================
RCS file: /mnt/src/share/examples/cvsup/stable-supfile,v
retrieving revision 1.21
diff -u -r1.21 stable-supfile
--- stable-supfile	2000/07/09 16:03:53	1.21
+++ stable-supfile	2000/08/04 21:58:55
@@ -78,7 +78,8 @@
 #
 # The easiest way to get the main source tree is to use the "src-all"
 # mega-collection.  It includes all of the individual "src-*" collections,
-# except the export-restricted collections.
+# except the export-restricted collections.  Please note:  If you want
+# to track -STABLE, you will want to leave "src-all" uncommented.
 src-all
 
 # These are the individual collections that make up "src-all".  If you

- jim

-- 
jim mock <jim@jmock.com>        work: jim@osd.bsdi.com | jim@FreeBSD.org
http://soupnazi.org/              BSDi Open Source Div | http://bsdi.com
Comment 2 jim 2000-08-04 23:27:23 UTC
On Fri, 04 Aug 2000 at 18:22:22 -0700, Jeff Blaine wrote:
> > > How to repeat:
> > > Try to upgrade your 4.0-RELEASE machine's kernel to 4.0-STABLE by
> > > only CVS updating from src-sys.  It doesn't work.
> > 
> > That's part of your problem right there.  You don't update to
> > -STABLE by just upgrading your kernel.  You build world which is
> > explained in the handbook.  At any rate, here's a proposed patch for
> > the stable-supfile.  Comments are appreciated.
> 
> Right, all I was getting at is...I don't see anywhere in the handbook
> where it says, "Kernel-only upgrades are not done in the FreeBSD
> world.  To upgrade your kernel, you need to start tracking sys-all
> entirely in either -CURRENT or -STABLE entirely."

Hmm, I think it's there somewhere, but I can't remember off-hand where.
Maybe it's in the FAQ.  I'll have to look.

> Seems silly until you consider how many people use Linux where
> upgrading only the kernel very much a part of monthly life for those
> people who live on the bleeding edge (by choice, I'm not one of those
> people of course).
> 
> Maybe I didn't look hard enough, but I really didn't find anything
> like that, so I was left in the land of wing-it.
> 
> ...and your patch _should_ do the trick to stop this from happening,

Ok, I'll commit it in a few minutes.

> but I'm wondering if something more obvious than a trailing comment
> in the CVS update file isn't order.  But that's not my call.

Agreed.  If I can't find it in the FAQ or handbook, I'll add it in there
somewhere.

- jim

-- 
jim mock <jim@jmock.com>        work: jim@osd.bsdi.com | jim@FreeBSD.org
http://soupnazi.org/              BSDi Open Source Div | http://bsdi.com
Comment 3 Jim Mock freebsd_committer freebsd_triage 2000-08-04 23:30:03 UTC
State Changed
From-To: open->closed

Notes added to the relevant supfiles.  Thanks!
Comment 4 jeffblaine 2000-08-05 02:22:22 UTC
> > How to repeat:
> > Try to upgrade your 4.0-RELEASE machine's kernel to 4.0-STABLE by
> > only CVS updating from src-sys.  It doesn't work.
> 
> That's part of your problem right there.  You don't update to -STABLE by
> just upgrading your kernel.  You build world which is explained in the
> handbook.  At any rate, here's a proposed patch for the stable-supfile.
> Comments are appreciated.

Right, all I was getting at is...I don't see anywhere in the handbook
where it says, "Kernel-only upgrades are not done in the FreeBSD world.
To upgrade your kernel, you need to start tracking sys-all entirely
in either -CURRENT or -STABLE entirely."

Seems silly until you consider how many people use Linux where upgrading
only the kernel very much a part of monthly life for those people who
live on the bleeding edge (by choice, I'm not one of those people of
course).

Maybe I didn't look hard enough, but I really didn't find anything
like that, so I was left in the land of wing-it.

...and your patch _should_ do the trick to stop this from happening,
but I'm wondering if something more obvious than a trailing comment
in the CVS update file isn't order.  But that's not my call.

Thanks for your time.