[edgy] /var/run is mounted before /var

Bug #68293 reported by packet on 2006-10-25
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)

Bug Description

Binary package hint: initscripts


The current edgy initscripts try to mount /var/run before /var could be mounted. This obviously fails and in the end, networking does not work (because /var/run/network also seems to be missing)

It doesn't obviously fail, it works just fine -- we have code to make sure that /var can be mounted and /var/run and /var/lock retained over top.

It's more likely that you haven't got a /var/run or /var/lock directory on your root filesystem underneath /var

Changed in sysvinit:
status: Unconfirmed → Rejected
Robin Sheat (eythian) wrote :

I'd like to suggest that those directories be created if they don't already exist. It causes really hard to solve problems if they aren't there. In my case: http://www.kallisti.net.nz/blog/2006/10/trials-of-moving-var-in-ubuntu/

They can't be created, the entire reason that they exist as RAM filesystems is that the root filesystem is read-only at that point.

The suggestion is to create them on shutdown after unmounting the other filesystems, but before remounting the root.

Robin Sheat (eythian) wrote :

Ah. Well, perhaps a test that outputs a meaningful error message. "/var/run must exist on the '/' filesystem for networking to operate" or something?

packet (packet) wrote :

Thanks for the info, mkdir /var/run, /var/lock on my root filesystem fixed the problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers