Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 currently have my deafult network interface disabled at boot time. Here's why; my main machine is a laptop and I use it in different situations a lot. If I have the eth0 interface set to start on boot and I have the network unplugged, it takes about 5 minutes for it to realize this and continue booting. Is there a way to cut back the time it takes for the computer to boot without having to set eth0 to not start at boot.
Assuming you're using DHCP, try opening /etc/sysconfig/network if it exists, and adding the line "DHCP_TIMEOUT=10" (or however many seconds you'd like).
It varies a little between different distros, so if that doesn't work, what are you running?
If I remember right, the /sbin/ifup script starts the network interfaces, and calls the dhcpcd program from it. You could try searching through the file and if you see dhcpcd being called, add "-t 10" after it (for a timeout of 10 seconds).
Originally posted by faralen If I remember right, the /sbin/ifup script starts the network interfaces, and calls the dhcpcd program from it. You could try searching through the file and if you see dhcpcd being called, add "-t 10" after it (for a timeout of 10 seconds).
Otherwise, sorry, out of ideas...
faralen is right, I did this exact thing on my laptop. It works.