<pitti> oSoMoN: that looks ok; is /dev/shm a symlink?
<oSoMoN> pitti, no, /dev/shm is not a symlink, it’s a plain directory
(drwxr-xr-x)
<ogra_> aha
and not 1777
<oSoMoN> yup
but I have no idea why it doesn’t have the right permissions
<oSoMoN> (which is my original question)
<pitti> ogra_: ah, it should be a symlink
<pitti> err, oSoMoN
<pitti> well, it really shouldn't be, but with Debian's layout it should
<oSoMoN> pitti, do you know what is responsible for creating it in the first place, when creating a chroot?
<pitti> oSoMoN: it depends on how you build it, but I figure somewhere between initscript's postinst and debootstrap; mk-sbuild and friends might also make some adjustments there, and sbuild has its own fstabs
For reference:
<pitti> oSoMoN: that looks ok; is /dev/shm a symlink?
<oSoMoN> pitti, no, /dev/shm is not a symlink, it’s a plain directory
(drwxr-xr-x)
<ogra_> aha
and not 1777
<oSoMoN> yup
but I have no idea why it doesn’t have the right permissions
<oSoMoN> (which is my original question)
<pitti> ogra_: ah, it should be a symlink
<pitti> err, oSoMoN
<pitti> well, it really shouldn't be, but with Debian's layout it should
<oSoMoN> pitti, do you know what is responsible for creating it in the first place, when creating a chroot?
<pitti> oSoMoN: it depends on how you build it, but I figure somewhere between initscript's postinst and debootstrap; mk-sbuild and friends might also make some adjustments there, and sbuild has its own fstabs