<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Craig Mayhew's Blog &#187; Ubuntu</title>
	<atom:link href="http://www.craigmayhew.com/blog/tag/ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.craigmayhew.com/blog</link>
	<description></description>
	<lastBuildDate>Sun, 29 Jan 2012 21:51:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Chroot in Ubuntu</title>
		<link>http://www.craigmayhew.com/blog/2010/03/chroot-in-ubuntu/</link>
		<comments>http://www.craigmayhew.com/blog/2010/03/chroot-in-ubuntu/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 06:43:17 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Chroot]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=1046</guid>
		<description><![CDATA[If you ever manage to damage your ubuntu install so badly that it won&#8217;t boot (as I recently did when trying to remove the gnome GUI) then boot from a LiveCD and then open up a terminal.
Type the following commands:
change to the media directory (where our drives should be)
# cd /media
Create a new directory called [...]]]></description>
			<content:encoded><![CDATA[<p>If you ever manage to damage your ubuntu install so badly that it won&#8217;t boot (as I recently did when trying to remove the gnome GUI) then boot from a LiveCD and then open up a terminal.</p>
<p>Type the following commands:</p>
<p>change to the media directory (where our drives should be)<br />
# cd /media</p>
<p>Create a new directory called Ubuntu (We will use this to mount our boot drive too)<br />
# mkdir ubuntu</p>
<p>Mount the boot drive, you will need to replace X with the correct letter<br />
# mount /dev/sdaX /media/ubuntu</p>
<p>Mount some other required locations<br />
# mount &#8211;bind /proc /media/ubuntu/proc<br />
# mount &#8211;bind /dev /media/ubuntu/dev<br />
# mount &#8211;bind /dev/pts /media/ubuntu/dev/pts</p>
<p>Run chroot, using this command and we are now root as if we had booted from the boot drive and not the liveCD:<br />
# chroot /media/ubuntu</p>
<p>Your now in your Ubuntu system as root. If your unsure precisely why your system won&#8217;t boot then running an update is usually a good place to start. Good luck!<br />
# aptitude update</p>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2010/03/chroot-in-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The package vmware-server needs to be reinstalled, but I can&#8217;t find an archive for it</title>
		<link>http://www.craigmayhew.com/blog/2010/03/the-package-vmware-server-needs-to-be-reinstalled-but-i-cant-find-an-archive-for-it/</link>
		<comments>http://www.craigmayhew.com/blog/2010/03/the-package-vmware-server-needs-to-be-reinstalled-but-i-cant-find-an-archive-for-it/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 07:00:14 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[dpkg]]></category>
		<category><![CDATA[rpm]]></category>
		<category><![CDATA[Synaptic Package Manger]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=1042</guid>
		<description><![CDATA[I recently tried installing a .deb packagae I had made by converting an rpm. Synaptic package manager however errored and since then won&#8217;t open. Every time I started synaptic I was getting this error:
The package vmware-server needs to be reinstalled, but I can&#8217;t find an archive for it
This command solved it and will force the [...]]]></description>
			<content:encoded><![CDATA[<p>I recently tried installing a .deb packagae I had made by converting an rpm. Synaptic package manager however errored and since then won&#8217;t open. Every time I started synaptic I was getting this error:</p>
<p>The package vmware-server needs to be reinstalled, but I can&#8217;t find an archive for it</p>
<p>This command solved it and will force the removal of my incosistent package:</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
dpkg --remove --force-remove-reinstreq vmware-server
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2010/03/the-package-vmware-server-needs-to-be-reinstalled-but-i-cant-find-an-archive-for-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retrieve Drive UUIDs in Ubuntu</title>
		<link>http://www.craigmayhew.com/blog/2010/03/retrieve-drive-uuids-in-ubuntu/</link>
		<comments>http://www.craigmayhew.com/blog/2010/03/retrieve-drive-uuids-in-ubuntu/#comments</comments>
		<pubDate>Sat, 27 Mar 2010 14:20:48 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[UUID]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=1027</guid>
		<description><![CDATA[One easy command to retrieve all drive UUIDs.

ls -lF /dev/disk/by-uuid

]]></description>
			<content:encoded><![CDATA[<p>One easy command to retrieve all drive UUIDs.</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
ls -lF /dev/disk/by-uuid
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2010/03/retrieve-drive-uuids-in-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Greasemonkey scripts won&#8217;t update on Ubuntu</title>
		<link>http://www.craigmayhew.com/blog/2010/02/greasemonkey-scripts-wont-update-on-ubuntu/</link>
		<comments>http://www.craigmayhew.com/blog/2010/02/greasemonkey-scripts-wont-update-on-ubuntu/#comments</comments>
		<pubDate>Sun, 07 Feb 2010 20:11:00 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Guides/Fixes]]></category>
		<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Greasemonkey]]></category>
		<category><![CDATA[Linux Permissions]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=920</guid>
		<description><![CDATA[The usual reason for not being able to update the scripts is that your permissions are wrong in your Firefox folder. Your Grease Monkey scripts will be in your firefox folder. The default place for this is (please substitute {username} for your actual Ubuntu user name):

cd /home/{username}/.mozilla/firefox/gm_scripts/

You need to make sure you are the owner [...]]]></description>
			<content:encoded><![CDATA[<p>The usual reason for not being able to update the scripts is that your permissions are wrong in your Firefox folder. Your Grease Monkey scripts will be in your firefox folder. The default place for this is (please substitute {username} for your actual Ubuntu user name):</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
cd /home/{username}/.mozilla/firefox/gm_scripts/
</pre>
<p>You need to make sure you are the owner of this folder. This command will make sure you are. Again please substitute whats inside the {} brackets.</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
chown -R {username}:{usergroup} /home/{username}/.mozilla/firefox/gm_scripts
</pre>
<p>If that still fails to fix the problem, then you also need to make sure you have write permissions on your firefox settings folder.</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
chmod -R 755 /home/{username}/.mozilla/firefox/gm_scripts
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2010/02/greasemonkey-scripts-wont-update-on-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ZFS on Ubuntu</title>
		<link>http://www.craigmayhew.com/blog/2009/11/zfs/</link>
		<comments>http://www.craigmayhew.com/blog/2009/11/zfs/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 23:03:23 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[General/Techie]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[ZFS]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=647</guid>
		<description><![CDATA[Installation on Ubuntu 9.04
Filip Brcic is kindly providing Ubuntu packages for zfs-fuse.
To install zfs-fuse add the Filip Brcic&#8217;s launchpad repo to a source list.
sudo nano /etc/apt/sources.list.d/zfs-fuse.list
Add&#8230;
At the time of writing, the karmic version of this doesn&#8217;t work so keep the word jaunty in repositories and it should be ok.
deb http://ppa.launchpad.net/brcha/ubuntu jaunty main
deb-src http://ppa.launchpad.net/brcha/ubuntu jaunty main
Then [...]]]></description>
			<content:encoded><![CDATA[<p>Installation on Ubuntu 9.04</p>
<p>Filip Brcic is kindly providing Ubuntu packages for zfs-fuse.</p>
<p>To install zfs-fuse add the Filip Brcic&#8217;s launchpad repo to a source list.</p>
<p>sudo nano /etc/apt/sources.list.d/zfs-fuse.list</p>
<p>Add&#8230;<br />
At the time of writing, the karmic version of this doesn&#8217;t work so keep the word jaunty in repositories and it should be ok.</p>
<p>deb http://ppa.launchpad.net/brcha/ubuntu jaunty main<br />
deb-src http://ppa.launchpad.net/brcha/ubuntu jaunty main</p>
<p>Then update apt.</p>
<p>sudo apt-get update</p>
<p>Now install zfs-fuse.</p>
<p>sudo apt-get install zfs-fuse</p>
<p>CAVEATS:<br />
if you get this message then you need to run the command as root:<br />
connect: Permission denied<br />
internal error: failed to initialize ZFS library</p>
<p>zfs get compressratio</p>
<p>Further Reading:<br />
https://wiki.ubuntu.com/ZFS<br />
https://wiki.ubuntu.com/ZFS/ZPool<br />
http://www.lildude.co.uk/zfs-cheatsheet/<br />
http://blogs.sun.com/bonwick/entry/zfs_dedup</p>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/11/zfs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tell Ubuntu to avoid using SWAP partition with swappiness setting</title>
		<link>http://www.craigmayhew.com/blog/2009/10/tell-ubuntu-to-avoid-using-swap-partition/</link>
		<comments>http://www.craigmayhew.com/blog/2009/10/tell-ubuntu-to-avoid-using-swap-partition/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 07:00:53 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Guides/Fixes]]></category>
		<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[Swap Space]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Virtual Memory]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=476</guid>
		<description><![CDATA[By Default Ubuntu will move data in RAM onto the swap file/partition on the hard disk long before it runs out of memory. It will pick data that isn&#8217;t accessed often but this can still be an annoying slow down on the system. To prevent the over use of SWAP space and speed things up [...]]]></description>
			<content:encoded><![CDATA[<p>By Default Ubuntu will move data in RAM onto the swap file/partition on the hard disk long before it runs out of memory. It will pick data that isn&#8217;t accessed often but this can still be an annoying slow down on the system. To prevent the over use of SWAP space and speed things up all we need to do is change one setting&#8230; swappiness.</p>
<p>Swappiness can be set from 0 to 100. The default is 60 and the lower it is the more the computer will try to keep everything in RAM.</p>
<p>If you want to temporarily change the swappiness then run this command with desired swappiness level:</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
sudo sysctl vm.swappiness=10
</pre>
<p>Alternatively if you want the change to be permanent then edit this file:</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
sudo gedit /etc/sysctl.conf
</pre>
<p>Set swappiness to the desired level (in this case 1) by either modifying this line in the file &#8220;/etc/sysctl.conf&#8221; or if it doesn&#8217;t exist, add it at the end.</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
vm.swappiness=1
</pre>
<p>Reboot the computer for the change to take effect.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/10/tell-ubuntu-to-avoid-using-swap-partition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ubuntu Slow Boot: &#8220;ata8: SRST failed (error:-16)&#8221;</title>
		<link>http://www.craigmayhew.com/blog/2009/09/ubuntu-slow-boot-ata8-srst-failed-error-16/</link>
		<comments>http://www.craigmayhew.com/blog/2009/09/ubuntu-slow-boot-ata8-srst-failed-error-16/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 07:00:24 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Guides/Fixes]]></category>
		<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[SATA]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=424</guid>
		<description><![CDATA[Ubuntu has started being a little slow to boot, as it turns out one of the drives was the cause of this. During the boot up processes ubuntu would hang for a while and then spit out the following: &#8220;ata8: SRST failed (error:-16)&#8221;. It seems one of my drives wasn&#8217;t responding properly during boot up.
To [...]]]></description>
			<content:encoded><![CDATA[<p>Ubuntu has started being a little slow to boot, as it turns out one of the drives was the cause of this. During the boot up processes ubuntu would hang for a while and then spit out the following: &#8220;ata8: SRST failed (error:-16)&#8221;. It seems one of my drives wasn&#8217;t responding properly during boot up.</p>
<p>To fix this I tried:</p>
<p>- Disabling floppy drive in bios (This didn&#8217;t help, but I&#8217;m sure it will speed things up slightly as I don&#8217;t have a floppy drive)<br />
- Set the &#8220;IDE detect time out (sec)&#8221; to 0. It was originally 35. (This didn&#8217;t help. Be careful when changing this option if you are using IDE drives)<br />
- Unplugged the SATA cable from my DVD drive and plugged it back in again. (PROBLEM SOLVED!)</p>
<p>I imagine either my sata cable is slightly loose or dodgy and reseating it has sorted the problem. If the problem occurs again then I will replace the cable.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/09/ubuntu-slow-boot-ata8-srst-failed-error-16/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Cannot find or run the base session script. Running Gnome in failsafe session instead.&#8221;</title>
		<link>http://www.craigmayhew.com/blog/2009/09/cannot-find-or-run-the-base-session-script-running-gnome-in-failsafe-session-instead/</link>
		<comments>http://www.craigmayhew.com/blog/2009/09/cannot-find-or-run-the-base-session-script-running-gnome-in-failsafe-session-instead/#comments</comments>
		<pubDate>Mon, 28 Sep 2009 07:00:28 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Guides/Fixes]]></category>
		<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Gnome]]></category>
		<category><![CDATA[Linux Permissions]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=396</guid>
		<description><![CDATA[After logging into my Ubuntu 9.04 machine I&#8217;m greeted with the following message &#8220;Cannot find or run the base session script. Running Gnome in failsafe session instead&#8221;. The reason for this was I had messed up my permissions and the following fixed it:
After logging in and recieving the errors message press Ctrl-Alt-F1 to drop back [...]]]></description>
			<content:encoded><![CDATA[<p>After logging into my Ubuntu 9.04 machine I&#8217;m greeted with the following message &#8220;Cannot find or run the base session script. Running Gnome in failsafe session instead&#8221;. The reason for this was I had messed up my permissions and the following fixed it:</p>
<p>After logging in and recieving the errors message press Ctrl-Alt-F1 to drop back into command line. Then run the following:</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
Sudo chmod 755 /etc/gdm/Xsession
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/09/cannot-find-or-run-the-base-session-script-running-gnome-in-failsafe-session-instead/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Ubuntu Error &#8220;sudo: /etc/sudoers is mode 0640, should be 0440&#8243;</title>
		<link>http://www.craigmayhew.com/blog/2009/09/ubuntu-error-sudo-etcsudoers-is-mode-0640-should-be-0440/</link>
		<comments>http://www.craigmayhew.com/blog/2009/09/ubuntu-error-sudo-etcsudoers-is-mode-0640-should-be-0440/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 07:30:03 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Guides/Fixes]]></category>
		<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Linux Permissions]]></category>
		<category><![CDATA[Sudoers]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=398</guid>
		<description><![CDATA[If for whatever reason you change the permissions on your sudoers file you will get a similar error to &#8220;sudo: /etc/sudoers is mode 0640, should be 0440&#8243; whenever you try to run the sudo command. The problem is that because the permissions are wrong on the sudoers file, linux won&#8217;t let you run the sudo [...]]]></description>
			<content:encoded><![CDATA[<p>If for whatever reason you change the permissions on your sudoers file you will get a similar error to &#8220;sudo: /etc/sudoers is mode 0640, should be 0440&#8243; whenever you try to run the sudo command. The problem is that because the permissions are wrong on the sudoers file, linux won&#8217;t let you run the sudo command!</p>
<p>To get around this press &#8220;Esc&#8221; at the grub loader screen when linux is booting and enter into the latest recovery mode. Then select the option that allows you to drop into a command line as root and type </p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
chmod 0440 /etc/sudoers
</pre>
<p>Then reboot and your troubles should be solved!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/09/ubuntu-error-sudo-etcsudoers-is-mode-0640-should-be-0440/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Command to find the 10 largest files in linux</title>
		<link>http://www.craigmayhew.com/blog/2009/04/command-to-find-the-10-largest-files-in-linux/</link>
		<comments>http://www.craigmayhew.com/blog/2009/04/command-to-find-the-10-largest-files-in-linux/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 08:44:58 +0000</pubDate>
		<dc:creator>Craig Mayhew</dc:creator>
				<category><![CDATA[Linux/Ubuntu]]></category>
		<category><![CDATA[Command]]></category>
		<category><![CDATA[OpenSUSE]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.craigmayhew.com/blog/?p=83</guid>
		<description><![CDATA[The following command will list the top 10 largest files in your linux file system. I&#8217;ve confirmed it works on OpenSUSE and Ubuntu 8.04. Remember to run this command as root if you want to search the entire file system.

find / 2>/dev/null -type f -ls &#124; sort -k 7 -r -n &#124; head -10

]]></description>
			<content:encoded><![CDATA[<p>The following command will list the top 10 largest files in your linux file system. I&#8217;ve confirmed it works on OpenSUSE and Ubuntu 8.04. Remember to run this command as root if you want to search the entire file system.</p>
<pre style="border: 1px solid #FFFFFF; padding: 5px; overflow:auto;">
find / 2>/dev/null -type f -ls | sort -k 7 -r -n | head -10
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.craigmayhew.com/blog/2009/04/command-to-find-the-10-largest-files-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

