Hi, To be even more clear:
HOST: bigon@soldur:~$ ls -ld /dev/shm /run/shm ls: impossible d'accéder à /run/shm: Aucun fichier ou dossier de ce type drwxrwxrwt. 2 root root 300 nov 25 16:05 /dev/shm CHROOT: (sid-amd64-sbuild)root@soldur:/# ls -ld /dev/shm /run/shm lrwxrwxrwx. 1 root root 8 Nov 23 2012 /dev/shm -> /run/shm drwxr-xr-x. 2 root root 4096 Nov 23 2012 /run/shm Creating /run/shm on the host is also fixing this. Is it possible that schroot is actually trying to resolve the /dev/shm -> /run/shm symlink outside of the chroot? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
