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.
Hey all, I'm just wondering if anyone can help me get dhcpcd to automatically connect on startup, rather than me forced to enter the terminal to do so.
Why play around trying to get the outdated kernel to work when you can update to the latest? It would probably be quicker compiling 2.6.x than trying to track down the current problem anyway.
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
For me it's not. And for me, I used netconfig just to get an idea of how /etc/rc.d/rc.inet1.conf should look like (I was a *complete* newbie at that time).
Anyway, I think the 2.4 kernels are stable & mature enough, and that I would rather look into the problem or live with it than to upgrade to 2.6.
Originally posted by wpyh Then the 2.4 kernel seems to have some problems with it. Why not try find out the problem rather than upgrade to a new kernel?
Because this works. It seems to me, that I found the problem; it's the kernel.
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Well, you're the thread starter, so... yeah, I think not everyone has to read kernel source. I don't have much experience with dhcp, so I can't say anything much here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.