Slashdot Mirror

An anonymous reader quotes The Register: Late last month, open-source contributor Raymond Nicholson proposed a change to the manual for glibc, the GNU implementation of the C programming language's standard library, to remove "the abortion joke," which accompanied the explanation of libc's abort() function... The joke, which has been around since the 1990s and is referred to as a censorship joke by those supporting its inclusion, reads as follows:

25.7.4 Aborting a Program... Future Change Warning: Proposed Federal censorship regulations may prohibit us from giving you information about the possibility of calling this function. We would be required to say that this is not an acceptable way of terminating a program.

On April 30, the proposed change was made, removing the passage from the documentation. That didn't sit well with a number of people involved in the glibc project, including the joke's author, none other than Free Software Foundation president and firebrand Richard Stallman, who argued that the removal of the joke qualified as censorship... Carlos O'Donnell, a senior software engineer at Red Hat, recommended avoiding jokes altogether, a position supported by many of those weighing in on the issue. Among those voicing opinions, a majority appears to favor removal.
But in a post to the project mailing list, Stallman wrote "Please do not remove it. GNU is not a purely technical project, so the fact that this is not strictly and grimly technical is not a reason to remove this." He added later that "I exercise my authority over glibc very rarely -- and when I have done so, I have talked with the official maintainers. So rarely that some of you thought that you are entirely autonomous. But that is not the case. On this particular question, I made a decision long ago and stated it where all of you could see it."

The Register reports that "On Monday, the joke was restored by project contributor Alexandre Oliva, having taken Stallman's demand as approval to do so."

NotInHere (3654617) writes with news that Google's Project Zero has been busy at work. A month ago they reported an off-by-one error in glibc that would overwrite a word on the heap with NUL and were met with skepticism at its ability to be used in an attack. Google's 'Project Zero' devised an exploit of the out-of-bounds NUL write in glibc to gain root access using the setuid binary pkexec in order to convince skeptical glibc developers. 44 days after being reported, the bug has been fixed. They even managed to defeat address space randomization on 32-bit platforms by tweaking ulimits. 64-bit systems should remain safe if they are using address space randomization.

hypnosec writes "A new version of GNU C Library (glibc) has been released and with this new version comes support for the upcoming 64-bit ARM architecture a.k.a. AArch64. Version 2.17 of glibc not only includes support for ARM, it also comes with better support for cross-compilation and testing; optimized versions of memcpy, memset, and memcmp for System z10 and zEnterprise z196; and optimized version of string functions, on top of some quite a few other performance improvements, states the mailing list release announcement. Glibc v 2.17 can be used with a minimum Linux kernel version 2.6.16."

An anonymous reader writes "The GNU C Library version 2.16 was released with many new features over the weekend. The announcement cites support for the Linux x32 ABI, ISO C11 compliance, performance improvements for math functions and some architectures, and more than 230 bug fixes."

First time accepted submitter bheading writes "Following years under controversial leadership which, among other things, led to a fork (which was in turn adopted by some of the major distributions) the glibc development process has been reinvented to follow a slightly more informal, community-based model. Here's hoping glibc benefits from a welcome dose of pragmatism."

ceswiedler writes "Aurelien Jarno has just uploaded a fork of glibc called eglibc, which is targeted at embedded systems and is source- and binary-compatible with glibc. It has a few nice improvements over glibc, but the primary motivation seems to be that it's a 'more friendly upstream project' than glibc. Glibc's maintainer, Ulrich Drepper, has had a contentious relationship with Debian's project leadership; in 2007 the Debian Project Leader sent an email criticizing Drepper for refusing to fix a bug on glibc on the ARM architecture because in Drepper's words it was 'for the sole benefit of this embedded crap.'"

Abhikhurana writes "I work for a company which designs a variety of video surveillance devices (such as MPEG4 video servers). Traditionally, these products have been based on proprietary OSs such as Nucleus and VxWorks. Now, we are redesigning a few of our products and I am trying to convince my company to go down the Linux route. Understandably, our management is quite skeptical about that and so I was asked by our CTO to recommend a few RTOSs which have mature networking stacks and which work well on ARM platform. I know that there are many embedded Linux based distributions out there. There are commercial ones such as Montavista, LynuxWorks, free ones such as uclinux, muLinux and some Linux like distros such as Ecos. What is the most stable and best community supported embedded Linux distribution out there?"

nerdyH points to this smile-inducing story at LinuxDevices which begins "An inexpensive house-brand 802.11b/g wireless router from Fry's (Outpost.com) has been adopted by a group of Linux hackers that aims to make Fry's 'AirLink' devices 'as capable as name-brand gadgets.' The AirLink101 AR315W is based on a Marvell board that can run Linux or eCos, and has a six-port 10/100 Ethernet switch built in. It's listed for $45 online, but is reportedly on sale for $20 in some Fry's stores."

Jonathan Larmour points out the "release of eCos 2.0, the configurable RTOS for the deeply embedded market. This release features a new licence based on the GPL, but with an exception to make it more suitable for embedded use. It's also now an independent free software project from the original developers Red Hat (which bought Cygnus Solutions) after the development team was canned. Most of the team still work on eCos but for different companies. It also has a wide range of ports but has managed to keep a low profile, which should now change with the new stable release. More at http://ecos.sourceware.org/ "

Jonathan Larmour points out the "release of eCos 2.0, the configurable RTOS for the deeply embedded market. This release features a new licence based on the GPL, but with an exception to make it more suitable for embedded use. It's also now an independent free software project from the original developers Red Hat (which bought Cygnus Solutions) after the development team was canned. Most of the team still work on eCos but for different companies. It also has a wide range of ports but has managed to keep a low profile, which should now change with the new stable release. More at http://ecos.sourceware.org/ "

Jonathan Larmour points out the "release of eCos 2.0, the configurable RTOS for the deeply embedded market. This release features a new licence based on the GPL, but with an exception to make it more suitable for embedded use. It's also now an independent free software project from the original developers Red Hat (which bought Cygnus Solutions) after the development team was canned. Most of the team still work on eCos but for different companies. It also has a wide range of ports but has managed to keep a low profile, which should now change with the new stable release. More at http://ecos.sourceware.org/ "

Jonathan Larmour points out the "release of eCos 2.0, the configurable RTOS for the deeply embedded market. This release features a new licence based on the GPL, but with an exception to make it more suitable for embedded use. It's also now an independent free software project from the original developers Red Hat (which bought Cygnus Solutions) after the development team was canned. Most of the team still work on eCos but for different companies. It also has a wide range of ports but has managed to keep a low profile, which should now change with the new stable release. More at http://ecos.sourceware.org/ "