Date: Wed, 24 Jul 2002 21:21:15 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Terry Lambert <tlambert2@mindspring.com> Cc: "M. Warner Losh" <imp@bsdimp.com>, matusita@jp.FreeBSD.org, ru@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/release/i386 drivers.conf Message-ID: <20020725022114.GB68693@dan.emsphone.com> In-Reply-To: <3D3F5F40.AC5A33EF@mindspring.com> References: <20020705005426Y.matusita@jp.FreeBSD.org> <20020724173037.GE87477@sunbay.com> <20020725032910A.matusita@jp.FreeBSD.org> <20020724.184701.17239163.imp@bsdimp.com> <3D3F5F40.AC5A33EF@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 24), Terry Lambert said: > "M. Warner Losh" wrote: > > I've noticed that some of the older cam drivers are about all that is > > in the way of making CAM truly loadable. By that I mean having a > > kernel with all supported devices that aren't loadable forces CAM to > > be in the kernel because some of the SCSI devices aren't (yet) > > loadable. However, that's relatively easy to fix. > > I've noticed that the fact that I boot from a CDROM or a SCSI > hard drive is in the way of making CAM loadable. 8-) 8-). You should be able to load the theoretical CAM module with /boot/loader with no problems, actually. > Anything in the boot path needs to be static, by definition, or you > face the Catch-22 of needing to load the driver in order to be able > to load the driver. > > ...This wouldn't be a problem, if VM86 supported disk I/O, and > you could replace drivers on the fly... -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020725022114.GB68693>