mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-12-27 11:43:52 -05:00
3ea5d3b1db
This is a rough draft of LFS w/ OpenRC without SysVinit. This is nowhere close for a merge as I need to confirm this works with LFS. Beyond that, BLFS also must get support, and BLFS will be a battlefield. Until we get to that point, please do not have this merged. This branch has been created because the LSB is getting changed, where SysVinit will not be part of it. However, OpenRC will be. OpenRC also provides technology projects like GNOME use. SysVinit simply will not get those technologies. I believe OpenRC will be the way to go, going forward for an educational alternative to the Systemd version of LFS. SysVinit can act as an init system under OpenRC, which would introduce unneeded complexity. That's why this removes SysVinit. This shall get rendered at https://linuxfromscratch.org/~zeckma/. MLFS support is not planned until merge into trunk. Feedback is appreciated.
202 lines
8.0 KiB
XML
202 lines
8.0 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % general-entities SYSTEM "../general.ent">
|
|
%general-entities;
|
|
]>
|
|
|
|
<sect1 id="ch-config-network" revision="openrc">
|
|
<?dbhtml filename="network.html"?>
|
|
|
|
<title>General Network Configuration</title>
|
|
|
|
<indexterm zone="ch-config-network">
|
|
<primary sortas="d-network">network</primary>
|
|
<secondary>configuring</secondary></indexterm>
|
|
|
|
<sect2>
|
|
<title>Creating Network Interface Configuration Files</title>
|
|
|
|
<para>The <filename>/etc/conf.d/network</filename> file determines which
|
|
interfaces are brought up and down by the <command>network</command>
|
|
service.</para>
|
|
|
|
<note>
|
|
<para>If the procedure in the previous section was not used, udev
|
|
will assign network card interface names based on system physical
|
|
characteristics such as enp2s1. If you are not sure what your interface
|
|
name is, you can always run <command>ip link</command> or <command>ls
|
|
/sys/class/net</command> after you have booted your system.
|
|
</para>
|
|
|
|
<para>The interface names depend on the implementation and
|
|
configuration of the udev daemon running on the system. The udev
|
|
daemon for LFS (installed in <xref linkend="ch-system-udev"/>) will
|
|
not run until the LFS system is booted. So the interface names
|
|
in the LFS system cannot always be determined by running
|
|
those commands on the host distro,
|
|
<emphasis>even in the chroot environment</emphasis>.</para>
|
|
</note>
|
|
|
|
<para>To specify the interfaces you want to have brought up, edit
|
|
the <filename>/etc/conf.d/network</filename> configuration file, which has
|
|
plenty of comments.</para>
|
|
|
|
</sect2>
|
|
<sect2 id="resolv.conf">
|
|
<title>Creating the /etc/resolv.conf File</title>
|
|
|
|
<indexterm zone="resolv.conf">
|
|
<primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
|
|
</indexterm>
|
|
|
|
<para>The system will need some means of obtaining Domain Name Service
|
|
(DNS) name resolution to resolve Internet domain names to IP addresses, and
|
|
vice versa. This is best achieved by placing the IP address of the DNS
|
|
server, available from the ISP or network administrator, into
|
|
<filename>/etc/resolv.conf</filename>. Create the file by running the
|
|
following:</para>
|
|
|
|
<screen><userinput>cat > /etc/resolv.conf << "EOF"
|
|
<literal># Begin /etc/resolv.conf
|
|
|
|
domain <replaceable><Your Domain Name></replaceable>
|
|
nameserver <replaceable><IP address of your primary nameserver></replaceable>
|
|
nameserver <replaceable><IP address of your secondary nameserver></replaceable>
|
|
|
|
# End /etc/resolv.conf</literal>
|
|
EOF</userinput></screen>
|
|
|
|
<para>The <varname>domain</varname> statement can be omitted
|
|
or replaced with a <varname>search</varname> statement. See the man page for
|
|
resolv.conf for more details.</para>
|
|
|
|
<para>Replace <replaceable><IP address of the nameserver></replaceable>
|
|
with the IP address of the DNS most appropriate for the setup. There will
|
|
often be more than one entry (requirements demand secondary servers for
|
|
fallback capability). If you only need or want one DNS server, remove the
|
|
second <emphasis>nameserver</emphasis> line from the file. The IP address
|
|
may also be a router on the local network.</para>
|
|
|
|
<note>
|
|
<para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para>
|
|
</note>
|
|
|
|
</sect2>
|
|
|
|
<sect2 id="ch-config-hostname">
|
|
<title>Configuring the System Hostname</title>
|
|
|
|
<indexterm zone="ch-config-hostname">
|
|
<primary sortas="d-hostname">hostname</primary>
|
|
<secondary>configuring</secondary>
|
|
</indexterm>
|
|
|
|
<para>During the boot process, the file <filename>/etc/hostname</filename>
|
|
is used for establishing the system's hostname.</para>
|
|
|
|
<para>Create the <filename>/etc/hostname</filename> file and enter a
|
|
hostname by running:</para>
|
|
|
|
<screen><userinput>echo "<replaceable><lfs></replaceable>" > /etc/hostname</userinput></screen>
|
|
|
|
<para><replaceable><lfs></replaceable> needs to be replaced with the
|
|
name given to the computer. Do not enter the Fully Qualified Domain Name
|
|
(FQDN) here. That information goes in the
|
|
<filename>/etc/hosts</filename> file.</para>
|
|
|
|
</sect2>
|
|
|
|
<sect2 id="ch-config-hosts">
|
|
<title>Customizing the /etc/hosts File</title>
|
|
|
|
<indexterm zone="ch-config-hosts">
|
|
<primary sortas="e-/etc/hosts">/etc/hosts</primary>
|
|
</indexterm>
|
|
|
|
<indexterm zone="ch-config-hosts">
|
|
<primary sortas="d-localnet">localnet</primary>
|
|
<secondary>/etc/hosts</secondary>
|
|
</indexterm>
|
|
|
|
<indexterm zone="ch-config-hosts">
|
|
<primary sortas="d-network">network</primary>
|
|
<secondary>/etc/hosts</secondary>
|
|
</indexterm>
|
|
|
|
<para>Decide on a fully-qualified domain name (FQDN), and possible aliases
|
|
for use in the <filename>/etc/hosts</filename> file. If using static IP
|
|
addresses, you'll also need to decide on an IP address. The syntax
|
|
for a hosts file entry is:</para>
|
|
|
|
<screen><literal>IP_address myhost.example.org aliases</literal></screen>
|
|
|
|
<para>Unless the computer is to be visible to the Internet (i.e., there is
|
|
a registered domain and a valid block of assigned IP addresses—most
|
|
users do not have this), make sure that the IP address is in the private
|
|
network IP address range. Valid ranges are:</para>
|
|
|
|
<screen><literal>Private Network Address Range Normal Prefix
|
|
10.0.0.1 - 10.255.255.254 8
|
|
172.x.0.1 - 172.x.255.254 16
|
|
192.168.y.1 - 192.168.y.254 24</literal></screen>
|
|
|
|
<para>x can be any number in the range 16-31. y can be any number in the
|
|
range 0-255.</para>
|
|
|
|
<para>A valid private IP address could be 192.168.1.2.</para>
|
|
|
|
<para>If the computer is to be visible to the Internet, a valid FQDN
|
|
can be the domain name itself, or a string resulted by concatenating a
|
|
prefix (often the hostname) and the domain name with a <quote>.</quote>
|
|
character. And, you need to contact the domain provider to resolve the
|
|
FQDN to your public IP address.</para>
|
|
|
|
<para>Even if the computer is not visible to the Internet, a FQDN is
|
|
still needed for certain programs, such as MTAs, to operate properly.
|
|
A special FQDN, <literal>localhost.localdomain</literal>, can be used
|
|
for this purpose.</para>
|
|
|
|
<para>Create the <filename>/etc/hosts</filename> file by running:</para>
|
|
|
|
<screen><userinput>cat > /etc/hosts << "EOF"
|
|
<literal># Begin /etc/hosts
|
|
|
|
127.0.0.1 localhost.localdomain localhost
|
|
127.0.1.1 <replaceable><FQDN></replaceable> <replaceable><HOSTNAME></replaceable>
|
|
<replaceable><192.168.1.2></replaceable> <replaceable><FQDN></replaceable> <replaceable><HOSTNAME></replaceable> <replaceable>[alias1] [alias2 ...]</replaceable>
|
|
::1 localhost ip6-localhost ip6-loopback
|
|
ff02::1 ip6-allnodes
|
|
ff02::2 ip6-allrouters
|
|
|
|
# End /etc/hosts</literal>
|
|
EOF</userinput></screen>
|
|
|
|
<para>The <replaceable><192.168.1.2></replaceable>,
|
|
<replaceable><FQDN></replaceable>, and
|
|
<replaceable><HOSTNAME></replaceable> values need to be
|
|
changed for specific uses or requirements (if assigned an IP address by a
|
|
network/system administrator and the machine will be connected to an
|
|
existing network). The optional alias name(s) can be omitted.</para>
|
|
|
|
<!-- This is not very useful
|
|
|
|
<para>If a network card is not going to be configured, create the
|
|
<filename>/etc/hosts</filename> file by running:</para>
|
|
|
|
<screen role="nodump"><userinput>cat > /etc/hosts << "EOF"
|
|
<literal># Begin /etc/hosts (no network card version)
|
|
|
|
127.0.0.1 localhost
|
|
127.0.1.1 <replaceable><FQDN></replaceable> <replaceable><HOSTNAME></replaceable>
|
|
::1 localhost ip6-localhost ip6-loopback
|
|
ff02::1 ip6-allnodes
|
|
ff02::2 ip6-allrouters
|
|
|
|
# End /etc/hosts (no network card version)</literal>
|
|
EOF</userinput></screen> -->
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|