[Mageia-dev] Nouveau nvidia vesa conflict

[Colin Guthrie]

'Twas brillig, and zezinho at 25/02/13 15:10 did gyre and gimble:
> Em 24-02-2013 21:20, Thomas Backlund escreveu:
>> So just install that one, regenerate the initrd and reboot.
>>
> Would it be a bad idea that dracut install
> triggers by itself a initrd rebuild?

Well, consider when this problem was introduced rather than when it was
fixed.... it would have then actively *broken* your initrd's rather than
fixing them.

It's also a much bigger problem overall. The initrd copies binaries and
libraries from your running system to create the initrd. You could argue
that replacing any one of those components should also trigger a rebuild...

Don't get me wrong, I think we should likely put some kind of
infrastructure in place to make this easier, but I also don't want to
see several initrd rebuilds during an upgrade. It's better to do it
once, right at the end, but I don't think we really have any kind of
"post-everything" kind of trigger we can use for that.

FWIW, looking at how the kernel is packaged and how initrds are
generated (or not) is on my todo list (hopefully with Thomas'
support/input) for MGA4). In an ideal world we'd simply skip initrds for
systems that don't need them (I've very deliberately configured my new
laptop in a way that it shouldn't need an initrd for exactly this reason).

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/