SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Click Here to receive this Complete Guide absolutely free.
I'm trying to follow the "Kernel compiling guide for newbies..." thread in this forum and I've come to the "make menuconfig" part. The problem is that the make command doesn't work - all I get is command not found. If someone could point me to a tutorial I'll appreciate it (I've read the Slack-book, but couldn't find an answer).
Edit: Upon further investigation I've found out that the ./configure command isn't working either, do these two command errors have to do with a missing developer package?
now './configure' will not work, because and executable file named configure is not included in the kernel source. -- ./<filename> is a way to execute a program (usually some sort of script) located in the current working directory. do 'ls /usr/src/linux' and you'll see that there is no executable file named 'configure'.
yup, if you want to build/compile things from source, you're going to need this. do: 'which make' and you'll see that you don't have it.
I'm using Slackware 10 and am about to install the GNU make that you recommended. What boggles me (and my friends) is that such an elementary function/program as Make isn't included in Slackware, isn't it one of the most important functions in Linux?
There is a easy way, just put your slackware cd in, goto the d directory inside slackware dir, and installpkg (see: man installpkg) the packages you need.
You'll need to install more packages than make and gcc, I'd recommend you to install all in the d dir except you want to save some space, exclude python and/or j2sdk (if you're not going to use it although a lot of things nowadays depends on them). The rest is just small to keep it or necessary to compile lot of things.
Well that's because each package is accompanied by 2 other files .asc file has the checksum to see if the file is corrupted or not, and .txt has it's description. You shouldn't worry about that, try cd /mnt/cdrom/slackware/d and there run: pkgtool and choose the first option (install packages from the current directory). pkgtool is a front-end to installpkg (any doubt, again see the man page :P).