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. Perhaps apps with include user space tools and kernel modules should be split, so it's possible to have modules for several kernel for one version of the app. I'm not saying that we should make modules for every possible kernel configuration out there, just for those that we officially distribute (like on 013).
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). And if there are a couple of known kernel configurations, we can make module packages for them. -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
