Ignore:
Timestamp:
05/03/2004 10:59:46 AM (20 years ago)
Author:
Matthew Burgess <matthew@…>
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:
0c43171, 2ec64b3, a4a675f
Parents:
287ea55
Message:
  • Merged newxml into HEAD

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/network.xml

    r287ea55 r673b0d8  
     1<?xml version="1.0" encoding="ISO-8859-1"?>
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
     3  <!ENTITY % general-entities SYSTEM "../general.ent">
     4  %general-entities;
     5]>
    16<sect1 id="ch-scripts-network">
    27<title>Configuring the network script</title>
    3 <?dbhtml filename="network.html" dir="chapter07"?>
     8<?dbhtml filename="network.html"?>
     9
     10<indexterm zone="ch-scripts-network">
     11<primary sortas="d-network">network</primary>
     12<secondary>configuring</secondary></indexterm>
    413
    514<para>This section only applies if you're going to configure a network
     
    918create any configuration files relating to network cards. If that is the
    1019case, you must remove the <filename>network</filename> symlinks from all the
    11 runlevel directories
     20run-level directories
    1221(<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
    1322
     
    1524<title>Configuring default gateway</title>
    1625
    17 <para>If you're on a network you may need to set up the default gateway for
     26<para>If you're on a network you may need to set up the default gateway (a node on your network that provides access to other networks) for
    1827this machine. This is done by adding the proper values to the
    1928/etc/sysconfig/network file by running the following:</para>
     
    4352update the network_devices by providing it with the new path.</para>
    4453
    45 <para>Now, new files are created in that directory containing the following.
     54<para>Now, new files are created in that directory.
    4655The following command creates a sample ifconfig.eth0 file:</para>
    4756
    4857<screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
    4958ONBOOT=yes
     59SERVICE=static
    5060IP=192.168.1.1
    5161NETMASK=255.255.255.0
     
    5565<para>Of course, the values of those variables have to be changed
    5666in every file to match the proper setup. If the ONBOOT variable is set
    57 to yes, the network script will bring it up during the booting of the system.
    58 If set to anything else but yes, it will be ignored by the network script
    59 and thus not brought up.</para>
     67to yes, the network script will bring up the equivalent NIC (Network Interface Card)
     68 during the booting of the system.
     69If set to anything but yes, the equivalent NIC will be ignored by the network script
     70and not brought up.</para>
     71
     72<para>The SERVICE entry defines the method of obtaining the IP address.
     73The LFS bootscripts have a modular IP assignment format, and by creating
     74additional files in /etc/sysconfig/network-devices/services, you can allow
     75other IP assignment methods.  This would commonly be used if you need DHCP,
     76which is addressed in the BLFS book.</para>
    6077
    6178</sect2>
     
    6481<title>Creating the /etc/resolv.conf file</title>
    6582
    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
     83<para>If you're going to be connected to the Internet then most likely you'll
     84need some means of DNS name resolution to resolve Internet domain names to IP
     85addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator,
    6986into <filename>/etc/resolv.conf</filename>. Create the file by running the
    7087following:</para>
     
    7996
    8097<para>Of course, replace &lt;IP address of your nameserver&gt; 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>
     98address of the DNS most appropriate for your setup. There will often be
     99more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
    83100
    84101</sect2>
    85102
    86103</sect1>
    87 
Note: See TracChangeset for help on using the changeset viewer.