2010/9/20 Richard Shaw <hobbes1069@xxxxxxxxx>: > On Mon, Sep 20, 2010 at 7:49 AM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: >> So, if this bug is valid as described it's a significant security issue. >> However, I'm not sure it's simple. I've just checked, and none of my F14 >> test spins (basically RC2) have a modprobe.conf booted live. The clean >> installed system from the desktop live image that I have in my test VM >> currently doesn't have one either. Neither does my 'work' system itself. >> >> If it's dracut as you surmise, it may perhaps happen only on installing >> a kernel after initial install. I guess also it may only happen when >> installing from non-live media. We should definitely look into this >> urgently. >> >> What's the last-touched date of your /etc/modprobe.conf ? Do you know >> when that is in relation to the lifetime of the install? > > I have some anecdotal evidence. I installed F13 (x86_64) on my dad's > computer this weekend. I did not see the empty modprobe.conf until > after I did a kernel update. I'm using compiled 2.6.35.4-28 here. So it can be issue with F13 kernel package. > The only packages I updated was the > kernel and the firmware package at that time. > > Richard Regards, Michal -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
