I probably could have done more to it, but I wanted to just finish and get the release out so I could roll an update for my personal distro with the new version of Epoch in it. Nonetheless, this release should be pretty stable and is a recommended update. It is safe to update 1.0 and 1.1 releases to 1.2.0 without rebooting. Replace the 'epoch' binary with the new version and then run 'epoch reexec'. Check /var/log/system.log and it should tell you that you've been updated to 1.2.0. NOTE: if you do NOT run 'epoch reexec' after replacing the binary, your root filesystem will not be able to be remounted read-only on system shutdown and that could lead to data loss. There is no good reason I can think of that you would not want to run 'epoch reexec'.
Here is a list of changes:
Changes since 1.1.1:
* Cleaned up a huge amount of code that was just fugly as hell. This is the big change. * Removed unsigned long abuse caused by my (at the time) severe OCD. * New service status output format. Looks cleaner. * Extremely deprecated AlignStatusReports attribute completely removed. I doubt even one person will be affected by this. * Add three new attributes: StartingStatusFormat, FinishedStatusFormat, and StatusNames to manually specify an alternate service status output format.
* Specific bugfixes:
* Don't set a config problem check to WARNING after we already found a FAILURE.
* Fix overwriting service messages, caused by our old status format.
* Fix inaccurate reporting of scheduled shutdown times, now report seconds too.
Epoch Init System 1.2.0 released.
So, I've pushed out the final version of the Epoch Init System 1.2.0 "Peroxide". It's mostly a bugfix release and cleans up most of the nasty code in Epoch. Here's the tarball: http://universe2.us/epoch_1.2.0.tar.gz
I probably could have done more to it, but I wanted to just finish and get the release out so I could roll an update for my personal distro with the new version of Epoch in it. Nonetheless, this release should be pretty stable and is a recommended update. It is safe to update 1.0 and 1.1 releases to 1.2.0 without rebooting. Replace the 'epoch' binary with the new version and then run 'epoch reexec'. Check /var/log/system.log and it should tell you that you've been updated to 1.2.0. NOTE: if you do NOT run 'epoch reexec' after replacing the binary, your root filesystem will not be able to be remounted read-only on system shutdown and that could lead to data loss.
There is no good reason I can think of that you would not want to run 'epoch reexec'.
Here is a list of changes:
Changes since 1.1.1:
* Cleaned up a huge amount of code that was just fugly as hell. This is the big change.
* Removed unsigned long abuse caused by my (at the time) severe OCD.
* New service status output format. Looks cleaner.
* Extremely deprecated AlignStatusReports attribute completely removed. I doubt even one person will be affected by this.
* Add three new attributes: StartingStatusFormat, FinishedStatusFormat, and
StatusNames to manually specify an alternate service status output format.
* Specific bugfixes:
* Don't set a config problem check to WARNING after we already found a FAILURE.
* Fix overwriting service messages, caused by our old status format.
* Fix inaccurate reporting of scheduled shutdown times, now report seconds too.
Post Comment