Date: Thu, 28 Sep 2000 13:18:58 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: stable@FreeBSD.ORG Subject: Re: cvs commit: src/release Makefile Message-ID: <20000928131858.A90273@dragon.nuxi.com> 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 References: <matusita@jp.FreeBSD.org> <88250.970121205@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000928131858.A90273>