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.
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Rep:
TCP/IP enabling
I've noticed that the kernels that are precompiled on the Slack cds have TCP/IP enabled. When I've taken the old config file that was used to compile that kernel, and apply it to a newer vanilla kernel I have difficulty with netconfig. Specifically, if I'm running a new kernel when I run netconfig it says that I don't have TCP/IP enabled. TCP/IP is enabled when I run the kernel that came with Slack.
I'm about to compile the 2.4.31 kernel (again) since I messed up my Slack 10 install and had to wipe it. I have Slack 10.1 installed with the 2.4.29 kernel and am planning on doing a make oldconfig and then a make xconfig so I can see what it chose.
mine is as old but I sysadmin lots of linux boxes and my experience is to keep the kernel and the distro in sync and things work great... slax 10.1 with a 2.4 seems very odd to me, you may have to compile it by hand to make it work... personally, sounds like alot of effort to me. I run newer distros on older machines and the kernel has not been a problem... on a range of distros.
Maybe have another go at it... but the 2.4 kernel has so many limits I only keep it on debian servers.
I think you are looking for INET option.
Btw for menu-driven kernel configuration target menuconfig has turned out for me well. It has well-arranged ncurses based interface so it works in a terminal.
Originally posted by linuxhippy I've noticed that the kernels that are precompiled on the Slack cds have TCP/IP enabled. When I've taken the old config file that was used to compile that kernel, and apply it to a newer vanilla kernel I have difficulty with netconfig.
Be sure that you're not running the command make mrproper after copying the .config file or it will get deleted and the kernel configuration will use a default it has (not suitable for most people).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
but I sysadmin lots of linux boxes and my experience is to keep the kernel and the distro in sync and things work great... slax 10.1 with a 2.4 seems very odd to me, you may have to compile it by hand to make it work... personally, sounds like alot of effort to me. I run newer distros on older machines and the kernel has not been a problem... on a range of distros.
