FS#39994 - [mkinitcpio] File extensions like *.conf~ are also added
Attached to Project:
Arch Linux
Opened by t-ask (tAsk) - Monday, 21 April 2014, 18:15 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 21 June 2014, 16:39 GMT
Opened by t-ask (tAsk) - Monday, 21 April 2014, 18:15 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 21 June 2014, 16:39 GMT
|
Details
Description:
I edited the file "/etc/modprobe.d/uvesafb.conf" and my editor created also "/etc/modprobe.d/uvesafb.conf~". With the command "mkinitcpio -v | grep vesa" I get also the "*.conf~" file listed: adding module: uvesafb adding file: /usr/lib/modprobe.d/uvesafb.conf adding file: /etc/modprobe.d/uvesafb.conf adding file: /etc/modprobe.d/uvesafb.conf~ <---- overwriting file: /usr/lib/modprobe.d/uvesafb.conf Should that be the case? |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 21 June 2014, 16:39 GMT
Reason for closing: Fixed
Additional comments about closing: https://projects.archlinux.org/mkinitcpi o.git/commit/?id=02d387b2370
Saturday, 21 June 2014, 16:39 GMT
Reason for closing: Fixed
Additional comments about closing: https://projects.archlinux.org/mkinitcpi o.git/commit/?id=02d387b2370
Comment by
Dave Reisner (falconindy) - Monday,
21 April 2014, 18:26 GMT
There's no harm done. modprobe isn't going to read anything that
doesn't end with .conf anyways.