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

Why Is PCLinuxOS 2007 Better Than Ubuntu ?

Filed under
PCLOS
Ubuntu

geniushackers.com/blog: I am one of Linux enthusiast like you people, and have used almost all major Linux distros in past.Currently I triple boot Windows XP/Ubuntu Feisty /PCLinuxOS 2007.I am very impressed with PCLOS 2k7, even more than i was with Ubuntu. So i though why not write something which may help other people….

10 Substantial Events in Linux History

Filed under
Linux

adamstechblog.com: Here are a few substantial events in Linux history: 1991 - Linus Torvalds posts his first message about his free operating system resembling MINIX. He mentions that the operating system will probably never support anything other than AT-hard drives.

Mysteries of Ubuntu's Wubi

Filed under
Software

mmol-6453.livejournal: So I've found myself wondering why my Ubuntu disks show up under NTFS. While it's obvious in hindsight, I thought I'd share.

Do we really need Crossover? (or using WINE for Dreamweaver 8)

Filed under
Software

alternativenayk.wordpress: I had been experimenting with Crossover 6 on my Ubuntu and PCLinux with basic success. But recently, on my newly installed openSUSE 11, I though I’d try a direct WINE install of Dreamweaver 8, and guess what? It worked.

Horny for Ubuntu 8.10: first look at Intrepid Ibex

Filed under
Ubuntu

arstechnica.com: The first alpha release of Ubuntu 8.10, codenamed Intrepid Ibex, was made available on Saturday. This preliminary Intrepid prerelease includes updated packages, a new version of the Linux kernel, and an experimental new visual style.

few more howtos:

Filed under
HowTos
  • Ubuntu: How to Extract Audio From YouTube Video

  • Convert audio files with Audio-convert-mod
  • Converting your m4a music files to mp3
  • Simple Cumulative Math Using Awk On Unix or Linux
  • Chrooting into a Linux environment

OpenSUSE 11 GA

Filed under
SUSE

bmc.com/blogs/steve-carl: I mentioned in that post about the test stack that I was testing OpenSUSE 11 Alpha. It has since GA'ed, so it was time to go back and have a look. Unlike Fedora 9, OpenSUSE 11 had installed fairly easily even in Alpha state. I expected the GA to be smooth, and it was.

Ubuntu Weekly Newsletter #97

Filed under
Ubuntu

The Ubuntu Weekly Newsletter, Issue 96 for the weeks June 22nd - June 28th, 2008 is now available. In this issue we cover: Ubuntu 8.04.1 freeze proposed, Intrepid Alpha 1 released, a new Universe contributor, Brainstorm updates, Ubuntu Women project status, new Ubuntu members, LoCo news, and Launchpad news.

Follow-Up: Attack on Exherbo.org machine

Filed under
Gentoo

ahfaeroey.wordpress: Some of you might have read my previous blog post about the attack on Exherbo’s quote database that I wrote about yesterday. As promised I am going to write a follow up post about how this was handled and what the result of the cooperation with Gentoo’s infrastructure team was.

few shorts:

Filed under
News
  • The first 24 hours with openSUSE 11

  • Firefox 3 gets a thumbs-up from me
  • Playing with Fluxbox
  • 10 Reasons why i love GIMP Graphics Tool
  • Project Neon: KDE 4 nightly builds

few howtos:

Filed under
HowTos
  • Disable Login and Logout Sound on Ubuntu

  • tweeting from the command line
  • Replacing Openoffice Splash Screen
  • Bypass School Internet Filters
  • View A Package Changelog Entry With Aptitude or Synaptic
  • Configuring Debian for UTF-8

From Windows to Ubuntu

Filed under
Ubuntu

billhiggins.us/weblog: Chief among these “things I’d like to change when I have the time” was my use of Windows XP as my operating system. So I downloaded a Ubuntu ISO CD image, burned that, backed up my data, then formatted my hard drive and installed Linux.

Ubuntu Hardy Heron on a Mac Mini

Filed under
Ubuntu

rfdlinux.wordpress: My broadband connection was barely 24 hours old when work began on migrating to the latest version of Ubuntu. Hardy Heron, as it’s called, is very nice on the Mini. What follows is how I did it, what I used, what worked, and what didn’t.

Pardus 2008 : A testdrive

Filed under
Linux

wamukota.blogspot: A few weeks ago I was asked to testdrive Pardus - a distro of Turkish origin. It was released on june 27 and here is my report on this distro.

The 'killer' linux ....Ships AHOY!

Filed under
Linux

linuxgeeksunited.blogspot: Everyone uses the "car" analogy. Expecting Linux to someday ZOOM ahead of the pack and leave the likes of MS and Apple in the dust on the track. This mental approach doesn't always do it for people and they get discouraged because of the mindset like that they walked in with.

The popular emergence of apt-git?

Filed under
Software

jldugger.livejournal: It's no secret that Canonical is a large proponent of Bazaar (bzr) and would like to use Ubuntu as a guinea pig for large scale deployments. At UDS Prague, James Westby gave an interview about using "distributed version control systems" (DVCS) for coordinating development. The interviewer is a bit confused about how the Ubuntu flavors interact, so I think an explanation of DVCS and Ubuntu development is in order.

Why Ubuntu's LTS releases are inferior to Red Hat Enterprise Linux

Filed under
Linux

utoronto.ca/blog: It's time to update my view of Ubuntu with my most recent set of feelings. Well, with why I feel my most recent set of feelings, which is that Ubuntu LTS is significantly inferior to Red Hat Enterprise Linux.

Free as in Beer

Filed under
OSS

sharplinux.blogspot: As I mentioned in my last Independence Day post, most free software is free in the monetary sense of the word. One of Richard Stallman's memorable and concise ways of making the "free" distinction is to say "think free speech, not free beer." The problem with the term "free software" seems to be that many users can't think past the "free-as-in-beer" quality.

Two great time-saving tips for Firefox 3

Filed under
Moz/FF

techspot.com/blog: Firefox is by far the most used alternative browser. I believe that comes in part thanks to its flexibility for customization and the myriad of useful add-ons you can get for it. My following tips, however, lay on the side of about:config tweaks.

How I got over the hurdles to migrate from XP to Kubuntu 8.04

Filed under
Ubuntu

agileskills2.org/blog: I find that Kubuntu needs a few critical tweaks before it is useable by end users, in particular, in the CJK market. Such tweaks are not very well documented and take quite some serious research efforts, even for an experienced Linux/Ubuntu server administrator.

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.