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.
It doesn'y really matter which version of slackware you are using - the option is in the kermel, not the os. You need to recompile kernel with support for high memory. Read the compile kernel guide above.
It will look like this in the .config for the kernel in /usr/src/linux:
If you needed more, 2.4.x can support up to 64GB of memory, it would look like this:
For the short and quick steps to recompile the kernel, do the following:
1. Next open up '/usr/src/linux/Makefile'
Uncomment the line...
2. Also edit your existing /etc/lilo.conf and rename your current default kernel vmlinuz to something like vmlinuz.old and rename the Label to Linux-Old. You do this so if the new kernel breaks, you can reboot into the old kernel to go fix, etc.
3. make menuconfig # skip this if you just use the existing .config in /usr/src/linux and uncomment the lines outlined above or create such lines.
4. make dep
5. make clean
6. make bzImage
7. make install
8. make modules
9. make modules_install
10. Verify and reboot.
Slackware utilized the make install and this will copy over the vmlinuz and update lilo.conf with the new kernel, etc. Good to double check before rebooting.
is it possible that after i rebuild the kernel, my machine wont boot ?
because this is my office mail server, if it does not work then I in trouble.
You can always run into this issue when building a new kernel. That's why the steps involved keep the old kernel around, so you can reboot and rebuild, reconfigure, troubleshoot what went wrong.
The only time I've never had a kernel fail on me in Slackware is cause I was stupid and didn't include the right modules for my NIC, so it worked, I just lacked network connectivity. A quick reboot, change config to include my NIC and it was as easy as make modules and make modules_install and I was up and running after a reboot again.