Bug#638019: /run/initctl

2012-01-09 Thread Robert Millan
El 9 de gener de 2012 0:10, Roger Leigh rle...@codelibre.net ha escrit: Please could you try the package at http://people.debian.org/~rleigh/sysvinit/sysvinit_2.88dsf-19.dsc Let me know if the postinst logic is acceptable to you.  It works for me, and the increasing delay should work for all

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Fri, Jan 06, 2012 at 03:25:53PM +0100, Robert Millan wrote: I didn't notice this was actually a Release Goal [1]. Tagging appropiately. I should note that the patch I sent has an unwanted side-effect: unability to send messages to init until after first reboot, which means first reboot

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 11:22:41AM +, Roger Leigh wrote: On Fri, Jan 06, 2012 at 03:25:53PM +0100, Robert Millan wrote: I didn't notice this was actually a Release Goal [1]. Tagging appropiately. I should note that the patch I sent has an unwanted side-effect: unability to send

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
Hi Roger, Thanks for looking at this. El 8 de gener de 2012 12:22, Roger Leigh rle...@debian.org ha escrit: How about on upgrade we symlink /run/initctl → /dev/initctl if /run/initctl does not exist? Programs can therefore be switched to using /run/initctl immediately. This seems fine,

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 01:51:03PM +0100, Robert Millan wrote: Hi Roger, Thanks for looking at this. El 8 de gener de 2012 12:22, Roger Leigh rle...@debian.org ha escrit: How about on upgrade we symlink /run/initctl → /dev/initctl if /run/initctl does not exist? Programs can therefore

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 14:15, Roger Leigh rle...@codelibre.net ha escrit: I thought about it a bit more, and the symlink is not needed. If we create /run/initctl and re-exec init, it will then open the new pipe.  We can then delete the old one and the process is complete.  This can be done

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 02:26:52PM +0100, Robert Millan wrote: El 8 de gener de 2012 14:15, Roger Leigh rle...@codelibre.net ha escrit: I thought about it a bit more, and the symlink is not needed. If we create /run/initctl and re-exec init, it will then open the new pipe.  We can then

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 14:56, Roger Leigh rle...@codelibre.net ha escrit: The postinst currently calls init u, but I think that's problematic-- it would call the new binary using the new path. On the contrary, isn't this precisely what we wanted? No symlink needed then. -- Robert Millan --

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 15:00, Robert Millan r...@debian.org ha escrit: El 8 de gener de 2012 14:56, Roger Leigh rle...@codelibre.net ha escrit: The postinst currently calls init u, but I think that's problematic-- it would call the new binary using the new path. On the contrary, isn't this

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 03:01:57PM +0100, Robert Millan wrote: El 8 de gener de 2012 15:00, Robert Millan r...@debian.org ha escrit: El 8 de gener de 2012 14:56, Roger Leigh rle...@codelibre.net ha escrit: The postinst currently calls init u, but I think that's problematic-- it would call

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 15:14, Roger Leigh rle...@codelibre.net ha escrit: The problem is that there isn't a signal to force a re-exec.  You have to do it through the control pipe. Ah I see. In retrospect, this seems like a bad decision. Well, gotta work with what we've got...  init u sends

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 03:34:13PM +0100, Robert Millan wrote: El 8 de gener de 2012 15:14, Roger Leigh rle...@codelibre.net ha escrit: path, init u on its own won't work.  I would suggest this strategy: 1) Create /run/initctl 2) Symlink /dev/initctl (or /etc/.initctl) to /run/initctl

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 16:20, Roger Leigh rle...@codelibre.net ha escrit: If we don't do that, then we are left running the old /sbin/init binary, which is an important part of the upgrade. Only until reboot. A reboot is necessary for the upgrade anyway (needed by kernel).  Or if telinit/init

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 04:29:43PM +0100, Robert Millan wrote: El 8 de gener de 2012 16:20, Roger Leigh rle...@codelibre.net ha escrit: If we don't do that, then we are left running the old /sbin/init binary, which is an important part of the upgrade. Only until reboot. A reboot is

Bug#638019: /run/initctl

2012-01-08 Thread Robert Millan
El 8 de gener de 2012 16:47, Roger Leigh rle...@codelibre.net ha escrit: No, 2) is replacing with a symlink, while 6) is removing the now unneeded symlink.  I noticed that if you mv /dev/initctl /dev/initctl.old, init (I presume) immediately recreates /dev/initctl. The following sequence

Bug#638019: /run/initctl

2012-01-08 Thread Roger Leigh
On Sun, Jan 08, 2012 at 03:01:57PM +0100, Robert Millan wrote: El 8 de gener de 2012 15:00, Robert Millan r...@debian.org ha escrit: El 8 de gener de 2012 14:56, Roger Leigh rle...@codelibre.net ha escrit: The postinst currently calls init u, but I think that's problematic-- it would call

Bug#638019: /run/initctl

2012-01-06 Thread Robert Millan
user rle...@debian.org usertag 638019 run-transition thanks I didn't notice this was actually a Release Goal [1]. Tagging appropiately. I should note that the patch I sent has an unwanted side-effect: unability to send messages to init until after first reboot, which means first reboot can't be