Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

New submitter Alessandro Zarrilli writes: Linux has been able do multipath routing for a long time: it means being able to have routes with multiple gateways and to use them in a (weighted) round-robin fashion. But Linux is missing a tool to actively monitor the state of internet uplinks and change the routing accordingly. Without it, from a LAN perspective, it's like having a RAID-0: just one uplink goes down and all of your LAN-to-WAN traffic goes down too. Documentation and examples on the subject are lacking; existing solutions are few and deeply integrated in firewall/routing specific distributions. To address these issues, a new standalone tool was just released: Fault Tolerant Router. It also includes a complete (iptables + ip policy routing) configuration generator.

jones_supa writes NVIDIA has fixed a long-standing issue in the Ubuntu Unity desktop by patching Compiz. When opening the window of a new application, it would go black or become transparent on NVIDIA hardware. There have been bug reports dating back to Ubuntu 12.10 times. The problem was caused by Compiz, which had some leftover code from a port. An NVIDIA developer posted on Launchpad and said the NVIDIA team has been looking at this issue, and they also proposed a patch. "Our interpretation of the specification is that creating two GLX pixmaps pointing at the same drawable is not allowed, because it can lead to poorly defined behavior if the properties of both GLX drawables don't match. Our driver prevents this, but Compiz appears to try to do this," wrote NVIDIA's Arthur Huillet. The Compiz patch has been accepted upstream.

An anonymous reader writes: It's been over a year since Valve announced its Linux-based SteamOS, the biggest push yet from a huge company to bring mainstream gaming to Linux. In this article, Ars Technica takes a look at how their efforts are panning out. Game developers say making Linux ports has gotten dramatically easier: "There are great games shipping for Linux from development teams with no Linux expertise. They hit the 'export to Linux' button in the Unity editor and shipped it and it worked out alright. We didn't get flying cars, but the future is turning out OK so far."

Hardware drivers are still a problem, getting in the way of potential performance gains due to Linux's overall smaller resource footprint than Windows. And while the platform is growing, it's doing so slowly. Major publishers are still hesitant to devote time to Linux, and Valve is taking their time building for it. Their Steam Machine hardware is still in development, and some of their key features are being adopted by other gaming giants, like Microsoft. Still, Valve is sticking with it, and that's huge. It gives developers faith that they can work on supporting Linux without fear that the industry will re-fragment before their game is done.

An anonymous reader writes Following polling on Linus Torvald's Google+ page, he's decided to make the next kernel version Linux 4.0 rather than Linux 3.20. Linux 4.0 is going to bring many big improvements besides the version bump with there being live kernel patching, pNFS block server support, VirtIO 1.0, IBM z13 mainframe support, new ARM SoC support, and many new hardware drivers and general improvements. Linux 4.0 is codenamed "Hurr durr I'ma sheep."

m.alessandrini writes Children grow up, and inevitably they will start using internet and social networks, both for educational and recreational purposes. And it won't take long to them to learn to be autonomous, especially with all the smartphones and tablets around and your limited time. Unlike the years of my youth, when internet started to enter our lives gradually, now I'm afraid of the amount of inappropriate contents a child can be exposed to unprepared: porn, scammers, cyberbullies or worse, are just a click away.

For Windows many solutions claim to exist, usually in form of massive antivirus suites. What about GNU/Linux? Or Android? Several solutions rely on setting up a proxy with a whitelist of sites, or similar, but I'm afraid this approach can make internet unusable, or otherwise be easy to bypass. Have you any experiences or suggestions? Do you think software solutions are only a part of the solution, provided children can learn hacking tricks better than us, and if so, what other 'human' techniques are most effective?

jones_supa writes The record amount of security challenges in 2014 undermined the confidence many had in high quality of open source software. Jim Zemlin, executive director of the Linux Foundation, addressed the issue head-on during last week's Linux Collaboration Summit. Zemlin quoted the oft-repeated Linus' law, which states that given enough eyes, all bugs are shallow. "In these cases the eyeballs weren't really looking", Zemlin said. "Modern software security is hard because modern software is very complex," he continued. Such complexity requires dedicated engineers, and thus the solution is to fund projects that need help. To date, the foundation's Core Infrastructure Initiative has helped out the NTP, OpenSSL and GnuPG projects, with more likely to come. The second key initiative is the Core Infrastructure Census, which aims to find the next Heartbleed before it occurs. The census is looking to find underfunded projects and those that may not have enough eyeballs looking at the code today."

alphadogg writes Now more than ever, the development of the Linux kernel is a matter for the professionals, as unpaid volunteer contributions to the project reached their lowest recorded levels in the latest "Who Writes Linux" report, which was released today. According to the report, which is compiled by the Linux Foundation, just 11.8% of kernel development last year was done by unpaid volunteers – a 19% downturn from the 2012 figure of 14.6%. The foundation says that the downward trend in volunteer contributions has been present for years. According to Linus Torvalds, the shift towards paid developers hasn’t changed much about kernel development on its own. “I think one reason it hasn't changed things all that much is that it's not so much unpaid volunteers are going away as people who start writing kernel code get hired really quickly,” he said.

Artem Tashkinov writes: Luke Wolf, a KDE developer, argues that PC-BSD might become a serious desktop OS contender by year 2020, since Linux so far has failed to grasp any serious market share. He writes, "Consider this: In the past 10 years has the distribution you run changed significantly in what it offers over other distributions? I think you'll find the answer is largely no. I do have to give a shout out to openSUSE for the OBS, but otherwise I've used my desktop in the same exact way that I have always used it within the continuity of distribution X,Y, or Z since I started using them. Distributions simply aren't focused on desktop features, they're leaving it up to the DEs to do so." He continues, "PC-BSD on the other hand in fitting with the BSD mindset of holistic solutions is focused on developing desktop features and is moving rapidly to implement them." What do you think?

lkcl writes The introduction of systemd has unilaterally created a polarization of the GNU/Linux community that is remarkably similar to the monopolistic power position wielded by Microsoft in the late 1990s. Choices were stark: use Windows (with SMB/CIFS Services), or use UNIX (with NFS and NIS). Only the introduction of fully-compatible reverse-engineered NT Domains services corrected the situation. Instructions on how to remove systemd include dire warnings that "all dependent packages will be removed", rendering a normal Debian Desktop system flat-out impossible to achieve. It was therefore necessary to demonstrate that it is actually possible to run a Debian Desktop GUI system (albeit an unusual one: fvwm) with libsystemd0 removed. The reason for doing so: it doesn't matter how good systemd is believed to be or in fact actually is: the reason for removing it is, apart from the alarm at how extensive systemd is becoming (including interfering with firewall rules), it's the way that it's been introduced in a blatantly cavalier fashion as a polarized all-or-nothing option, forcing people to consider abandoning the GNU/Linux of their choice and to seriously consider using FreeBSD or any other distro that properly respects the Software Freedom principle of the right to choose what software to run. We aren't all "good at coding", or paid to work on Software Libre: that means that those people who are need to be much more responsible, and to start — finally — to listentowhatpeoplearesaying. Developing a thick skin is a good way to abdicate responsibility and, as a result, place people into untenable positions.

jones_supa writes: The 1.7.0 release of Wayland is now available for download. The project thanks all who have contributed, and especially the desktop environments and client applications that now converse using Wayland. In an official announcement from Bryce Harrington of Samsung, he says the Wayland protocol may be considered 'done' but that doesn't mean there's not work to be done. A bigger importance is now given to testing, documentation, and bugfixing. As Wayland is maturing, we are also getting closer to the point where the big Linux distros will eventually start integrating it to their operating system.

jones_supa writes: Linus Torvalds made this post about Linux version numbering: "So, I made noises some time ago about how I don't want another 2.6.39 where the numbers are big enough that you can't really distinguish them. We're slowly getting up there again, with 3.20 being imminent, and I'm once more close to running out of fingers and toes. I was making noises about just moving to 4.0 some time ago. But let's see what people think. So — continue with v3.20, because bigger numbers are sexy, or just move to v4.0 and reset the numbers to something smaller?" To voice your opinion, the Google+ post allows you to discuss the matter and cast a vote in a poll.

New submitter cyranix writes "You may never have to reboot your Linux machine ever again, even for kernel patching," and excerpts from the long (and nicely human-readable) description of newly merged kernel code that does what Ksplice has for quite a while (namely, offer live updating for Linux systems, no downtime required), but without Oracle's control.
It provides a basic infrastructure for function "live patching" (i.e. code
redirection), including API for kernel modules containing the actual
patches, and API/ABI for userspace to be able to operate on the patches
(look up what patches are applied, enable/disable them, etc). It's
relatively simple and minimalistic, as it's making use of existing kernel
infrastructure (namely ftrace) as much as possible. It's also
self-contained, in a sense that it doesn't hook itself in any other kernel
subsystem (it doesn't even touch any other code). It's now implemented for
x86 only as a reference architecture, but support for powerpc, s390 and
arm is already in the works (adding arch-specific support basically boils
down to teaching ftrace about regs-saving).

jones_supa writes Open source software can always be acquired without charge, but can still incur significant development costs. Elementary OS wants to make people aware of this, and have changed their website to suggest donating when downloading, and make users explicitly enter "$0" if they want a free download. This is the same strategy Canonical has used when offering Ubuntu. The Elementary OS blog explains: "Developing software has a huge cost. Some companies offset that cost by charging hundreds of dollars for their software, making manufacturers pay them to license the software, or selling expensive hardware with the OS included. Others offset it by mining user data and charging companies to target ads to their users. [...] If we want to see the world of open source software grow, we should encourage users to pay for its development; otherwise it'll be underfunded or developers will have to resort to backdoor deals and advertising. And nobody wants that future." Currently the only people who have received money for working on Elementary OS have been community members through their bounty program.

Probably -- if the device I want supports itProbably -- if it works as promisedProbably -- credit cards will be like checks in another decadeNot sure -- no strong opinions either wayDoubtful -- not a useful technology to meDoubtful -- it will be too fragmentedDoubtful -- privacy/security concernsDoes throwing my spare change at the cashier count as mobile?