http://well.com/user/tux/Joels Blog2009-03-25T12:34:30ZJoel Westerberghttp://well.com/user/tuxtag:well.com/user/tux,2009-03-25:/blog/articles/xterm/Nice colors in xterm2009-03-25T12:34:30Z2009-01-07T06:51:03Z<p>Here’s a nice white on black color scheme for xterm, put this in your ~/.Xdefaults file</p>
<pre>
xterm*color0: #1a1a1a
xterm*color1: #ba8b8b
xterm*color2: #86af80
xterm*color3: #c6d01e
xterm*color4: #3c8ec4
xterm*color5: #9a70b2
xterm*color6: #9fc1cc
xterm*color7: #c6c6c6
xterm*color8: #71a3b7
xterm*color9: #e5505f
xterm*color10: #8cba87
xterm.color11: #e0d95c
xterm*color12: #5899c4
xterm.color13: #ad73ba
xterm*color14: #338eaa
xterm*color15: #f7f7f2
</pre>__EXCERPT__tag:well.com/user/tux,2009-03-18:/blog/articles/debian/Debian notes2009-03-18T07:34:51Z2009-03-19T13:45:54Z<p>Trying to grok an unknown package management system is daunting at first. Buut when you get your bearings it starts to get easier. Having played with debian packages for a day now I feel that it’s not as easy to work with as the gentoo ebuild system which I am used to, but it’s a lot faster to install the packages of course.</p>
<p>Some useful commands</p>
<p>Downloads a source package and unpacks it:<br />
apt-get source <package-name></p>
<p>Where are the binary packages kept when downloaded?<br />
/var/cache/apt/archives/*.deb</p>
<p>Unpack a .deb file:<br />
ar -x *.deb</p>
<p>Howto build a .deb package from source. Inside the main folder:<br />
dpkg-buildpackage</p>
<p>Howto build a .deb package from binary. Below the main folder<br />
dpkg -b <foldername></p>
<p>Install debian package directly<br />
dpkg -i package.deb</p>Setting up custom debian packages for simple deploymenttag:well.com/user/tux,2009-02-14:/blog/articles/adventures-with-ruby1.9/Adventures with ruby 1.9 yaml2009-02-14T11:08:02Z2009-02-14T12:30:17Z<p>Initial stuff: all my source files are in utf-8 and generates errors… what to do? add this to .profile did the trick:</p>
<p>export <span class="caps">RUBYOPT</span>=“-w -Ku”</p>tag:well.com/user/tux,2008-10-19:/blog/articles/vserver-bash-completion/Fixing bash completion for vserver2008-10-19T08:07:27Z2008-10-19T08:14:03Z<p>By default bash completion doesn’t work for linux vserver in gentoo. On the linux vserver pages there’s a bash completion script available for download but it doesn’t compile. I’ve put together a very simple bash completion script here that does only what I need most – expand on available vservers and the safe options.</p>
<p>On gentoo you need to emerge bash-completion first – but you already knew that didn’t you?</p>
<p>Here’s the source for my script /etc/bash_completion.d/vserver </p>
<pre>
_vserver()
{
local cur prev opts
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
opts="enter start stop restart chkconf status exec"
vservers=$(for x in `ls /vservers -1`; do echo ${x} ; done )
if [[ ${prev} == "vserver" ]] ; then
COMPREPLY=( $(compgen -W "${vservers}" -- ${cur}) )
return 0
else
COMPREPLY=( $(compgen -W "${opts}" -- ${cur}) )
return 0
fi
}
complete -F _vserver vserver
</pre>By default vserver TAB doesn't do anything. It's easy to correct this with a simple scripttag:well.com/user/tux,2008-08-09:/blog/articles/eyelids-are-getting-heavier/Eyelids are getting heavier2008-08-09T00:55:33Z2008-08-09T00:58:54Z<p>Channeling the talking moose: your eyelids are gettig heavier and heavier. You are getting sleeepy. Just want to fix the last stuff and publish this site now!</p>Channeling the talking moose: your eyelids are gettig heavier and heavier. You are getting sleeepy. Just want to fix the last stuff and publish this site now!