Doesn't create /var/run or /var/lock directories underneath /var mountpoint

[Scott James Remnant (Canonical)]

If the user decides to have /var on a separate mountpoint, ubiquity just copies the current system without taking care to make /var/run or /var/lock *underneath* this mountpoint so that they are available during early boot, before /var itself has been mounted.

On the non-ubiquiuty system this is taken care of by the initscripts postinst on either fresh installation, or on upgrade from breezy (so dpkg-reconfigure isn't sufficient on this).

This can be fixed by either deliberately making empty /var/run and /var/lock directories on the root filesystem before mounting the /var partition over top, or by running the initscripts postinst with just "configure" as an argument -- which bind-mounts the root filesystem elsewhere so that the directories can be made on it rather than the /var filesystem.

[Scott James Remnant (Canonical) (canonical-scott)]

Critical because this causes any installation with a separate /var to fail to boot correctly

[Scott James Remnant (Canonical) (canonical-scott)]

http://people.ubuntu.com/~scott/bzr/ubiquity/

[Colin Watson (cjwatson)]

I think I'd rather do this in partman-target while it's mounting filesystems.

[Colin Watson (cjwatson)]

This should sort it out:

partman-target (41ubuntu1) dapper; urgency=low

  * Create /var/lock and /var/run on the root filesystem before /var is
    mounted, so that udev can use them (closes: Malone #44142).

 -- Colin Watson <email address hidden> Thu, 11 May 2006 10:17:10 +0100

I'll incorporate this into ubiquity as part of my next upload.