loading modules not in /boot/kernel from loader.conf

I have had bad experiences with loading modules anywhere except /boot/loader.conf and even so there is some hacking in the rc to make it work fine for example: (sleep 5;ntfs-3g )& is the last line in the rc > > Remember that this is the loader which will be loading the > module, so if /usr i

Re: loading modules not in /boot/kernel from loader.conf

On 11/12/2007 2:54 AM, Aryeh M. Friedman wrote: You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko Remember that this is the loader which will be loading the module, so if /usr is a separate partition then this will no

Re: loading modules not in /boot/kernel from loader.conf

Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Engel wrote: Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fus

Re: loading modules not in /boot/kernel from loader.conf

Tino Engel wrote: Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? Yeah, if you put a kernel module in /boo

Re: loading modules not in /boot/kernel from loader.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Engel wrote: > Aryeh M. Friedman schrieb: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> >> >>> You could make a softlink... >>> >> >> Thats what raised the question I was doing ln -s >> /usr/local/modules/fuse.ko /boot/kernel/fuse.ko >> >

Re: loading modules not in /boot/kernel from loader.conf

Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? ___ freebsd-que

Re: loading modules not in /boot/kernel from loader.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.

Re: loading modules not in /boot/kernel from loader.conf

Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The fusefs rc script will run kldload /usr/local/modules/fuse.ko. You don't need to add anything to loader.conf . Secondly, you should add kernel modules to the /boot/modules dir not /boot/kernel. Thanks but I

Re: loading modules not in /boot/kernel from loader.conf

In the last episode (Dec 10), Aryeh M. Friedman said: > sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a > fuse_load="YES" will not work because of this. But, mv/cp/ln'ing it > to /boot/kernel gets nuked if you rebuild/install the kernel. How to > get around this? The loader als

Re: loading modules not in /boot/kernel from loader.conf

Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a fuse_load="YES" will not work because of this. But, mv/cp/ln'ing it to /boot/kernel gets nuked if you rebuild/install the kernel. How to get around this? --

Re: loading modules not in /boot/kernel from loader.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > The fusefs rc script will run kldload /usr/local/modules/fuse.ko. > You don't need to add anything to loader.conf . Secondly, you > should add kernel modules to the /boot/modules dir not > /boot/kernel. Thanks but I use a handwritten /etc/rc that

loading modules not in /boot/kernel from loader.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a fuse_load="YES" will not work because of this. But, mv/cp/ln'ing it to /boot/kernel gets nuked if you rebuild/install the kernel. How to get around this? -BEGIN PGP SIGNATURE-