<?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>Jiramot.info &#187; ubuntu</title>
	<atom:link href="http://www.jiramot.info/tag/ubuntu/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jiramot.info</link>
	<description>me?.note.each{ println it }</description>
	<lastBuildDate>Fri, 30 Jul 2010 19:57:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Setting up a Subversion Server on Ubuntu Gutsy Gibbon server</title>
		<link>http://www.jiramot.info/setting-up-a-subversion-server-on-ubuntu-gutsy-gibbon-server</link>
		<comments>http://www.jiramot.info/setting-up-a-subversion-server-on-ubuntu-gutsy-gibbon-server#comments</comments>
		<pubDate>Sun, 31 Jan 2010 09:11:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://www.jiramot.info/?p=496</guid>
		<description><![CDATA[Setting up a Subversion Server on Ubuntu Gutsy Gibbon server
 All the required packages are available in the Ubuntu repositories.
Installing Subversion
Use apt-get:
sudo apt-get update
sudo apt-get install subversion

Creating a Repository
Let&#8217;s say you want your repository to be in /var/svn/repos, type in these commands:
cd /var
sudo mkdir svn
sudo svnadmin create /var/svn/repos

In order to control who has access to [...]]]></description>
			<content:encoded><![CDATA[<h2>Setting up a Subversion Server on Ubuntu Gutsy Gibbon server</h2>
<p><!-- start main content --> <!-- google_ad_section_start -->All the required packages are available in the Ubuntu repositories.</p>
<h3>Installing Subversion</h3>
<p>Use <tt>apt-get</tt>:</p>
<pre>sudo apt-get update
sudo apt-get install subversion
</pre>
<h3>Creating a Repository</h3>
<p>Let&#8217;s say you want your repository to be in <tt>/var/svn/repos</tt>, type in these commands:</p>
<pre>cd /var
sudo mkdir svn
sudo svnadmin create /var/svn/repos
</pre>
<p>In order to control who has access to the repository we will now add a user who will own the repository files. Adding a user also adds a group with the same name.</p>
<pre>sudo adduser svn
</pre>
<p>Now make it impossible for anyone to log in as this user by editing <tt>/etc/passwd</tt> to set the <tt>svn</tt> user shell to <tt>/bin/false</tt>. Do this using the <tt>vipw</tt> command.  Find the line which starts <tt>svn</tt> (it should be the last line in the file) and change <tt>/bin/bash</tt> to <tt>/bin/false</tt>.</p>
<p>Now change the ownership of the repository files.</p>
<pre>sudo chown -R svn.svn svn
</pre>
<p>In order for someone to be permitted to use the repository they must be added to the <tt>svn</tt> group. My user name is <tt>martin</tt> so I am going to add myself to the <tt>svn</tt> group.</p>
<pre>sudo vigr
</pre>
<p>Go to the end of the file and add your user name to the end of the line which starts <tt>svn</tt>.  The end of the file should look similar to this:</p>
<pre>admin:x:110:martin
svn:x:1001:martin
</pre>
<p>Now set up an <tt>ssh</tt> server, clients will connect to this machine using <tt>ssh</tt>:</p>
<pre>sudo apt-get install openssh-server
</pre>
<p>The repository can now be accessed using the <tt>svn+ssh</tt> protocol. Test this as follows:</p>
<pre>svn co svn+ssh://<em>username</em>@<em>machinename</em>/var/svn/repos
</pre>
<p>You will be prompted about the RSA fingerprint of the server and asked for your password. You should end up with a directory called <tt>repos</tt> which is a working copy of your new repository.</p>
<p>As things stand you will be asked for your password every time you connect to the machine which is rather tedious. You can also authenticate with <tt>ssh</tt> by using a public/private key pair. If you are using a Windows client then install PuTTY and use PuTTYgen to create a key. Don&#8217;t forget to save the public and private key files. There is a text box at the top of the PuTTYgen window labeled &#8220;Public key for pasting into OpenSSH authorized_keys file&#8221;, you need to put the line of text in that box into a file called <tt>.ssh/authorized_keys2</tt> in your home directory on the server. Set the permissions on the files like this:</p>
<pre>chmod 0700 .ssh
chmod 0600 .ssh/authorized_keys2
</pre>
<p>On the Windows machine fire up pageant (another program which comes with PuTTY) and load your private key. You should now be able to connect to the server without being asked for a password. I prefer to disable password based access to the server by editing <tt>/etc/ssh/sshd_config</tt> and adding the line <tt>PasswordAuthentication no</tt>.</p>
<p>On a Linux client use <tt>ssh-keygen</tt> to create the key pair.</p>
<h3>Apache</h3>
<p>Subversion also supports the WebDAV protocol, to set this up Apache is needed. I am assuming that you installed Ubuntu as a LAMP server.</p>
<pre>sudo apt-get install libapache2-svn
</pre>
<p>The following isn&#8217;t recommended for a real implementation as we are going to add to the default web files. It would be far better to create a new virtual host, but that is a subject itself.</p>
<p>Ubuntu has a file for each active virtual host in <tt>/etc/apache2/sites-enabled</tt>, after installing Ubuntu server there will be a file called <tt>000-default</tt> in the <tt>sites-enabled</tt> directory and this is the file we are going to edit.</p>
<pre>cd /etc/apache2/sites-enabled
sudo vi 000-default
</pre>
<p>In the  directive add:</p>
<pre>    &lt;Location /svn/repos&gt;
      DAV svn
      SVNPath /var/svn/repos
    &lt;/Location&gt;
</pre>
<p>Then execute this command:</p>
<pre>sudo /etc/init.d/apache2 force-reload
</pre>
<p>You should now be able to see the repository at the URL <tt>http://<em>machinename</em>/svn/repos</tt>.</p>
<h3>Securing Web Access</h3>
<p>Add this to the location directive:</p>
<pre>      AuthType Basic
      AuthName "Subversion Repository"
      AuthUserFile /etc/apache2/passwords
      Require valid-user
</pre>
<p>Now add a user name and password to the Apache password file:</p>
<pre>sudo htpasswd -cb /etc/apache2/passwords martin dgjan08
</pre>
<p>And another forced reload:</p>
<pre>sudo /etc/init.d/apache2 force-reload
</pre>
<p>Now if you visit the repository URL you will have to enter a valid user name and password.</p>
<h3>Trac</h3>
<p>Trac is a ticketing system and Wiki which integrates very well with Subversion. Start by installing Trac:</p>
<pre>sudo apt-get install trac python-setuptools libapache2-mod-python enscript
</pre>
<p>Now create a Trac database:</p>
<pre>sudo mkdir /var/www/trac
sudo trac-admin /var/www/trac/repos initenv</pre>
<p>Then answer its questions, take the defaults, our Subversion repository is in <tt>/var/svn/repos</tt>.</p>
<p>Now to get Apache to run Trac.</p>
<pre>cd /var/www
sudo chown -R www-data.svn trac
</pre>
<p>Head back to <tt>/etc/apache2/sites-enabled</tt> and edit <tt>000-default</tt> again, adding this:</p>
<pre>    &lt;Location /trac/[[:alnum]]+/login"&gt;
      AuthType Basic
      AuthName "Subversion Repository"
      AuthUserFile /etc/apache2/passwords
      Require valid-user
    &lt;/Location&gt;

    &lt;Location /trac&gt;
      SetHandler mod_python
      PythonInterpreter main_interpreter
      PythonHandler trac.web.modpython_frontend
      PythonOption TracEnvParentDir /var/www/trac
      PythonOption TracUriRoot /trac
    &lt;/Location&gt;
</pre>
<p>And then run this again:</p>
<pre>sudo /etc/init.d/apache2 force-reload
</pre>
<h3>Building Trac from source</h3>
<p>If you want the most recent version of Trac (0.10.4) then you will have to build and install it. Do the following:</p>
<pre>sudo apt-get remove trac
wget http://ftp.edgewall.com/pub/trac/trac-0.10.4.tar.gz
tar zxf trac-0.10.4.tar.gz
cd trac-0.10.4/
sudo mkdir /usr/local/trac
sudo python setup.py install --prefix=/usr
</pre>
<p>The rest of the instructions are the same.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jiramot.info/setting-up-a-subversion-server-on-ubuntu-gutsy-gibbon-server/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix Intel Graphics on Ubuntu 9.04 &#8211; Enabling Visual Effects</title>
		<link>http://www.jiramot.info/fix-intel-graphics-on-ubuntu-9-04-enabling-visual-effects</link>
		<comments>http://www.jiramot.info/fix-intel-graphics-on-ubuntu-9-04-enabling-visual-effects#comments</comments>
		<pubDate>Sat, 18 Jul 2009 21:40:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://www.jiramot.info/?p=336</guid>
		<description><![CDATA[When I installed Ubuntu 9.04, I noticed something missing that I&#8217;ve been accustomed to for some time now; those cool Compiz effects were gone. I noticed this when I ran Ubuntu from the Live CD but I thought maybe it was a bug in the Live CD or maybe my CD was scratched. Well the [...]]]></description>
			<content:encoded><![CDATA[<p>When I installed Ubuntu 9.04, I noticed something missing that I&#8217;ve been accustomed to for some time now; those cool Compiz effects were gone. I noticed this when I ran Ubuntu from the Live CD but I thought maybe it was a bug in the Live CD or maybe my CD was scratched. Well the problem actually ended up not being a problem at all. It was actually because of a &#8220;safety precaution&#8221; added by the developers of Ubuntu.</p>
<p>The developers of Ubuntu decided to blacklist the Intel graphics cards from using Compiz as there seems to be a couple of hiccups that needs to be fixed such as some random freezes and hangs. Even though the team is going to release an update that will remove the blacklist when things are all fixed, I know people are still interested in removing the blacklist themselves manually.</p>
<p>Well no worries. Removing the blacklist is dead simple, but remember; there&#8217;s a blacklist for a reason. If you still wish to remove the blacklist then copy the text below in the Terminal:</p>
<blockquote><p>
mkdir -p ~/.config/compiz/ &#038;&#038; echo SKIP_CHECKS=yes >> ~/.config/compiz/compiz-manager
</p></blockquote>
<p>Now you need to enable the visual effects by right clicking on your desktop, clicking &#8220;Change Desktop Background&#8221; in the menu, going to the &#8220;Visual Effects&#8221; tab and choosing either normal or extra visual effects.</p>
<p>Removing the blacklist has not caused any crashes on my computer but if it has caused problems on your computer or you simply wish to wait for the proper update to remove the blacklist then re-enabling the blacklist is also very simple to do. Just type in the text below in the Terminal:</p>
<blockquote><p>
rm -rf ~/.config/compiz/
</p></blockquote>
<p>Remember to disable visual effects before doing this as it may cause some problems.</p>
<p>source <a href="http://www.learningubuntu.com/articles/fix-intel-graphics-ubuntu-904-enabling-visual-effects">http://www.learningubuntu.com/articles/fix-intel-graphics-ubuntu-904-enabling-visual-effects</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.jiramot.info/fix-intel-graphics-on-ubuntu-9-04-enabling-visual-effects/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
