Re: modprobe changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



2009/7/2 Thomas Bächler <thomas@xxxxxxxxxxxxx>:
> Aaron Griffin schrieb:
>>
>> I think you're mistaken. Our modprobe doesn't have any message of the
>> sort, relating to Arch. The error you are seeing is due to a change in
>> the way modprobe parses config files. It used to read
>> /etc/modprobe.conf and/or /etc/modprobe.d/* - now it only reads
>> /etc/modprobe.d/*.conf
>>
>> The message is modprobe telling you something is wrong with the config
>> files. Most likely you just have a .pacsav file in /etc/modprobe.d/
>
> This is annoying, I thought it would simply ignore those files. Now it seems
> that it reads them, but prints that warning. Do you think we should patch it
> to at least ignore .pacsave files until they remove this warning and
> backward-compatibility?
>
>

I've noticed an issue regarding mkinitcpio and the new modprobe changes that
requires a symlink from /etc/modprobe.conf to /etc/modprobe.d/modprobe.conf
in order for options for any modules you load in the initramfs to be applied,
just incase this hasn't been reported yet.

Damien


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux