Language Selection

English French German Italian Portuguese Spanish

Review: openSuse 11.0 (and KDE 4)

Filed under
SUSE

I’ve never used Suse or openSuse. I’ve been a “loyal” Fedora user since Fedora Core 1 and I have Ubuntu on my laptop since it had awesome laptop support. It’s been a few years and nothing horrible has happened because of the Microsoft pact and it came as a liveDVD in the latest Linux Format Magazine. I was trying to wait until KDE 4.1 came out for Fedora so that could be my first experience with KDE 4, but that’s been delayed nearly a month now (while they, rightly, fix some bugs) so I decided to go ahead with the Suse review.

Suse is the second oldest distro that’s still around. It started off as being based off of Slackware and later on was somewhat based on Red Hat, borrowing rpm and some other technologies. Since then it’s gone off on its own and is now considered one of the big boys. A few years after Red Hat shelved its personal distro and converted over to the community-sponsored Fedora, Suse decided to do the same thing with openSuse. Just like Fedora, they’ve had some uneven releases. However, openSuse 11 is supposed to be their comeback release. Historically, Suse has been one of the biggest supporters of KDE as the default desktop although that has fallen off a little seince they’ve been trying to compete with Red Hat in the business world.

It’s important to note, however, that Novell’s Suse team has put a LOT of work into their KDE desktop. This liveDVD is running KDE 4.0, yet they didn’t seem to have any problems getting icons on the desktop. Lots of people were complaining about being unable to do so in Fedora and other distros using KDE 4. Apparently, they just didn’t take the time that Suse did to engineer a really good KDE 4 release. (Frankly, I’m surprised that Siego didn’t point to openSuse 11.0 as an example of a well-implemented KDE 4.0 release!) They’ve also solved the problem of the ugly black panel that was too large. So, plus points go to Novell’s openSuse/Suse KDE team. They deserve an applause for doing this so well!

More here




Also: On openSUSE, sorta

More in Tux Machines

Security Leftovers

  • Security updates for Thursday
  • Security Tips for Installing Linux on Your SysAdmin Workstation
    Once you’ve chosen a Linux distro that meets all the security guidelines set out in our last article, you’ll need to install the distro on your workstation.
  • Fedora 26 crypto policy Test Day today (2017-03-30)!
  • Open-source developers targeted in sophisticated malware attack
    For the past few months, developers who publish their code on GitHub have been targeted in an attack campaign that uses a little-known but potent cyberespionage malware. The attacks started in January and consisted of malicious emails specifically crafted to attract the attention of developers, such as requests for help with development projects and offers of payment for custom programming jobs. The emails had .gz attachments that contained Word documents with malicious macro code attached. If allowed to execute, the macro code executed a PowerShell script that reached out to a remote server and downloaded a malware program known as Dimnie.
  • A scramble at Cisco exposes uncomfortable truths about U.S. cyber defense
    When WikiLeaks founder Julian Assange disclosed earlier this month that his anti-secrecy group had obtained CIA tools for hacking into technology products made by U.S. companies, security engineers at Cisco Systems (CSCO.O) swung into action. The Wikileaks documents described how the Central Intelligence Agency had learned more than a year ago how to exploit flaws in Cisco's widely used Internet switches, which direct electronic traffic, to enable eavesdropping. Senior Cisco managers immediately reassigned staff from other projects to figure out how the CIA hacking tricks worked, so they could help customers patch their systems and prevent criminal hackers or spies from using the same methods, three employees told Reuters on condition of anonymity.
  • NTPsec: a Secure, Hardened NTP Implementation
    Network time synchronization—aligning your computer's clock to the same Universal Coordinated Time (UTC) that everyone else is using—is both necessary and a hard problem. Many internet protocols rely on being able to exchange UTC timestamps accurate to small tolerances, but the clock crystal in your computer drifts (its frequency varies by temperature), so it needs occasional adjustments. That's where life gets complicated. Sure, you can get another computer to tell you what time it thinks it is, but if you don't know how long that packet took to get to you, the report isn't very useful. On top of that, its clock might be broken—or lying. To get anywhere, you need to exchange packets with several computers that allow you to compare your notion of UTC with theirs, estimate network delays, apply statistical cluster analysis to the resulting inputs to get a plausible approximation of real UTC, and then adjust your local clock to it. Generally speaking, you can get sustained accuracy to on the close order of 10 milliseconds this way, although asymmetrical routing delays can make it much worse if you're in a bad neighborhood of the internet.
  • Zelda Coatings
    I assume that every permutation of scams will eventually be tried; it is interesting that the initial ones preyed on people's avarice and dishonesty: "I will transfer millions to your bank account, then you share with me" - with subsequent scams appealing to another demographic: "I want to donate a large sum to your religious charity" - to perhaps capture a more virtuous but still credulous lot. Where will it end ?

Tizen and Android

Linux and Linux Foundation

Mesa and Intel Graphics