From owner-freebsd-stable Thu Sep 28 13:19: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 734E637B422 for ; Thu, 28 Sep 2000 13:19:02 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA90308; Thu, 28 Sep 2000 13:18:58 -0700 (PDT) (envelope-from obrien) Date: Thu, 28 Sep 2000 13:18:58 -0700 From: "David O'Brien" To: Jordan Hubbard Cc: stable@FreeBSD.ORG Subject: Re: cvs commit: src/release Makefile Message-ID: <20000928131858.A90273@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <88250.970121205@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <88250.970121205@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Wed, Sep 27, 2000 at 11:06:45PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 27, 2000 at 11:06:45PM -0700, Jordan Hubbard wrote: > > Users are already notified at the top of Makefile, and moreover, > > vnconfig(8) does (or if not yet, should) check if vn device is > > available (and if not available, vnconfig(8) loads vn module). > > > > There is no need to call kldload(8) in Makefile, IMO. > > Agreed - vnconfig is supposed to load the vn module and does, > at least, in -current. If that functionality is missing > from -stable then it should be merged. It doesn't work on 4.1-R/AXP. And if it did, *which* vn.ko file will be loaded? From a Functionality stand point this is dangerous as w/in the chrooted tree the only vn.ko available is for the release being built, not the vn.ko that matches the kernel. Security stand point kldload(8) cannot load the matching vn.ko when run from a chrooted environment. The only save way is to run kldload before any chroot'ing. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message