libeatmydata

libeatmydata release-10

Milestone information

Project:
libeatmydata
Series:
trunk
Version:
release-10
Released:
 
Registrant:
Stewart Smith
Release registered:
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon libeatmydata-10.tar.gz (md5, sig) libeatmydata Revision 10 source tarball 46
last downloaded 17 weeks ago
Total downloads: 46

Release notes 

Version "10". now with (optional, compile time) support for only eating data if a specific file exists on the filesystem.

Changelog 

View the full changelog

------------------------------------------------------------
revno: 10 [merge]
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2009-06-26 10:35:13 +1000
message:
  merge CHECK_FILE. Allows eatmydata to only be active iff a file exists
    ------------------------------------------------------------
    revno: 9.1.1
    committer: <email address hidden>
    branch nick: libeatmydata
    timestamp: Thu 2009-06-25 18:22:00 +0200
    message:
      Support for toggling overrides at runtime through presence of a file.

      If CHECK_FILE is defined as a filename, it is checked any time *sync is
      called. If the file is not present, all calls are passed unmodified
      through to libc.

      This allows libeatmydata to be turned on systemwide in /etc/ld.so.preload
      and only activated when a specific file such as "/eatmydata" is present.
      Handy for scripting laptop-mode to avoid spinups, temporary latency
      reduction when playing music with slow SSDs, etc.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.