As explained above, /run is mounted by initramfs-tools, thus changing the package.
** Package changed: systemd (Ubuntu) => initramfs-tools (Ubuntu) ** Summary changed: - systemd doesn't respect /etc/fstab for internal mounts + check /etc/fstab for custom /run mount options -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1540803 Title: check /etc/fstab for custom /run mount options Status in initramfs-tools package in Ubuntu: Triaged Bug description: Under upstart, I can have the following line in my /etc/fstab: tmpfs /run tmpfs defaults,size=10M 0 0 At mount time, mountall will use /etc/fstab as an override for the internal fstab (/lib/init/fstab) and so I end up with /run mounted with a 10MB limit. Under systemd, the exact same fstab appears to be ignored and I end up with a /run that has a limit of half my memory. This may very well surprise users upgrading production environments from 14.04 to 16.04 or users that have to follow some strict partitioning and mount configuration policies (we've seen a couple of those by now) so it'd be good to have this resolved. I did testing with /run in LXD containers on 14.04 (upstart) and 16.04 (systemd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1540803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
