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:
>
> http://savannah.nongnu.org/proje
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,
p
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
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.
KatolaZ, Ian feel free to drop Cc's again, I won't be offended :)
Alessio Treglia - 16.10.18, 07:31:
> On Mon, Oct 15, 2018
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 p
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
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 o
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
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.
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, since we will keep
> maintai
Hi,
I mentioned this on debian-devel already in the thread about Buster
maybe losing sysvinit support, but I thought it was worth flagging to
the HURD/BSD lists since it seems relevant to your interests :-)
There's a couple of posts in the archive of where the elogind for buster
work is:
http://
Hello,
Matthew Vernon, le mar. 16 oct. 2018 14:10:23 +0100, a ecrit:
> I mentioned this on debian-devel already in the thread about Buster
> maybe losing sysvinit support, but I thought it was worth flagging to
> the HURD/BSD lists since it seems relevant to your interests :-)
FYI, I have bounced
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 next to the systemd u
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 required to ship an
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 current state of init
>>> diversity is supposed to be? Is it assum
[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 sy
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 anyway,
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 arches
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.
>
>
[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
> scripts.
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
>
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 sysvini
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. Th
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 p
24 matches
Mail list logo
