Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
My shiny new lfs system boots up. Mmmmmm, nice. But what of eth0?
I've compiled in the PCMCIA cardbus support (it's a Netgear FA411 for which a drivers included in the kernel). But when I boot into runlevel 3, it complains that the ifconfig.eth0 script is incomplete. Am I missing something in the ifconfig.eth0 file?
That'll be it. No dhcp client installed. The lfs chapter gave the impression that it wasn't needed but i guess they were only talking about setting up machines with static IP addresses in that chapter. (Does anyone set up machines with static IPs any more?).
The reason I said "Does anyone install with static IP" was talking about end-user machines, not servers of course (unless it's edonkey ). It comes back to the old IPv4 and IPv6 problem.
DHCP is the market's answer to IPv4. Just like we hoped solar-powered cars might be the answer to oil shortages. DHCP is good though - as an end user, I'd prefer it because I'm a moving target for wouldbe miscreants. It might not be secure for a determined attacker but there's usually a firewall of some description sitting between you and the cloud.
The length of the lease on cable IP addresses must depend on traffic. There's really no other way to do it. And if you think about it, not having a static IP always makes sense if you're not running a server.
I still think that static is better for your lan. Since you know the address of everything, you can easilly get to any machine.... you might need to access boxes that aren't servers. you can then easilly set up hosts so that you don't have to remember all of the ip's w/out needing a dns server.
Also, If you have a large network, it would be too easy for somebody to come along and plug their laptop into the network and start crack'n around... plus, it would make it a lot harder to determine where the intruder plugged in.