On Thu, Sep 24, 2015 at 03:51:16PM +0200, Tomasz Torcz wrote:
> On Thu, Sep 24, 2015 at 03:01:21PM +0200, Lennart Poettering wrote:
> > That stackexchange link lists a pile of garbage. We have an official
> > API to check whether the system is booted with systemd:
> > sd_booted(). It's documented h
On Thu, 24.09.15 15:51, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> On Thu, Sep 24, 2015 at 03:01:21PM +0200, Lennart Poettering wrote:
> > That stackexchange link lists a pile of garbage. We have an official
> > API to check whether the system is booted with systemd:
> > sd_booted(). It's docume
On Thu, Sep 24, 2015 at 03:01:21PM +0200, Lennart Poettering wrote:
> That stackexchange link lists a pile of garbage. We have an official
> API to check whether the system is booted with systemd:
> sd_booted(). It's documented here:
>
> http://www.freedesktop.org/software/systemd/man/sd_booted.ht
On Thu, 24.09.15 13:18, Jonathan de Boyne Pollard
(j.deboynepollard-newsgro...@ntlworld.com) wrote:
> In an ideal world you would be able to have a routine that detected the
> running
> system manager, and then did whatever was appropriate to that system manager
> to
> power off, from sending s
Daniel P. Berrange:
> Maybe it wasn't actually upstart, but one of the other init systems.
> I just recall getting a patch from Debian folks to support it via
> the /run/initctl path, rather than /dev, and assumed that was upstart
> related.
It wasn't upstart or one of the other init systems. It
Lennart Poettering:
> We already declared the interface "obsolete" in the docs, which makes me
> particularly keen on dropping it...
You've heard from the Debian systemd maintainers. You haven't heard from
the Debian sysvinit maintainers. Their subtly different position on
/run/initctl, exemplifie
Hello all,
sorry for the late reply, I've been swamped with other stuff recently.
Lennart Poettering [2015-09-22 2:31 +0200]:
> a) there's support in systemctl to reboot the system by sending the
>right bytes to /dev/initctl as fallback, so that you can reboot a
>sysvinit system with "sy
What we could add is a --disable switch which makes
units/systemd-initctl.{socket,service} and src/initctl/ conditional so
distros that don't need it anymore can disable it (or make it disabled
by default and let distros which need it enable it).
Would that work for you, Lennart?
2015-09-23 1:17
2015-09-23 0:45 GMT+02:00 Lennart Poettering :
> On Wed, 23.09.15 00:38, Michael Biebl (mbi...@gmail.com) wrote:
>
>> Hi,
>>
>> yes, in Debian we'll need /dev/initctl support for at least another
>> release cycle so users can switch between the init system and safely
>> reboot (in both directions).
On Mon, Sep 21, 2015 at 8:31 PM, Lennart Poettering
wrote:
> Heya!
>
> Since a long time systemd has been shipping with two-way compat
> support for /dev/initctl, and I am tempted to remove it. Before I do
> so, I'd like some input on the relevance of this interface:
Gentoo currently utilizes thi
On Wed, 23.09.15 00:38, Michael Biebl (mbi...@gmail.com) wrote:
> Hi,
>
> yes, in Debian we'll need /dev/initctl support for at least another
> release cycle so users can switch between the init system and safely
> reboot (in both directions).
How does Debian switch between the init systems? Cou
Hi,
yes, in Debian we'll need /dev/initctl support for at least another
release cycle so users can switch between the init system and safely
reboot (in both directions).
If it's not too much of a nuisance, it would be great if it could
still be provided a bit longer upstream, otherwise we'll have
On Tue, Sep 22, 2015 at 02:31:25AM +0200, Lennart Poettering wrote:
> Heya!
>
> Since a long time systemd has been shipping with two-way compat
> support for /dev/initctl, and I am tempted to remove it. Before I do
> so, I'd like some input on the relevance of this interface:
I'd guess that debian
On Tue, Sep 22, 2015 at 12:48:21PM +0200, Lennart Poettering wrote:
> On Tue, 22.09.15 11:41, Daniel P. Berrange (berra...@redhat.com) wrote:
>
> > > One more addendum to the original mail:
> > >
> > > We already declared the interface "obsolete" in the docs, which makes
> > > me particularly kee
On Tue, 22.09.15 11:41, Daniel P. Berrange (berra...@redhat.com) wrote:
> > One more addendum to the original mail:
> >
> > We already declared the interface "obsolete" in the docs, which makes
> > me particularly keen on dropping it...
>
> I guess one thing is that even if support for /dev/intc
On Tue, Sep 22, 2015 at 12:32:25PM +0200, Lennart Poettering wrote:
> On Tue, 22.09.15 10:11, Daniel P. Berrange (berra...@redhat.com) wrote:
>
> > > And most importantly: the entire protocol use by sysvinit via
> > > /dev/initctl is deeply flawed, since it sends messages over
> > > /dev/initctl t
On Tue, 22.09.15 10:11, Daniel P. Berrange (berra...@redhat.com) wrote:
> > And most importantly: the entire protocol use by sysvinit via
> > /dev/initctl is deeply flawed, since it sends messages over
> > /dev/initctl that are not a divisor of PIPE_SIZE in length. Thus, if
> > PID 1 didn't read m
On Tue, Sep 22, 2015 at 02:31:25AM +0200, Lennart Poettering wrote:
> Heya!
>
> Since a long time systemd has been shipping with two-way compat
> support for /dev/initctl, and I am tempted to remove it. Before I do
> so, I'd like some input on the relevance of this interface:
>
> a) there's suppo
Heya!
Since a long time systemd has been shipping with two-way compat
support for /dev/initctl, and I am tempted to remove it. Before I do
so, I'd like some input on the relevance of this interface:
a) there's support in systemctl to reboot the system by sending the
right bytes to /dev/initctl
19 matches
Mail list logo
