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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Do that in some subdirectory, not in /, like /usr/src/mymodules.
Then put your install dir and lib/modules dirs inside that. Put the files in there. The cd into /usr/src/mymodules and run makepkg. Be sure to give a proper name-version-arch-build.tgz name for the package and the name part should match exactly the 'name:' entries in the slack-desc file.

@gnashley shh i must go all the way again then
ill do it tomorrow, can you tell me whats the difference in process between makepkg and src2pkg, yet ive never done it under / but in /home/matters/testmodules/ ive put all but and then ive just tar.gz and then rename it to tgz that all i didnt run makepkg.

Im close to finish the project. its nice knowledge

read please my other post about package dependency maybe you know what i mean.

htexmex thanks for contribution too, im just too much in deep reason why is why and like to learn the process in betweeen )

I believe files are only removed if they exist only in that package - ie, there is no other package where they're listed.

If you have a default kernel installed as a package, the modules will be in, let's say: /lib/modules/2.6.14

Now let's say you custom compile the same kernel, 2.6.14, then they'll end up in the same place, so when you removepkg mymodules it checks the list of files in packages in /var/log/packages and says "ahha, these exist in kernel-modules-that-came-with-slack.tgz, i shall leave them alone". So, you end up with the /var/log/packages/ entry for mymodules gone, but the modules it installed, probably not.

The solution to this would be to have a suffix on your kernel stuff which is an option somewhere ... you'd have to hope some nice poster will help out here or google it, because i don't recall.

... and so the princess kissed the frog who turned into a handsome prince, and they all lived happily ever after. The end. *zzZzzz*