Changeset 45340ae
- Timestamp:
- 01/10/2004 01:10:21 AM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 12c8f83b
- Parents:
- 1969cea
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r1969cea r45340ae 50 50 </itemizedlist> 51 51 </listitem> 52 53 <listitem><para>January 9th, 2004 [greg]: Chapter 7 - Configuring the network 54 script: Added instructions to create /etc/resolv.conf. Closes 55 733.</para></listitem> 52 56 53 57 <listitem><para>January 9th, 2004 [greg]: Chapter 8 - Making the LFS system -
chapter07/network.xml
r1969cea r45340ae 61 61 </sect2> 62 62 63 <sect2> 64 <title>Creating the /etc/resolv.conf file</title> 65 66 <para>If you're going to be connected to the internet then most likely you'll 67 need some means of DNS name resolution to resolve internet domain names to IP 68 addresses. This is best achieved by placing the IP address of a DNS server 69 into <filename>/etc/resolv.conf</filename>. Create the file by running the 70 following:</para> 71 72 <screen><userinput>cat > /etc/resolv.conf << "EOF"</userinput> 73 # Begin /etc/resolv.conf 74 75 nameserver <IP address of your nameserver> 76 77 # End /etc/resolv.conf 78 <userinput>EOF</userinput></screen> 79 80 <para>Of course, replace <IP address of your nameserver> with the IP 81 address of the DNS server most appropriate for your setup. This will often be 82 provided by your ISP or it may even be a router on your local network.</para> 83 84 </sect2> 85 63 86 </sect1> 64 87
Note:
See TracChangeset
for help on using the changeset viewer.