130309 Philip Webb wrote:
> 130309 »Q« wrote:
>> 130309 Philip Webb wrote:
>>> Doing my usual Saturday system update, I saw a prominent msg
>>> telling me that 'module-init-tools' has been masked
>>> & to use 'kmod' or 'modutils' -- the msgs vary -- to replace it.
>>> When I did so (both), Nvidia
On Sat, 9 Mar 2013 21:02:02 -0600
»Q« wrote:
> On Sat, 9 Mar 2013 21:22:23 -0500
> Philip Webb wrote:
>
> > It looks as if the change needs a 'news' msg.
>
> If it turns out to be solved by the tools flag for kmod, I gotta
> disagree. I also use -* , but I don't think we should get news items
On Sat, 9 Mar 2013 21:22:23 -0500
Philip Webb wrote:
> It looks as if the change needs a 'news' msg.
If it turns out to be solved by the tools flag for kmod, I gotta
disagree. I also use -* , but I don't think we should get news items
whenever that's going to break something for us; we've effe
130309 »Q« wrote:
> 130309 Philip Webb wrote:
>> Doing my usual Saturday system update, I saw a prominent msg
>> telling me that 'module-init-tools' has been masked
>> & to use 'kmod' or 'modutils' -- the msgs vary -- to replace it.
>> When I did so (both), Nvidia wouldn't start, even after remerg
On Sat, 9 Mar 2013 08:07:45 -0500
Philip Webb wrote:
> Doing my usual Saturday system update, I saw a prominent msg
> telling me that 'module-init-tools' has been masked
> & to use 'kmod' or 'modutils' -- the msgs vary -- to replace it.
> When I did so (both), Nvidia wouldn't start, even after re
5 matches
Mail list logo