Usual Disclaimers Apply: This guide should not be used to subvert copyright restrictions. Responsibility falls to the user to ensure they are not breaking the laws of the country in which they reside or breaching any restrictions placed on content published in, or on infrastructure where other jurisdictions and/or terms of service may apply. Ignorance is no defense*, if you don’t like the regulations as they stand, exercise your democratic rights and propose a solution for change. Continue reading “Grabbing Video (back) from YouTube”
I’ve been playing with a few VMs as I try to figure out a new infrastructure for our office, and as part of this I’ve taken a particular shine to CentOS as a minimal build for my virtual servers. I then decided I wanted to get a few sandbox environments running with desktop software and, well.. that’s where the fun began!
After about twelvety-zillion restores from snapshots and reading, and forum trawling, and more restores, I think I’ve come up with a winning way to turn a humble CentOS 7 minimal build, booting to the lonely command prompt, into a bastion of desktoppy goodness. Hopefully this will be of use to someone else out there, if not – it will serve and a handy reminder to me as to what I did to get things running.
From Google, and the various Linux community forums, this is a fairly common problem so, in an effort to be more useful than those who simply post a link to the GRUB man page, or an article which spells out how dumb it is to install Windows AFTER Ubuntu – I thought I’d drop my experience and the resolution here – I’m bound to need it at some point in the future.
The Fix:
While the suggestedBoot-Repair GUI didn’t do the trick for me, the following did result in an eventual #WIN.
Boot from a Ubuntu LIVE CD/USB
From a terminal, enter the following
sudo fdisk -l
This will identify the device / drive. For me (and most users) this will tend to be /dev/sda
If you are still uncertain you can also run sudo blkid for more details and review the partition labels & sizes
Mount the Ubuntu boot partition
sudo mount /dev/sdXY /mnt
e.g. sudo mount /dev/sda1 /mnt
Run grub-install as below to drop the GRUB2 files back onto the boot partition where they should reside
sudo grub-install --root-directory=/mnt /dev/sdX
e.g. sudo grub-install --root-directory=/mnt /dev/sda
Reboot (into your freshly resurrected Ubuntu installation)
Open a terminal and refresh the GRUB2 menu with:
sudo update-grub
That’s it.. you SHOULD now have both Ubuntu and Windows 7 detected at boot and be able to choose between them.
Thanks to the Ubuntu Community for this page – and all the others which pointed to different solutions and variants of this fix. If the above doesn’t work for you, Google is your friend – there’s a heap more articles out there which should offer you an eventual solution.
I was having a chat to some people on Friday on why some devices were successful and some were… not.
Essentially what it came down to was the user experience and, while the hardware plays a part in this experience, the interface was the major driver of intuitive and efficient use.
To that end, I decided to have a bit of fun with some fan boys and, over the weekend I installed a Mac theme/overlay for Ubuntu called ‘Macbuntu‘
It’s a surprisingly simple process, for Ubuntu 10.10 users it’s 4 simple lines in terminal as follows (thanks Lifehacker):
wget https://downloads.sourceforge.net/project/macbuntu/macbuntu-10.10/v2.3/Macbuntu-10.10.tar.gz -O /tmp/Macbuntu-10.10.tar.gz
tar xzvf /tmp/Macbuntu-10.10.tar.gz -C /tmp
cd /tmp/Macbuntu-10.10/
./install.sh
Choosing the default options all the way through will leave you (after a reboot) with a desktop which is fairly close to that of Mac OSX.
On my EEE netbook the eye candy costs me ~20% more CPU but it served its purpose today when I put it in front of a couple of Steve Jobs diciples and saw them bug out that an open OS could indeed deliver an experience close to that of their beloved Macs.
This post has been far too long in coming – mainly because some miscrent broke into my car and stole a bunch of my gear – including the charger for my 6 hour old ASUS EEE 1005PE. The replacment charger took over 40 days to source (that’s what you get for living in New Zealand).
Anyway, this georgous wee netbook replaced my vintageEEE 701 4G and came pre loaded with Windows 7 Starter – and a bunch of trialware which took an absolute age to purge from the drive. It’s now dual-booting Win7 and Ubuntu10.04 (which is my primary OS of choice).
As a side note – under Ubuntu 10.04, the Atheros AR2427Â wireless card fails to be detected due a different hardware device ID of 002c which the ath9k wifi driver in the current (~ June 2010) kernel does not understand. However, all is not lost – simply follow the HOWTO written by James Little to add the patched driver to your current kernal and, 5 minutes later, you’ll have a wireless Ubuntu netbook once again (Thanks James!!)
Seriously, this was simple – and even better, it’s STABLE!
Instructions for this install are basically the same as those for my previous post using Ubuntu 9.04 and VM Svr 2.0.1 – except, now we need new patch files and the good folk at Ubuntu Geek have already written a great HOWTO Guide which steps through everything you need to do – so I’ll just summarise the changes in case you want to follow my guide with the changes 🙂
In a previous article, I covered off the installation of Kubuntu 9.10 (Karmic Koala) onto an aging, but much loved and reliable ASUS 701 EEE Netbook. In this entry, I will detail a few of the additional bits of functionality I’ve added to the already awesome Netbook Remix (NBR) of this latest OS drop.
As always, if there are things you think I should be including, or better ways of doing stuff, let me know in the comments 🙂
Pairing Bluetooth to a Nokia E71
Using an inexpensive bluetooth adapter allows you to get online without having to drag out cables etc when you’re on the bus, in the car – wherever.
The adapter detected fine – but then came the job of setting up the pairing with my Nokia E71:
On the EEE
From the Home Screen, open the ‘Internet’ group, then open up ‘kbluetooth’
You should see a bluetooth icon appear on your toolbar
Right-click the bluetooth icon, and select ‘Settings’ > ‘Bluetooth Adapters’ from the dropdown menu.
From the ‘Bluetooth Adapter’ dialogue box, set:
Adapter Name: ‘[WhateverYouWant]’
Mode: ‘Discoverable’
NOTE: Your Netbook is now being all promiscuous and stuff to the world, long-term, this isn’t good.
Click OK
On the Nokia E71
Select ‘Menu’ > ‘Connectivity’ > ‘Bluetooth’ and set:
Bluetooth ‘On’
Visibility ‘Shown to all’(the same promiscuous warnings apply)
My Phones Name ‘[WhateverYouWant]’
Remote SIM ‘Off’ (not sure what it does, didn’t need it on)
Now, scroll/tab to the right and you’ll see the ‘Paired Devices’ list.
Select ‘Options’ > ‘New Paired Device’
Your phone should now scan for any bluetooth devices in range (if your workplace is anything like mine you’ll see a heap of devices)
‘Select’ the device with the name you set in the EEE steps above.
The phone will now prompt for a passcode – Enter a passcode (numeric) into your phone.
On the EEE
You should now be prompted to enter a passcode on the EEE, enter the same numeric code
On the E71
You will be asked to ‘Authorise device [the EEE] to make connections automatically’, select ‘Yes’
Your connection should now appear in the phone
(Optional)
Select ‘Options’ > ‘Assign short name’ and change the name of the device to something more friendly if you wish.
On the EEE
Right-click the bluetooth icon, and select ‘Settings’ > ‘Bluetooth Device Manager’ from the dropdown menu.
Your E71 should appear in the list, select the device and click ‘Set Trusted’
Congratulations, your devices are now paired… now to do something useful with the connection!
Installing EEE Control (EEE PC Tray)
EEE Control is a utility written to allow easy management of the ASUS EEE embedded devices such as en/disable the Webcam, SDCard, Wifi as well as setting power and performance schemes.
To set it up under Kubuntu NBR, simply open a terminal window and enter the following:
You should see an icon appear on your taskbar which allows you to access the functionality supported by your model of EEE netbook.
Installing UbuntuONE
“Ubuntu One is your personal cloud. You can use it to back up, store, sync and share your data with other Ubuntu One users.”
…it’s just not in the Kubuntu NBR by default. To fix this, simply open a terminal window and enter the following:
sudo apt-get install ubuntuone-client-gnome
You will then find a UbuntuOne cloud icon in your ‘Internet’ applications group, and from there you are only a simple configuration away from your 2GB of free storage out in the interwebs somewhere.
Installing Skype
Skype is a VoIP client, if you haven’t heard of it in the last 5 years, you’ve probably been living under a rock – it works, the voice quality is acceptable and while the video capability can be variable, it’s got a huge number of subscribers so, give it a crack – you’ll probably find a number of your friends are already on there. My Current Skype Status is:
So – Karmic is out, and for those who are looking to upgrade to the new goodness, there’s a few simple tricks to make the process pretty much painless.
If you’re already running (K)Ubuntu 9.04, simply open up a terminal window and type:
update-manager -d
For those installing from scratch (and to be honest – it’s what I tend to still do, hang up from the Windows days?) things are almost as simple.
Getting the Files
Grab a 2GB or larger USB stick
Hit the web for your ISO files
For the Firefox users, I’d recommend using a multi-threaded downloader with MD5 verification like ‘DownThemAll’
Once the files are downloading (and they’ll take awhile as everyone hits the servers initially (trying a torrent may help), head on to the next step… Making your USB bootable
Grab Unetbootin for your OS for a really easy way to create a bootable USB drive
Insert your USB stick, double check where it’s loaded then create!
On your EEE 701
Because of the native resolution of the original EEE, a number of dialogue boxes don’t fit so well on the screen. This is mostly only a hassle during the installation as, afterward, you should be able to hold down the <Alt> key while click-dragging the window you want to see the bottom of.
If you have an external monitor available, connect it and change the screen settings to display a more reasonable resolution, larger than the crippling 800×400 of the native 701 🙂
If you do not have an external monitor available, don’t panic – we can simply use the keystroke navigation as detailed below
Ubuntu Install (First Screen)
Press <Alt> + <F> (Forward)
Welcome Screen
Choose your language then <Alt> + <F>
TimeZone / Where are you
Select your location
<Alt> + <F>
Keyboard Layout
This should detect fine so…
<Alt> + <F>
Prepare Disk Space
To install to 4GB SSD (This will delete EVERYTHING ON THE DISK and install from a blank partition)
<Alt> + <E>
<Alt> + <F>
Partitions will calculate
For a Custom Install (to use SDHC card in a EEE for instance)
<Alt> + <S> (to Specify partitions)
<Alt> + <F>
Setup partitions as you wish
I chose to use /dev/sdc (the SDHC card) creating a Primary partition of [Full Size of Storage minus Amount of installed RAM (for swap) ]
Set mount point to ‘/’ and use the ext4 file system
Create a logical partition using the rest of available disk as swap (which should be size as the amount of RAM in your system)
<Alt> + <F>
Partitions will calculate
Who are you- Obvious really:
Your Name <Tab>
Login/Username <Tab>
Password <Tab>
Password Verify <Tab>
Device Name<Tab>
Choose your Login type
“Require My password” <Alt> + <M> – Default
“Login Automatically” <Alt> + <L> or
“Require my password to login and Decrypt Home folder” <Alt> + <R>
<Alt> + <F>
Summary
Last chance to check all your selections
Alt + I (to Install)
And now the installation will start…
At the end of the installation process, you will be prompted to remove the install media (USB drive) and reboot the machine.
The following guide will take you through installing VMWare Server 2 on a minimal install headless Ubuntu v9.04 (Jaunty) Server. For a step by step on setting up the minimal server, read the article I posted here.
Getting the Pre-requisite Packages
First up, you will need to SSH into your server, and paste in the following command to install some additional packages which allow for the changes required to the kernel and the building of the VMWare server.
Once the extra packages are installed, you will need to grab the TAR ball from the VMWare site, and drop it into the directory where you wish to run your VMs from. For me, I’ve chosen to keep them under my users home directory in a directory called (imaginativly) ‘VM’. The following commands will make the directory ‘VM’ under your users root directory, then change to that directory:
mkdir ~/VM
cd ~/VM
From the PC you are using to SSH to the server, open a browser and visit the VMWare Server page from here you will need to download the server which will require you to create a VMware account, and login so that a licence key can be emailed to you.
Once logged in, you will be directed to the download page containing all the binaries for VMware Server.
Download the relevant TAR image for your architecture and linux version to your local machine, and do an MD5 checksum to make sure it arrived intact.
There is also a patch which you will require, you will need a login to the Ubuntu Forums however, to access the file below:
From here, transfer the TAR and the patch file in whatever way works best for you. If you followed my server build guide and installed the optional SAMBA extensions, you should be able to easily open the home directory on your server via a Windows network share – or similar for you particular operating system.
Running the Installer
Back to our SSH session now, unpack the patch into your “~/VM/” directory, then extract the VMware Server TAR ball and run the installer:
tar xvfz VMware-server-*.tar.gz
cd vmware-server-distrib
sudo patch ./bin/vmware-config.pl ~/VM/vmware-config.pl.patch.txt
sudo ./vmware-install.pl
Accept the default options (there are a LOT of them) throughout the installation and allow the installer to build any modules or kernels it needs to during the setup.
Choose the Administrative User
When prompted for the name of the current administrative user, select YES and type in YOUR user name (otherwise it’ll use root)
Select the Directory to Store the Virtual Machines
When prompted for the directory to store your virtual machine files, type in /home/[YourUsername]/VM/Virtual Machines and allow the installer to create the directory
Entering the Serial Number
Next you will be prompted for the serial number which should have been emailed to you for your VM Server installation, simply copy out of your email and paste into the SSH window.
Back to selecting the default values now until you are returned to the prompt.
Just in case things didn’t go well
If you think you may have made a mistake in the configuration, you can easily re-run the configuration tool by typing:
sudo /usr/bin/vmware-config.pl
If you REALLY made a hash of it, you can always remove the installation by typing:
sudo /usr/bin/vmware-uninstall.pl
and start again 🙂
Accessing the VMServer Console
After you installation sucessfully completes you will be returned to the prompt in your SSH session. That’s it – you’re done. All you need to do now, is attach to the VM Server console via your browser by typing in the address of your server box which will look something like this:
Read the documentation, and start setting up some Virtual Machines, or download any useful looking Virtual Appliances that catch your eye from the appliance marketplace.
Note: If you experience issues with the web console appearing to ‘hang’ ensure that you have loaded the lastest Java Runtime Environment (JRE) – get it here.
This article will address the base (minimal) build that I’ve been using while trying out a number of Virtual Environments for use in my home network. I’ve chosen to use an Ubuntu Server v9.04 (Jaunty) as my base OS – partiallybecause I use a lot of Ubuntu machines, but mainly – because it’s a popular choice with a very supportive community behind it who are all too happy to help others who get into difficulties.
Getting the Software & Burning the Disc
First things first, get yourself over to the Ubuntu Server Download page and get the relevant .iso image for your computers architecture. Because I’m installing on a Shuttle XPC Sn95G5, I’ll be going with the 64bit version.
I’ve been playing with a few VMs as I try to figure out a new infrastructure for our office, and as part of this I’ve taken a particular shine to CentOS as a minimal build for my virtual servers. I then decided I wanted to get a few sandbox environments running with desktop software and, well.. that’s where the fun began!
From Google, and the various Linux community forums, this is a fairly common problem so, in an effort to be more useful than those who simply post a link to the GRUB man page, or an article which spells out how dumb it is to install Windows AFTER Ubuntu – I thought I’d drop my experience and the resolution here – I’m bound to need it at some point in the future.
I was having a chat to some people on Friday on why some devices were successful and some were… not.
This post has been far too long in coming – mainly because some miscrent broke into my car and stole a bunch of my gear – including the charger for my 6 hour old ASUS EEE 1005PE. The replacment charger took over 40 days to source (that’s what you get for living in New Zealand).
This article will address the base (minimal) build that I’ve been using while trying out a number of Virtual Environments for use in my home network. I’ve chosen to use an Ubuntu Server v9.04 (Jaunty) as my base OS – partiallybecause I use a lot of Ubuntu machines, but mainly – because it’s a popular choice with a very supportive community behind it who are all too happy to help others who get into difficulties.