[ale] Loading kernel modules at boot

[Benjie]

the easiest thing to do would be to add " modprobe fuse"  to /etc/rc.local.
That should load the module every time your system boots.  If the module has
been compiled, has its dependencies defined, and is aliased in modules.conf,
I would think it would load automagically when you use the fusermount
command.

Benjie
On 3/19/06, Stephen Cristol <stephen at bee.net> wrote:
>
> I've installed the fuse kernel module [1] from source and would like
> to load it at boot time.
>
> I can successfully load it manually using:
>
>    sudo /sbin/modprobe coda
>
> Running "/sbin/modinfo fuse" gives me the following information:
>
>    filename:       /lib/modules/2.6.9-34.EL/kernel/fs/fuse/fuse.ko
>    alias:          char-major-10-229
>    author:         Miklos Szeredi <miklos at szeredi.hu>
>    description:    Filesystem in Userspace
>    license:        GPL
>    vermagic:       2.6.9-34.EL 686 REGPARM 4KSTACKS gcc-3.4
>    depends:
>
> Based on that, I added the line "alias char-major-10-229 fuse" to /
> etc/modprobe.conf (under CentOS 4.2). This has not had the desired
> effect. I am not sure if it had any effect. Typing either "dmesg |
> grep fuse" or "dmesg | grep char" produces no output.
>
> Any suggestions on how to get the fuse module to load at boot?
>
> If I can't get it to load via this mechanism, is there an alternative
> that would load early enough for it to be available to a service (in /
> etc/rc.d/init.d)?
>
> Thanks,
> S
>
>
> [1] http://fuse.sourceforge.net/
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>



--
Better to have a president who makes love instead of war.  Even better if he
understands the difference between the two.
-------------- next part --------------
An HTML attachment was scrubbed...