You are not logged in.
Pages: 1
hi! i want to modprobe the virtual box module (sudo modprob vboxdrv) on every startup! where i have to write the module? there is no /etc/modules file to edit.
thanks
Last edited by manolos (2009-09-18 10:25:08)
Offline
Can't you just add it to modules in /etc/rc.conf MODULES=(... vboxdrv ...)?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Can't you just add it to modules in /etc/rc.conf MODULES=(... vboxdrv ...)?
Indeed, this is the way on arch.
Offline
This isn't the first time you'd be looking at /etc/rc.conf, I hope?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
or ...
you can insert it in /etc/rc.local
Offline
or ...
you can insert it in /etc/rc.local
Nasty hack
Add it to MODULES in rc.conf
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
perbh wrote:or ...
you can insert it in /etc/rc.localNasty hack
Add it to MODULES in rc.conf
Essentially they do the same thing.
from rc.sysinit
for mod in "${MODULES[@]}; do
if [ "$mod" = "$mod#!}" ]; then
/sbin/modprobe $mod
fi
done
But having said that, putting a modprobe statement in rc.local is pointless when it's "meant" to go in the MODULES array. Best to keep everything in one spot
Offline
Essentially they do the same thing.
Yep, but duplicating the functionality of another part of the system will drive you insane in 12 months when you're trying to figure out why module XXX is being loaded when it isn't in MODULES
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I still beg to differ.
MODULES should contain the things to make the system up and running - extras go into /etc/rc.local
I've been playing around with linux since 1996 and arch since 2005 - I have always done it this way and never had any problems "12 months later".
Let us just accept that some like it "this" way and others "that" way - thank goodness that at least we have a choice.
Offline
I still beg to differ.
MODULES should contain the things to make the system up and running - extras go into /etc/rc.local
I've been playing around with linux since 1996 and arch since 2005 - I have always done it this way and never had any problems "12 months later".
Let us just accept that some like it "this" way and others "that" way - thank goodness that at least we have a choice.
Fair enough, but it is ill advised to tell someone else to do it, because a few months later for them, they don't remember that you told them to do something contrary to norm.
The human being created civilization not because of willingness but of a need to be assimilated into higher orders of structure and meaning.
Offline
For the benefit of future readers of this thread trying to solve this problem... The normal practise is to put everything in the MODULES array within rc.conf unless you have a predisposition to doing things "different"
Yes, the beauty of choice!
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
For the added benefit of future readers of this thread ... You don't need to put anything in the MODULES array unless you want to :
1) load certain modules in a certain order .
2) blacklist a certain module .
3) Add a module that is both needed and not auto-loaded .
Otherwise , let MOD_AUTOLOAD and udev do there magic .
Last edited by Nezmer (2009-09-16 08:40:07)
English is not my native language .
Offline
thank you all! it was stupid question i know... but my arch is 1 year old and i forgot many things like how to add a module on startup im still a noob i think!!
Offline
Pages: 1