**** BEGIN LOGGING AT Mon Jul 17 03:00:03 2017 Jul 17 19:35:46 hello all, I'm building a distro with systemd and mounting rootfs as read only in tmpfs, but when I run "mount" I see that /home/root and /media are mounted with rw,noexec,relatime. I can't find how to disable this, is there a way prevent to mount /home/root and /media? If I put these mount point in fstab systemd overrides this. Jul 17 19:49:28 fabioberton[m]: when you enable read-only-rootfs image feature, by default volatile-binds is included. this package sets up bind mounts into /var/volatile to make certain needed paths writable, while copying any existing content in those paths from the rootfs to avoid breakage. you can control what paths this is done for via the VOLATILE_BINDS variable. see the volatile-binds reicpe for details. this sort of thing is also done via systemd's tmpfiles, but Jul 17 19:49:29 those work better at creating links when nothing already exists, which makes it difficult to change the behavior only when read-only-rootfs is enabled Jul 17 19:50:15 i have some local bits that switch the /var/volatile mount to a non-volatile data partition on my device, need to submit bits to make that easier or keep that as tmpfs but add another path for persistent user data Jul 17 19:51:09 kergoth (IRC): thanks, I'll check that Jul 17 19:52:04 there's a fair bit of inconsistency in handling of paths that need to be placed in tmpfs or otherwise writable paths, right now. volatiles is used for sysvinit, tmpfiles for systemd, and volatile-binds fills in a gap that neitehr of those qutie cover, but volatile-binds is missing a sysvinit startup script too, so that's systemd only.. Jul 17 21:32:24 khem, I am looking at the System.map differences btw gcc6 and gcc7 Jul 17 21:33:28 one thing is strange... Jul 17 21:33:44 gcc6 c001c324 t cpuhp_issue_call Jul 17 21:33:57 c001c1d0 t cpuhp_issue_call.constprop.2 Jul 17 21:34:00 ^ Jul 17 21:34:16 this is gcc7 Jul 17 21:51:08 anyone know why when I'm linking a library, start.S is looking for main: https://gist.github.com/cbrake/c108ab51ba7c4c05d6513e35b3a93d38 Jul 17 21:51:48 this issue has come up several times with pyro (may be related to the recipe sysroots change, or GCC changes) **** BEGIN LOGGING AT Tue Jul 18 02:14:50 2017 **** ENDING LOGGING AT Tue Jul 18 03:00:03 2017