On Wed, Oct 24, 2018 at 11:30:17AM +0200, Marc Haber wrote:
> On Tue, 23 Oct 2018 16:43:07 +0200, Wouter Verhelst
> wrote:
> >This has been discussed before and rejected. It makes no sense.
>
> technically, but a lot of sense if it helps silencing another
> instance of an "exchange standard
On Tue, 23 Oct 2018 16:43:07 +0200, Wouter Verhelst
wrote:
>This has been discussed before and rejected. It makes no sense.
... technically, but a lot of sense if it helps silencing another
instance of an "exchange standard arguments" discussion about systemd.
Greetings
Marc
--
On Sat, Oct 20, 2018 at 08:22:35AM +0800, Paul Wise wrote:
> On Fri, Oct 19, 2018 at 7:30 PM Martin Steigerwald wrote:
>
> > As long as people choose to strip of dependencies to libsystemd from
> > packages like util-linux, avoiding a fork would not work with how Debian
> > and Debian based
On 10/19/18 12:25 PM, Bastian Blank wrote:
> On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
>> So Devuan almost doubles the percentage of sysvinit-core installations.
>
> Devuan is _not_ Debian. They forked it
They *claimed* it was a fork, though in reality Devuan is just
Ivan Shmakov writes ("Re: Debian Buster release to partially drop non-systemd
support "):
> Ian Jackson writes:
> > Please come to debian-init-divers...@chiark.greenend.org.uk.
>
> Do you plan to also make that list accessible via NNTP (perhaps
> via
> Ian Jackson writes:
> KatolaZ writes:
>> The problem that spurred this thread is that sysvinit needs a
>> maintainer. That’s why some of us are here: our intention is to
>> help with maintaining sysvinit in Debian if possible, since we will
>> keep maintaining it in Devuan
On Oct 20, Paul Wise wrote:
> It might be feasible to introduce nosystemd build profiles to Debian
> source packages and then create a shed/bikeshed/PPA (once that
> infrastructure exists) that contains rebuilds using that build
> profile. That would allow Devuan's libsystemd stripping to be
>
On Sat, Oct 20, 2018 at 06:54:07PM +0200, Arne Babenhauserheide wrote:
> > Should Debian also support "noalsa", "noavahi", "nocups",
> > "nopulseaudio", "nosysvinit", "nodbus", "nopam", "nowayland",
>
> Are alsa, avahi, cups, pulseaudio, sysvinit, dbus, pam and wayland all
> similar in scope to
On Sat, Oct 20, 2018 at 06:54:07PM +0200, Arne Babenhauserheide wrote:
> Ansgar Burchardt writes:
> > Should Debian also support "noalsa", "noavahi", "nocups",
> > "nopulseaudio", "nosysvinit", "nodbus", "nopam", "nowayland",
> Are alsa, avahi, cups, pulseaudio, sysvinit, dbus, pam and wayland
Ansgar Burchardt writes:
> Should Debian also support "noalsa", "noavahi", "nocups",
> "nopulseaudio", "nosysvinit", "nodbus", "nopam", "nowayland",
Are alsa, avahi, cups, pulseaudio, sysvinit, dbus, pam and wayland all
similar in scope to systemd? If not, then this question is a strawman.
Does "Debian uses Systemd by default" mean "Debian is married with
Systemd forever"?
Should Debian exclude other desktop environments but Gnome, because
Gnome shell is the default one? Then drop Qt and Wx compatibility?
__
I'm using this express-made address because personal addresses
Bastian Blank wrote:
On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> So Devuan almost doubles the percentage of sysvinit-core installations.
Devuan is _not_ Debian. They forked it, with the full knowledge that
they might have to do all the work to support their choices.
Paul Wise writes:
> On Fri, Oct 19, 2018 at 7:30 PM Martin Steigerwald wrote:
>> As long as people choose to strip of dependencies to libsystemd from
>> packages like util-linux, avoiding a fork would not work with how Debian
>> and Debian based distributions are built.
>
> It might be feasible to
On Fri, Oct 19, 2018 at 7:30 PM Martin Steigerwald wrote:
> As long as people choose to strip of dependencies to libsystemd from
> packages like util-linux, avoiding a fork would not work with how Debian
> and Debian based distributions are built.
It might be feasible to introduce nosystemd
On Wed 17/Oct/2018 23:06:24 +0200 Russ Allbery wrote:
>> You say "more than adequate". I don't particularly see it as providing a
>> solid system as you don't get restart on failure. Now I can see how
>> people say that this is not a problem as daemons should not crash in the
>> first place.
Bastian Blank - 19.10.18, 12:25:
> On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> > So Devuan almost doubles the percentage of sysvinit-core
> > installations.
> Devuan is _not_ Debian. They forked it, with the full knowledge that
> they might have to do all the work to
Holger Levsen - 19.10.18, 12:02:
> On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> > A minority? Yes. But a sizable one.
>
> It doesn't matter how many people use it, if noone is willing to
> maintain it. *If* people are maintaining it, it also doesnt matter
> how many
On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> So Devuan almost doubles the percentage of sysvinit-core installations.
Devuan is _not_ Debian. They forked it, with the full knowledge that
they might have to do all the work to support their choices. They had
the chance to
On Fri, 2018-10-19 at 11:35 +0200, Martin Steigerwald wrote:
> Martin Steigerwald - 19.10.18, 10:57:
> > That written, I estimate or guess that the people preferring to use
> > another initialization system than the initialization system in
> > Systemd are in the minority. Yet, this minority might
On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> A minority? Yes. But a sizable one.
It doesn't matter how many people use it, if noone is willing to maintain
it. *If* people are maintaining it, it also doesnt matter how many people
are using it :)
*Someone* needs to do the
Martin Steigerwald - 19.10.18, 10:57:
> That written, I estimate or guess that the people preferring to use
> another initialization system than the initialization system in
> Systemd are in the minority. Yet, this minority might be larger than
> you think. Especially as popularity contest does
__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 19/10/18 a les 09:37, Philipp Kern ha escrit:
> On 2018-10-19 08:39, Narcis Garcia
dropping debian-hurd
Bernd Zeimetz - 18.10.18, 22:07:
> - the typical package maintainer won't test initscripts
I am not typical then.
> After using a lot of systemd now I will never go back to init scripts.
> Systemd comes with a steep learning curve, but one you've stated
> using its features
On Fri, 2018-10-19 at 09:37 +0200, Philipp Kern wrote:
> On 2018-10-19 08:39, Narcis Garcia wrote:
> > El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit:
> > > For my packages I can state that I do not have a single machine
> > > which is not using systemd - and to be honest - I won't waste my
> >
That’s interesting though - could we use GNU shepherd to:
a) support kFreeBSD?
b) automatically translate systemd units to sheep(?) (limited subset might work)
The other alternative is OpenRC - here’s the same question - could we have
systemd units as authoritative definition and have OpenRC
On 2018-10-19 08:39, Narcis Garcia wrote:
El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit:
For my packages I can state that I do not have a single machine which
is
not using systemd - and to be honest - I won't waste my time in
writing/debugging initscripts.
Most of people want to use a GNU
__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit:
> For my packages I can state that I do
On 10/13/18 12:58 PM, Holger Levsen wrote:
> On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote:
>>> Has policy changed regarding support for multiple inits, or is it just that
>>> no one is maintaining the shim and sysvinit-core?
>>
>> The latter. systemd-shim has been orphaned for
On Thu, 18 Oct 2018 06:58:14 +0100, Jonathan Dowland wrote:
> On Wed, Oct 17, 2018 at 08:33:47PM -0700, Russ Allbery wrote:
>>MAILTO was the main thing that I remember missing in terms of pure
>>functionality.
>
> This is not a complete substitute for all uses of MAILTO, but I found
> the
On 10/13/18 12:58 PM, Holger Levsen wrote:
> On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote:
>>> Has policy changed regarding support for multiple inits, or is it just that
>>> no one is maintaining the shim and sysvinit-core?
>>
>> The latter. systemd-shim has been orphaned for
Jonathan Dowland writes:
> On Thu, Oct 18, 2018 at 09:09:38AM +0100, Jonathan Dowland wrote:
>>Thanks for passing that along: I'm using it with Exim and haven't
>>noticed this particular problem, but it's useful to know it could
>>happen.
>
> Ah, because I have User=nobody, and so the systemd
Adam Borowski writes:
[..]
>
> Ouch. This is downright terrifying. It should be quite obvious why things
> other than exim can break when called from there.
>
> And there's no good way for a random tool you may use to know it might get
> suddenly SIGKILLed out of the blue.
The only workaround
On Thu, Oct 18, 2018 at 09:09:38AM +0100, Jonathan Dowland wrote:
Thanks for passing that along: I'm using it with Exim and haven't
noticed this particular problem, but it's useful to know it could
happen.
Ah, because I have User=nobody, and so the systemd sub-process can't
reap the privileged
On Thu, Oct 18, 2018 at 08:46:10AM +0200, Kamil Jońca wrote:
> > Put an OnFailure= line in systemd units that you want to mail you if
> > they go wrong
> >
> >> [Unit]
> >> OnFailure=status-email-user@%n.service
>
> But this not play well with exim4.
> See:
>
On Thu, Oct 18, 2018 at 08:46:10AM +0200, Kamil Jońca wrote:
But this not play well with exim4.
See:
https://lists.freedesktop.org/archives/systemd-devel/2018-September/041417.html
(and thread as a whole)
Thanks for passing that along: I'm using it with Exim and haven't
noticed this particular
Jonathan Dowland writes:
> On Wed, Oct 17, 2018 at 08:33:47PM -0700, Russ Allbery wrote:
>>MAILTO was the main thing that I remember missing in terms of pure
>>functionality.
>
> This is not a complete substitute for all uses of MAILTO, but I found
> the following useful so I share it in case
On Wed, Oct 17, 2018 at 08:33:47PM -0700, Russ Allbery wrote:
MAILTO was the main thing that I remember missing in terms of pure
functionality.
This is not a complete substitute for all uses of MAILTO, but I found
the following useful so I share it in case you weren't aware of it.
Define a
Paul Wise writes:
> On Thu, Oct 18, 2018 at 5:24 AM Russ Allbery wrote:
>> Timer units are also a more complicated problem since they're not a
>> superset of cron behavior. They do some things better than cron jobs;
>> they do other things much *worse* than cron jobs. I have cron jobs
>> that
On Thu, Oct 18, 2018 at 5:24 AM Russ Allbery wrote:
> Timer units are also a more complicated problem since they're not a
> superset of cron behavior. They do some things better than cron jobs;
> they do other things much *worse* than cron jobs. I have cron jobs that I
> wanted to convert to
Philipp Kern writes:
> On 17.10.2018 06:52, Russ Allbery wrote:
>> I think a package of a daemon that does not inherently require any
>> systemd-specific features and would work straightforwardly with
>> sysvinit, but has only a systemd unit file and no init script, is not
>> only buggy but
On 17.10.2018 06:52, Russ Allbery wrote:
> I think a package of a daemon that does not inherently require any
> systemd-specific features and would work straightforwardly with sysvinit,
> but has only a systemd unit file and no init script, is not only buggy but
> RC-buggy. That's what Policy
Philipp Kern writes:
> I don't understand. If I submit a merge request to the maintainer, it's
> on me to test what I submit actually works. So if I add stuff for a
> completely different init system I have to test it. The question is: Is
> the package buggy if it does not contain an init script
Hi Petter,
(Dropping backports)
Petter Reinholdtsen writes:
>> 1. systemd-shim is not necessary, even for DEs (except GNOME3).
>> 2. sysvinit-core is very stable and do not need new uploads.
>
> Thank you for expressing so well the cause of the fate for sysvinit in
> Debian. It seem clear its
Michael Biebl - 16.10.18, 22:08:
> Am 16.10.18 um 21:36 schrieb Adam Borowski:
> > Systemd's algorithm for btrfs RAID is:
> So your complaint is specific to btrfs RAID which afaik is still
> considered unstable?
Certain BTRFS RAID like RAID 1 and RAID 10 levels are considered stable
by upstream
On Tue, Oct 16, 2018 at 10:08:59PM +0200, Michael Biebl wrote:
> Am 16.10.18 um 21:36 schrieb Adam Borowski:
> > Systemd's algorithm for btrfs RAID is:
>
> So your complaint is specific to btrfs RAID which afaik is still
> considered unstable?
Care to specify what's unstable with btrfs RAID?
Am 16.10.18 um 22:24 schrieb Ian Jackson:
> Is this advocacy subthread really useful ? If we have bugs to report
> in systemd stuff we should report them in the BTS, not debate them on
> debian-devel.
>
> Adam Borowski writes ("Re: Debian Buster release to partially drop
&
Is this advocacy subthread really useful ? If we have bugs to report
in systemd stuff we should report them in the BTS, not debate them on
debian-devel.
Adam Borowski writes ("Re: Debian Buster release to partially drop non-systemd
support"):
> On Tue, Oct 16, 2018 at 08:38:06PM +
Am 16.10.18 um 21:36 schrieb Adam Borowski:
> Systemd's algorithm for btrfs RAID is:
So your complaint is specific to btrfs RAID which afaik is still
considered unstable?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
On Tue, Oct 16, 2018 at 08:38:06PM +0200, Bastian Blank wrote:
> On Tue, Oct 16, 2018 at 07:20:24PM +0200, Adam Borowski wrote:
> > On Tue, Oct 16, 2018 at 05:54:34PM +0200, Petter Reinholdtsen wrote:
> > > Absolutely. And the sysvinit boot system have lots of unsolved problems
> > > we never got
On Tue, Oct 16, 2018 at 07:20:24PM +0200, Adam Borowski wrote:
> On Tue, Oct 16, 2018 at 05:54:34PM +0200, Petter Reinholdtsen wrote:
> > Absolutely. And the sysvinit boot system have lots of unsolved problems
> > we never got around to figuring out, related to disk and other device
> > setup.
On Tue, Oct 16, 2018 at 05:54:34PM +0200, Petter Reinholdtsen wrote:
> > SysV init leaves all the really hard problems to these, as it cannot
> > really do much by itself. That's a fact that people that keep yelling
> > "but SysV init was so easy!" keep finessing..
>
> Absolutely. And the
On Tue, 2018-10-16 at 14:48 +0200, Philipp Kern wrote:
> The question is: Is
> the package buggy if it does not contain an init script but a systemd
> unit and it seems to be the case. Note that there are a *lot* of useful
> options in a systemd unit that would need emulation to make properly
[Martin Pitt]
> It's not only that. The sysvinit package *itself* doesn't actually do
> much really. That's not to downplay your past involvement there of
> course (e. g. developing insserv alone was a huge task), but the
> *real* maintenance is in all the packages that *ship* SysV init
>
Petter Reinholdtsen [2018-10-16 15:55 +0200]:
> [Benda Xu]
> > I was about to reply to this thread, but you have completely expressed
> > what I want to say:
> >
> > 1. systemd-shim is not necessary, even for DEs (except GNOME3).
> > 2. sysvinit-core is very stable and do not need new uploads.
>
On Tue, 16 Oct 2018, Adam Borowski wrote:
> > > With only two modified binary packages (policykit-1 and udisks2) I’ve
> 1. You need to recompile these packages, this is not something an average
> user or even sysadmin knows how to do.
I publish .deb packages for them (although not for all
On Tue, Oct 16, 2018 at 07:47:36PM +0800, Benda Xu wrote:
> Thorsten Glaser writes:
> > … this applies to the shim only. I was a bit surprised seeing on
> > someone else’s system that it was no longer installable, but almost
> > all systemd-free systems of people I know do not use the shim
[Benda Xu]
> I was about to reply to this thread, but you have completely expressed
> what I want to say:
>
> 1. systemd-shim is not necessary, even for DEs (except GNOME3).
> 2. sysvinit-core is very stable and do not need new uploads.
Thank you for expressing so well the cause of the fate for
On 2018-10-16 at 08:48, Philipp Kern wrote:
> On 2018-10-16 14:36, Ian Jackson wrote:
>
>> Philipp Kern writes ("Re: Debian Buster release to partially drop
>> non-systemd support"):
>>
>>> Could someone reiterate about what the curr
On 2018-10-16 14:36, Ian Jackson wrote:
Philipp Kern writes ("Re: Debian Buster release to partially drop
non-systemd support"):
Could someone reiterate about what the current state of init diversity
is supposed to be? Is it assumed to be best effort of every maintainer
being requir
Philipp Kern writes ("Re: Debian Buster release to partially drop non-systemd
support"):
> Could someone reiterate about what the current state of init diversity
> is supposed to be? Is it assumed to be best effort of every maintainer
> being required to ship an init script
KatolaZ writes ("Re: Debian Buster release to partially drop non-systemd
support"):
> The problem that spurred this thread is that sysvinit needs a
> maintainer. That's why some of us are here: our intention is to help
> with maintaining sysvinit in Debian if possible,
Matthew Vernon - 16.10.18, 13:27:
> Ian Jackson writes:
> > Also we are hampered by the lack of a safe space to communicate and
> > coordinate. I looked at some of the technical work done in other
> > distros to try to make desktoppy stuff continue to work well, and it
> > generally seems sane.
On 2018-10-16 13:27, Matthew Vernon wrote:
So:
http://www.chiark.greenend.org.uk/mailman/listinfo/debian-init-diversity
It's a standard mailman list with a public archive. I'm hoping people
interested in init system diversity in Debian can use it as a place to
co-ordinate. I don't want it to be
KatolaZ - 16.10.18, 13:39:
> On Tue, Oct 16, 2018 at 12:38:19PM +0200, Michael Biebl wrote:
>
> [cut]
>
> > What you say is obviously wrong, and you should know that if you
> > follow devuan.
> >
> > Even the founder of Devuan regularly uses exactly the words Ansgar
> > described.
> > Chris
I intend this to be my last response on that topic here. So even if you
choose to reply in a way that I feel hurt about, I intend to just let go
and end the hurting cycle within my heart instead of replying another
time.
Ansgar Burchardt - 16.10.18, 12:20:
> On Tue, 2018-10-16 at 09:57 +0200,
Hi Thorsten,
Thorsten Glaser writes:
> … this applies to the shim only. I was a bit surprised seeing on
> someone else’s system that it was no longer installable, but almost
> all systemd-free systems of people I know do not use the shim anyway,
> so I’d take the Subject line with a few grains
On Tue, Oct 16, 2018 at 12:38:19PM +0200, Michael Biebl wrote:
[cut]
>
> What you say is obviously wrong, and you should know that if you follow
> devuan.
>
> Even the founder of Devuan regularly uses exactly the words Ansgar
> described.
> Chris Lamb not to long ago was target of those
Ian Jackson writes:
> Also we are hampered by the lack of a safe space to communicate and
> coordinate. I looked at some of the technical work done in other
> distros to try to make desktoppy stuff continue to work well, and it
> generally seems sane. But some of those projects are quite toxic
Am 16.10.18 um 09:57 schrieb Martin Steigerwald:
> Ansgar Burchardt - 16.10.18, 08:53:
>> If some people consistently call others a "cancer", accuse them of
>> "vandalizing" open source, spread obvious FUD and so on, then I don't
>> think they would fit in well in Debian's culture where they would
On Tue, 2018-10-16 at 09:57 +0200, Martin Steigerwald wrote:
> Ansgar Burchardt - 16.10.18, 08:53:
> > If some people consistently call others a "cancer", accuse them of
> > "vandalizing" open source, spread obvious FUD and so on, then I don't
> > think they would fit in well in Debian's culture
Ansgar Burchardt writes:
...
> Please no. I don't think it would help Debian to have toxic people
> maintain packages.
You are using a fairly blunt tool if you judge people based on their
preference of operating system. ;-)
Let's instead judge people by the way they behave.
I admit that I
Martin Steigerwald writes ("Re: Debian Buster release to partially drop
non-systemd support"):
> Ian, cc'ing you to make you aware of this discussion, in case you
> aren't, and give you an opportunity to comment on your aim to adopt
> sysvinit package from some time ago.
T
On Tue, 2018-10-16 at 09:48 +0100, Jonathan Dowland wrote:
> On Tue, Oct 16, 2018 at 08:59:16AM +0200, Narcis Garcia wrote:
> > I'm using this express-made address because personal addresses
> > aren't
> > masked enough at this mail public archive. Public archive
> > administrator
> > should fix
On Mon, Oct 15, 2018 at 04:03:45PM +0200, Ansgar Burchardt wrote:
Please no. I don't think it would help Debian to have toxic people
maintain packages.
At least some of the people who were at least once involved in Devuan
(I haven't kept on top) were once valued Debian contributors - e.g.
On Tue, Oct 16, 2018 at 08:59:16AM +0200, Narcis Garcia wrote:
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
The right way to fight spam is to
Z
Re: [devuan-dev] Debian Buster release to partially drop non-systemd
support
https://lists.dyne.org/lurker/message/20181016.042148.1688fecb.en.html
> And no, it's not just that infobot factoid or just random people that
> are totally unrelated to Devuan.
A claim without facts. So FUD
On Mon, 2018-10-15 at 22:31 -0700, Alessio Treglia wrote:
> On Mon, Oct 15, 2018 at 9:51 PM Enzo Nicosia
> wrote:
> > Please, just tell us who we should contact (current/last
> > maintainer?) to start working on that.
>
> That's easy [1].
It is, but the link you gave is a rather cryptic way of
that the package is ready for adoption, as Petter
also already mentioned:
Re: Debian Buster release to partially drop non-systemd support
https://lists.debian.org/debian-devel/2018/10/msg00171.html
For adopting it, one would need to become at least a Debian maintainer,
or… have someone who spon
__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 15/10/18 a les 16:18, Thorsten Glaser ha escrit:
> Several people have said they
Martin Steigerwald writes:
> Ansgar Burchardt - 15.10.18, 16:03:
>> Please no. I don't think it would help Debian to have toxic people
>> maintain packages.
>>
>> (As an example, Devuan's infobot has fun facts like this one:
>> "<+infobot> 'sth is poettering' means it acts invasive, possessive,
On Mon, Oct 15, 2018 at 9:51 PM Enzo Nicosia wrote:
> Please, just tell us who we should contact (current/last
> maintainer?) to start working on that.
That's easy [1].
Thanks.
[1]
https://qa.debian.org/developer.php?login=pkg-sysvinit-de...@lists.alioth.debian.org
--
Alessio Treglia
On Tue, Oct 16, 2018 at 09:16:37AM +0800, Paul Wise wrote:
> On Tue, Oct 16, 2018 at 12:18 AM Adam Borowski wrote:
>
> > The main problem with sysvinit is the lack of a git repository.
>
> There is an upstream git repository with commits up to September 2018:
>
>
On Tue, Oct 16, 2018 at 12:18 AM Adam Borowski wrote:
> The main problem with sysvinit is the lack of a git repository.
There is an upstream git repository with commits up to September 2018:
http://savannah.nongnu.org/projects/sysvinit
http://git.savannah.nongnu.org/cgit/sysvinit.git
--
bye,
On Mon, Oct 15, 2018 at 06:02:37PM +0200, Adam Borowski wrote:
> On Mon, Oct 15, 2018 at 04:18:57PM +0200, Thorsten Glaser wrote:
> > I’ve volunteered to help out earlier in the thread, within constraints
> > (but rather that than to see things go and break).
>
> The main problem with sysvinit is
Adam Borowski, le lun. 15 oct. 2018 18:02:37 +0200, a ecrit:
> On Mon, Oct 15, 2018 at 04:18:57PM +0200, Thorsten Glaser wrote:
> > Matthew Vernon wrote:
> > >interest/effort in getting sysvinit (and related bits) in a better state
> > >for buster, do drop me a line.
> >
> > I’ve volunteered to
On Mon, 15 Oct 2018, Petter Reinholdtsen wrote:
> Note, I can with authority, as the person introducing dependency based
> boot and shutdown ordering in Debian, report that insserv were not
> introduced for parallell boot, nor for boot speed. It was introduced to
> correct broken boot and
[Thorsten Glaser]
> Hmm. This does not answer the question, while it does point out one
> package. I’d rather sysvinit not depend on insserv, it used to work
> fine without that kind of added complexity, and AIUI, it was only
> used for parallel boots
Note, I can with authority, as the person
Martin Steigerwald - 15.10.18, 17:56:
> Anyway, I will make Devuan people aware of this discussion. Let's see
> whether someone likes to cooperate.
As Evilham also pointed out, Devuan people are aware of this discussion
already:
[devuan-dev] sysvinit in debian is under threat of being dropped
Svante Signell, le lun. 15 oct. 2018 17:49:23 +0200, a ecrit:
> On Mon, 2018-10-15 at 17:06 +0200, Samuel Thibault wrote:
> > It's a matter of people subscribing to the
> > pkg-sysvinit-de...@lists.alioth.debian.org list and discussing there,
> > I
> > don't see why anything heavier would be
On Mon, Oct 15, 2018 at 04:18:57PM +0200, Thorsten Glaser wrote:
> Matthew Vernon wrote:
>
> >I'm aware of some work ongoing at the moment to try and improve matters
> >(currently looking at elongind, for example). If anyone's got some
>
> What’s elongind? elogind? Never heard of it…
elogind is
Ansgar Burchardt - 15.10.18, 16:03:
> On Mon, 2018-10-15 at 14:20 +0100, Jonathan Dowland wrote:
> > On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote:
> > > I believe Andreas Henriksson is right, the packages are going to
> > > be
> > > removed unless someone with time and
On Mon, 2018-10-15 at 17:06 +0200, Samuel Thibault wrote:
>
> It's a matter of people subscribing to the
> pkg-sysvinit-de...@lists.alioth.debian.org list and discussing there,
> I
> don't see why anything heavier would be needed.
I thought alioth was no more, but maybe the mailing list remains?
Evilham, le lun. 15 oct. 2018 16:27:25 +0200, a ecrit:
> Where to now?
> At devuan-dev, Adam Sampson has suggested that the debian-bsd and
> debian-hurd communities are also very interested in keeping non-systemd
> things working,
Yes, but they aren't populated so much either, with already a lot
Dear debian-devel,
Am 15/10/2018 um 15:20 schrieb Jonathan Dowland:
> [ re-adding TG who requested CCs in an earlier message, but has not
> set Mail-Followup-To:. You've probably missed half the conversation,
> Thorsten… ]
>
> On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote:
On Mon, 15 Oct 2018, Jonathan Dowland wrote:
> [ re-adding TG who requested CCs in an earlier message, but has not
> set Mail-Followup-To:. You've probably missed half the conversation,
> Thorsten… ]
Thanks… will follow up on those I read up on in the web interface
(why is there no NNTP
On Mon, 2018-10-15 at 14:20 +0100, Jonathan Dowland wrote:
> On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote:
> > I believe Andreas Henriksson is right, the packages are going to be
> > removed unless someone with time and interest show up to take care of
> > them. A good
On Mon, Oct 15, 2018 at 02:20:03PM +0100, Jonathan Dowland wrote:
> Is it worth interested parties reaching out to the Devuan project
> regarding person-power for sysvinit maintenance?
It's hard to discuss this with a straight face, but in any case even they
admit they don't have any
[ re-adding TG who requested CCs in an earlier message, but has not
set Mail-Followup-To:. You've probably missed half the conversation,
Thorsten… ]
On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote:
I believe Andreas Henriksson is right, the packages are going to be
removed
Holger Levsen writes:
> On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote:
>> > Has policy changed regarding support for multiple inits, or is it just that
>> > no one is maintaining the shim and sysvinit-core?
>>
>> The latter. systemd-shim has been orphaned for over 2 years, and
On Mon, Oct 15, 2018 at 08:46:31AM +0200, Laurent Bigonville wrote:
> Thorsten Glaser wrote:
>
> > On Sun, 14 Oct 2018, Andreas Henriksson wrote:
> >
> > > Please note that sysvinit dependencies still have open RC bugs which
> > > noone is caring for.
> >
> > Oof. How do I find them out? The
1 - 100 of 108 matches
Mail list logo
