rc.local starts after usbd, and module driver that is attached after
inserting the device does not attach!
is it bug?
don't we load modules in /boot/loader.conf ?
yes i do, but kldload is too here.
if i - say - attach USB pendrive with no umass.ko loaded, nothing is of
course attached
At 04:13 PM 11/27/2005, Wojciech Puchar wrote:
/etc/lkm.conf in NetBSD?
How about /etc/rc.local or create a script file to go in
/usr/local/etc/rc.d to do what you want?
rc.local starts after usbd, and module driver that is attached after
inserting the device does not attach!
is it bug?
/etc/lkm.conf in NetBSD?
How about /etc/rc.local or create a script file to go in
/usr/local/etc/rc.d to do what you want?
rc.local starts after usbd, and module driver that is attached after
inserting the device does not attach!
is it bug?
___
fr
On Sat, Nov 26, 2005 at 10:11:33PM +0100, Wojciech Puchar wrote:
> where is right place to do it, other than loader.conf, to load it after
> kernel is started.
>
> i would like to defer usb bus discovery so SCSI bus numbering is
> independent of USB storage devs connected.
>
> i put it for now
where is right place to do it, other than loader.conf, to load it after
kernel is started.
i would like to defer usb bus discovery so SCSI bus numbering is
independent of USB storage devs connected.
i put it for now in usbd but is there any place made for that, like
/etc/lkm.conf in NetBSD?
