It is much easier for me to maintain a git repo than to update my blog so Crouton Fedora is moved here:

https://github.com/nmilosev/crouton-fedora

Now 100% VNC server free. :)

Have fun!

I’ve created a small Chrome App for if you are using my version of Crouton with Fedora which makes it possible to quickly connect to the running VNC server. RealVNC was great to me, but I couldn’t really configure it to my liking. I found this, an old project based on noVNC for Chrome and based my work of it. Here it is in action:

sorry for gif quality here, svbtle doesn’t like it, please right click it and see it in a separate tab

This app connects to whatever VNC server is on the localhost:5901. It connects with high quality and fullscreen which is recommended for a local VNC server. The contents of my ~/.vnc/config file are:

securitytypes=None
geometry=1366x768
depth=24
localhost

• localhost - only accepts connections from localhost
• securittypes - since I only allow connections from localhost i disabled all security so I don’t have to type my password every time
• depth - color...

Please read this post first:

http://nmilosev.svbtle.com/crouton-with-fedora-chroot-chromebook

Anyway, after a day of tinkering with my version of Crouton with Fedora, a new, much improved version is ready.

Changelog (of sorts):

• Completely independent from the old Fedora 20 source, now only using Fedora 23 sources and DNF (yay!)
• This means that Fedora 24 script will be much easier to make
• Much faster installation time because we no longer update F20 to F23 and no importing keys
• Cleaned up the script… a lot

Quick instructions

1. Developer unlock your Chromebook
2. From crosh shell:

cd ~/Downloads
wget http://bit.ly/1QsQG1k -O crouton-fedora.tar.gz
tar xvf crouton-fedora.tar.gz 
sudo sh ./crouton-fedora/installer/main.sh -r fedora23 -t fedora

And wait.

It won’t ask you for username/password. Defaults are fedora/fedora so please change them with passwd.

To install a DE please refer...

Update 28th January 2016

A new much improved version is now available:

http://nmilosev.svbtle.com/crouton-with-fedora-chroot-2-0

Crouton is a chroot utility for ChromeOS devices which allows you to run a Linux distro alongside ChromeOS. Currently it supports Debian, Ubuntu and Kali linux and there is a fork for Arch Linux and Mageia. Now there is something missing from this sentence, and you probably already know what it is. Yep, I’ve managed to install Fedora alongside my ChromeOS because, hey why not, and because I kinda install Fedora on everything, which you already know if you ever checked my blog. I recently bought a Toshiba Chromebook (used) and I’m really happy with it. It’s fast, it’s pretty, it’s light and it runs Fedora. :)

First some important stuff:

• my work is based on the official latest (at the moment of writing) version of Crouton project
• it is also heavily...

If you are using a touchscreen on your Fedora workstation you should really check out project called Onboard. Its a replacement for the GNOME on-screen keyboard and its really great. I’m using Fedora 23 with GNOME on my Toshiba Encore WT8 Intel BayTrail tablet and I find that the Onboard keyboard is really much better than the default keyboard, mainly because it’s much easier to customize it and supports advanced stuff like function keys, different layouts etc.

Sadly Onboard keyboard is only packaged for Debian based systems so there isn’t a readily available repository for Fedora with it. However it’s not very difficult to get it installed in Fedora 23.

Get Onboard source from launchpad and unpack it

cd
wget https://launchpad.net/onboard/1.1/1.1.2/+download/onboard-1.1.2.tar.gz
tar xvf onboard-1.1.2.tar.gz
cd onboard-1.1.2

*please check if there is a newer version available

Get

One of the few things missing from the official Fedora repositories is the Chromium browser. On an i686 or x86_64 system its pretty easy to find the correct Chromium build and install it. Sadly on ARM it seems like nobody is building it (not even the Chromium build bots, last version is from 2014). Recently I got my hands on a Raspberry Pi 2 and naturally installed Fedora 23 with LXDE on it using the exquisite multiboot tool BerryBoot. So far it’s running great, and even Mono works on it! About Chromium though:

First off, it is possible, and it’s not a terribly hard thing to do with a little help from our friends from openSUSE to whom I give huge props for building Chromium browser for our devices.

Arch Linux also builds Chromium for ARM but I got strangled by the dependencies and decided to go with the openSUSE RPM. The big plus for openSUSE version is that it embeds needed libraries...

In my recent projects I’ve managed to run Fedora (for fun) on pretty much everything including:

• My phone (see my other post about GNURoot)
• NVIDIA Optimus laptop
• Raspberry Pi 2 (armhfp 23 with LXDE works great for me)
• Azure Virtual Machine (see my other post about it)

The problem is, I have an Intel Baytrail tablet (Toshiba Encore WT8) which was the only one who hasn’t received the Fedora treatment. Until now.

First of all, get acquainted with the Fedlet project. It’s great, really huge props to Adam for maintaining it, the comment section is full of golden advice. Also a gold mine of sorts is the Asus T100 on Ubuntu Google Plus group, be sure to check it out. So lets get into it:

You don’t have to use Fedlet

I used a standard Fedora 23 Workstation i686 image. The only thing I pulled from the Fedlet image was EFI folder with the bootloader (BOOTIA32.EFI), which isn’t included by...

Windows Azure is a great cloud computing platform. Sadly the support for Fedora virtual machines is virtually zero as of today (September 2015), so we are going to change that. I’ll show you how to run a virtual machine with Fedora 22 Cloud Edition on Azure and SSH into it.

First of all you should check this link:
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd/

There you can find detailed instructions which I used to setup (login into) Azure Powershell. After you are logged in to your Azure in Azure Powershell, and you have selected the correct subscription, follow these steps.

You are gonna need a Storage account for the .vhd file. Chances are you already have it, if you ever created a VM on Azure.

You are also going to need the Fedora Cloud virtual hard drive which sadly isn’t available officially from Fedora or Microsoft. But I...

Update!

http://nmilosev.svbtle.com/fedora-on-nonrooted-android-phones-2016-update

If you haven’t tried the fantastic app for Android called GNURoot, i strongly urge you to. In a nutshell, if you wanted Linux on your Android phone via chroot, you had to root your phone. This app doesn’t need root to work because it uses [PRoot](proot.me) - chroot clone which doesn’t require root. So you get a full linux environment without rooting your phone/tablet which is really great. Also, there are virtually no performance hits.

So, if you download GNURoot, you immediately have several options to install Linux on your phone/tablet. There is Debian Wheezy (with or without X server), a relatively fresh Gentoo snapshot (which I will be using later), Fedora 17 (sad face), and Aboriginal, which wasn’t available in my country. Now, you can see immediately why I wanted to write this article. While...

If you have InsydeH2O bios, you may have some trouble booting from UEFI flash drive (with linux or Win8 or higher).

There is a ton of advice, like to switch to CSM boot mode, but that defeats the point of UEFI. So some tips for you:

To make UEFI flash drive, you don’t need any special tools, you just need FAT32 formatted usb drive with an active partition and EFI folder on it. So for example, I wanted to try Ubuntu 15.04 on my machine (Toshiba Qosmio X70-A-12X) so I did the following:

• Formatted my trusty Kingston 2GB drive with diskpart (select disk X, clean, create partition primary, select partition 1, active, format quick fs=fat32
• Mounted Ubuntu iso with Windows 8.1, copied all the files from it to the USB.
• Thats it… (UEFI rocks)

To boot this drive after many hours of trying, sadly only because of a bug:

• Reset your bios to default settings!
• Leave Secureboot ON
• Turn...