From owner-freebsd-hackers Tue Jan 20 21:58:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15462 for hackers-outgoing; Tue, 20 Jan 1998 21:58:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15419 for ; Tue, 20 Jan 1998 21:57:33 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id QAA09665; Wed, 21 Jan 1998 16:27:03 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA08171; Wed, 21 Jan 1998 16:27:02 +1030 (CST) (envelope-from grog) Message-ID: <19980121162701.64963@lemis.com> Date: Wed, 21 Jan 1998 16:27:01 +1030 From: Greg Lehey To: David Kelly Cc: FreeBSD Hackers Subject: Re: How to get an older if_de.c? References: <199801202309.RAA10002@PeeCee.tbe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801202309.RAA10002@PeeCee.tbe.com>; from David Kelly on Tue, Jan 20, 1998 at 05:09:40PM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk You sent this message to -hardware, which doesn't seem appropriate. I'm following up to -hackers. On Tue, Jan 20, 1998 at 05:09:40PM -0600, David Kelly wrote: > I'm guessing the solution to my de0 problem is an older version of > if_de.c ??? > > dmesg says: > de0 rev 35 int a irq 11 on pci0:14 > de0: not configured; 21040 pass 2.0 required (0.0 found) > > or maybe there is a way to hack my early December version > into compliance? In the mean time an old NE2000 clone has > been pressed into service. > > I have the CVS directory tree, updated via CTM as of this > morning. If some one could get me started on how to use CVS > to trace the history of if_de.c and extract a selected version > then I'd be happy. Would also like to know how to protect that > copy against further upgrades on my machine. OK. 1. To get the revision history, use cvs log: > $ cvs log if_de.c > RCS file: /src/cvs/src/sys/pci/if_de.c,v > Working file: if_de.c > head: 1.77 > branch: > locks: strict > access list: > symbolic names: These are mappings between names and RCS version numbers. You won't see the names again in the list of changes, which list only the version numbers. Refer back here to tranform the version number to a version name. > v971020: 1.1.1.5 > RELENG_2_2_5_RELEASE: 1.54.2.9 > v971017: 1.1.1.4 > NETBSD: 1.1.1 > v970703: 1.1.1.3 > WOLLMAN_MBUF: 1.65.0.2 > BP_WOLLMAN_MBUF: 1.65 > v970513: 1.1.1.2 > v970508: 1.1.1.1 > MATT_THOMAS: 1.1.1 > RELENG_2_2_2_RELEASE: 1.54.2.5 > post_smp_merge: 1.64 > pre_smp_merge: 1.64 > RELENG_2_2_1_RELEASE: 1.54.2.3 > RELENG_2_2_0_RELEASE: 1.54.2.3 > RELENG_2_1_7_RELEASE: 1.29.2.8 > RELENG_2_1_6_1_RELEASE: 1.29.2.7 > RELENG_2_1_6_RELEASE: 1.29.2.7 > RELENG_2_2: 1.54.0.2 > RELENG_2_2_BP: 1.54 > RELENG_2_1_5_RELEASE: 1.29.2.5 > wollman_polling: 1.44.0.2 > RELENG_2_1_0_RELEASE: 1.29.2.5 > RELENG_2_1_0: 1.29.0.2 > RELENG_2_1_0_BP: 1.29 > RELENG_2_0_5_RELEASE: 1.28.2.1 > RELENG_2_0_5: 1.28.0.2 > RELENG_2_0_5_BP: 1.28 > RELENG_2_0_5_ALPHA: 1.27 > OLAH_TTCP: 1.7.0.2 > RELEASE_2_0: 1.7 > BETA_2_0: 1.6 > ALPHA_2_0: 1.4 > V941001: 1.1 > keyword substitution: kv > total revisions: 102; selected revisions: 102 The following are the change strings for each version. > description: > ---------------------------- > revision 1.77 > date: 1998/01/08 23:42:24; author: eivind; state: Exp; lines: +5 -2 > Make INET a proper option. > > This will not make any of object files that LINT create change; there > might be differences with INET disabled, but hardly anything compiled > before without INET anyway. Now the 'obvious' things will give a > proper error if compiled without inet - ipx_ip, ipfw, tcp_debug. The > only thing that _should_ work (but can't be made to compile reasonably > easily) is sppp :-( > > This commit move struct arpcom from to > . > ---------------------------- > revision 1.76 > date: 1997/12/15 20:31:25; author: eivind; state: Exp; lines: +3 -1 > Throw options IPX, IPXIP and IPTUNNEL into opt_ipx.h. > > The #ifdef IPXIP in netipx/ipx_if.h is OK (used from ipx_usrreq.c and > ifconfig.c only). > > I also fixed a typo IPXTUNNEL -> IPTUNNEL (and #ifdef'ed out the code > inside, as it never could have compiled - doh.) 2. To check out a version, you can use either a date spec, a version name, or a version number. For example, you may determine that you want the version before the SMP merge (label pre_smp_merge: 1.64). Here's the checkin information (from cvs log): revision 1.64 date: 1997/04/05 07:59:41; author: phk; state: Exp; lines: +2 -2 Recognize ZNYX 314 cards that have a MAC address with the low bit set. You can use one of the following methods to check out this version: a. By date: cvs update -D "5 April 1997 07:59:41 UTC" if_de.c Note that RCS (and thus cvs) keeps its dates in UTC, so it's best to specify your dates in UTC. You can specify them locally, but you then need to convert the time correctly. RCS looks for the latest version which existed at the time you specified: if you specify "5 April 1997 07:59 UTC", you will get an older version, but if you specify "5 April 1997 08:00 UTC" you'll get the one you want. b. By revision number: cvs update -r1.64 if_de.c c. By revision tag: cvs update -r pre_smp_merge if_de.c A word of caution: all these methods are "sticky". Any further update will give you the same version until you tell cvs something else. For example, when you're ready for the latest and greatest version again, you can write: cvs update -A if_de.c cvs keeps information on the current version in the file CVS/Entries. To see which version you currently have, enter: $ grep if_de.c CVS/Entries /if_de.c/1.64/Wed Jan 21 05:48:58 1998//D97.04.05.08.00.00 Let me know if you need any more information; I'll add this to the next edition of "The Complete FreeBSD". Greg