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

AMD FirePro V4800 & FirePro V7800

Filed under
Hardware

phoronix.com: For those looking into an entry-to-mid-range or high-end workstation graphics card, today we are completing our look at AMD's Evergreen-based FirePro family with a review of the ATI FirePro V4800 and ATI FirePro V7800.

Who Will Show Up to Linux's Steam-Powered Playground?

Filed under
Gaming
  • Who Will Show Up to Linux's Steam-Powered Playground?
  • PipeWalker 0.8.2 Released
  • The Chzo Mythos Is Coming To GNU/Linux

Akademy 2010: Aaron Seigo Interview

Filed under
KDE
Interviews

kdenews.org: In about 6 weeks the biggest yearly gathering of the KDE community starts in Tampere. To give you all a little taste of Akademy 2010, Guillermo Amaral interviewed Aaron Seigo and asked him about his keynote.

DistroWatch Weekly, Issue 354

Filed under
Linux

This week in DistroWatch Weekly:

  • Interviews: OpenBSD's Stefan Sperling
  • News: Mandriva CEO on company situation, BLAG gets revived with new alpha, Pioneer Linux closes shop, APT and RPM package management
  • Questions and answers: Linux adoption
  • Released last week: PCLinuxOS 2010 "Openbox", Puppy Linux 5.0, CentOS 5.5
  • Upcoming releases: Linux Mint 9, OpenBSD 4.7, Mandriva Linux 2010.1 RC
  • New additions: Peppermint OS
  • New distributions: OwnOS CreativeSuite, Xin
  • Reader comments

Read more in this week's issue of DistroWatch Weekly....

When Microsoft hardware works more easily on Ubuntu than XP

itwire.com: How often have you heard the words "it's difficult to get this software/hardware working on Linux, that's why it hasn't caught the mass imagination"?

The Consumer Electronics OS War

Filed under
OS

pcmag.com: There's a major battle for OS domination in the consumer electronic space that may make the ones occurring on PCs and smartphones small by comparison.

Distro Hoppin`: Puppy Linux 5.0

Filed under
Linux

itlure.com: Puppy Linux is, by far, my favorite super-lightweight Linux distribution out there. Though lacking some features that exist in the distro giants, the sheer speed and responsiveness of it are amazing. Not to mention the hundreds of tiny little applications that do a great job of handling all sorts of tasks.

A Random Btrfs Experience

Filed under
Linux

rich0gentoo.wordpress: After all the buzz about btrfs and Ubuntu I figured I’d try experimenting with it a little. So, how did it go?

Linux 2.6.34 Kernel Released

Filed under
Linux
  • Linux 2.6.34 Kernel Released! Time For 2.6.35
  • What's new in Linux 2.6.34

today's leftovers & howtos:

Filed under
News
HowTos
  • A Quick Gimp Tutorial For Hiding People
  • SSC specifies open source software in tender process
  • Ubuntu 10.04 installation fun
  • Origami class: Fun with screen-vs
  • Decibel – Simple Audio Player For Linux
  • The Berkeley DB fiasco — Barely avoided
  • Firefox 3.6.4 Build 4 Released
  • TouchFreeze 0.2.5 for Linux
  • VideoLink, assembles a DVD video filesystem
  • Meet the GIMP: Episode 140
  • Alternative widgets explorer [Plasma]
  • Creating a scalable virtualization cluster with Ganeti
  • [AVATAR] Become a real Na'Vi using GIMP

Dimpress 3D – Sliding Panels – First Results

Filed under
Software

liveblue.wordpress: Three months has passed and there Dimpress 3D got his first cute face! We’ve developed a plugin structure and a plugin that describes a model for 3D presentations called Sliding Panels.

Review: Peppermint OS

Filed under
Linux

cristalinux.blogspot: While we wait for the release of some of the major distros' mid year upgrades, I thought I'd present a new Linux flavor which looks and performs very well: Peppermint OS.

Do Package Managers Spoil Us?

Filed under
Software

linux-blog.org: I thought of this interesting question the other day while messing around with Slackware 9.0 which was one of the last versions of Slackware to come on a single disk. The goal was to try to take a Slackware 9.0 install to the most recent stable and it was almost accomplished.

What IS Linux (and what it should be)?

Filed under
Linux

ghacks.net: One of the issues I come across often is how Linux is perceived and what it needs to do to continue to grow. It’s a very complex issue based on a lot of pre-determined opinions and deeply embedded history.

How and Why Contributing to FOSS Can Benefit Your Organization

Filed under
OSS

sys-con.com: At first glance, the ecosystem in the Free and Open Source Software (FOSS) world can seem a bit complicated. So, where does this all begin?

Does Nightingale Matter

Filed under
Software

blogs.techrepublic.com: It didn’t take long before one of the active Songbird developers forked Songbird into a new Linux-first project called Nightingale. But already this project seems to be unstable enough to make one believe it will fail before it takes flight.

Grahame Morrison – No feuds on his watch?

Filed under
OSS

openbytes.wordpress: Is Mr Morrison "stirring the pot"? Does he actually think differences of opinion or "feuds" are harmful? We all remember "Ah....Youre killing FOSS"

Debian + Backports is Better than the Latest Ubuntu

Filed under
Linux

pclinuxos2007.blogspot: Debian Stable has a bad reputation of being little obsolete. It's never able to catch up with time. But I don't buy to the view that Debian Stable is outdated.

Tuxification

Filed under
Linux

linux-magazine.com: As you might have guessed, I have a lot of Linux-based T-shirts....a LOT of them. And I enjoy wearing those T-shirts. From time to time wearing the image of Tux encourages strangers who would normally never say anything to strike up a conversation.

Writing made easy for young students: Introducing WriteType

Filed under
Software

trombonechamp.wordpress: After several months of development, it is finally time to introduce the world to WriteType. WriteType is an application designed to aid young students in writing and typing on the computer.

Syndicate content

More in Tux Machines

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

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30