Re: correct way to specify a new module to load on boot and add parameters
- To: firstname.lastname@example.org
- Subject: Re: correct way to specify a new module to load on boot and add parameters
- From: Joachim Fahnenmüller <email@example.com>
- Date: Tue, 2 Aug 2005 21:55:47 +0200
- Message-id: <20050802195547.GA2429@debianpc>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <001601c59793$5f9a94c0$0302000a@MLENZLAPTOP>
- References: <001601c59793$5f9a94c0$0302000a@MLENZLAPTOP>
On Tue, Aug 02, 2005 at 01:52:46PM -0500, Matthew Lenz wrote:
> .. i am adding bonding to all my servers ethernet interfaces and I need to make the bonding module load on boot with specific parameters. I currently modified the /etc/modules file and added my
> bonding mode=active-backup primary=eth0 miimon=250
> made the appropriate /etc/network/interfaces changes and reboots.. everything works perfectly.
Right. /etc/modules is for the modules to be loaded on boot.
> I just want to know if I put the module stuff in the right place. It seems thatI also could have put an alias for bond0 bonding .etc. etc. in /etc/modules.conf but i wasn't sure.
An alias in /etc/modules.conf means: The module will be loaded when the alias
(device) is called. BTW: Don't change /etc/modules.conf directly, but write a
separate file in /etc/modutils/. See man update-modules.
> which way is correct so that package updates to the system won't overwrite my config?