On Fri, 24 Nov 2006 11:20:11 +0100 "Jonas Karlsson" <[EMAIL PROTECTED]> wrote:
> After the resent discussion on the user list about getting a kernel module > to work, I remembered an old discussion about how to match module with > kernel version if someone made a package with a kernel module. Somehow it > should be visible on the package name which kernel is needed so > InstallPackage could fetch the correct package. Moreover, it could be a version window. For instance, there are some funky drivers that were released for 2.X.XX, and as long as they work, a new one is not released. > I also think that perhaps we should create a kernel package once in a > while. I mean, do we really expect users to be on 2.6.11.9 from the > release of 012 until they upgrade to 013? On one hand, it's really easy to > compile an own kernel with Compile, but not all users would want that (for > different reasons). Completely agreed. > And if there are a couple of known kernel > configurations, we can make module packages for them. It would be nice -- you install a generic kernel, but later you can choose to update to a more specific kernel (tuned for some major CPU, like amd64 or so). This may look like babysitting, but my experiences with "common" users is that they won't do anything if the slightest doubt crosses their minds, and will stick to 2.6.8 forever. I believe this would only require slightly different kernel configurations, for different i686 CPUs (and, why not, amd64 even using a x86-32 base system?). The drawback is that this may create weird arch-specific bug reports. But you can always blame Lucas! :) -- Ricardo Nabinger Sanchez <[EMAIL PROTECTED],wait4.org}> Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
