Dear maintainers of sysvinit,
We are currently using sysvinit in a development version of Dragora
GNU/Linux-Libre[1][2]. I am wondering if it is possible to publish a new
version of sysvinit including all the patches and bug-fixes at the date.
This is why I am writing this email:
http://lists.non
[Matias A. Fonzo]
> Dear maintainers of sysvinit,
>
> We are currently using sysvinit in a development version of Dragora
> GNU/Linux-Libre[1][2]. I am wondering if it is possible to publish a
> new version of sysvinit including all the patches and bug-fixes at
> the date.
The problem was that I
[Richard Tollerton]
> The fix is obvious enough -- rename the shutdown() function to
> something else. I also do the same for warn(), which is also exported,
> presumably because it collides with warn(3). I looked through all the
> other binaries and these appear to be the only two functions being
[Andrew Gregory]
> Even though the libcrypt detection was looking for libcrypt.a, sulogin
> was being linked against libcrypt dynamically anyway because -static was
> not used. Using libcrypt.a failed to find libcrypt on systems without
> static libs, causing compiler errors.
Right. Make sense.
I just registerered sysvinit as a project to be scanned for bugs on
https://scan.coverity.com/projects/1267 > and uploaded a build
of the current svn trunk.
If you want access to the results and help out fixing the issues,
please register and ask for project membership. I'll approve or
reject req
