[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Only forbid use of old alternatives to /run in wheezy+1?

On Sat, 16 Apr 2011, rleigh wrote:
We haven't made any plans to remove it yet.  We'll look more closely
at the best way to do that once all the users are moved over.  Given
the small number, it's quite likely this won't take very long.  If
it turns out that there are other users of /lib/init/rw, it's not a
problem keeping it around for wheezy.  But if there aren't, there's
no need to retain it.

If there is a cleaner method than using versioned Breaks, I'm sure we
can look at that instead--nothing concrete is planned yet for the
removal, so all suggestions are welcome.

I suggest:
 - on upgrade, bind mount or symlink /run/init -> /lib/init/rw
 - on boot, after mounting /run, mkdir /run/init; ln -s /run/init /lib/init/rw

Or in other words - exactly like we're handling /var/lock and /dev/shm except
without a possible separate tmpfs.

This keeps /lib/init/rw available at all times and doesn't require any
particular upgrade order. The link could be dropped in wheezy+1 but there's no
urgency to do so.

I was under the impression that this was already part of the plan, did
/run/init get dropped for some reason?

Edward Allcutt

Reply to: