It is perhaps easy to read that line, think it doesn't affect you, and then move on. But thats just not the case.
The time-zone database (sometimes referred to as the Olson database) is the computing world's principle source of time-zone data. It is embedded in every Unix and Java for starters, and will be used by many websites and probably by your iPhone. You may know it via the IDs, such as "Europe/London" or "America/New_York".
I want to thank all users who tested our beta version and release candidates and ensured by that a regression free update. I am very glad on how smooth this major transition of the compositor seems to work according to the very low number of bug reports in this cycle.
On Mesa enabled desktop systems there is also the possibility to go a step further and leave GLX completely behind by compiling KWin for OpenGL ES/EGL only.
We’ve extolled the virtues of SSH numerous times, for both security and remote access. Let’s take a look at the server itself, some important “maintenance” aspects, and some quirks that can add turbulence to an otherwise smooth ride.
While we’ve written this guide with Linux in mind, this can also apply to OpenSSH in Mac OS X and Windows 7 via Cygwin.
Monday, September 19 2011 @ 07:21 AM CST Contributed by: Linegod
To what extent does Android respect the freedom of its users? For a computer user that values freedom, that is the most important question to ask about any software system.
In the free/libre software movement, we develop software that respects users' freedom, so we and you can escape from software that doesn't. By contrast, the idea of "open source" focuses on how to develop code; it is a different current of thought whose principal value is code quality rather than freedom.Thus, the concern here is not whether Android is "open", but whether it allows users to be free.
Legacy file formats are evil. They tend to have no written specifications, and when you start reverse-engineering them, you often discover layers of questionable solutions built on top of even more questionable solutions that are carried around for backwards compatibility sake.
So why go through pains of supporting them at all? Simply put, because it's the legacy which isn't always in the past really, because businesses don't like upgrades. Designers keep local cliparts in all kinds of arcane file formats, big publishing houses keep using DOC instead of DOCX, and system integration companies still toss around VSD files.
Well, done at last! After some time gathering opinions from readers and quite some more time testing each one of the contenders, I have finished my comparison of the best of the best in KDE distros.
I took the plunge to migrate my personal / business desktop PC from Mandriva 2010.2 to Mageia 1 today (Sunday, 4 September 2011). I used the instructions from this page: Migrate from Mandriva Linux. Specifically the section titled, “b) Upgrading inline, using urpmi (CLI)”. The migration is roughly three quarters done as I type this. I decided to try to use the PC while I ran the migration from console 1 (Ctrl Alt F1). In preparation for this I closed programs I suspected would be most affected.
I tested Mandriva 2011 "Hydrogen" on a live USB, first made with MultiSystem and then made with UnetBootin. I was surprised that Mandriva booted after having the live USB made with UnetBootin, because for the last few years Mandriva ISO files have failed to work right with UnetBootin.
Saturday, August 27 2011 @ 10:07 AM CST Contributed by: Linegod
When users complain about GNOME 3, inevitably they compare its release to KDE 4.0's. One KDE developer has told me that he dislikes the comparison, but, in the absence of other parallels, it continues to be made.
However, one part of the analogy that hasn't been explored is KDE's recovery from its user revolt, and whether GNOME is in any position to emulate that as well.
