SlackwareThis Forum is for the discussion of Slackware Linux.
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've downloaded whax (http://www.iwhax.net) and tried to run it. It runs so slow that I can't work with it. Now I want to add the modules of whax to the real slackware. How do I do this and how do I use them then?
I just read up on their website, it appears that to make a Whax module, you take a standard slack package, and run a script of their creation to create a .mo file. Slackware does not know what a .mo is, and would have no idea what to do with it. If Whax has a tool to turn their modules(.mo) back into slack packages(.tgz) then those could very possibly be installed in slackware.
A more sensible route would be to make a list of which items in Whax you would like to have, and get them elsewhere. I have most of the tools they are including installed on my own slackware laptop...largely compiled from source. This isn't as hard as it sounds, ans its something you're likely to want to learn anyways. Barring that, linuxpackages.net is full of pre-packages slackware packages that all kinds of people have created. Because these are all 3rd party, its somewhat hit and miss...Pat's packages are always most reliable, as is source code. That said, I have rarely had issues with packages from linuxpackages.net, and its likely you won't either...although compiling from source and using "checkinstall"(which is in slackware's /extra directory on the CDs) is probably the best path, short of learning to roll your own slackware packages, which is a little more involved.
I've got a little offtopic question but it's not worth a new topic so: Where do I get a real complete kernel that goes very well with slackware? Because I've just installed the complete slackware but the wrong kernel that doesn't support my USB stick and no APM and ALSA
if you installed a kernel from www.kernel.org them you havent installed the wrong kernel. You cant just install the kernel and get everything working on the fly. And there arent this of "real kernel for slackware" when you say you´re using Linux in the fact this is the name of the heart of the system, the kernel. Gnome isnt linux, openoffice isnt linux, the kernel is linux. So every linux are compiled with a linux kernel. If you take a BSD so you will take something the is not linux, its a BSD kernel.
For what I have knoledge, every kernel since 2.4 supports usb, apm and alsa, so isnt you kernel who havent give you enough support, its you that didnt compiled it right, with the right modules or with the right support just built in the kernel. Only if you dig very much in the kernel.org you probably are using a 2.4 or 2.6 kernel series.
You have to follow the proceed to compiled the kernel, for 2.6.x kernels (first of all you have to untar the file in the /usr/src):
#make mrproper
#make menuconfig
#make bzImage
#make modules_install
#make install
well, this isnt to be your kernel compilations manual, this is just a point, you can find in this forums a lot, but a lot of post about compiling the kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.