Date: Wed, 08 Jan 2003 17:54:57 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Julian H. Stacey" <jhs@berklix.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel panic on 4.7-STABLE to 5.0 RC2 upgrade. Message-ID: <3E1CD671.29FCBE72@mindspring.com> References: <200301090123.h091NQm39888@flip.jhs.private>
next in thread | previous in thread | raw e-mail | index | archive | help
"Julian H. Stacey" wrote: > Terry Lambert wrote: > > Because RC2 was not tagged, because We Fear CVS Tags(tm), you > > will need to use a date in order to create your own RC2. > > Perhaps release build team are trying to avoid touching every file > in the CVS tree, as global touching costs people receiving on modems > & non flat rate extra telecom charges, (regardless of whether receiving > via CVSup or CTM etc). I'm well aware of that (see other post). > RC2 seems important though; so Although there's no tag in src/Makefile,v > is there a CVS file containing a table of dates corresponding to > EG RC2, RC1 etc ? (& if one doesnt exist, how about creating one ?). RC2 has additional changes, above and beyond a simple date tag (see other post; I believe it was managed in P4, and you could use _that_ to recover it). A tag, in this case, would only be useful if the other RC2 changes (string changes, hacks to suppress known bugs, etc., mostly) were made in a branch off the tag, in the main source tree, rather than in P4. Not a convenient option, all around, I'm afraid, though I agree that release candidates should be tagged in the tree, so they can be recovered, for archival reasons, if nothing else. 8-(. The main point, though, is about getting the same sources for the RC2 that won't install, in order to build an RC2 that's identical, so it won't install, and then build an RC2 with a kernel with symbols and DDB and BREAK_TO_DEBUGGER, so we can find out *why* it won't install. At this point, the ball is in the court of the person claiming the upgrade fails, since no one can repeat it without his hardware (it seems)... meaning no one can debug it, without his hardware. My personal approach would be to use the souce tree from disk #2 (if one was made for the 5.0-RC2 distributions) for builds on the 4.7 box that he has on hand; that's easiest, and will result in an identical CDROM (sans date stamps). That's really all that's needed to track the reported bug on the sytem where it's supposedly showing its head. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E1CD671.29FCBE72>