From owner-freebsd-current Sat May 13 19:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 11D5F37BA7B for ; Sat, 13 May 2000 19:54:48 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id JAA11962; Sun, 14 May 2000 09:54:44 +0700 (NOVST) (envelope-from nnd) Date: Sun, 14 May 2000 09:54:44 +0700 (NOVST) Message-Id: <200005140254.JAA11962@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Subject: Re: make release problem In-Reply-To: <200005140234.TAA06797@mass.cdrom.com> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <200005140234.TAA06797@mass.cdrom.com> Mike Smith wrote: >> >> In trying to build "make release" today, I discovered that the >> "vn" driver is required now to build the boot floppies. > > What do you mean "now"? It's _always_ been required. > >> I would suggest that this driver be added to "GENERIC". For >> what it's worth, I added the driver to my kernel, rebooted, and >> completed the make release. > > vnconfig should just load the KLD; if this doesn't work, you can load it > manually. Rebuilding a kernel is not required (and shouldn't be). Some care must be taken when cross-building release - f.e. building 4.0-STABLE on the CURRENT system. Loading the KLD by vnconfig will use the newly build module in the chrooted environment i.e. 4.0-STABLE module while the kernel is CURRENT. So the module must be IN before to start 'make release'. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message