#3258: Mounting /dev/shm can break some hosts
------------------------------------------+---------------------------------
Reporter: matthew@… | Owner: lfs-book@…
Type: defect | Status: new
Priority: normal | Milestone: 7.3
Component: Book | Version: SVN
Severity: normal | Keywords:
------------------------------------------+---------------------------------
Comment(by bdubbs@…):
I'm not sure about the change. I agree that removing /dev/shm from the
host is a problem, but does $(mkdir -p $/LFS/run/shm) within the chroot
environment affect the host? I suspect it normally does nothing as the
item that the symlink points to is a directory so the -p in mkdir just
exits, doing nothing.
There could also be an issue of lack of isolation in the proposed change
in that nothing is done if the symlink does exist. Would just the line:
mount -vt tmpfs shm $LFS/run/shm
mount a new tmpfs over the old for use within chroot be better?
AFAIR the only reason for /dev/shm to exist in chroot is to satisfy some
tests in glibc.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/3258#comment:1>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
