From owner-freebsd-stable Sat Aug 29 15:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11239 for freebsd-stable-outgoing; Sat, 29 Aug 1998 15:10:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from word.smith.net.au (castles153.castles.com [208.214.165.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11234 for ; Sat, 29 Aug 1998 15:10:38 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id PAA08745; Sat, 29 Aug 1998 15:07:39 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808291507.PAA08745@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "William R. Somsky" cc: Fedor.Gubarev@itep.ru, freebsd-stable@FreeBSD.ORG Subject: Re: Failed to build kernel... In-reply-to: Your message of "Sat, 29 Aug 1998 12:10:46 MST." <199808291910.MAA02485.gramarye.wrsomsky@halcyon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 15:07:38 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm currently trying a "find /usr/src -name "*vfs*" -print | xargs rm" > and a re-cvsup, to see if there's anything strange on my system -- > mostly as just a random something that I can do, rather than with > any particular expectation of it helping -- and... now it works! > > I don't _think_ I tweaked anything else between it failing and working. > Unfortunately, I don't have a record of what the before-and-after > differences of my /usr/src tree. Wait... in vfs_bio.c:1177, the > line has been changed to remove the reference to LK_EXCLUSIVE... If you are going to follow the tree this closely, you should be reviewing messages sent to the cvs-all mailing list. You can filter out any that don't contain the string "RELENG_2_2", in order to keep track of just -stable. This would mean that you would know exactly what had happened, rather than asking several thousand people. > So, what happened? Did my "find | xargs rm" help, or did that file > just happend to get changed on the repository right inbetween my > trials? I dunno... If you are bringing down the whole CVS repository, you can check $CVSROOT/commitlogs/sys to see what has been going on. You can also review the CVS history of various files at www.freebsd.org. We don't appear to have an HTML-ified version of the commitlogs online at this stage; this would be an ideal contribution from someone with a bit of text-to-HTML conversion skill. > Incidentally, on the subject of cvsup, I understand that it won't > delete files that it doesn't have a record that it created, but > isn't-there/shouldn't-there-be some way to get it to at least _list_ > what files are present on the local system don't exist on the master > server? I've had crufties left over a time or two from when something > got out of sync, and since I'm coming in over a dialup line for my IP, > I really don't want to delete the whole tree and re-cvsup it in it's > entirety. Cvsup of /usr/src and /usr/ports works fine for me over > the phone for updates, say once to a few times a week -- takes a five > minutes or so -- but a full checkout of the entire tree takes hours -- > I've only done that once or twice, when things seemed to have gotten > way out of sync. The presence of extra files in the tree isn't normally actually a problem. > Even just a (checksummed?) list of the /usr/src, /usr/ports tree, > possibly just stored as an extra file in those trees would be all > I need to detect crufties... If you want to produce such a tool, you have to look no further than /sup//checkouts.cvs I'd be certain that you'd have quite an audience for it, should you be interested in distribution. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message