[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sysvinit-devel] Make a new sysvinit upstream release?

From: Michał Kulling
Subject: Re: [sysvinit-devel] Make a new sysvinit upstream release?
Date: Sat, 08 Feb 2014 20:22:01 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

W dniu 08.02.2014 19:04, Petter Reinholdtsen pisze:
[Michał Kulling]
Hi everyone,

i'm watching sysvinit mailing list from several weeks, and I thing
it's good time to move sysvinit source to
I would love to move from svn to git, but want to keep it on savannah.
Do you have time to handle the svn->git migration?
Now I migrate my company repo from SVN to GIT, and we decise migrate only source code without history. So, migrating source code, i think, to github not need a lot of time.

But I believe we should release what we got from svn this time, and
try to get the next release done using git.  I do not want to delay
this release because such migration.

SVN is too old source versioning software, many people and projects
move from svn to git. Basically, github include wiki pages and issue
Savannah also provide wiki and issue tracker. :)

Now I'm working for some additional functionalities for sysvinit,
which exteneding service management (start-stop-deamon sux?).
What exactly are you planning, and why?

I'm planning replace start-stop-daemon to more functional process. Starting services with new, named new-start-stop-daemon, extend functionality to registering, monitoring and user friendly services management.

Now basic SysV init don't provide any service management interface - debian have update.rc scripts, rhel chkconfig/ntsysv. We can add our interface with much more functionality.

I'll present my vision in next dwo weeks with working code.

Perhaps you also could help fix all the issues discovered by Coverity?

Sure, i can try.

Where i can find a report?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]