I download the RHEL 6b2 and noticed the modprobe.conf was no longer present. I used modprobe.conf to place "options" for ethernet drivers like which order to install the drivers. e1000e before forcedeth - things like that. Anyway - seems like that file is no longer present. what is the "future" way to handle driver options? Thanks Jerry
On 07/06/2010 11:54 AM, Jerry Geis wrote:> I download the RHEL 6b2 and noticed the modprobe.conf > was no longer present. > > I used modprobe.conf to place "options" for ethernet drivers > like which order to install the drivers. e1000e before forcedeth - > things like that. > Anyway - seems like that file is no longer present. > > what is the "future" way to handle driver options? > > Thanks > > Jerry > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >Create a new file in /etc/modprobe.d, with the options you normally put in /etc/modprobe.conf. Any file in that directory is loaded just as /etc/modprobe.conf was. Emmett
On 07/06/2010 01:54 PM, Jerry Geis wrote:> I download the RHEL 6b2 and noticed the modprobe.conf > was no longer present. > > I used modprobe.conf to place "options" for ethernet drivers > like which order to install the drivers. e1000e before forcedeth - > things like that. > Anyway - seems like that file is no longer present. > > what is the "future" way to handle driver options?Similar content is now broken up into separate .conf files in directory /etc/modprobe.d so that individual packages can now have sole ownership of a file rather than trying to pack all their parameters into a single, hard to maintain file. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.
On 07/06/2010 02:54 PM Jerry Geis wrote:> I download the RHEL 6b2 and noticed the modprobe.conf > was no longer present. > > I used modprobe.conf to place "options" for ethernet drivers > like which order to install the drivers. e1000e before forcedeth - > things like that. > Anyway - seems like that file is no longer present. > > what is the "future" way to handle driver options? > > Thanks > > JerryOn this system (with the latest 5.5 updates) there is an /etc/modprobe.conf file. It must have been created by the system... because I didn't create it. Nor have I made any changes to it... ever. Moreover, the Access, Modify, and Change timestamps all correspond to the last time the system was booted. According to "man modprobe.conf": There is a generate_modprobe.conf program which should do a reasonable job of generating modprobe.conf from your current (2.4 or 2.2) modules setup. This program, however, isn't present on my system. Manpages should have dates in the content revealing their last update.