On Thu, Oct 17, 2013 at 02:59:37PM +0200, Warpme wrote: > On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote: > >On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote: > >>Maybe we should disable [re]mounting / by systemd at all? > >All systemd does, is call 'mount -o remount /'. I have no idea how you end > >up with a read-only filesystem. > > > >As a work-around, you can add > >/etc/systemd/system/systemd-remount-fs.service.d/90-remount.conf with > > > >[Service] > >ExecStartPost=mount -o remount,rw / > > > >and/or run systemd in debug mode (add systemd.log_level=debug on the kernel > >command line), to see what is going on. > > > >Zbyszek > > > Adding > > /etc/systemd/system/systemd-remount-fs.service.d/90-remount.conf > > not helps. Hm.
> When I enable debugging by adding systemd.log_level=debug I'm receiving tons > of messages about started/failed journal. > Probably due / being in ro mode. That's possible. Try removing or renaming /var/log/journal... journald should then stay in /run/log/journal. > Is it possible that ro issue is because I'm building systemd with minimal > enabled features ? > > > My configure line is following: ... Those shouldn't matter. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
