An anonymous reader writes: Philip Newborough, the developer behind CrunchBang Linux, has put an end to work on the distro. CrunchBang was built as a layer on top of Debian using the Openbox window manager that focused on performance and customization. Newborough says the changing landscape of Linux over the past decade has obviated the need for a distro like CrunchBang. "Whilst some things have stayed exactly the same, others have changed beyond all recognition. It's called progress, and for the most part, progress is a good thing. That said, when progress happens, some things get left behind, and for me, CrunchBang is something that I need to leave behind. I'm leaving it behind because I honestly believe that it no longer holds any value, and whilst I could hold on to it for sentimental reasons, I don't believe that would be in the best interest of its users, who would benefit from using vanilla Debian."

jones_supa writes A lot of development work is happening on systemd with just the recent couple of weeks seeing over 200 commits. With the most recent work that has landed, the networkd component has been improved with new features. Among the additions are IP forwarding and masquerading support (patch). This is the minimal support needed and these settings get turned on by default for container network interfaces. Also added was minimal firewall manipulation helpers for systemd's networkd. The firewall manipulation helpers (patch) are used for establishing NAT rules. This support in systemd is provided by libiptc, the library used for communicating with the Linux kernel's Netfilter and changing iptables firewall rulesets. Those wishing to follow systemd development on a daily basis and see what is actually happening under the hood, can keep tabs via the systemd Git viewer.

An anonymous reader writes: Anthony Ferrara, a developer advocate at Google, has published a blog post with some statistics showing the sorry state of affairs for website security involving PHP. After defining a list of secure and supported versions of PHP, he used data from W3Techs to find a rough comparison between the number of secure installs and the number of insecure or outdated installs. After doing some analysis, Ferrara sets the upper bound on secure installs at 21.71%. He adds, "These numbers are optimistic. That's because we're counting all version numbers that are maintained by a distribution as secure, even though not all installs of that version number are going to be from a distribution. Just because 5.3.3 is maintained by CentOS and Debian doesn't mean that every install of 5.3.3 is maintained. There will be a small percentage of installs that are from-source. Therefore, the real 'secure' number is going to be less than quoted." Ferrara was inspired to dig into the real world stats after another recent discussion of responsible developer practices.

zdzichu writes: The group of anonymous Italians behind the recent Debian fork have published their first progress report. It covers a wide range of topics: the 4.5k€ of donations received so far, moving distro infrastructure from GitHub to GitLab, progress on LoginKit (which replaces systemd's logind), fraud accusations, logo discussions, and few more important points.

jaromil writes: The so called "Veteran Unix Admin" collective has announced that the fork of Debian will proceed as a result of the recent systemd controversy. The reasons put forward are not just technical; included is a letter of endorsement by Debian Developer Roger Leigh mentioning that "people rely on Debian for their jobs and businesses, their research and their hobbies. It's not a playground for such radical experimentation." The fork is called "Devuan," pronounced "DevOne." The official website has more information.

paskie writes: Voting on a Debian General Resolution that would require packagers to maintain support even for systems not running systemd ended tonight with the resolution failing to gather enough support.

This means that some Debian packages could require users to run systemd on their systems in theory — however, in practice Debian still works fine without systemd (even with e.g. GNOME) and this will certainly stay the case at least for the next stable release Jessie.

However, the controversial general resolution proposed late in the development cycle opened many wounds in the community, prompting some prominent developers to resign or leave altogether, stirring strong emotions — not due to adoption of systemd per se, but because of the emotional burn-out and shortcomings in the decision processes apparent in the wake of the systemd controversy.

Nevertheless, work on the next stable release is well underway and some developers are already trying to mend the community and soothe the wounds.

An anonymous reader writes Debian developer Tollef Fog Heen submitted his resignation to the Debian Systemd package maintainers team mailing list today (Sun. Nov. 16th, 2014). In his brief post, he praises the team, but claims that he cannot continue to contribute due to the "load of continued attacks...becoming just too much." Presumably, he is referring to the heated and, at times, even vitriolic criticism of Debian's adoption of Systemd as the default init system for its upcoming Jessie release from commenters inside and outside of the Debian community. Currently, it is not known if Tollef will cease contributing to Debian altogether. A message from his twitter feed indicates that he may blog about his departure in the near future.

An anonymous reader writes: Long-time Debian developer Joey Hess has posted a resignation letter to the Debian mailing list. Hess was a big part of the development of the Debian installer, debhelper, Alien, and other systems. He says, "It's become abundantly clear that this is no longer the project I originally joined in 1996. We've made some good things, and I wish everyone well, but I'm out. ... If I have one regret from my 18 years in Debian, it's that when the Debian constitution was originally proposed, despite seeing it as dubious, I neglected to speak out against it. It's clear to me now that it's a toxic document, that has slowly but surely led Debian in very unhealthy directions."

jones_supa writes Kubuntu Vivid is the development name for what will be released in April next year as Kubuntu 15.04. The exciting news is that following some discussion and some wavering, the Kubuntu team will be switching to Plasma 5 by default. They claim that it has shown itself as a solid and reliable platform and it's time to show it off to the world. There are some bits which are missing from Plasma 5 which are planned to be filled in over the next six months. As another technical detail, Debian git is now used to store the packaging in a Kubuntu branch, so hopefully it will be easier to share updates.

A friend of mine who buys and sells used books, movies, etc. recently purchased a box full of software on CD, including quite a few old Linux distributions, and asked me if I'd like them. The truth is, I would like them, but I've already collected over the last two decades more than I should in the way of Linux distributions, on at least four kinds of media (starting with floppies made from a CD that accompanied a fat book on how to install some distribution or other -- very useful in the days of dialup). I've got some boxes (Debian Potato, and a few versions of Red Hat and Mandrake Linux), and an assortment of marketing knickknacks, T-shirts, posters, and books. I like these physical artifacts, and they're not dominating my life, but I'd prefer to actually give many of them to someplace where they'll be curated. (Or, if they should be tossed, tossed intelligently.) Can anyone point to a public collection of some kind that gathers physical objects associated with Free software and Open Source, and makes them available for others to examine? (I plan to give some hardware, like a pair of OLPC XO laptops, to the same Goodwill computer museum highlighted in this video, but they probably don't want an IBM-branded radio in the shape of a penguin.)

walterbyrd (182728) sends this article about systemd from Paul Venezia, who writes: In discussions around the Web in the past few months, I've seen an overwhelming level of support of systemd from Linux users who run Linux on their laptops and maybe a VPS or home server. I've also seen a large backlash against systemd from Linux system administrators who are responsible for dozens, hundreds, or thousands of Linux servers, physical and virtual. ... The release of RHEL 7 has brought the reality of systemd to a significant number of admins whose mantra is stability over all else and who perhaps had not waded into the choppier waters of Fedora or Debian unstable to work with systemd before it arrived in RHEL.

New submitter Tsolias writes It appears that systemd is still a hot topic in the Debian community. As seen earlier today, there is a new movement shaping up against the adoption of systemd for the upcoming stable release [of Debian], Jessie. They claim that "systemd betrays the UNIX philosophy"; it makes things more complex, thus breaking the "do one thing and do it well" principle. Note that the linked Debian Fork page specifically says that the anonymous developers behind it support a proposal to preserve options in init systems, rather than demanding the removal of systemd, and are not opposed to change per se. They just don't want other parts of the system to be wholly dependent on systemd. "We contemplate adopting more recent alternatives to sysvinit, but not those undermining the basic design principles of "do one thing and do it well" with a complex collection of dozens of tightly coupled binaries and opaque logs."

Scott James Remnant, now Technical Lead on ChromeOS, was a Debian developer before that. That's how he became involved from the beginning (becoming Developer Manager, and then serving on the Technical Board) on the little derivative distribution that Mark Shuttleworth decided to make of Debian Unstable, and for which the name Ubuntu was eventually chosen. On this date in 2004, Ubuntu 4.10 -- aka Warty Warthog, or just Warty -- was released, and Remnant has shared a detailed, nostalgic look back at the early days of the project that has (whatever else you think of it ) become one of the most influential in the world of open source and Free software. I was excited that Canonical sent out disks that I could pass around to friends and family that looked acceptably polished to them in a way that Sharpie-marked Knoppix CD-ROMs didn't, and that the polish extended to the installer, the desktop, and the included constellation of software, too.

New submitter cgdae writes Does anyone know how to stop PulseAudio/Pavucontrol from changing sound settings whenever there is a hardware change such as headphones being plugged in/out or docking/undocking my laptop ? I recently had to install PulseAudio on my Debian system because the Linux version of Skype started to require it. Ever since, whenever i dock/undock or use/stop using headphones, all sound disappears, and i have to go to Pavucontrol and make random changes to its 'Output Devices' or 'Speakers' or 'Headphones' tab, or mute/unmute things, or drag a volume slider which has inexplicably moved to nearly zero, until sound magically comes back again. I've tried creating empty PulseAudio config files in my home directory, and/or disabling the loading of various PulseAudio modules in /etc/pulse/*.conf, but i cannot stop PulseAudio from messing things up whenever there's a hardware change. It's really frustrating that something like PulseAudio doesn't have an easy-to-find way of preventing it from trying (and failing) to be clever.

[In case it's relevant, my system is a Lenovo X220 laptop, with Debian jessie, kernel 3.14-2-amd64. I run fvwm with an ancient config.]

An anonymous reader writes: A couple of months ago the technical committee for Debian decided in favor of systemd. This is now a subject for discussion once again, and Ian Jackson says he wants a general resolution, so every developer within the Debian project can decide. After a short time, the required amount of supporters was reached, and the discussion can start once again.

An anonymous reader writes With 23% of the year remaining, Linux Voice has donned flameproof clothing to subjectively examine what it feels have been the best distros of the year so far, including choices for beginners, desktop fashionistas and performance fetishists, before revealing a surprising overall winner.

Mcusanelli writes: GNOME 3, the open source desktop environment for Linux systems that once earned a lot of ire, is receiving newfound praise for the maturity of GNOME Shell and other improvements. The recent release of version 3.14 capped off a series of updates that have gone a long way toward resolving users' problems and addressing complaints. One of the big pieces was the addition of "Classic mode" in 3.8, which got it into RHEL 7, and Debian is switching back as well.

kdryer39 sends this news from CSO: A remotely exploitable vulnerability has been discovered by Stephane Chazelas in bash on Linux, and it is unpleasant. The vulnerability has the CVE identifier CVE-2014-6271. This affects Debian as well as other Linux distributions. The major attack vectors that have been identified in this case are HTTP requests and CGI scripts. Another attack surface is OpenSSH through the use of AcceptEnv variables. Also through TERM and SSH_ORIGINAL_COMMAND. An environmental variable with an arbitrary name can carry a nefarious function which can enable network exploitation.

An anonymous reader writes: Debian will switch back to using GNOME as the default desktop environment for the upcoming Debian 8.0 Jessie release, due out in 2015. The decision is based on accessibility and systemd integration, along with a host of other reasons. Debian switched away from GNOME back in 2012 .

snydeq writes Desktop workloads and server workloads have different needs, and it's high time Linux consider a split to more adequately address them, writes Deep End's Paul Venezia. You can take a Linux installation of nearly any distribution and turn it into a server, then back into a workstation by installing and uninstalling various packages. The OS core remains the same, and the stability and performance will be roughly the same, assuming you tune they system along the way. Those two workloads are very different, however, and as computing power continues to increase, the workloads are diverging even more. Maybe it's time Linux is split in two. I suggested this possibility last week when discussing systemd (or that FreeBSD could see higher server adoption), but it's more than systemd coming into play here. It's from the bootloader all the way up. The more we see Linux distributions trying to offer chimera-like operating systems that can be a server or a desktop at a whim, the more we tend to see the dilution of both. You can run stock Debian Jessie on your laptop or on a 64-way server. Does it not make sense to concentrate all efforts on one or the other?"