Christoph Egger <[email protected]> writes: > Julien Cristau <[email protected]> writes: >> On Wed, Jun 4, 2014 at 21:03:07 +0200, Aurelien Jarno wrote: >> >>> On Sat, May 17, 2014 at 02:49:07PM +0200, Julien Cristau wrote: >>> > Hi, >>> > >>> > the latest version of libxshmfence failed during tests because trying to >>> > create a file in /dev/shm failed with ENOENT. Is it possible that the >>> > sid chroots on fano and fils are missing /dev/shm, or that it's a >>> > dangling symlink? >>> >>> Since the /run transition, in the chroot case /dev/shm should be a >>> symlink to /run/shm. It is like that on GNU/Linux. On GNU/kFreeBSD >>> the scripts are correctly creating the symlink, but given /dev is >>> a devfs filesystem, it is lost when exiting the chroot. >>> >> That /run transition is all broken, at least for shm. It's also undone >> with systemd, which doesn't do the /run/shm thing at all, AFAICT. In my >> /etc/schroot/sbuild/fstab here I have >> tmpfs /dev/shm tmpfs defaults 0 0 >> >> Could something similar be done on kfreebsd? > > Just adding fails: > > E: 10mount: E: boost::filesystem::create_directory: Operation not > supported: "/var/lib/schroot/mount/sid-ka-sbuild-1401909931-44836/dev/shm" > > % mkdir /dev/shm > mkdir: cannot create directory '/dev/shm': Operation not supported > > mounting the tmpfs on /run/shm and symlinking works well. I'll try > figure out what kfreebsd-* has done pre /run/shm
Otherwise we can of course add a symlink as well -- it's just a bit more than one fstab line then -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
