Hi, Jerry Stuckle <stuckleje...@gmail.com> writes: > The problem here is lack of time and/or skills. I would love to help, > but I already have my plate full. Additionally, I've done device > drivers and applications, but never dealt with init systems. There > would be a big learning curve. And then there is the politics of being > accepted by the DD community. Maybe some people don't think it's too > bad - but I get enough politics in real life that I don't want to deal > with it in a volunteer position.
If you do not have time/skill/motivation to deal with it yourself, there is also the option of hiring someone to do the work for you. See [1] for a list of people offering services for Debian to start with. [1] <https://www.debian.org/consultants/> > So why, instead of spending all this time on a new init system didn't > developers already familiar with sysvinit work on it? Systemd wasn't > one person alone. Presumably nobody was interested enough to do so. >> 1. Reviving the existing init systems. Modernizing them, making them >> into true, interchangeable drop-in replacements of each other, which do >> the task assigned, and do it well. Each of them accomplishing at least >> the common subset of tasks an init system is supposed to provide. > > That would be great, but it's not going to happen. The TC has already > indicated systemd is going to be the default, and packages are already > beginning to require systemd. I predict more and more packages will > require systemd as time goes on. It's not going to happen, because... > This would also be great. However, who's going to spend the time > building these replacements? Maintaining/upgrading sysvinit is minor > compared to this job, and even that couldn't be done. ... nobody wants to work on it (at least not for free). Ansgar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zjbrkvtm....@deep-thought.43-1.org
