[Top][All Lists]

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

Re: [sysvinit-devel] Testing a new beta

From: Matias Fonzo
Subject: Re: [sysvinit-devel] Testing a new beta
Date: Mon, 28 May 2018 15:58:55 -0300

Cool.  Another version of sysvinit, We can test it on Dragora -devel.

I suggest to change the -fstack-protector option to
-fstack-protector-strong by default, which provides a good balance
between security, performance.  Also, do not forget to distribute an
alternative format, for us.. the people who tries to avoid .xz.  :-)

(If you don't like lzip, it could be in .tar.bz2, alongside
the .tar.xz).


On Mon, 28 May 2018 12:34:30 -0300
Jesse Smith <address@hidden> wrote:

> Hi all. I am testing a new beta snapshot of SysV init. This one
> carries the version label 2.90-beta and can be downloaded from the
> usual location [1].
> This beta mostly focuses on minor code clean-up. A few little issues
> were cleaned up and issues with newer compilers (like GCC 7) were
> fixed.
> The shutdown process now recognizes when the computer has been put to
> sleep after shutdown was run. Assuming the system clock is accurate,
> we now shutdown when originally asked to instead of at the original
> time + time spent in suspend mode.
> The /run/initctl interface was documented and now has its own man
> page.
> Upon receiving SIGUSR2, init will close all of its files, including
> its control pipe. The pipe can be reopened with SIGUSR1.
> There have been minor updates to #include directives to handle changes
> in the way some defines are packaged, and a few updates to the
> Makefile to make building/distributing sysvinit easier.
> Fixed a nasty bug where building sysvinit on Fedora would appear to
> work, but without properly linking to crypt() causing either a crash
> or undefined behaviour.
> Those are the highlights and the rest can be found in the tarball's
> doc/Changelog file.
> These changes have been tested on amd64 and ARM. And I'm hoping this
> beta will attract more testers to confirm everything is working
> properly.
> 1.

reply via email to

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