Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Dec 2007 20:41:53 -0500
From:      "Aryeh Friedman" <aryeh.friedman@gmail.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   loading modules not in /boot/kernel from loader.conf
Message-ID:  <bef9a7920712101741s138b3d48gb5044097f6aee8a8@mail.gmail.com>
In-Reply-To: <bef9a7920712101740w38917ff7m494e6b8bbb57975c@mail.gmail.com>
References:  <475D402D.1080000@gmail.com> <475D92C8.7020404@gmail.com> <475D4CDB.1070608@gmail.com> <475DA681.7070302@web.de> <475D6127.60801@gmail.com> <475DC259.6070006@mawer.org> <bef9a7920712101740w38917ff7m494e6b8bbb57975c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 is a separate partition then this will not work as
> /usr doesn't get mounted until much, much later in the boot process...
>
> Alternatively, if you're using your own home-brew rc script, why not
> just add a kldload fuse into it?
>
> --Antony
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bef9a7920712101741s138b3d48gb5044097f6aee8a8>