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

2011-04-17 Thread Roger Leigh
On Sun, Apr 17, 2011 at 07:44:55AM +0200, Goswin von Brederlow wrote: Edward Allcutt edw...@allcutt.me.uk writes: On Sat, 16 Apr 2011, Roger Leigh wrote: On Sat, Apr 16, 2011 at 05:58:19PM +0100, Edward Allcutt wrote: I suggest: - on upgrade, bind mount or symlink /run/init -

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

2011-04-17 Thread Thomas Hood
This is not to say we couldn't remove it on startup though. You should not remove /lib/init/rw on the next reboot. If the upgrade stops due to an error then the system might be rebooted before the upgrade is continued. /lib/init/rw needs to remain present until all packages using it have

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

2011-04-16 Thread Thomas Hood
While I applaud the introduction of /run, I have some concerns about how quickly users of alternatives to /run could be required to switch to the new location. Consider the following scenario. Package P is using /lib/init/rw. At some point the new version of initscripts is installed. The

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

2011-04-16 Thread rleigh
On Sat, Apr 16, 2011 at 12:39:03PM +0200, Thomas Hood wrote: While I applaud the introduction of /run, I have some concerns about how quickly users of alternatives to /run could be required to switch to the new location. Consider the following scenario. Package P is using /lib/init/rw.

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

2011-04-16 Thread Edward Allcutt
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,

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

2011-04-16 Thread Roger Leigh
On Sat, Apr 16, 2011 at 05:58:19PM +0100, Edward Allcutt wrote: 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

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

2011-04-16 Thread Edward Allcutt
On Sat, 16 Apr 2011, Roger Leigh wrote: On Sat, Apr 16, 2011 at 05:58:19PM +0100, Edward Allcutt wrote: 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

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

2011-04-16 Thread Goswin von Brederlow
Edward Allcutt edw...@allcutt.me.uk writes: On Sat, 16 Apr 2011, Roger Leigh wrote: On Sat, Apr 16, 2011 at 05:58:19PM +0100, Edward Allcutt wrote: 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