Re: /dev/shm on kfreebsd buildds
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. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140604190307.gl31...@hall.aurel32.net
Re: /dev/shm on kfreebsd buildds
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/shmtmpfs defaults0 0 Could something similar be done on kfreebsd? Cheers, Julien signature.asc Description: Digital signature
Re: /dev/shm on kfreebsd buildds
Julien Cristau jcris...@debian.org 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/shmtmpfs defaults0 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 Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87y4xccw05@anonymous.siccegge.de
Re: /dev/shm on kfreebsd buildds
Christoph Egger christ...@debian.org writes: Julien Cristau jcris...@debian.org 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/shmtmpfs defaults0 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 debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87tx80cvvj@anonymous.siccegge.de
Re: Re: /dev/shm on kfreebsd buildds
Hi, On Sun, 25 May 2014 21:14:20 +0200, Christoph Egger wrote: There's no such thing as a /dev/shm in kfreebsd-* buildd chroots at the moment. How are these created on linux-sbuild? The hosts sseem to have /dev/shm btw. This problem sounds familiar from BSD jail setup, where the early bootscripts don't handle this for you as they do on the host. I documented this procedure: https://wiki.debian.org/Debian_GNU/kFreeBSD/Jails : # Compatibility symlink from /dev/shm to /run/shm ln -s /run/shm /srv/jail/$JID/dev/ We should only need sbuild to do something similar. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/538cdfee.4040...@pyro.eu.org
Re: /dev/shm on kfreebsd buildds
Ahoi! Julien Cristau jcris...@debian.org writes: 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? There's no such thing as a /dev/shm in kfreebsd-* buildd chroots at the moment. How are these created on linux-sbuild? The hosts sseem to have /dev/shm btw. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer pgp5p5yKY5yhC.pgp Description: PGP signature
/dev/shm on kfreebsd buildds
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? Thanks, Julien signature.asc Description: Digital signature
