Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I made a package for my ALSA driver. I would like it to automatically run the snddevices script and install itself to the appropriate kernel directory. For example, I compiled the package on the 2.6.14.3 kernel, and now I want to install it on a 2.6.16.9 kernel. The appropriate /lib/modules/KernelVersion has changed. Is there a way to make it correctly find the modules directory for any later kernel? Thanks.
To be honest, while you can get away with your approach for a while, sooner or later it is going to break. I think you're much better off running the slackbuild scripts for ALSA when you upgrade your kernel rather than trying to fiddle with a package to get it to install.
I can install ALSA no problems with Slackware. I just build it from source, install and run a few scripts. I reinstall my kernel a lot though. I am a beginner and I mess up things ALL the time. So, I want to make this package once and have it last forever. Perhaps a better idea would be for me to make my own build script. When my version gets outdated (ie. upgrading the kernel), I just rebuild the whole package.
So, I want to make this package once and have it last forever. Perhaps a better idea would be for me to make my own build script. When my version gets outdated (ie. upgrading the kernel), I just rebuild the whole package.
I certainly understand the sentiment, but sooner or later the kernel is going to change something that will break the modules. Personally, I find it much easier to rebuild things like ALSA from source rather than copying modules from one kernel to the next. And since Pat supplies both the ALSA source code and the scripts used to build the official Slackware packages in the sources directory (on CD4 if you have the CDs), you don't even have to make your own build scripts.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.