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.
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.
/etc/resolv.conf is a configuration file, not a script.
What exactly did you try, and what were you trying to accomplish?
To specify a nameserver, use the "nameserver" directive (for instance, nameserver 8.8.8.8). man resolv.conf will tell you about the various configuration options.
resolv.conf gets overwritten by network configuration helpers like DHCPD or NetworkManager. To manage your nameservers with helpers present you have to configure them instead. Only if your network configuration is totally manual - I. E. no helpers are running - editing resolv.conf will work.
Since your new LFS system booted for the first time only a few hours ago today, I doubt that things like NetworkManager or DHCP and their effect on resolve.conf are involved here yet. I could be wrong in this case though. Sometimes people do like to go straight to dynamic IP addressing over the static IP addressing in the LFS book.
I wonder if your problem is possibly the configuration of your network device (i.e., drivers, firmware, config files, etc.). Anyway, problems with those things seem to be way more common at this early stage IMO.
I recommend that you take a moment to describe what the problem actually is and what you've accomplished so far to configure the network device and confirm it's being brought up and acquiring an IP address from your access point. Resolving DNS addresses is of no importance until that kind of stuff is right and working. Maybe the network device is connected and working, but there's no way to tell from the posts so far.
Ok, i am going to explain my problem.
When i rebooted lfs for the first time I tried to conect to google (ping google.com) , i think the error is in the /etc/resolv.conf file, but i am not sure.
How i conect to internet?
I tryed all the resolv.conf nameservers and domains, but no works, when i put ping google.com it shows that messange:
Ping:inaccesible network, i doent tryed traceroute and yes, i have network via ethernet
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.