From owner-freebsd-current Sat May 13 19:44:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 1CFAF37BC15; Sat, 13 May 2000 19:44:45 -0700 (PDT) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id WAA08007; Sat, 13 May 2000 22:42:35 -0400 (EDT) Received: by lab1.tfd.com id AA16163 (5.67b/IDA-1.5); Sat, 13 May 2000 22:42:25 -0400 Date: Sat, 13 May 2000 22:42:25 -0400 From: Kent Hauser Message-Id: <200005140242.AA16163@lab1.tfd.com> To: kent@lab1.tfd.com, msmith@FreeBSD.ORG Subject: Re: make release problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Curious. I've done several (say a dozen) make release builds in the last 4 months of 4.0-CURRENT & 5.0-CURRENT. The previous one was about 2 weeks ago. I've never had "vn" in my kernel, nor had a problem. Maybe something in the latest "loadable kernel modules" synchronization/version control changes have prevented automatic loading? In any event, I've never had this trouble before. For what it's worth, today after I got "make world" to work, I rebuilt my kernel & did a make release (for my other machines). I had to add "vn" to my kernel for the first time to get "release" to work. You mileage may vary.... Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message