Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Roger Leigh
On Wed, Feb 01, 2012 at 09:44:58PM +0100, Michael Biebl wrote: > On 01.02.2012 17:42, Michael Biebl wrote: > > I'd guess there is more code out there hardcoding the location of the > > initctl socket (I could do an archive wide grep for "/dev/initctl" fwiw). > > FYI: http://people.debian.org/~bieb

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Michael Biebl
On 01.02.2012 17:42, Michael Biebl wrote: > I'd guess there is more code out there hardcoding the location of the > initctl socket (I could do an archive wide grep for "/dev/initctl" fwiw). FYI: http://people.debian.org/~biebl/results.dev-initctl -- Why is it that all of the instruments seekin

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Michael Biebl
Two more issues: After installing the updated systemd-initctl.{service,socket}, they need to be restarted in postinst. systemctl try-restart for the service and restart for the socket is most likely what we want here. On 01.02.2012 17:57, Roger Leigh wrote: > On Wed, Feb 01, 2012 at 05:42:28PM +0

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Laurent Bigonville
tag 657990 + patch thanks Hi, Please see the attached patch. Cheers Laurent Bigonville--- systemd-37/debian/control 2011-10-12 08:57:21.0 +0200 +++ systemd-37/debian/control 2012-02-01 16:57:18.0 +0100 @@ -36,7 +36,7 @@ Recommends: libpam-systemd Suggests: systemd-gui, python

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Roger Leigh
On Wed, Feb 01, 2012 at 05:42:28PM +0100, Michael Biebl wrote: > If we provide a /dev/initctl → /run/initctl symlink, we don't need that > Breaks afaics and I think we should add such a a symlink anyway for > backwards compatibility. > I'd guess there is more code out there hardcoding the location

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Michael Biebl
On 01.02.2012 17:42, Michael Biebl wrote: > On 01.02.2012 17:20, Laurent Bigonville wrote: >> tag 657990 + patch >> thanks >> >> Hi, >> >> Please see the attached patch. >> > >> -Breaks: lvm2 (<< 2.02.84-1) >> +Breaks: lvm2 (<< 2.02.84-1), sysvinit (<< 2.88dsf-19) > > If we provide a /dev/initctl

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-02-01 Thread Michael Biebl
On 01.02.2012 17:20, Laurent Bigonville wrote: > tag 657990 + patch > thanks > > Hi, > > Please see the attached patch. > > -Breaks: lvm2 (<< 2.02.84-1) > +Breaks: lvm2 (<< 2.02.84-1), sysvinit (<< 2.88dsf-19) If we provide a /dev/initctl → /run/initctl symlink, we don't need that Breaks afaic

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-01-31 Thread Michael Biebl
On 31.01.2012 21:56, Roger Leigh wrote: > On Tue, Jan 31, 2012 at 07:46:03PM +0100, Michael Biebl wrote: >> I guess you don't have systemd-sysv installed, i.e. halt and shutdown >> are provided by sysvinit? >> >> As already mentioned, you can either use systemctl directly or create a >> /dev/log →

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-01-31 Thread Roger Leigh
On Tue, Jan 31, 2012 at 07:46:03PM +0100, Michael Biebl wrote: > I guess you don't have systemd-sysv installed, i.e. halt and shutdown > are provided by sysvinit? > > As already mentioned, you can either use systemctl directly or create a > /dev/log → /run/log symlink manually. > > Roger, would i

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-01-31 Thread Michael Biebl
On 30.01.2012 17:05, Laurent Bigonville wrote: > Package: systemd > Version: 37-1 > Severity: grave > Justification: renders package unusable I'd argue it's sysvinit breaking systemd, but ok :-) > > Hi, > > /dev/initctl has moved to /run/initctl. > > This means that shutdown and other commands

Bug#657990: systemd: /dev/initctl has moved to /run/initctl

2012-01-30 Thread Laurent Bigonville
Package: systemd Version: 37-1 Severity: grave Justification: renders package unusable Hi, /dev/initctl has moved to /run/initctl. This means that shutdown and other commands are now failing with errors like "init: timeout opening/writing control channel /run/initctl" preventing the user to rebo