Re: Grrr... modprobe.conf

2010-09-20 Thread Michał Piotrowski
2010/9/20 Jon Masters : > Right. I get what you're trying to say. Yes, indeed, whatever is > creating the legacy file should stop doing that. Are we sure it's not > anaconda doing it during installation? I don't have this file my rawhide system - it was installed from F14 Alpha KDE Live CD. Of co

Re: Grrr... modprobe.conf

2010-09-20 Thread Jon Masters
On Mon, 2010-09-20 at 20:57 +0200, Michał Piotrowski wrote: > W dniu 20 września 2010 20:47 użytkownik drago01 napisał: > > 2010/9/20 Michał Piotrowski : > >> W dniu 20 września 2010 20:03 użytkownik drago01 > >> napisał: > >>> Why? > >>> The file is obsolete for a while now, apps that rely on i

Re: Grrr... modprobe.conf

2010-09-20 Thread Michał Piotrowski
W dniu 20 września 2010 20:47 użytkownik drago01 napisał: > 2010/9/20 Michał Piotrowski : >> W dniu 20 września 2010 20:03 użytkownik drago01 napisał: >>> Why? >>> The file is obsolete for a while now, apps that rely on it if any >>> should crash and burn and use the proper interface (/etc/modpro

Re: Grrr... modprobe.conf

2010-09-20 Thread drago01
2010/9/20 Michał Piotrowski : > W dniu 20 września 2010 20:03 użytkownik drago01 napisał: >> Why? >> The file is obsolete for a while now, apps that rely on it if any >> should crash and burn and use the proper interface (/etc/modprobe.d) >> I can't think of a reason why "someone will change this

Re: Grrr... modprobe.conf

2010-09-20 Thread Michał Piotrowski
W dniu 20 września 2010 20:03 użytkownik drago01 napisał: > Why? > The file is obsolete for a while now, apps that rely on it if any > should crash and burn and use the proper interface (/etc/modprobe.d) > I can't think of a reason why "someone will change this again". In the same way that someon

Re: Grrr... modprobe.conf

2010-09-20 Thread drago01
2010/9/20 Michał Piotrowski : > W dniu 20 września 2010 15:02 użytkownik drago01 napisał: >> Well depends on the cirumstances. > > I fully agree. > >> >> As the file is supposed to be obsolete anyway ... we should just make >> modprobe ignore it ;) > > This is not a solution to the problem. Now th

Re: Grrr... modprobe.conf

2010-09-20 Thread John Reiser
. >> >> Jon. >> >> >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel > > Messages to the list are available in the web archive. Please give a helpful reply, or none at all. The ea

Re: Grrr... modprobe.conf

2010-09-20 Thread Robert 'Bob' Jensen
- "Jon Masters" wrote: > > I'm missing the original mail in this thread because I think it went > to > a different list. Can someone forward it to me, please. Thanks. > > Jon. > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/

Re: Grrr... modprobe.conf

2010-09-20 Thread Jon Masters
On Mon, 2010-09-20 at 14:54 +0200, Michał Piotrowski wrote: > 2010/9/20 Bryn M. Reeves : > > On 09/20/2010 01:37 PM, Tom Horsley wrote: > >> On Mon, 20 Sep 2010 11:56:56 +0200 > >> Michał Piotrowski wrote: > >> > >>> You can blacklist the firewall modules - it can be critical :) > >> > >> Actually,

Re: Grrr... modprobe.conf

2010-09-20 Thread Michał Piotrowski
W dniu 20 września 2010 15:02 użytkownik drago01 napisał: > Well depends on the cirumstances. I fully agree. > > As the file is supposed to be obsolete anyway ... we should just make > modprobe ignore it ;) This is not a solution to the problem. Now the file will be ignored, but in a few months

Re: Grrr... modprobe.conf

2010-09-20 Thread drago01
2010/9/20 Michał Piotrowski : > 2010/9/20 Bryn M. Reeves : >> On 09/20/2010 01:37 PM, Tom Horsley wrote: >>> On Mon, 20 Sep 2010 11:56:56 +0200 >>> Michał Piotrowski wrote: >>> You can blacklist the firewall modules - it can be critical :) >>> >>> Actually, I think you can run any arbitrary co

Re: Grrr... modprobe.conf

2010-09-20 Thread Michał Piotrowski
2010/9/20 Bryn M. Reeves : > On 09/20/2010 01:37 PM, Tom Horsley wrote: >> On Mon, 20 Sep 2010 11:56:56 +0200 >> Michał Piotrowski wrote: >> >>> You can blacklist the firewall modules - it can be critical :) >> >> Actually, I think you can run any arbitrary command to >> load a module, Or pass any