[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

I just created a vivid chroot with `pcreate -a amd64 -d vivid vivid- amd64` and I verified that inside it /dev/shm is a directory with permissions "drwxrwxrwt". Thanks Martin! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sy

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu3 --- sysvinit (2.88dsf-53.2ubuntu3) vivid; urgency=medium * debian/initscripts.postinst: Create /dev/shm directory with 1777 permissions, so that chroots stay compatible to what you'd find on a real system. (LP:

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

** Branch linked: lp:ubuntu/vivid-proposed/sysvinit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1399772 Title: /dev/shm is not writable inside vivid chroot on trusty h

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

** Changed in: sysvinit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1399772 Title: /dev/shm is not writable inside

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

Directories in a pristine trusty VM after debootstrapping utopic and vivid: $ ls -ld /{dev,run}/shm /tmp/{utopic,vivid}/{dev,run}/shm ls: cannot access /tmp/vivid/run/shm: No such file or directory lrwxrwxrwx 1 root root8 Dec 18 18:37 /dev/shm -> /run/shm drwxrwxrwt 2 root root 40 Dec 18 18:

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

** Changed in: sysvinit (Ubuntu) Status: New => In Progress ** Changed in: sysvinit (Ubuntu) Milestone: None => ubuntu-15.01 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpa

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1399772 Title: /dev/shm is not writable

[Touch-packages] [Bug 1399772] Re: /dev/shm is not writable inside vivid chroot on trusty host

This is reproducible with simple debootstraps of utopic vs. vivid. It looks as though a fair bit of relevant code was dropped from initscripts.postinst somewhere along the way, which I suspect is relevant. ** Package changed: ubuntu => sysvinit (Ubuntu) -- You received this bug notification bec