Changeset 0cbb853
- Timestamp:
- 01/06/2023 04:57:22 AM (3 months ago)
- Branches:
- xry111/arm64
- Children:
- 83ce6e3
- Parents:
- 688a8f5 (diff), af944eb (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
appendices/dependencies.xml
r688a8f5 r0cbb853 1475 1475 1476 1476 <!-- Begin Jinja2 dependency info --> 1477 <bridgehead re nderas="sect2" id="jinja2-dep">Jinja2</bridgehead>1478 1479 <segmentedlist id="jinja2-depends" >1477 <bridgehead revision='systemd' renderas="sect2" id="jinja2-dep">Jinja2</bridgehead> 1478 1479 <segmentedlist id="jinja2-depends" revision='systemd'> 1480 1480 <segtitle>&dependencies;</segtitle> 1481 1481 <seglistitem> … … 1484 1484 </segmentedlist> 1485 1485 1486 <segmentedlist id="jinja2-rundeps" >1486 <segmentedlist id="jinja2-rundeps" revision='systemd'> 1487 1487 <segtitle>&runtime;</segtitle> 1488 1488 <seglistitem> … … 1491 1491 </segmentedlist> 1492 1492 1493 <segmentedlist id="jinja2-testdeps" >1493 <segmentedlist id="jinja2-testdeps" revision='systemd'> 1494 1494 <segtitle>&testsuites;</segtitle> 1495 1495 <seglistitem> … … 1498 1498 </segmentedlist> 1499 1499 1500 <segmentedlist id="jinja2-before" >1500 <segmentedlist id="jinja2-before" revision='systemd'> 1501 1501 <segtitle>&before;</segtitle> 1502 1502 <seglistitem> … … 1505 1505 </segmentedlist> 1506 1506 1507 <segmentedlist id="jinja2-optdeps" >1507 <segmentedlist id="jinja2-optdeps" revision='systemd'> 1508 1508 <segtitle>&external;</segtitle> 1509 1509 <seglistitem> … … 2072 2072 2073 2073 <!-- Begin MarkupSafe dependency info --> 2074 <bridgehead renderas="sect2" id="markupsafe-dep" >MarkupSafe</bridgehead>2075 2076 <segmentedlist id="markupsafe-depends" >2074 <bridgehead renderas="sect2" id="markupsafe-dep" revision='systemd'>MarkupSafe</bridgehead> 2075 2076 <segmentedlist id="markupsafe-depends" revision='systemd'> 2077 2077 <segtitle>&dependencies;</segtitle> 2078 2078 <seglistitem> … … 2081 2081 </segmentedlist> 2082 2082 2083 <segmentedlist id="markupsafe-rundeps" >2083 <segmentedlist id="markupsafe-rundeps" revision='systemd'> 2084 2084 <segtitle>&runtime;</segtitle> 2085 2085 <seglistitem> … … 2088 2088 </segmentedlist> 2089 2089 2090 <segmentedlist id="markupsafe-testdeps" >2090 <segmentedlist id="markupsafe-testdeps" revision='systemd'> 2091 2091 <segtitle>&testsuites;</segtitle> 2092 2092 <seglistitem> … … 2095 2095 </segmentedlist> 2096 2096 2097 <segmentedlist id="markupsafe-before" >2097 <segmentedlist id="markupsafe-before" revision='systemd'> 2098 2098 <segtitle>&before;</segtitle> 2099 2099 <seglistitem> … … 2102 2102 </segmentedlist> 2103 2103 2104 <segmentedlist id="markupsafe-optdeps" >2104 <segmentedlist id="markupsafe-optdeps" revision='systemd'> 2105 2105 <segtitle>&external;</segtitle> 2106 2106 <seglistitem> … … 2136 2136 <segtitle>&before;</segtitle> 2137 2137 <seglistitem> 2138 <seg>Systemd</seg> 2138 <seg> 2139 <phrase revision='sysv'>None</phrase> 2140 <phrase revision='systemd'>Systemd</phrase> 2141 </seg> 2139 2142 </seglistitem> 2140 2143 </segmentedlist> … … 2750 2753 2751 2754 <!-- Begin systemd dependency info --> 2752 <bridgehead renderas="sect2" id="systemd-dep" >Systemd</bridgehead>2753 2754 <segmentedlist id="systemd-depends" >2755 <bridgehead renderas="sect2" id="systemd-dep" revision='systemd'>Systemd</bridgehead> 2756 2757 <segmentedlist id="systemd-depends" revision='systemd'> 2755 2758 <segtitle>&dependencies;</segtitle> 2756 2759 <seglistitem> … … 2761 2764 </segmentedlist> 2762 2765 2763 <segmentedlist id="systemd-rundeps" >2766 <segmentedlist id="systemd-rundeps" revision='systemd'> 2764 2767 <segtitle>&runtime;</segtitle> 2765 2768 <seglistitem> … … 2768 2771 </segmentedlist> 2769 2772 2770 <segmentedlist id="systemd-testdeps" >2771 <segtitle>&testsuites;</segtitle> 2772 <seglistitem> 2773 <seg>None</seg> 2774 </seglistitem> 2775 </segmentedlist> 2776 2777 <segmentedlist id="systemd-before" >2778 <segtitle>&before;</segtitle> 2779 <seglistitem> 2780 <seg>None</seg> 2781 </seglistitem> 2782 </segmentedlist> 2783 2784 <segmentedlist id="systemd-optdeps" >2773 <segmentedlist id="systemd-testdeps" revision='systemd'> 2774 <segtitle>&testsuites;</segtitle> 2775 <seglistitem> 2776 <seg>None</seg> 2777 </seglistitem> 2778 </segmentedlist> 2779 2780 <segmentedlist id="systemd-before" revision='systemd'> 2781 <segtitle>&before;</segtitle> 2782 <seglistitem> 2783 <seg>None</seg> 2784 </seglistitem> 2785 </segmentedlist> 2786 2787 <segmentedlist id="systemd-optdeps" revision='systemd'> 2785 2788 <segtitle>&external;</segtitle> 2786 2789 <seglistitem> … … 2837 2840 2838 2841 <!-- Begin Sysvinit dependency info --> 2839 <bridgehead renderas="sect2" id="sysvinit-dep" >Sysvinit</bridgehead>2840 2841 <segmentedlist id="sysvinit-depends" >2842 <bridgehead renderas="sect2" id="sysvinit-dep" revision='sysv'>Sysvinit</bridgehead> 2843 2844 <segmentedlist id="sysvinit-depends" revision='sysv'> 2842 2845 <segtitle>&dependencies;</segtitle> 2843 2846 <seglistitem> … … 2846 2849 </segmentedlist> 2847 2850 2848 <segmentedlist id="sysvinit-rundeps" >2851 <segmentedlist id="sysvinit-rundeps" revision='sysv'> 2849 2852 <segtitle>&runtime;</segtitle> 2850 2853 <seglistitem> … … 2853 2856 </segmentedlist> 2854 2857 2855 <segmentedlist id="sysvinit-testdeps" >2858 <segmentedlist id="sysvinit-testdeps" revision='sysv'> 2856 2859 <segtitle>&testsuites;</segtitle> 2857 2860 <seglistitem> … … 2860 2863 </segmentedlist> 2861 2864 2862 <segmentedlist id="sysvinit-before" >2863 <segtitle>&before;</segtitle> 2864 <seglistitem> 2865 <seg>None</seg> 2866 </seglistitem> 2867 </segmentedlist> 2868 2869 <segmentedlist id="sysvinit-optdeps" >2865 <segmentedlist id="sysvinit-before" revision='sysv'> 2866 <segtitle>&before;</segtitle> 2867 <seglistitem> 2868 <seg>None</seg> 2869 </seglistitem> 2870 </segmentedlist> 2871 2872 <segmentedlist id="sysvinit-optdeps" revision='sysv'> 2870 2873 <segtitle>&external;</segtitle> 2871 2874 <seglistitem> … … 3110 3113 <segtitle>&before;</segtitle> 3111 3114 <seglistitem> 3112 <seg>Jinja2</seg> 3115 <seg> 3116 <phrase revision='sysv'>None</phrase> 3117 <phrase revision='systemd'>Jinja2</phrase> 3118 </seg> 3113 3119 </seglistitem> 3114 3120 </segmentedlist> … … 3263 3269 <segtitle>&before;</segtitle> 3264 3270 <seglistitem> 3265 <seg>GCC and Systemd</seg>3271 <seg>GCC <phrase revision='systemd'>and Systemd</phrase></seg> 3266 3272 </seglistitem> 3267 3273 </segmentedlist> -
chapter01/changelog.xml
r688a8f5 r0cbb853 41 41 --> 42 42 <listitem> 43 <para>2023-01-01</para><!-- Happy New Year! --> 44 <itemizedlist> 45 <listitem> 46 <para>[thomas] - Remove an obsolete sed from mpc.</para> 47 </listitem> 48 </itemizedlist> 49 </listitem> 50 51 <listitem> 52 <para>2022-12-31</para> 53 <itemizedlist> 54 <listitem> 55 <para>[bdubbs] - Update to iana-etc-20221220. Addresses 56 <ulink url="&lfs-ticket-root;5006">#5006</ulink>.</para> 57 </listitem> 58 <listitem revision="sysv"> 59 <para>[bdubbs] - Update to sysvinit-3.06. Fixes 60 <ulink url="&lfs-ticket-root;5186">#5186</ulink>.</para> 61 </listitem> 62 <listitem> 63 <para>[bdubbs] - Update to mpc-1.3.1. Fixes 64 <ulink url="&lfs-ticket-root;5185">#5185</ulink>.</para> 65 </listitem> 66 <listitem> 67 <para>[bdubbs] - Update to meson-1.0.0. Fixes 68 <ulink url="&lfs-ticket-root;5190">#5190</ulink>.</para> 69 </listitem> 70 <listitem> 71 <para>[bdubbs] - Update to man-pages-6.02. Fixes 72 <ulink url="&lfs-ticket-root;5188">#5188</ulink>.</para> 73 </listitem> 74 <listitem> 75 <para>[bdubbs] - Update to linux-6.1.1. Fixes 76 <ulink url="&lfs-ticket-root;5179">#5179</ulink>.</para> 77 </listitem> 78 <listitem> 79 <para>[bdubbs] - Update to file-5.44. Fixes 80 <ulink url="&lfs-ticket-root;5191">#5191</ulink>.</para> 81 </listitem> 82 <listitem> 83 <para>[bdubbs] - Update to bc-6.2.1. Fixes 84 <ulink url="&lfs-ticket-root;5189">#5189</ulink>.</para> 85 </listitem> 86 </itemizedlist> 87 </listitem> 88 89 <listitem revision="systemd"> 90 <para>2022-12-28</para> 91 <itemizedlist> 92 <listitem> 93 <para>[renodr] - Patch systemd against CVE-2022-4415. Fixes 94 <ulink url="&lfs-ticket-root;5187">#5187</ulink>.</para> 95 </listitem> 96 </itemizedlist> 97 </listitem> 98 99 <listitem> 43 100 <para>2022-12-15</para> 44 101 <itemizedlist> -
chapter01/whatsnew.xml
r688a8f5 r0cbb853 300 300 <para>&readline-fixes-patch;</para> 301 301 </listitem> 302 303 <listitem revision="systemd"> 304 <para>&systemd-upstream-patch;</para> 305 </listitem> 302 306 </itemizedlist> 303 307 -
chapter03/patches.xml
r688a8f5 r0cbb853 136 136 </varlistentry> 137 137 138 <!-- 138 139 139 <varlistentry revision="systemd"> 140 140 <term>Systemd Upstream Patch - <token>&systemd-upstream-patch-size;</token>:</term> … … 144 144 </listitem> 145 145 </varlistentry> 146 --> 146 147 147 <!-- 148 148 <varlistentry> -
chapter08/mpc.xml
r688a8f5 r0cbb853 42 42 <sect2 role="installation"> 43 43 <title>Installation of MPC</title> 44 45 <para>First, make a fix identified upstream:</para>46 47 <screen><userinput remap="pre">sed -i '273{ h; d; }; 274,286 { H; d; }; 287 G' src/mpc.h</userinput></screen>48 49 <note>50 <para>This sed is a little complex and needs some explanation. It holds51 the line 273 in a buffer, adds lines 274-286 to it. It then writes the52 buffer out after line 287 is read. The result is that the line 287 is53 moved upwards from an incorrect location to its correct location in an54 #ifdef block.</para>55 </note>56 44 57 45 <para>Prepare MPC for compilation:</para> -
chapter08/systemd.xml
r688a8f5 r0cbb853 41 41 <title>Installation of systemd</title> 42 42 43 <!-- 44 <para>First, fix a n issue introduced by glibc-2.36.</para>43 44 <para>First, fix a security issue in systemd-coredump:</para> 45 45 46 46 <screen><userinput remap="pre">patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen> 47 --> 47 48 48 49 49 <para>Remove two unneeded groups, -
chapter09/profile.xml
r688a8f5 r0cbb853 17 17 <para>The shell program <command>/bin/bash</command> (hereafter referred to 18 18 as <quote>the shell</quote>) uses a collection of startup files to help 19 create anenvironment to run in. Each file has a specific use and may affect19 create the environment to run in. Each file has a specific use and may affect 20 20 login and interactive environments differently. The files in the <filename 21 class="directory">/etc</filename> directory provide global settings. If an22 equivalent file exists in the home directory, itmay override the global21 class="directory">/etc</filename> directory provide global settings. If 22 equivalent files exist in the home directory, they may override the global 23 23 settings.</para> 24 24 … … 31 31 commands.</para> 32 32 33 <para>For more information, see <command>info bash</command> under the 34 <emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para> 33 <para>For more information, see the <emphasis>Bash Startup Files</emphasis> and 34 <emphasis>Interactive Shells</emphasis> sections in the <emphasis>Bash 35 Features</emphasis> chapter of the Bash info pages (<command>info bash</command>).</para> 35 36 36 37 <para>The files <filename>/etc/profile</filename> and … … 92 93 93 94 <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>. 94 It is important that the locale found using the heuristic above is tested prior95 to it beingadded to the Bash startup files:</para>95 It is important that the locale found using the heuristic above is tested before 96 it is added to the Bash startup files:</para> 96 97 97 98 <screen role="nodump"><userinput>LC_ALL=<locale name> locale language … … 130 131 "de_DE@euro" in order to get this locale recognized by Xlib.</para> 131 132 --> 132 <para>Other packages can also function incorrectly (but maynot necessarily133 <para>Other packages may also function incorrectly (but will not necessarily 133 134 display any error messages) if the locale name does not meet their expectations. 134 In thosecases, investigating how other Linux distributions support your locale135 In such cases, investigating how other Linux distributions support your locale 135 136 might provide some useful information.</para> 136 137 … … 148 149 <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended 149 150 one for United States English users) locales are different. <quote>C</quote> 150 uses the US-ASCII 7-bit character set, and treats bytes with the high bit set151 as invalid characters. That's why, e.g., the <command>ls</command> command152 substitutes them withquestion marks in that locale. Also, an attempt to send151 uses the US-ASCII 7-bit character set, and treats bytes with the high-order bit set 152 <quote>on</quote> as invalid characters. That's why, e.g., the <command>ls</command> command 153 displays them as question marks in that locale. Also, an attempt to send 153 154 mail with such characters from Mutt or Pine results in non-RFC-conforming 154 155 messages being sent (the charset in the outgoing mail is indicated as <quote>unknown 155 8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that156 8-bit</quote>). So you can only use the <quote>C</quote> locale if you are sure 156 157 you will never need 8-bit characters.</para> 157 158 158 159 <para>UTF-8 based locales are not supported well by some programs. 159 Work is in progress to document and, if possible, fix such problems , see160 Work is in progress to document and, if possible, fix such problems. See 160 161 <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para> 161 162 -
chapter09/usage.xml
r688a8f5 r0cbb853 20 20 <title>How Do the System V Bootscripts Work?</title> 21 21 22 <para>Linux uses a special booting facility named SysVinit that is based on a 23 concept of <emphasis>run-levels</emphasis>. It can be quite different from one 24 system to another, so it cannot be assumed that because things worked in one 25 particular Linux distribution, they should work the same in LFS too. LFS has its 26 own way of doing things, but it respects generally accepted standards.</para> 22 <para>This version of LFS uses a special booting facility named SysVinit, based on a 23 series of <emphasis>run levels</emphasis>. The boot procedure can be quite different from one 24 system to another; the fact that things worked one way in a particular Linux 25 distribution does not guarantee they will work the same way in LFS. LFS has its 26 own way of doing things, but it does respect generally accepted standards.</para> 27 28 <para>There is an alternative boot procedure called <command>systemd</command>. We will 29 not discuss that boot process any further here. For a detailed description visit 30 <ulink url="https://www.linux.com/training-tutorials/understanding-and-using-systemd/"/>.</para> 27 31 28 32 <para>SysVinit (which will be referred to as <quote>init</quote> from now on) 29 works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels30 ( actually, there are more run-levels, but theyare for special cases and are31 generally not used. See <filename>init(8)</filename> for more details ), and32 each one of those corresponds to theactions the computer is supposed to33 perform when it starts up . The default run-level is 3. Here are the34 descriptions of the different run -levels as they are implemented in LFS:</para>33 uses a run levels scheme. There are seven run levels, numbered 0 to 6. 34 (Actually, there are more run levels, but the others are for special cases and are 35 generally not used. See <filename>init(8)</filename> for more details.) 36 Each one of the seven corresponds to actions the computer is supposed to 37 perform when it starts up or shuts down. The default run level is 3. Here are the 38 descriptions of the different run levels as they are implemented in LFS:</para> 35 39 36 40 <literallayout>0: halt the computer 37 41 1: single-user mode 38 2: reserved for customization, otherwise doesthe same as 342 2: reserved for customization, otherwise the same as 3 39 43 3: multi-user mode with networking 40 4: reserved for customization, otherwise doesthe same as 344 4: reserved for customization, otherwise the same as 3 41 45 5: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>) 42 46 6: reboot the computer</literallayout> … … 46 50 Classically, run level 2 above was defined as 47 51 "multi-user mode without networking", but this was only the case 48 many years ago when multiple users could log into a system connectedvia49 serial ports. In today's environment it makes no sense and50 we designate it now as "reserved".52 many years ago when multiple users could connect to a system via 53 serial ports. In today's environment it makes no sense, and 54 we now say it is "reserved". 51 55 </para> 52 56 </note> … … 66 70 </indexterm> 67 71 68 <para>During thekernel initialization, the first program that is run69 is either specified on the command line or, by default72 <para>During kernel initialization, the first program that is run 73 (if not overridden on the command line) is 70 74 <command>init</command>. This program reads the initialization file 71 75 <filename>/etc/inittab</filename>. Create this file with:</para> … … 102 106 103 107 <para>An explanation of this initialization file is in the man page for 104 <emphasis>inittab</emphasis>. For LFS, the key command that is runis105 <command>rc</command>. The initialization file above will instruct108 <emphasis>inittab</emphasis>. In LFS, the key command is 109 <command>rc</command>. The initialization file above instructs 106 110 <command>rc</command> to run all the scripts starting with an S in the 107 111 <filename class="directory">/etc/rc.d/rcS.d</filename> directory … … 114 118 This library also reads an optional configuration file, 115 119 <filename>/etc/sysconfig/rc.site</filename>. Any of the system 116 configuration fileparameters described in subsequent sections can be117 alternatively placed in this fileallowing consolidation of all system120 configuration parameters described in subsequent sections can be 121 placed in this file, allowing consolidation of all system 118 122 parameters in this one file.</para> 119 123 … … 121 125 to <filename>/run/var/bootlog</filename>. Since the <filename 122 126 class="directory">/run</filename> directory is a tmpfs, this file is not 123 persistent across boots , howeverit is appended to the more permanent file127 persistent across boots; however, it is appended to the more permanent file 124 128 <filename>/var/log/boot.log</filename> at the end of the boot process.</para> 125 129 … … 127 131 <title>Changing Run Levels</title> 128 132 129 <para>Changing run -levels is done with <command>init133 <para>Changing run levels is done with <command>init 130 134 <replaceable><runlevel></replaceable></command>, where 131 <replaceable><runlevel></replaceable> is the target run -level. For example, to135 <replaceable><runlevel></replaceable> is the target run level. For example, to 132 136 reboot the computer, a user could issue the <command>init 6</command> command, 133 137 which is an alias for the <command>reboot</command> command. Likewise, … … 137 141 <para>There are a number of directories under <filename 138 142 class="directory">/etc/rc.d</filename> that look like <filename 139 class="directory">rc?.d</filename> (where ? is the number of the run -level) and143 class="directory">rc?.d</filename> (where ? is the number of the run level) and 140 144 <filename class="directory">rcS.d</filename>, all containing a number of 141 symbolic links. Some begin with a <emphasis>K</emphasis>,the others begin with145 symbolic links. Some links begin with a <emphasis>K</emphasis>; the others begin with 142 146 an <emphasis>S</emphasis>, and all of them have two numbers following the 143 147 initial letter. The K means to stop (kill) a service and the S means to start a 144 148 service. The numbers determine the order in which the scripts are run, from 00 145 to 99—the lower the number the earlier it gets executed. When146 <command>init</command> switches to another run -level, the appropriate services147 are either started or stopped, depending on the run level chosen.</para>149 to 99—the smaller the number, the sooner tht script runs. When 150 <command>init</command> switches to another run level, the appropriate services 151 are either started or stopped, depending on the run level chosen.</para> 148 152 149 153 <para>The real scripts are in <filename … … 228 232 <para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts 229 233 <command>udevd</command>, triggers any "coldplug" devices that have 230 already been created by the kernel and waits for any rules to complete.234 already been created by the kernel, and waits for any rules to complete. 231 235 The script also unsets the uevent handler from the default of 232 236 <filename>/sbin/hotplug </filename>. This is done because the kernel no 233 longer needs to call out to an external binary. Instead237 longer needs to call an external binary. Instead, 234 238 <command>udevd</command> will listen on a netlink socket for uevents that 235 239 the kernel raises.</para> 236 240 237 <para>The <command>/etc/rc.d/init.d/udev_retry</command> initscript takes241 <para>The <command>/etc/rc.d/init.d/udev_retry</command> script takes 238 242 care of re-triggering events for subsystems whose rules may rely on 239 file systems that are not mounted until the <command>mountfs</command>243 file systems that are not mounted until the <command>mountfs</command> 240 244 script is run (in particular, <filename class="directory">/usr</filename> 241 245 and <filename class="directory">/var</filename> may cause this). This 242 246 script runs after the <command>mountfs</command> script, so those rules 243 247 (if re-triggered) should succeed the second time around. It is 244 configured fromthe <filename>/etc/sysconfig/udev_retry</filename> file;248 configured by the <filename>/etc/sysconfig/udev_retry</filename> file; 245 249 any words in this file other than comments are considered subsystem names 246 250 to trigger at retry time. To find the subsystem of a device, use 247 251 <command>udevadm info --attribute-walk <device></command> where 248 <device> is an absolute path in /dev or /sys such as /dev/sr0or252 <device> is an absolute path in /dev or /sys, such as /dev/sr0, or 249 253 /sys/class/rtc.</para> 250 254 … … 261 265 262 266 <para>The <command>setclock</command> script reads the time from the hardware 263 clock, also known as the BIOS or theComplementary Metal Oxide Semiconductor267 clock, also known as the BIOS or Complementary Metal Oxide Semiconductor 264 268 (CMOS) clock. If the hardware clock is set to UTC, this script will convert the 265 269 hardware clock's time to the local time using the 266 270 <filename>/etc/localtime</filename> file (which tells the 267 <command>hwclock</command> program which time zone to use). There is no271 <command>hwclock</command> program which time zone to use). There is no 268 272 way to detect whether or not the hardware clock is set to UTC, so this 269 needs tobe configured manually.</para>273 must be configured manually.</para> 270 274 271 275 <para>The <command>setclock</command> program is run via … … 280 284 set to local time. If the output from <command>hwclock</command> is not local 281 285 time, chances are it is set to UTC time. Verify this by adding or subtracting 282 the proper amount of hours for the timezone to the time shown by286 the proper number of hours for your time zone to the time shown by 283 287 <command>hwclock</command>. For example, if you are currently in the MST 284 time zone, which is also known as GMT -0700, add seven hours to the local288 time zone, which is also known as GMT -0700, add seven hours to the local 285 289 time.</para> 286 290 … … 326 330 bootscript that sets up the keyboard map, console font, and console kernel log 327 331 level. If non-ASCII characters (e.g., the copyright sign, the British pound 328 sign andEuro symbol) will not be used and the keyboard is a U.S. one, much332 sign, and the Euro symbol) will not be used and the keyboard is a U.S. one, much 329 333 of this section can be skipped. Without the configuration file, (or 330 334 equivalent settings in <filename>rc.site</filename>), the … … 334 338 <filename>/etc/sysconfig/console</filename> file for configuration 335 339 information. Decide which keymap and screen font will be used. Various 336 language-specific HOWTOs can also help with this ,see <ulink340 language-specific HOWTOs can also help with this; see <ulink 337 341 url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in 338 342 doubt, look in the <filename class="directory">/usr/share/keymaps</filename> 339 343 and <filename class="directory">/usr/share/consolefonts</filename> directories 340 for valid keymaps and screen fonts. Read <filename>loadkeys(1)</filename> and344 for valid keymaps and screen fonts. Read the <filename>loadkeys(1)</filename> and 341 345 <filename>setfont(8)</filename> manual pages to determine the correct 342 346 arguments for these programs.</para> … … 359 363 <listitem> 360 364 <para>This variable specifies the arguments for the 361 <command>loadkeys</command> program, typically, the name of keymap365 <command>loadkeys</command> program, typically, the name of the keymap 362 366 to load, e.g., <quote>it</quote>. If this variable is not set, the 363 367 bootscript will not run the <command>loadkeys</command> program, … … 391 395 map to load. E.g., in order to load the <quote>lat1-16</quote> font 392 396 together with the <quote>8859-1</quote> application character map 393 (a s it is appropriate in the USA),397 (appropriate in the USA), 394 398 <!-- because of the copyright sign --> 395 399 set this variable to <quote>lat1-16 -m 8859-1</quote>. 396 In UTF-8 mode, the kernel uses the application character map for397 conver sion of composed 8-bit key codes in the keymap to UTF-8, and thus400 In UTF-8 mode, the kernel uses the application character map to 401 convert 8-bit key codes to UTF-8. Therefore 398 402 the argument of the "-m" parameter should be set to the encoding of the 399 403 composed key codes in the keymap.</para> … … 405 409 <term>UNICODE</term> 406 410 <listitem> 407 <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or411 <para>Set this variable to <quote>1</quote>, <quote>yes</quote>, or 408 412 <quote>true</quote> in order to put the 409 413 console into UTF-8 mode. This is useful in UTF-8 based locales and … … 523 527 sometimes needs to put an accent on the letter <quote>alpha</quote>. 524 528 The solution is either to avoid the use of UTF-8, or to install the 525 X window system that doesn't have this limitationin its input529 X window system, which doesn't have this limitation, in its input 526 530 handling.</para> 527 531 </listitem> … … 532 536 who need such languages should install the X Window System, fonts that 533 537 cover the necessary character ranges, and the proper input method (e.g., 534 SCIM ,supports a wide variety of languages).</para>538 SCIM supports a wide variety of languages).</para> 535 539 </listitem> 536 540 … … 566 570 567 571 <sect2 id="ch-config-sysklogd"> 568 <title>Configuring the sysklogd Script</title>572 <title>Configuring the Sysklogd Script</title> 569 573 570 574 <indexterm zone="ch-config-sysklogd"> … … 601 605 <filename class='directory'>/etc/sysconfig/</filename> directory. If the 602 606 associated variables are present in both these separate files and 603 <filename>rc.site</filename>, the values in the script specific files have604 precedence. </para>607 <filename>rc.site</filename>, the values in the script-specific files take 608 effect. </para> 605 609 606 610 <para><filename>rc.site</filename> also contains parameters that can … … 616 620 617 621 <para>The LFS boot scripts boot and shut down a system in a fairly 618 efficient manner, but there are a few tweaks thatyou can make in the619 rc.site file to improve speed even more and to adjust messages according622 efficient manner, but there are a few tweaks you can make in the 623 rc.site file to improve speed even more, and to adjust messages according 620 624 to your preferences. To do this, adjust the settings in 621 625 the <filename>/etc/sysconfig/rc.site</filename> file above.</para> … … 625 629 <listitem><para>During the boot script <filename>udev</filename>, there is 626 630 a call to <command>udev settle</command> that requires some time to 627 complete. This time may or may not be required depending on devices present631 complete. This time may or may not be required depending on the devices 628 632 in the system. If you only have simple partitions and a single ethernet 629 633 card, the boot process will probably not need to wait for this command. To … … 631 635 632 636 <listitem><para>The boot script <filename>udev_retry</filename> also runs 633 <command>udev settle</command> by default. This command is only needed by634 defaultif the <filename class='directory'>/var</filename> directory is635 separately mounted . This is because the clock needs the file636 <filename>/var/lib/hwclock/adjtime</filename> . Other customizations may637 <command>udev settle</command> by default. This command is only needed 638 if the <filename class='directory'>/var</filename> directory is 639 separately mounted, because the clock needs the 640 <filename>/var/lib/hwclock/adjtime</filename> file. Other customizations may 637 641 also need to wait for udev to complete, but in many installations it is not 638 ne eded. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.642 necessary. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y. 639 643 </para></listitem> 640 644 … … 665 669 <listitem><para>During shutdown, the <command>init</command> program sends 666 670 a TERM signal to each program it has started (e.g. agetty), waits for a set 667 time (default 3 seconds), andsends each process a KILL signal and waits671 time (default 3 seconds), then sends each process a KILL signal and waits 668 672 again. This process is repeated in the <command>sendsignals</command> 669 673 script for any processes that are not shut down by their own scripts. The -
chapter10/grub.xml
r688a8f5 r0cbb853 24 24 <para> 25 25 If you've installed GRUB for UEFI with optional dependencies following 26 BLFS, you should skip this page, and config GRUB with UEFI support26 BLFS, you should skip this page, and configure GRUB with UEFI support 27 27 using the instructions provided in 28 28 <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>, … … 71 71 the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> 72 72 is the hard drive number and <emphasis>m</emphasis> is the partition 73 number. The hard drive number starts from zero, but the partition number74 start s from one for normal partitions and five for extended partitions.73 number. The hard drive numbers start from zero, but the partition numbers 74 start from one for normal partitions (from five for extended partitions). 75 75 Note that this is different from earlier versions where 76 76 both numbers started from zero. For example, partition <filename … … 121 121 this, you will need to mount the separate partition, move all files in the 122 122 current <filename class="directory">/boot</filename> directory (e.g. the 123 linux kernel you just built in the previous section) to the new partition.123 Linux kernel you just built in the previous section) to the new partition. 124 124 You will then need to unmount the partition and remount it as <filename 125 125 class="directory">/boot</filename>. If you do this, be sure to update 126 126 <filename>/etc/fstab</filename>.</para> 127 127 128 <para>Using the current lfs partition will also work, but configuration 128 <para>Leaving <filename class="directory">/boot</filename> on 129 the current LFS partition will also work, but configuration 129 130 for multiple systems is more difficult.</para> 130 131 … … 232 233 <filename>grub.cfg</filename> refers to some <quote>old</quote> 233 234 designators. If you wish to avoid such a problem, you may use 234 the UUID of partition and filesystem instead ofGRUB designator to235 specify a partition.235 the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to 236 specify a device. 236 237 Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show 237 the UUID of your filesystems (in<literal>UUID</literal> column) and238 partitions (in <literal>PARTUUID</literal> column). Then replace238 the UUIDs of your filesystems (in the <literal>UUID</literal> column) and 239 partitions (in the <literal>PARTUUID</literal> column). Then replace 239 240 <literal>set root=(hdx,y)</literal> with 240 <literal>search --set=root --fs-uuid <replaceable><UUID of the filesystem where the kernel is installed></replaceable></literal>, and replace 241 <literal>search --set=root --fs-uuid <replaceable><UUID of the filesystem 242 where the kernel is installed></replaceable></literal>, and replace 241 243 <literal>root=/dev/sda2</literal> with 242 <literal>root=PARTUUID=<replaceable><UUID of the partition where LFS is built></replaceable></literal>.</para> 243 <para>Note that the UUID of a partition and the UUID of the filesystem 244 in this partition is completely different. Some online resources may 244 <literal>root=PARTUUID=<replaceable><UUID of the partition where LFS 245 is built></replaceable></literal>.</para> 246 <para>Note that the UUID of a partition is completely different from the 247 UUID of the filesystem in this partition. Some online resources may 245 248 instruct you to use 246 249 <literal>root=UUID=<replaceable><filesystem UUID></replaceable></literal> 247 250 instead of 248 251 <literal>root=PARTUUID=<replaceable><partition UUID></replaceable></literal>, 249 but doing so will require an initramfs which is beyond the scope of252 but doing so will require an initramfs, which is beyond the scope of 250 253 LFS.</para> 251 254 <para>The name of the device node for a partition in 252 <filename class='directory'>/dev</filename> may also change ( more253 unlikely than GRUB designator change though). You can also replace255 <filename class='directory'>/dev</filename> may also change (this is less 256 likely than a GRUB designator change). You can also replace 254 257 paths to device nodes like <literal>/dev/sda1</literal> with 255 258 <literal>PARTUUID=<replaceable><partition UUID></replaceable></literal>, -
git-version.sh
r688a8f5 r0cbb853 30 30 31 31 export LC_ALL=en_US.utf8 32 export TZ= US/Pacific32 export TZ=America/Chicago 33 33 34 34 commit_date=$(git show -s --format=format:"%cd" --date=local) -
packages.ent
r688a8f5 r0cbb853 59 59 <!ENTITY bash-fin-sbu "1.4 SBU"> 60 60 61 <!ENTITY bc-version "6. 1.1">62 <!ENTITY bc-size "44 5KB">61 <!ENTITY bc-version "6.2.1"> 62 <!ENTITY bc-size "446 KB"> 63 63 <!ENTITY bc-url "https://github.com/gavinhoward/bc/releases/download/&bc-version;/bc-&bc-version;.tar.xz"> 64 <!ENTITY bc-md5 " 9a7ffa015c499272e7d41b4c0f28e691">64 <!ENTITY bc-md5 "ad4b3546e5bd5cc6f46b887fb2992ae4"> 65 65 <!ENTITY bc-home "https://git.yzena.com/gavin/bc"> 66 66 <!ENTITY bc-fin-du "7.4 MB"> … … 180 180 <!ENTITY expect-tmp-sbu "0.2 SBU"> 181 181 182 <!ENTITY file-version "5.4 3">183 <!ENTITY file-size "1,1 36KB">182 <!ENTITY file-version "5.44"> 183 <!ENTITY file-size "1,159 KB"> 184 184 <!ENTITY file-url "https://astron.com/pub/file/file-&file-version;.tar.gz"> 185 <!ENTITY file-md5 " 8effd70da368210a6c6eece037f978eb">185 <!ENTITY file-md5 "a60d586d49d015d842b9294864a89c7a"> 186 186 <!ENTITY file-home "https://www.darwinsys.com/file/"> 187 187 <!ENTITY file-tmp-du "34 MB"> … … 318 318 <!ENTITY gzip-fin-sbu "0.3 SBU"> 319 319 320 <!ENTITY iana-etc-version "202212 09">321 <!ENTITY iana-etc-size "58 5KB">320 <!ENTITY iana-etc-version "20221220"> 321 <!ENTITY iana-etc-size "586 KB"> 322 322 <!ENTITY iana-etc-url "https://github.com/Mic92/iana-etc/releases/download/&iana-etc-version;/iana-etc-&iana-etc-version;.tar.gz"> 323 <!ENTITY iana-etc-md5 "b 5e3e7ee1f65edff9284e614000a3815">323 <!ENTITY iana-etc-md5 "b394b994883d01d8b33c80bc57917117"> 324 324 <!ENTITY iana-etc-home "https://www.iana.org/protocols"> 325 325 <!ENTITY iana-etc-fin-du "4.8 MB"> … … 383 383 <!ENTITY less-fin-sbu "less than 0.1 SBU"> 384 384 385 <!ENTITY lfs-bootscripts-version "202 20920"> <!-- Scripts depend on this format -->385 <!ENTITY lfs-bootscripts-version "20230101"> <!-- Scripts depend on this format --> 386 386 <!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB"> 387 387 <!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz"> … … 424 424 425 425 <!ENTITY linux-major-version "6"> 426 <!ENTITY linux-minor-version " 0">427 <!ENTITY linux-patch-version "1 1">426 <!ENTITY linux-minor-version "1"> 427 <!ENTITY linux-patch-version "1"> 428 428 <!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">--> 429 429 <!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;"> 430 <!ENTITY linux-size "13 0,780KB">430 <!ENTITY linux-size "131,573 KB"> 431 431 <!ENTITY linux-url "&kernel;linux/kernel/v&linux-major-version;.x/linux-&linux-version;.tar.xz"> 432 <!ENTITY linux-md5 " 7a47796e842b77519613abbca6037c91">432 <!ENTITY linux-md5 "3482feaa021961d10ac88e789788bf07"> 433 433 <!ENTITY linux-home "https://www.kernel.org/"> 434 434 <!-- measured for 5.13.4 / gcc-11.1.0 on x86_64 : minimum is … … 472 472 <!ENTITY man-db-fin-sbu "0.4 SBU"> 473 473 474 <!ENTITY man-pages-version "6.0 1">475 <!ENTITY man-pages-size "1,7 48KB">474 <!ENTITY man-pages-version "6.02"> 475 <!ENTITY man-pages-size "1,759 KB"> 476 476 <!ENTITY man-pages-url "&kernel;linux/docs/man-pages/man-pages-&man-pages-version;.tar.xz"> 477 <!ENTITY man-pages-md5 " 83b25a1a120df78ec4c01221a1926463">477 <!ENTITY man-pages-md5 "05b9e8ce59f6257141fe9e4edd5bd149"> 478 478 <!ENTITY man-pages-home "https://www.kernel.org/doc/man-pages/"> 479 479 <!ENTITY man-pages-fin-du "33 MB"> … … 488 488 <!ENTITY markupsafe-fin-sbu "less than 0.1 SBU"> 489 489 490 <!ENTITY meson-version " 0.64.1">491 <!ENTITY meson-size "2,0 41 KB">490 <!ENTITY meson-version "1.0.0"> 491 <!ENTITY meson-size "2,051 KB"> 492 492 <!ENTITY meson-url "&github;/mesonbuild/meson/releases/download/&meson-version;/meson-&meson-version;.tar.gz"> 493 <!ENTITY meson-md5 " 9f260adfcbc66ed2e15047c6eb98e503">493 <!ENTITY meson-md5 "009b78125467cd9ee4d467175a5c12e1"> 494 494 <!ENTITY meson-home "https://mesonbuild.com"> 495 495 <!ENTITY meson-fin-du "38 MB"> 496 496 <!ENTITY meson-fin-sbu "less than 0.1 SBU"> 497 497 498 <!ENTITY mpc-version "1.3. 0">498 <!ENTITY mpc-version "1.3.1"> 499 499 <!ENTITY mpc-size "756 KB"> 500 500 <!ENTITY mpc-url "https://ftp.gnu.org/gnu/mpc/mpc-&mpc-version;.tar.gz"> 501 <!ENTITY mpc-md5 " b0f5e2ad6009781777ed026bcf71bf0e">501 <!ENTITY mpc-md5 "5c9bc658c9fd0f940e8e3e0f09530c62"> 502 502 <!ENTITY mpc-home "https://www.multiprecision.org/"> 503 503 <!ENTITY mpc-fin-du "21 MB"> … … 655 655 <!ENTITY systemd-fin-sbu "2.5 SBU"> 656 656 657 <!ENTITY sysvinit-version "3.0 5">658 <!ENTITY sysvinit-size "2 29KB">657 <!ENTITY sysvinit-version "3.06"> 658 <!ENTITY sysvinit-size "247 KB"> 659 659 <!ENTITY sysvinit-url "&github;/slicer69/sysvinit/releases/download/&sysvinit-version;/sysvinit-&sysvinit-version;.tar.xz"> 660 <!ENTITY sysvinit-md5 " 57577060e5f21fd9899fa601aa45b064">660 <!ENTITY sysvinit-md5 "96771d0a88315c91199830ea49b859ca"> 661 661 <!ENTITY sysvinit-home "&savannah-nongnu;/projects/sysvinit"> 662 662 <!ENTITY sysvinit-fin-du "2.7 MB"> -
patches.ent
r688a8f5 r0cbb853 89 89 --> 90 90 <!ENTITY sysvinit-consolidated-patch "sysvinit-&sysvinit-version;-consolidated-1.patch"> 91 <!ENTITY sysvinit-consolidated-patch-md5 " 372d367918134f2f41daf54f2acf280a">92 <!ENTITY sysvinit-consolidated-patch-size "2. 4KB">91 <!ENTITY sysvinit-consolidated-patch-md5 "17ffccbb8e18c39e8cedc32046f3a475"> 92 <!ENTITY sysvinit-consolidated-patch-size "2.5 KB"> 93 93 94 <!-- 95 <!ENTITY systemd-upstream-patch "systemd-&systemd-version;- glibc_2.36_fix-1.patch">96 <!ENTITY systemd-upstream-patch-md5 " fd8dc901e73ad00dc72a351a0d4ac48c">97 <!ENTITY systemd-upstream-patch-size " 3.0 KB">98 --> 94 95 <!ENTITY systemd-upstream-patch "systemd-&systemd-version;-security_fix-1.patch"> 96 <!ENTITY systemd-upstream-patch-md5 "da817e69e897d35cdffd7c45ea06be39"> 97 <!ENTITY systemd-upstream-patch-size "76.0 KB"> 98 99 99 <!-- 100 100 <!ENTITY xz-upstream-fix-patch "xz-&xz-version;-upstream_fix-1.patch">
Note:
See TracChangeset
for help on using the changeset viewer.