Changeset 7f3f152 for chapter08/systemd.xml
- Timestamp:
- 06/14/2024 10:30:33 PM (3 weeks ago)
- Branches:
- multilib
- Children:
- d9c86378
- Parents:
- e0850a7 (diff), c04d98d (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. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/systemd.xml
re0850a7 r7f3f152 48 48 <screen><userinput remap="pre">sed -i -e 's/GROUP="render"/GROUP="video"/' \ 49 49 -e 's/GROUP="sgx", //' rules.d/50-udev-default.rules.in</userinput></screen> 50 51 <para>Next, fix compatibility with API headers from linux-6.9 and later:</para>52 53 <screen><userinput remap="pre">sed -i '/DEVMEM_MAGIC 0/{n;n;a \54 /* cb12fd8e0dabb9a1c8aef55a6a41e2c255fcdf4b (6.8) */ \55 #ifndef PID_FS_MAGIC \56 #define PID_FS_MAGIC 0x50494446 \57 #endif58 }' src/basic/missing_magic.h59 60 sed -i '/OVERLAYFS_SUPER_MAGIC/a \61 pidfs, {PID_FS_MAGIC}' src/basic/filesystems-gperf.gperf</userinput></screen>62 63 <!-- https://github.com/systemd/systemd/pull/30549 -->64 <para>Now fix a security vulnerability in the DNSSEC verification of65 <command>systemd-resolved</command> and a bug breaking running66 <command>systemd-analyze verify</command> on an instantiated systemd67 unit:</para>68 69 <screen><userinput remap='pre'>patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen>70 50 71 51 <para>Prepare systemd for compilation:</para> … … 245 225 ninja test</userinput></screen> 246 226 247 <!-- This testneeds /run/systemd/inaccessible/sock, which only exists227 <!-- test-namespace needs /run/systemd/inaccessible/sock, which only exists 248 228 after initializing the system with systemd. --> 249 <para>One test named <literal>systemd:core / test-namespace</literal> 250 is known to fail in the LFS chroot environment. Some other tests may 229 <para>Three tests: <literal>systemd:core / test-namespace</literal>, 230 <literal>test-chase</literal>, and <literal>test-systemd-tmpfiles</literal>, 231 are known to fail in the LFS chroot environment. Some other tests may 251 232 fail because they depend on various kernel configuration options.</para> 252 233
Note:
See TracChangeset
for help on using the changeset viewer.