Language Selection

English French German Italian Portuguese Spanish

About Tux Machines

Saturday, 20 Jan 18 - Tux Machines is a community-driven public service/news site which has been around for over a decade and primarily focuses on GNU/LinuxSubscribe now Syndicate content

Search This Site

Quick Roundup

Type Title Author Replies Last Postsort icon
Story What's CoreOS? An existential threat to Linux vendors Roy Schestowitz 09/10/2014 - 12:19pm
Story Linux Foundation Expands International Membership Roy Schestowitz 09/10/2014 - 12:09pm
Story Advice for front-end developers from Adrian Pomilio of Teradata Roy Schestowitz 09/10/2014 - 12:03pm
Story Alfresco Connects ECMs To SharePoint Roy Schestowitz 09/10/2014 - 11:56am
Story How open source technology is being deployed in science Roy Schestowitz 09/10/2014 - 11:03am
Story 10 Steps To Overcome Your Fear Of Using Open Source Software Roy Schestowitz 09/10/2014 - 11:01am
Story Phoronix on AMD Roy Schestowitz 09/10/2014 - 10:41am
Blog entry Tux Claus Rianne Schestowitz 09/10/2014 - 9:55am
Story Open-Source AMD Linux Developers Already Thinking About API Improvements Rianne Schestowitz 09/10/2014 - 8:46am
Story Five talented women in open source you should know Roy Schestowitz 09/10/2014 - 8:33am

Provisioning on Bare Metal the LinMin Way

Filed under
Software

practical-tech.com: It’s one thing to install Linux or Windows on a system of your own, it’s an entirely different thing to install Linux or Windows on a couple of dozen to a couple of thousand PCs. That’s where LinMin comes in.

5 Things Linux does better than Mac OS X

Filed under
Linux

internetling.com: I’ve been using Mac OS X alongside Debian since 2007 now, and I think I have a fairly good picture of how things work in both operating systems. In the end, the only feeling I got of Mac OS X is as if I were playing with Linux’ retarded little brother. Here are a few reasons why.

Linux Myths: Busted!

Filed under
Linux

linuxhaxor.net: One of the main reasons that most people are afraid to try Linux is because they have this preconceived notion about linux being too hard to use and difficult to maintain; or that they have to do something drastically differ ant and there is a steep learning curve to using linux.

Banshee 1.2 - 1.x Series Getting to Maturity

Filed under
Software

vivapinkfloyd.blogspot: The new Banshee 1.2 includes several new features over the last stable release, like the equaliser or the music recommendations panel. The full list of new or improved features is here. For those who didn't hear about Banshee yet, it's a pretty powerful audio player for GNOME which received more and more attention lately.

7 Best Linux Distributions for Multimedia Enthusiasts

Filed under
Linux

junauza.com: Graphic designers, movie editors, music composers, and multimedia addicts have specific needs when it comes to software. That is why there are specialized Linux distributions that cater to them. Here are 7.

15 Examples To Master Linux Command Line History

Filed under
HowTos

thegeekstuff.com: When you are using Linux command line frequently, using the history effectively can be a major productivity boost. In fact, once you have mastered the 15 examples that I’ve provided here, you’ll find using command line more enjoyable and fun.

images, pictures, screenshots, & graphs

Filed under
Linux
  • 10 Reasons why GUI Doesn’t Matter

  • 5 + 1 beautiful designs for Ubuntu 8.10 “Intrepid Ibex”
  • Make OpenOffice Work For You : Starting Out
  • 1000+ Desktop Wallpapers for your Asus Eee PC
  • Social network popularity around the world
  • Dell Says Ubuntu Comes With “No Security”

Ubuntu netbook

Filed under
Linux
Hardware

manilastandardtoday.com: ACER’s Aspire One is a solid netbook, but it can be much more. In the last two weeks, I’ve been using it as a full notebook, running office applications, editing digital photos, surfing the Web and watching videos on a robust, full-featured system.

openSUSE @ Akademy 2008

Filed under
SUSE

lizards.opensuse: In Sint-Katelijne-Waver, Belgium currently Akademy, the annual conference of the KDE project takes place. More than 300 people had a nice weekend listening to a whole bunch of very interesting talks of various topics around KDE. Over the week there will be special topics and BOFs and Hacking.

Byebye Ubuntu, Hello Fedora

Filed under
Linux

gibbalog.blogspot: My recent experiments with installing Ubuntu on my little home server came to an end this weekend. After finding tons of forum posts and various problems with installing SqueezeCenter on Hardy Heron I decided to try another approach.

today's leftovers

Filed under
News
  • Linux Myth: Installing “Third Party” Software is “Hard”

  • Red Hat Solutions Provide Reliability and Performance Gains for Munich Airport
  • Debian Bug Count Rising
  • Marble provides basic engine for free Google Earth replacement
  • Did the big boys really kill OLPC?
  • When happened this to GNOME?
  • openSUSE vanilla kernel part 2….
  • Vote on the OpenOffice.org 3.0 splash screen
  • Running Ubuntu on an Asus EEE 4G
  • Hadoop: When grownups do open source
  • Linux rises to top dog in servers
  • Why Ubuntu just might succeed
  • Linus Torvalds & the Woodshed
  • What the heck is Mozilla thinking?
  • KDE-PIM Hackers Present Integration of KDE 4 Frameworks
  • GPL Project Watch List for Week of 08/08
  • 12 great apps for bridging Windows, Linux and Macs
  • Recovering Deleted Files By Inode Number In Linux And Unix
  • There and back again: a narrative of OSCON 2008
  • Open Source Software Gaining Ground
  • Linux Application Checker Brings Distro Help

Hiding Software Versions - A Step Forward to a Secure Server

Filed under
HowTos

Howto change the default behavior of showing the software version for some popular packages on Ubuntu 8.04.1 Server, such as Postfix, Apache, PHP, and VSFTPD.

CentOS 5.2 - Send in the Clones

Filed under
Linux

techiemoe.com: CentOS, for those unfamiliar, is a clone distribution. The maintainers take the freely-available source code released by Redhat for its commercial Redhat Enterprise Linux (RHEL) product and recompile it, stripping out any trademarked artwork, then redistribute it as CentOS.

Dell shipping five Hardy Heron systems

Filed under
Ubuntu

desktoplinux.com: Dell is shipping two new laptops with widescreen LCD displays and Ubuntu Hardy Heron (8.04) operating systems with DVD playback. Additionally, the largest U.S. PC maker has started offering Hardy Heron on three models previously available with the earlier Gutsy Gibbon Ubuntu release.

Mandriva 2009 Beta 2 - KDE 4.1 thoughts and comments

Filed under
MDV

blog.linuxbox.co.nz: I recently downloaded the Mandriva 2009.0 beta 2 KDE 4.1 live cd. I kept of list of things I found as I had a look around it. I only focused on the desktop.

Top 4 Alternatives to Ubuntu Linux

Filed under
Linux

intranetjournal.com: Considering the success of Ubuntu Linux as a distribution of the open source operating system, it has become clear that locating good alternatives to this release is becoming increasingly difficult. With that said, I've decided to round up the best candidates.

Zenwalk 5.2 GNOME Edition (beta)

Filed under
Linux

celettu.wordpress: Finally. Since 1995, when Patrick Volkerding announced that he would no longer include GNOME in Slackware, people had to rely on projects like GWARE, GNOME Slackbuild or Dropline to enjoy their favourite desktop environment on the oldest Linux distribution around. Until now.

Debian: The OS for the rest of us

Filed under
Linux

blogs.techrepublic.com: Lately I have been poking at various Linux distributions to see what they have to offer. But most of the distributions I have looked at are geared toward new users, users with older (or strange) hardware, or corporate users. But what about those that do not fall into any of the above? What about those Linux users who want a challenge? Something that doesn’t hand-hold you through the entire computing experience? Well, you’re in luck.

some howtos:

Filed under
HowTos
  • Bash & (Ampersand)

  • Accessing Ubuntu files after reformatting Windows
  • Add Computer Network And Trash Icons To Desktop
  • Creating global keyboard shortcuts in GNOME
  • Bash Trap Control C
  • How to Install aMSN 0.98b with anti-aliasing in Ubuntu
  • Recover plesk access
  • Puppet can ease system administration tasks across the network
  • Floating Point Math in Bash, Part 2 (Wait for System Load)
  • Linux Guides (Must Read)

My disagreement with Richard Stallman

Filed under
OSS

geekzone.co.nz: Software and computers are all pervasive in today's world and thus demand our utmost diligence: The lives we live are run and organised by software, we depend on software, we trust our most intimate data to software systems. Thus, the importance of free software: Only free software can protect our freedoms.

Syndicate content

More in Tux Machines

KDE: Linux and Qt in Automotive, KDE Discover, Plasma5 18.01 in Slackware

  • Linux and Qt in Automotive? Let’s meet up!
    For anyone around the Gothenburg area on Feb 1st, you are most welcome to the Automotive MeetUp held at the Pelagicore and Luxoft offices. There will be talks about Qt/QML, our embedded Linux platform PELUX and some ramblings about open source in automotive by yours truly ;-)
  • What about AppImage?
    I see a lot of people asking about state of AppImage support in Discover. It’s non-existent, because AppImage does not require centralized software management interfaces like Discover and GNOME Software (or a command-line package manager). AppImage bundles are totally self-contained, and come straight from the developer with zero middlemen, and can be managed on the filesystem using your file manager This should sound awfully familiar to former Mac users (like myself), because Mac App bundles are totally self-contained, come straight from the developer with zero middlemen, and are managed using the Finder file manager.
  • What’s new for January? Plasma5 18.01, and more
    When I sat down to write a new post I noticed that I had not written a single post since the previous Plasma 5 announcement. Well, I guess the past month was a busy one. Also I bought a new e-reader (the Kobo Aura H2O 2nd edition) to replace my ageing Sony PRS-T1. That made me spend a lot of time just reading books and enjoying a proper back-lit E-ink screen. What I read? The War of the Flowers by Tad Williams, A Shadow all of Light by Fred Chappell, Persepolis Rising and several of the short stories (Drive, The Butcher of Anderson Station, The Churn and Strange Dogs) by James SA Corey and finally Red Sister by Mark Lawrence. All very much worth your time.

GNU/Linux: Live Patching, Gravity of Kubernetes, Welcome to 2018

  • How Live Patching Has Improved Xen Virtualization
    The open-source Xen virtualization hypervisor is widely deployed by enterprises and cloud providers alike, which benefit from the continuous innovation that the project delivers. In a video interview with ServerWatch, Lars Kurth, Chairman of the Xen Project Advisory Board and Director, Open Source Solutions at Citrix, details some of the recent additions to Xen and how they are helping move the project forward.
  • The Gravity of Kubernetes
    Most new internet businesses started in the foreseeable future will leverage Kubernetes (whether they realize it or not). Many old applications are migrating to Kubernetes too. Before Kubernetes, there was no standardization around a specific distributed systems platform. Just like Linux became the standard server-side operating system for a single node, Kubernetes has become the standard way to orchestrate all of the nodes in your application. With Kubernetes, distributed systems tools can have network effects. Every time someone builds a new tool for Kubernetes, it makes all the other tools better. And it further cements Kubernetes as the standard.
  • Welcome to 2018
    The image of the technology industry as a whole suffered in 2017, and that process is likely to continue this year as well. That should lead to an increased level of introspection that will certainly affect the free-software community. Many of us got into free software to, among other things, make the world a better place. It is not at all clear that all of our activities are doing that, or what we should do to change that situation. Expect a lively conversation on how our projects should be run and what they should be trying to achieve. Some of that introspection will certainly carry into projects related to machine learning and similar topics. There will be more interesting AI-related free software in 2018, but it may not all be beneficial. How well will the world be served, for example, by a highly capable, free facial-recognition system and associated global database? Our community will be no more effective than anybody else at limiting progress of potentially freedom-reducing technologies, but we should try harder to ensure that our technologies promote and support freedom to the greatest extent possible. Our 2017 predictions missed the fact that an increasing number of security problems are being found at the hardware level. We'll not make the same mistake in 2018. Much of what we think of as "hardware" has a great deal of software built into it — highly proprietary software that runs at the highest privilege levels and which is not subject to third-party review. Of course that software has bugs and security issues of its own; it couldn't really be any other way. We will see more of those issues in 2018, and many of them are likely to prove difficult to fix.

Linux Kernel Development

  • New Sound Drivers Coming In Linux 4.16 Kernel
    Due to longtime SUSE developer Takashi Iwai going on holiday the next few weeks, he has already sent in the sound driver feature updates targeting the upcoming Linux 4.16 kernel cycle. The sound subsystem in Linux 4.16 sees continued changes to the ASoC code, clean-ups to the existing drivers, and a number of new drivers.
  • Varlink: a protocol for IPC
    One of the motivations behind projects like kdbus and bus1, both of which have fallen short of mainline inclusion, is to have an interprocess communication (IPC) mechanism available early in the boot process. The D-Bus IPC mechanism has a daemon that cannot be started until filesystems are mounted and the like, but what if the early boot process wants to perform IPC? A new project, varlink, was recently announced; it aims to provide IPC from early boot onward, though it does not really address the longtime D-Bus performance complaints that also served as motivation for kdbus and bus1. The announcement came from Harald Hoyer, but he credited Kay Sievers and Lars Karlitski with much of the work. At its core, varlink is simply a JSON-based protocol that can be used to exchange messages over any connection-oriented transport. No kernel "special sauce" (such as kdbus or bus1) is needed to support it as TCP or Unix-domain sockets will provide the necessary functionality. The messages can be used as a kind of remote procedure call (RPC) using an API defined in an interface file.
  • Statistics for the 4.15 kernel
    The 4.15 kernel is likely to require a relatively long development cycle as a result of the post-rc5 merge of the kernel page-table isolation patches. That said, it should be in something close to its final form, modulo some inevitable bug fixes. The development statistics for this kernel release look fairly normal, but they do reveal an unexpectedly busy cycle overall. This development cycle was supposed to be relatively calm after the anticipated rush to get work into the 4.14 long-term-support release. But, while 4.14 ended up with 13,452 non-merge changesets at release, 4.15-rc6 already has 14,226, making it one of the busiest releases in the kernel project's history. Only 4.9 (16,214 changesets) and 4.12 (14,570) brought in more work, and 4.15 may exceed 4.12 by the time it is finished. So far, 1,707 developers have contributed to this kernel; they added 725,000 lines of code while removing 407,000, for a net growth of 318,000 lines of code.
  • A new kernel polling interface
    Polling a set of file descriptors to see which ones can perform I/O without blocking is a useful thing to do — so useful that the kernel provides three different system calls (select(), poll(), and epoll_wait() — plus some variants) to perform it. But sometimes three is not enough; there is now a proposal circulating for a fourth kernel polling interface. As is usually the case, the motivation for this change is performance. On January 4, Christoph Hellwig posted a new polling API based on the asynchronous I/O (AIO) mechanism. This may come as a surprise to some, since AIO is not the most loved of kernel interfaces and it tends not to get a lot of attention. AIO allows for the submission of I/O operations without waiting for their completion; that waiting can be done at some other time if need be. The kernel has had AIO support since the 2.5 days, but it has always been somewhat incomplete. Direct file I/O (the original use case) works well, as does network I/O. Many other types of I/O are not supported for asynchronous use, though; attempts to use the AIO interface with them will yield synchronous behavior. In a sense, polling is a natural addition to AIO; the whole point of polling is usually to avoid waiting for operations to complete.

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.