Some new screenshots from my laptop!!

I hope you like them. GTK theme is Nova-Lime (a nice alternative could be Murinna Mire Lime). Emerald theme is my own (mixed up from others)  and fonts are Heldastry Regular FT and Mulder Handriting Bold.


~# I was thinking for sometime now, to create a personal SVN server to use for my scripts and documents. More like a place holder that I would be able to have some kind of version control. So here is a short how to install and setup svn and trac (I just like its source browsing capabilities) without the need to install apache2 as well.

Subversion using svnserve.

Installing subversion & configuring repository.

1. Install subversion.

2. Create & initialize your svn repository:

  • mkdir $HOME/myrepo
  • svnadmin create $HOME/myrepo
  • Change the access rules for your repo:
    • vi $HOME/myrepo/conf/svnserve.conf & add/edit according to your needs:
      • realm = My Repository
      • anon-access = read
      • auth-access = write
      • password-db = passwd

3. Start svnserve:

  • sudo /usr/bin/svnserve -d -r $HOME/myrepo
  • if you don’t want to start svserve each time you boot, you may want to add a line like the above in “/etc/conf.d/local.start” (or rc.local if your are on Ubuntu).

Start using your repository

1. Import your your code:

  • mkdir ~/Scripts
  • touch ~/Scripts/script1.sh (or put your scripts in the directory).
  • svn import ~/Scripts -m “Initial Import” file:///$HOME/myrepo

2. List files in your repository:

3. Commit your changes:

  • cd into your working directory
    • cd ~/Scripts
    • commit any changes you have made
      • svn ci -m “first commit”

4. Add or delete new files to your repository:

  • Under your working directory:
    • svn add new_script.sh -m “New file Added”
    • svn delete old_script.sh -m “Old file deleted”

5. Check out your svn repository into a new directory:

  • create a new directory and cd into it
  • svn co file:///$HOME/myrepo

Do you use Cisco VPN client?? (I do 🙂 ) Do you also use a kernel 2.6.19 or later ??  Then apply this patch to be able to compile the needed modules.  Thanks to this guy I saved my self from a lot of hours searching in google for compilation errors.


If you want some screen shots from my current Gentoo system, here they are:

& some info –> GTK Theme: Nova Lime, Metacity: Calla (modified to match GTK theme), Normal Fonts: Heldastry Regular FT, Metacity Fonts: Mulder Handriting Bold and of course compiz & screenlets

Hope you like them …


Hehe … after a long long time I found the time to install Gentoo at my work Laptop.

Following CONRAD Install V400 Recharged Flying Colors guide from gentoo forums I had my laptop up and running in no more than a day and a half and I must say that I was impressed both by the time needed to set-up my system (I regret to admit that Intel Centrino Duo is doing quite a good job vs. my older AMC 3400+) and the responsiveness of the system when I finally boot into my Gnome!!

The only thing that troubled me (and still does) is ext4. Using Small Gentoo x86 r9 live CD I formatted my root (/) & home (/home) partions with:

  • mke2fs -j /dev/sdxy and mount them with
  • -t ext4dev -o noatime,extents,delalloc

Unfortunately the first time that fsck was executed during boot time, I got a huge amount of errors regarding inodes having EXTENTS Flag on but not being into extent format. However as soon fsck had finished I was still able to boot my machine Now after reformating my root partition ( I had kept a backup of / ) I am using 2.6.21-viper1 sources but I am still facing problems from time to time; whenever my / parttion is not unmounted cleanly kernel panics and I need to boot from the live cd and fsck the disk. This hopefully does not happen often!! Anyway its not that bad like it may sound!! To mention here that ext4 seems (this is my feeling) faster than ext3!

I ll keep posting about ext4 untill things get a bit more stable!!


I know that all over the net you can find articles and posts about how nice is this cute app. I wanted however to mention a small tip troubled me for a while (couple of minutes 😛 ) before figure it out. In order to preserve your scrollbar, add to your ~/.screenrc file the following entry:

termcapinfo xterm ti@:te@

Also a couple of reference just in case …

Very nice Screen FAQ

Visual Screen tutorial

Where I got my .screenrc from …

I like this app alot!!!

~


Hi,

After a long long time back to posting with some recent OB3 screenshots.

Hope you like!!

Ubuntu Edgy:2.6.17-11-generic , ob3 (svn), ob3 theme: Cuttooth, gtk2 theme: Cuttooth.


I am back ~

11Jun06

Hi out there!! There has been almost a month (maybe more) since my last post, but i had some real trouble the past few days 😦 .Anyway life goes on, so must I, so expect new posts and new interesting stuff pretty soon.


Wine Doors

27Apr06

    Among other things lately i 've been busy contributing to a very interesting project called "Wine Doors".

    As u can see at the project's page  Wine Doors is about obtaining, installing, uninstalling and working around the caveats associated with wine applications. Wine  Doors  is intended to  be a replacement for  the various wine utilities  that  are out there.  Anyway u can find more info  at the project's page.

    Also keep in mind that we are looking for developers to join the team. Ty .. I 'm out 🙂


One of the annoyances i 've encounter during my linux experiance with a couple of distros, is when i want to install a program from sources. To be more specific the problem is when i want to Uninstall such a program and the author hasn't provided a make "uninstall" rule.

So googling aroung for a solution i 've found latelly some workarounds which might proved interesting.

  • one quick & dirty sollution is to remove all the files by hand; Usually the files are installed into ' /usr/local ' & not into ' /usr ', so it's easy to just find them and remove them yourself. Anyway thats what i used to do up to now!
  • another, more elaborated, solution is to use a program called CheckInstall which wil supposedly create .tgz, .deb, or .rpm file from a source install so you can manage it with your system's package manager. I haven't yet test it thoroughly, but this sounds quite interesting.
  • last but not least is to run 'make -n install' (or 'make -n install > install.txt') before the actuall installation. This way u can actually examine what files r going to be installed and remove them by hand in the future.

Anyway thats it for now … to be continued …