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 Btrfs/EXT4/XFS/F2FS RAID 0/1/5/6/10 Linux Benchmarks On Four SSDs Rianne Schestowitz 06/11/2014 - 8:41pm
Story MySQL: Why the open source database is better off under Oracle Rianne Schestowitz 06/11/2014 - 6:06pm
Story Old hat: Fedora 21 beta late than never... and could be best ever Rianne Schestowitz 06/11/2014 - 5:56pm
Story Release of KDE Frameworks 5.4.0 Rianne Schestowitz 06/11/2014 - 5:47pm
Story Leftovers: Software Roy Schestowitz 06/11/2014 - 5:27pm
Story today's howtos Roy Schestowitz 06/11/2014 - 5:27pm
Story Leftovers: Gaming Roy Schestowitz 06/11/2014 - 5:26pm
Story Leftovers: Screenshots Roy Schestowitz 06/11/2014 - 5:25pm
Story Ubuntu GNOME 14.10: Unifying the Linux desktop Roy Schestowitz 06/11/2014 - 5:20pm
Story Canonical Confirms Involvement in Ubuntu Linux Tablet Roy Schestowitz 06/11/2014 - 5:19pm

More Patent Threats From Microsoft

Filed under
Microsoft

groklaw.net: Ina Fried has an interview with "Microsoft's top intellectual property lawyer", Horacio Gutierrez, and Gutierrez directly threatens to sue any company, like Red Hat, that refuses to sell out and do a patent deal like the one Novell signed up for.

Meet PCLinuxOS 2009 (Beta 1)

Filed under
PCLOS
-s

To the excitement of its many loyal users, the PCLinuxOS development team released the first beta of the highly anticipated 2009 release. It's been a long time coming but it seems it's finally on its way. There were no big surprizes found in this release, but lots of updates.

The 5 Best Xfce - based Linux Distributions

Filed under
Linux

internetling.com: I’ve been talking a lot about window managers and desktop environments. Nowadays most major distros simply go for KDE or GNOME, but it is not very common to see a distro use XFCE. This is a very sleek and useful little desktop environment, which provides great GTK compatibility and increases speed.

Debian (Etch) Linux

Filed under
Linux

symsysit.com: Debian is one of the mainstream and most popular distributions out there. It’s main target market is corporate desktops and Servers and it does very well in both fields. There are rumours out there, which do not do it justice, such as “Debian is very hard to install”, it isn’t at all.

Stable kernel 2.6.27.2

Filed under
Linux

lwn.net: The 2.6.27.2 stable kernel update is out; it contains about a dozen fixes for important problems. Meanwhile, the review process for 2.6.27.3 has already begun; that kernel can be expected sometime on or after October 22.

some howtos:

Filed under
HowTos
  • Customizing PCLinuxOS 2008 Minime

  • bashrun on opensuse
  • How to Backup Evolution
  • Mastering IPTables, Part 2
  • How To Install Free42 in Ubuntu
  • Advanced Tips For The ps Command
  • Commands you should never run

PCLinuxOS N1PTT-TR3 RELEASED!

Filed under
PCLOS

The Ripper Gang is pleased to announce the first public beta ISO release of what will ultimately become PCLinuxOS 2009. Due to some very personal issues, Texstar has taken a temporary leave of absence, but not to worry folks, he'll be back very soon.

No Linspire Love Lost

Filed under
Linux

practical-tech.com: When Michael Robertson sold Linspire to Xandros, I doubt many people saw a lawsuit coming his way from former Linspire CEO Kevin Carmony.

Looking at Perl

Filed under
Software

mr-oss.com: This article will be taking an introductory look at one of the most flexible programming languages known by almost any Linux/Unix system. Perl (Practical Extraction & Reporting Language) is an extremely powerful programming language that can be used for just about anything and runs on just about every operating system.

Professional-Level Photography With Linux

Filed under
Software

linuxtoday.com: Photography aficionados can be just as fussy and impossible-to-please as audio geeks. Only the most expensive, elite gear is good enough, and even then there are endless debates over which is the elitest.

The 1980s Netbook

Filed under
Linux
Hardware

itwire.com: Think bad hair and worse fashion. Think IBM Compatible Personal Computers. Think British. Yes, the eighties are back as Apricot Computers is reborn with the launch of, you guessed it, a Netbook.

Songbird 0.7.0 Review - Audio Player for Linux

Filed under
Software

tuxarena.blogspot: 'Songbird promises to be the Firefox of media players'. Although not (yet) as popular in the audio players world as Firefox is in the one of web browsers, Songbird looks and offers an interface which integrates both powerful browsing features and music collection management.

openSUSE Weekly News, Issue 42

Filed under
SUSE

opensuse.org: Issue #42 of openSUSE Weekly News is now out. In this week’s issue: Power Outage of most openSUSE servers, Retiring from the openSUSE Board, and Status openSUSE distribution.

The Sine Qua Non of the Free Desktop

Filed under
Software

oreilly.com: GNOME hacker Christian Schaller posed the question What do the free [desktops] need to grow in market share?. The comments are instructive.

10 features Ubuntu should implement

Filed under
Ubuntu

kumailht.com: Ubuntu is a great Linux distro and has achieved a lot in very less time. Here are a few ideas that Ubuntu could implement. Most of these are GUI changes that are very simple but exciting.

New version of Alien Arena 2008 released

Filed under
Gaming

PR: COR Entertainment announces the latest release of it's freeware, open sourced FPS shooter, Alien Arena 2008!

Running Google Chrome Under Wine 1.1.6 in Debian and Ubuntu

Google Chrome is an open-source web browser from Google, currently available only for the Windows platform. It aims to have a minimal and easy to use interface. Chrome uses the WebKit rendering engine, which was developed from KHTML, and it is used in various browsers like Konqueror on KDE4 or Safari (on Mac OS X).

Read more here

today's leftovers

Filed under
News
  • Kernel Log: Ext4 completes development phase as interim step to btrfs

  • Michael Robertson Continues Shell Game with Linspire's Missing Cash
  • Proprietary services vs. open-source services
  • History of Ubuntu, from Warthog to Ibex
  • Microsoft dances with open source businesses
  • Open source licence violations manual published
  • PCLinuxOS - Why would you want to try it out?
  • Lubi - Linux based Ubuntu Installer
  • Setting mouse gestures with EasyStroke and Gestikk
  • Ubuntu 8.10 and Evolution 2.24
  • Reminder: 7.04 Reaches End-Of-Life Sunday, 19 Oct 2008
  • Review: Firefox 3.1 Beta 1 -- The Best Is Yet To Come
  • Linux Foundation to boost user ties following summit
  • Jets 'n' Guns Enters Beta On Linux
  • People of openSUSE: Henne Vogelsang
  • The Untapped Open Source Online Gaming Opportunity
  • FOSSBazaar Tackles Open Source's Legal Obstacles

some howtos:

Filed under
HowTos
  • Four top tips for installing software on to Linux PCs

  • Connect to a wireless network with the command line
  • Command Line Bookmarks
  • Fun with Commands-I
  • Short Tip: GNU Screen with proper scroll, session management support
  • How to use samba on the command line
  • Sabayon - Sipie for Sirius Radio
  • Howto: Burn Audio Cd's From mp3 in ubuntu
  • Building ffmpeg on Ubuntu Linux
  • Suspend on Dell D820 openSUSE 11.1 (Beta 2) Nvidia Driver
  • Automatically process new files with fsniper

Mandriva One 2009 - Kaptivating KDE

Filed under
MDV

pbs01.wordpress: It has been a couple of days since the Mandriva team released Mandriva Linux 2009 in KDE and GNOME flavours. I decided to try Mandriva and see for myself how it has improved over Mandriva Linux 2008.1.

Syndicate content

More in Tux Machines

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.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos