Explore

Loading

Friday, January 4, 2013

Bodhi Linux 2.2.0 ships stable E17 desktop


The latest version of Bodhi Linux now ships with the stable Enlightenment E17 desktop environment that was released recently. Bodhi Linux 2.2.0 also includes a new kernel option for 32-bit installs and has introduced hybrid ISO images. This release makes the minimal desktop distribution one of the first Linux flavours to ship the stable version of E17.
Bodhi Linux now provides two 32-bit install images: a version with a PAE-enabled kernel for machines exceeding 4GB of RAM and an image that uses a non-PAE kernel. Like the 64-bit image, the PAE-enabled 32-bit ISO uses a Linux 3.7 kernel while the non-PAE image provides an older 3.2 kernel. All images are now hybrid ISOs, meaning that they can be copied to USB memory sticks with a simple dd command and can be easily burned to CDs as well. The documentation for the distribution has also been updated and the desktop profiles have been reworked for the final release of E17. These provide several different desktop layouts – from a barebones setup to tiling window management and a complete composited desktop.
Bodhi Linux 2.2.0 is available for 32-bit and 64-bit x86 systems as well as ARM devices such as the Raspberry Pi, Nexus 7 and others. These images can be downloaded from Sourceforge. At the time of writing, packages on the Bodhi Linux web site had not been updated. Users of the 2.x branch of the distribution can update their systems through their package manager.

Source:http://www.h-online.com/open/news/item/Bodhi-Linux-2-2-0-ships-stable-E17-desktop-1777022.html

Samsung: Tizen Linux phones will arrive in 2013

Hard on the heels of Wednesday's unveiling of Ubuntu Linux for phones, Samsung has now reportedly confirmed that it plans to ship new Linux-based mobile devices of its own later this year. 

Rather than Ubuntu Linux or Linux-based Android, however, Samsung's handsets will be based on Tizen Linux, a mobile OS that was launched by the Linux Foundation and the LiMo Foundation in late 2011.

Samsung plans "to unveil competitive Tizen devices within this year," a company spokesperson reportedly told CNET on Thursday, though no further specifics were provided.

Source:http://www.pcworld.com/article/2023649/samsung-tizen-linux-phones-will-arrive-in-2013.html

Friday, December 28, 2012

Download Shim


Secure Boot bootloader for distributions available now

Download Here:


http://www.codon.org.uk/~mjg59/shim-signed/

Linux (slowly) comes to Windows 8 PCs with UEFI secure boot


One of the largest underlying changes to Windows 8 is the long-overdue shift from BIOS to UEFI. UEFI (Unified Extensible Firmware Interface) is superior to BIOS (Basic Input/Output System) in almost every way, except for one: At the moment, UEFI prevents Linux distributions from being installed on Windows 8 machines.
UEFI, in essence, is a light-weight operating system that your computer loads at boot time. (See: Demystifying UEFI, the long-overdue BIOS replacement.) Because it’s an operating system, UEFI has full access to your hardware, and it can be programmed to do just about anything (thus the Extensible part of its acronym). UEFI interfaces can be mouse-driven (pictured below), and can perform complex tasks such as surfing the web or backing up your hard drives.
The UEFI specification itself also introduces a few new features to improve performance, flexibility, and security. The feature that has received by far the most attention is secure boot, as it can be used by PC OEMs to prevent other operating systems being installed on their hardware. Dell, if it so wishes, could build a PC that only runs Windows. On the flip side, Apple could stop Windows from being installed on its hardware.
Asus EFI BIOSOstensibly, secure boot isn’t meant to be used maliciously, though: Its primary purpose is to prevent a malware-infected PC from booting, thus protecting the user from possible data theft or worse. Secure boot works by means of cryptographic signing: A chip on the motherboard stores the cryptographic hash/key of important operating system files and drivers, and during boot-up those files are checked — if their hashes have changed, they’re assumed to be compromised, and the boot process stops. If you try to boot Linux, secure boot detects the altered hashes and halts boot. While Linux obviously isn’t malware, secure boot doesn’t know that.
The solution, of course, is to add the Linux file/driver hashes to the secure boot chip — but to do that, you need a secret password. In the case of Windows 8 machines (i.e. official OEM machines bearing the Windows 8 logo), only Microsoft and the OEM know the password. If the key was public, then malware authors would be able to add their own hashes, and thus the system would be worthless.
Changing the secure boot setting, in BIOSWhere does this leave Linux? One solution is to simply disable secure boot. Some OEM machines allow you to do this, while some (most notably the ARM-powered Windows RT devices) don’t. This is a bit of an unfair compromise, though, as it leaves your computer vulnerable to malware and rootkit infection. Another option would be for Linux distributors, such as Red Hat and Canonical, to collaborate with Microsoft to get their distros added to the secure boot system. It doesn’t seem like there has been much movement in that area, though.
The currently favored solution is a workaround: a pre-bootloader signed by Microsoft (so it passes secure boot) that can then be used to load a normal Linux bootloader without further signature checking. One Linux developer, Matthew Garrett, has managed to get Microsoft to sign a pre-bootloader called Shim. You can download it today and use it to boot Linux on your Windows 8 machine. Shim should soon find its way into SUSE, Fedora, Ubuntu, and other major Linux distros. The Linux Foundation is developing an “official” workaround, but as of November it still hadn’t received Microsoft’s blessing.

Source:http://www.extremetech.com/computing/144204-linux-slowly-comes-to-windows-8-pcs-with-uefi-secure-boot

Thursday, December 27, 2012

Linux tablet ?


The year of the Linux tablet is, like the year of the Linux desktop, destined never to arrive.
That doesn't mean we won't see Linux on a tablet, but you'll see Linux on a tablet the way you see it on the desktop - clinging to a tiny percentage of the market.
There is of course Android, which does use a Linux kernel somewhere under all that Java, but when Canonical or Red Hat talk about building Linux tablets, obviously Android is not what they have in mind.
For most, the dream of a Linux tablet means running a distro like Ubuntu, Mint or Fedora on some sort of tablet hardware.
Indeed, intrepid users have already hacked Linux onto Android tablets. But the first shipping Linux tablet looks like it will be the $99 "PengPod," a Frankentablet that will run both Android and Linux proper. The PengPod will, assuming its creators follow through with their plans, arrive in buyers' hands in January of 2013.
Unfortunately, the PengPod seems doomed to mediocrity. The PengPod was funded through the Kickstarter-like site Indiegogo that ensures a market, no matter how small, does exist. But the device itself looks like little more than an off-brand Android tablet with Linux running from a micro SD card. There is also an option to have Linux pre-installed on the internal flash, but those aren't shipping right away.


The PengPod may well satisfy the enthusiasts who backed it, but it's hardly going to make a flagship example of Linux excellence in a brand new form factor.
In fact the best evidence that there's never going to be a year of the Linux tablet is that it doesn't even look like there's going to be a year of the Windows tablet.
Microsoft's Surface tablet effort is not, according to early numbers and a plethora of anecdotal evidence, flying off the shelves and hardware manufacturers don't seem to be rushing out the Windows 8 tablets.
So far, despite Microsoft's best efforts, the tablet world is still very much orbiting the twin stars of iOS and Android.
Having used a Samsung Windows 8 tablet for a few months, I have a theory as to why: you think you want a full desktop computer on your tablet - I certainly did -- but you don't. It simply doesn't work.
In the case of Windows 8 you can blame some of the "not working" on the buggy, incomplete software that is Windows 8, but not all of the problems can be attributed to a shortcoming of touch APIs.
Much of what makes a full desktop interface terrible on a touch screen tablet is simply the whole desktop paradigm was never designed to be used on a tablet and it shows. The Metro interface for Windows 8 is excellent; different, but in my experience really well done.
Where Windows 8 on a tablet falls apart is when you try to bring the software keyboard to the traditional desktop interface on a tablet. The software keyboard takes up half the screen, which makes even simple tasks difficult. How to you rename a file and move it? First you tap it to select it, then you tap the button to bring up the keyboard, then you type, then you touch away the keyboard, then you touch the file again. It isn't just awkward and slow; it's downright antagonizing.

Read Full Story: http://www.theregister.co.uk/2012/12/26/year_of_the_linux_tablet/

Tuesday, December 25, 2012

Linux Mint 14 (Nadia) and Linux Mint Debian Edition-Christmas Mint



The elves in the Linux Mint development team have been very busy the past few weeks, and just in time for Christmas they have produced new and updated relases for all of the Mint distributions.
The main branch, Mint 14 (Nadia), derived from Ubuntu 12.10 with the Gnome-based Cinnamon and MATE desktops came out in November, then Linux Mint Debian Edition Update Pack 6 at the beginning of December.
That was followed last week by the release of the Xfce version, and the set was completed this weekend with the release of the KDE version. In the following gallery I will show the default desktop and menus, and give a brief description of the content and some of strengths of each version. But there is no substitute for trying it for yourself.
All of these distributions are "Live" images, so you can download and burn them to a DVD or copy them to a USB stick, and boot it up on your own computer without changing anything on your disk. Running the live image you can see whether all of your hardware is supported - don't believe all of the FUD that people spout about having to find device drivers, compile kernel modules or whatever.
The screenshots in this gallery were taken on six different laptops, with a variety of Intel and AMD cpu and graphics, and Wi-Fi adapters from Intel, Broadcom, Atheros and Ralink - and they all worked from the base installation. If the live distribution works for you, the Mint installer will help you get it installed on your system alongside Windows.

Credits:http://www.zdnet.com/linux-round-up-a-bunch-of-mints-for-christmas-7000009158/

Monday, December 24, 2012

How to easily install the very latest GNOME in any Distro with JHBuild


The point for having an upstream GNOME installation built from sources is if you are going to build an extension, a theme or a GTK App and take advantage of all the new features of next GNOME. However it is also useful if you want to help GNOME to get better by submitting bugs  ..or it could be useful if you are just curious to see what’s coming next :)
The tool for building GNOME is nothing else than JHBuild. 

Intro

I am not going to write a full guide for how to install GNOME with JHBuild by just giving some commands, instead I will explain some basic points and then you can check on the official documentation before you start building. So this is just a quick intro and doesn’t explain all possibilities of JHBuild tool.

What JHBuild is?

JHBuild is a small application/tool, that helps us to install software from sources by setting a sandboxed environment. It also handles every dependency of the software we want to build by downloading it, configuring it, building it and installing it.
JHBuild is part of freedesktop.org and started for GNOME, but today many applications provide JHBuild modulesets. In this tutorial we just get bother only with building GNOME.

Will JHBuild brake my system?

Absolute no! JHBuild will use an isolated from the rest of your system installation similar to NPM and RVM. However it can mess up with your Apps configuration files. For example if you build Gimp with JHBuild and you have also Gimp distributor package, both installation will use the same configs.
You can easily avoid that, by using a different account just for running latest GNOME.

How much time will take to build GNOME?

It depends from your connections and your system! A typical installation (in my case) includes Gnome-Shell, Gnome-Control-Center, Empathy and Gnome Themes ..plus all their dependencies. That means downloading and building around 120 packages from GIT. With my ~7Mbps connection and and an Intel Ivy Bridge i5, it takes approximately 3-4hours and it uses around 6-7GB of space.
However there is not need to staring at it, right? Updating is much faster.
Read More:http://worldofgnome.org/how-to-easily-install-the-very-latest-gnome-in-any-distro-with-jhbuild/