Ignore:
Timestamp:
09/20/2022 05:20:58 PM (19 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
ab29298
Parents:
cc8e57d
Message:

Adjust instructions for /dev/shm when creating virtual filesystems.
Some host create /dev/shm as a tmpfs. Some have is as
a symlink to a location in another directory. This
change handles both cases.

The change to the sysV bootscripts now creates /dev/shm
as a separate tmpfs from /run. This makes LFS sysV and
systemd versions treat /dev/shm the same.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/kernfs.xml

    rcc8e57d r16cd0963  
    9090      directory needs to be created.</para>
    9191
     92      <para>In other cases <filename>/dev/shm</filename> is a mountpoint
     93      for a tmpfs. In that case the mount of /dev above will only create
     94      /dev/shm in the chroot environment as a directory. In this situation
     95      we explicitly mount a tmpfs,</para>
     96
    9297<screen><userinput>if [ -h $LFS/dev/shm ]; then
    9398  mkdir -pv $LFS/$(readlink $LFS/dev/shm)
     99else
     100  mount -t tmpfs -o nosuid,nodev tmpfs $LFS/dev/shm
    94101fi</userinput></screen>
    95102
Note: See TracChangeset for help on using the changeset viewer.