Bug#800342: first mount /var, then write to it

[積丹尼 Dan Jacobson]

Package: systemd
Severity: important
Version: 226-3

Please first mount /var before trying to read / write to it! !

# journalctl |grep /var
Sep 27 16:16:57 jidanni2 resolvconf[168]: mkdir: cannot create directory '/var/run': Read-only file system
Sep 27 16:16:57 jidanni2 resolvconf[168]: /etc/resolvconf/update.d/dnsmasq: Error: Failed trying to create directory /var/run/dnsmasq
Sep 27 16:17:03 jidanni2 systemd-udevd[292]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 29' failed with exit code 99.
Sep 27 16:17:03 jidanni2 systemd-udevd[297]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1' failed with exit code 99.
Sep 27 16:17:03 jidanni2 systemd-udevd[299]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' failed with exit code 99.
Sep 27 16:17:04 jidanni2 systemd[1]: Mounting /var...
Sep 27 16:17:04 jidanni2 systemd[1]: Mounted /var.
Sep 27 16:17:10 jidanni2 smartd[500]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.FUJITSU_MHT2040AT-NN4GT531H3AR.ata.state
Sep 27 16:17:10 jidanni2 smartd[500]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.FUJITSU_MHT2040AT-NN4GT531H3AR.ata.state
Sep 27 16:17:10 jidanni2 dnsmasq[540]: no servers found in /var/run/dnsmasq/resolv.conf, will retry

See how smartd works smoothly, while all the others are disrupted.

Please don't assume that partitions are the same as on your computer.
Especially as when we made the partitions we were using the best
practices at the time.

Please implement a simple check to prevent the above from happening.

By the way, my computer no longer has sound. Maybe due to this.

Or give me a workaround.

I mean you do mount it eventually, but you do it at the wrong time.

"/..../" were all originally separate physical disks in Unix history.
Now they are all supposed to be the same perhaps, but at least you
should be able to offer workarounds that don't break anything.