Tuesday, May 12th, 2015

Time	Event
1:06p	The Foresight Linux Project shuts down The development of the Foresight Linux distribution has come to an end. "The Foresight Linux Council has determined that there has been insufficient volunteer activity to sustain meaningful new development of Foresight Linux. Faced with the need either to update the project's physical infrastructure or cease operations, we find no compelling reason to update the infrastructure." (Comment on this)
4:28p	Tuesday's security updates Debian has updated mercurial (two vulnerabilities). Mageia has updated async-http-client (two vulnerabilities), glpi (privilege escalation), kernel (multiple vulnerabilities), libarchive (denial of service), libssh (denial of service), mailman (path traversal attack), pnp4nagios (cross-site scripting), postgis (multiple vulnerabilities), ruby-redcarpet (cross-site scripting), and springframework (information disclosure). openSUSE has updated Chromium (13.2, 13.1: two vulnerabilities), curl (13.2, 13.1: information leak), dnsmasq (13.2, 13.1: information disclosure), gnu_parallel (13.2, 13.1: file overwrite), libreoffice (13.2: code execution), libssh (13.2, 13.1: denial of service), libtasn1 (13.2, 13.1: denial of service), pcre (13.2, 13.1: multiple vulnerabilities), and php5 (13.2, 13.1: multiple vulnerabilities). Slackware has updated mariadb (multiple unspecified vulnerabilities), mysql (multiple unspecified vulnerabilities), and wpa_supplicant (code execution). Ubuntu has updated libmodule-signature-perl (15.04, 14.10, 14.04, 12.04: multiple vulnerabilities) and openssl (12.04: re-enable TLSv1.2 by default). (Comment on this)
7:00p	Firefox 38.0 Mozilla has released Firefox 38.0. This version features new tab-based preferences and Ruby annotation support. Also, it will be the base for the next ESR release. The release notes contain more information. (Comment on this)
8:04p	[$] Trading off safety and performance in the kernel The kernel community ordinarily tries to avoid letting users get into a position where the integrity of their data might be compromised. There are exceptions, though; consider, for example, the ability to explicitly flush important data to disk (or more importantly, to avoid flushing at any given time). Buffering I/O in this manner can significantly improve disk write I/O throughput, but if application developers are careless, the result can be data loss should the system go down at an inopportune time. Recently there have been a couple of proposed performance-oriented changes that have tested the community's willingness to let users put themselves into danger. Click below (subscribers only) for the full story from this week's Kernel Page. (Comment on this)

<< Previous Day

2015/05/12 [Calendar]

Next Day >>