Re: Freshrpms update

On Thu, 2008-01-17 at 16:42 -0800, Troy Engel wrote:
> Τάσος Χρόνης wrote:
> > 
> >     Don't confuse things. It's the logic behind proprietary software which
> >     is inherently flawed :-) 
> > 
> > True. But what I said could be applied to open source modules outside 
> > linux tree like kqemu, lirc e.t.c.
> > IMHO  the dkms logic works better at least for me.
> 
> Due to the unavailability of an nvidia 96xx driver for F7 + 2.6.23 
> kernels I switched to Livna for these packages, so I've had a good bit 
> of time to try dkms verus kmod and kmod actually works better when 
> there's a kernel upgrade and no supporting driver, such as in my case.
> 
> dkms: driver fails to compile after rebooting a new kernel (as with F7 + 
> 2.6.23)? you're out of luck; your entire X config is based on that and X 
> will refuse to work until you fix it by hand. Very bad.
> 
> kmod: no driver installed (RPM) for current kernel? no problem, it falls 
> back to using the builtin nvidia open source driver and you never have 
> to mess with your configs. Install the new RPM when it's available, 
> reboot and it's back working. Very good.
> 
> My $0.02, kmod works better for video drivers - dkms fell flat on it's 
> face and kmod just kept on rolling.

Hey guys sorry it took me so long to catch this thread.  I have just
been way to busy.  

This has been discussed a bit on fedora-devel and fedora-desktop.  The
solution I proposed that was agreed could be accepted into fedora, would
be to integrate dkms into the /sbin/installkernel
and /sbin/new-kernel-pkg code.  This will allow a user to install a new
kernel and instantly know if all his dkms packages built against it
correctly.  I should also be able to read in settings so if certain
"necessary" modules fail to build then grub is not updated to default to
the new kernel.

Jon