Changeset f139a18c for general/sysutils/systemd.xml
- Timestamp:
- 06/02/2016 06:42:44 AM (8 years ago)
- Branches:
- systemd-13485
- Children:
- 620dc60
- Parents:
- af8b2d9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/sysutils/systemd.xml
raf8b2d9 rf139a18c 5 5 %general-entities; 6 6 7 <!ENTITY systemd-download-http "http://anduin.linuxfromscratch.org/sources/other/systemd/systemd-&lfs-systemd-version;.tar.xz"> 7 <!ENTITY systemd-download-http "http://anduin.linuxfromscratch.org/sources/other/systemd/systemd-&systemd-version;.tar.xz"> 8 <!ENTITY systemd-download-ftp " "> 9 <!ENTITY systemd-md5sum "7fd9c7b1296104ccc0b8aee4be3d3c23"> 10 <!ENTITY systemd-size "3,748 KB"> 11 <!ENTITY systemd-buildsize "1.0 GB"> 12 <!ENTITY systemd-time "4.9 SBU"> 13 8 14 ]> 9 15 10 <sect1 id="systemd" xreflabel="Systemd-& lfs-systemd-version;">16 <sect1 id="systemd" xreflabel="Systemd-&systemd-version;" revision="systemd"> 11 17 <?dbhtml filename="systemd.html"?> 12 18 … … 16 22 </sect1info> 17 23 18 <title>Systemd-& lfs-systemd-version;</title>24 <title>Systemd-&systemd-version;</title> 19 25 20 26 <indexterm zone="systemd"> … … 26 32 27 33 <para> 28 Even though <application>systemd</application> was installed while34 While <application>systemd</application> was installed when 29 35 building LFS, there are many features provided by the package that 30 were not included in the initial installation due to unmet dependencies. 36 were not included in the initial installation becasue 37 <application>Linux-PAM</application> was not yet installed. 31 38 The <application>systemd</application> package needs to be 32 39 rebuilt to provide a working <command>systemd-logind</command> service, 33 among many others.40 which provides many additonal features for dependent packages. 34 41 </para> 35 42 … … 39 46 <itemizedlist spacing="compact"> 40 47 <listitem> 41 <para>Systemd Download (HTTP): <ulink url="&systemd-download-http;"/></para> 48 <para>Download (HTTP): <ulink url="&systemd-download-http;"/></para> 49 </listitem> 50 <listitem> 51 <para>Download (FTP): <ulink url="&systemd-download-ftp;"/></para> 52 </listitem> 53 <listitem> 54 <para>Download MD5 sum: &systemd-md5sum;</para> 55 </listitem> 56 <listitem> 57 <para>Download size: &systemd-size;</para> 58 </listitem> 59 <listitem> 60 <para>Estimated disk space required: &systemd-buildsize;</para> 61 </listitem> 62 <listitem> 63 <para>Estimated build time: &systemd-time;</para> 42 64 </listitem> 43 65 </itemizedlist> … … 84 106 <para> 85 107 In order to build the <application>systemd</application> 86 <application>Python</application> module, lxml package 108 <application>Python</application> module, the 109 <application>lxml</application> package 87 110 needs to be installed for the corresponding 88 111 <application>Python</application> version (2 or 3). … … 143 166 --without-python \ 144 167 --with-default-dnssec=no \ 145 --docdir=/usr/share/doc/systemd-& lfs-systemd-version; &&168 --docdir=/usr/share/doc/systemd-&systemd-version; && 146 169 make</userinput></screen> 147 170 … … 160 183 <warning> 161 184 <para> 162 Installing the package will over ride all files installed by185 Installing the package will overwrite all files installed by 163 186 <application>systemd</application> in LFS. It is critical that 164 187 nothing uses either <application>systemd</application> or 165 <application>Udev</application> libraries or programs during166 the installation phrase. Best way to achieve that is to do the167 installation in the rescue mode. To switch to therescue mode,168 issuethe following command as the169 <systemitem class="username">root</systemitem> user from a TTY:188 <application>Udev</application> libraries during the installation. 189 The best way to ensure that these libraries are not being used is to 190 run the installation in rescue mode. To switch to rescue mode, 191 run the following command as the 192 <systemitem class="username">root</systemitem> user (from a TTY): 170 193 </para> 171 194 … … 202 225 The <filename>/etc/pam.d/system-sesion</filename> file needs to 203 226 be modified and a new file needs to be created in order for 204 <command>systemd-logind</command> to work correctly. To accomplish 205 that, run the following commands as the <systemitem 206 class="username">root</systemitem> user: 227 <command>systemd-logind</command> to work correctly. Run the following 228 commands as the <systemitem class="username">root</systemitem> user: 207 229 </para> 208 230 … … 234 256 <para> 235 257 At this point, you should reload the systemd daemon, and reenter 236 multi-user mode with the following commands as the237 <systemitem class="username">root</systemitem> user :258 multi-user mode with the following commands (as the 259 <systemitem class="username">root</systemitem> user): 238 260 </para> 239 261 … … 241 263 systemctl start multi-user.target</userinput></screen> 242 264 243 <warning><para>If upgrading from a previous version of systemd and you244 use an initrd, the system will hang during boot if you do not generate a245 new initrd with systemd-root-device.target included.</para></warning>265 <warning><para>If upgrading from a previous version of systemd and an 266 initrd is used for system boot, you should generate a new initrd before 267 rebooting the system.</para></warning> 246 268 247 269 </sect2> … … 257 279 258 280 <para> 259 Below are listednewly installed libraries and directories281 Listed below are the newly installed libraries and directories 260 282 along with short descriptions. 261 283 </para>
Note:
See TracChangeset
for help on using the changeset viewer.