Sadly the fault here is in the FHS, which specifies that those two
directories are under /var -- we need files in both directories to be
able to mount /var, so it's a bit of a chicken and egg situation. The
Ubuntu solution is reasonably elegant (bind-mount so that /var/run and
/var/lock are
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = Scott James Remnant (keybuk)
--
/var is mounted too late during the init sequence
https://bugs.launchpad.net/bugs/139230
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I'm sorry, but I am unable to replicate this bug; in order to help debug
it, you will need to provide more information.
The test setup I used had two 8GB SCSI drives, partitioned as follows:
/dev/sd[ab]1 - md0 - /boot
/dev/sd[ab]2 - swap
/dev/sd[ab]5 - md1 - LVM PV
LVM is configured with a
Yes, the problem is that you have to create /var/lock, /var/run in root
filesystem - even though you have /var as a separate filesystem. It is
confusing. Especially so for the people who initially do not have /var
as separate filesystem and decide at some point separate it. They have
to be very
** Changed in: upstart (Ubuntu)
Target: ubuntu-7.10-beta = ubuntu-7.10-rc
--
/var is mounted too late during the init sequence
https://bugs.launchpad.net/bugs/139230
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
marked my bug 134650 as a dupe to this one. There is some info in there
which might be interesting. This problem had broken networking for me.
--
/var is mounted too late during the init sequence
https://bugs.launchpad.net/bugs/139230
You received this bug notification because you are a member
