|Story||oVirt 3.5 Rolls Out||Roy Schestowitz||20/10/2014 - 7:58am|
|Story||Linux 3.18-rc1||Roy Schestowitz||20/10/2014 - 7:45am|
|Story||Firefox Hello Not Working and Mozilla Claims the Bug is Invalid||Roy Schestowitz||20/10/2014 - 7:40am|
|Story||Ubuntu 14.10 "Utopic Unicorn" Arrives in a Few Days||Rianne Schestowitz||19/10/2014 - 8:09pm|
|Story||Meizu MX4 Pro Spotter Running Ubuntu Touch||Rianne Schestowitz||19/10/2014 - 7:20pm|
|Story||KDE Telepathy 0.9.0 Released||Rianne Schestowitz||19/10/2014 - 7:17pm|
|Story||Porteus 3.1 RC1 Is a Bleeding Edge Slackaware-Based Distro with Linux Kernel 3.17||Rianne Schestowitz||19/10/2014 - 6:05pm|
|Story||Five Best Linux Desktop Environments||Rianne Schestowitz||19/10/2014 - 5:57pm|
|Story||IBM Tweaks Power-Linux Discount Deal In Europe||Rianne Schestowitz||19/10/2014 - 5:56pm|
|Story||Parsix OS Is an Interesting GNOME and Debian 7.0 "Whezzy" Blend||Rianne Schestowitz||19/10/2014 - 5:52pm|
KWin/Wayland 5.1 gained support for the fullscreen shell interface. My idea when adding this was to not have to implement DRM support in KWin, but (for the time being) leverage Weston. This simplifies development and allows us to move forward on a higher speed. Jason Ekstrand’s talk showed that the fullscreen shell provides more interesting aspects than our use case. The shell can also be used for use cases such as screen sharing: a compositor renders in addition to a fullscreen shell provided by a different compositor which can use it to e.g. capture a video stream or forward an rdp session. Very interesting and quite useful that we already support it and won’t have to add additional support for rdp into each compositor.
It's been said before, but maybe the time for Linux and i integration is finally drawing near.
"We have a fundamental belief that you can't survive in this new world of mobile, social, big data, and cloud without being able to integrate and interface into the system of record in a secure and scalable manner," says Stephen Leonard, general manager of IBM Systems and Technology Group sales.
IBM, with its major investment in Linux, thinks Power Systems are the best answer for making that integration and interface not only more effective, but also more cost efficient based on the existing systems of record and the data crunching performance that is being built into its hardware and software.
In fact, it is not really that money and Free Software are strange bedfellows. Not only is there nothing prohibiiting anyone to generate revenues with Free Software, it is even encouraged. We have adopted a (sane) practice for years, which is to provide binaries and source code of entire Free Software stacks for free. Reading the GPL you may notice that this is not at all something to be expected; if anything, you may sell your binaries tomorrow, and only give away your source code. The unhealthy part comes when the expectation that not only all this should be free, but that your time, expertise and your entire work should always remain free.
In the 3.18 mailbox pull request Jassi Brar explains, "A framework for Mailbox controllers and clients have been cooking for more than a year now. Everybody in the CC list had been copied on patchset revisions and most of them have made sounds of approval, though just one concrete Reviewed-by. The patchset has also been in linux-next for a couple of weeks now and no conflict has been reported. The framework has the backing of at least 5 platforms, though I can't say if/when they upstream their drivers (some businesses have 'changed')."
For the past year Google developers have been looking at dropping support for EXT* file-systems from ChromeOS while only today it's making the rounds on the Internet and of course Linux fans are enraged.
While ChromeOS is based on Linux and EXT4 continues to be the most widely used Linux file-system and still is used by default on most Linux distributions, Google developers are dropping support for EXT2/EXT3/EXT4 file-systems from their ChromeOS user-interface.
All of these text editors are console based applications which make them ideal for editing files on remote machines. Textadept also provides a graphical user interface, but remains fast and minimalist.
Console based applications are also light on system resources (very useful on low spec machines), can be faster and more efficient than their graphical counterparts, they do not stop working when X needs to be restarted, and are great for scripting purposes.
I have selected my favorite open source text editors that are frugal on system resources.
The launch of the Android 5.0 L update for Nexus 4, Nexus 5, Nexus 7, and Nexus 10 is right around the corner. Or at least that’s what the latest reports are indicating. Google failed to reveal when the new Android version will be released for the public, but several sources are confirming that we might get the Android 5.0 L update sooner than expected.
Being one of the most flexible, text-based chatting protocol, IRC has been around for over 20 years and it is still heavily used to this day.
Here are five Internet Relay Chat clients with a graphical interface. Terminal-based IRC clients are not covered here. I also didn't include (except for a Firefox extension included as a bonus - ChatZilla) clients which are available in general-purpose instant messaging applications, like Pidgin or Kopete, but if you use these, you should be aware they support IRC too, and for some users it may be a better option to use an application with unified interface for all the chatting protocols instead one separate program for each.
Going back two years with the Linux 3.7 kernel was the initial 64-bit ARM support and now eleven kernel releases later the initial enablement is still being battened up. With Linux 3.18 there's finally PCI support for ARM64.
Besides Linux 3.18 being closer to allowing the AArch64/ARM64 kernel code to compile under Clang and many ARM/ARM64 Linux kernel improvements, another 3.18 addition for the new 64-bit ARM architecture is the addition of PCI support.
Black Lab Linux started its life as a Windows XP alternative and the developers actually made a big deal about it. Even the interface was designed in such as way that it resembled the Windows XP desktop layout, at least to some degree. They since parted ways with that kind of desktop and statement, but they are still looking for their identity.
A few days ago I wrote about the GNOME Infrastructure moving to FreeIPA, the post was mainly an announcement to the relevant involved parties with many informative details for contributors to properly migrate their account details off from the old authentication system to the new one. Today’s post is a follow-up to that announcement but it’s going to take into account the reasons about our choice to migrate to FreeIPA, what we found interesting and compelling about the software and why we think more projects (them being either smaller or bigger) should migrate to it. Additionally I’ll provide some details about how I performed the migration from our previous OpenLDAP setup with a step-by-step guide that will hopefully help more people to migrate the infrastructure they managed themselves.
Unity is the default desktop environment in Ubuntu and it's been around for four years now, although not for the desktop version of the distribution. It was first used in Ubuntu Netbook Remix, which was a flavor dedicated for Netbook use. In fact, Ubuntu Netbook Remix 10.10 Maverick Meerkat was the first to adopt the new Unity desktop.
The regular Ubuntu 10.10 release still used GNOME 2.x for the desktop, which is one of the reasons why some users still say that 10.10 still is the best version ever made by Canonical.