sudo touch /forcefsck

To restore the gnome panel to defaults:

gconftool-2 --shutdown
rm -rf ~/.gconf/apps/panel
pkill gnome-panel

If clicking on any file location from say google chrome download list or other links gives an error the requested location is not a folder:

sudo apt-get remove exo-utils

#make a working dir
mkdir sandbox
cd sandbox
#checkout
svn co svn://svn-repo-machine/repo/path myproject --username myusernameatsvnserver
#go to work on items
cd myproject
#pull latest from server
svn up 
#queue a file for addition
svn add newfile.c
#queue for deletion
svn delete anoldfilewedontneed.c 
#get the info on what is different in your local vs server
svn status 
#list commit comments on a file
svn log AFILESOMEONECHANGED.c 
#commit one file. * will commit all that changed.
svn ci -m "Edited this file for ..." filethatgotchanged.c 

Now, configure vim as the svn diff tool.

 
cd ~/Dropbox
mkdir -p gitroot/research.git && cd !$
git --bare init
 
cd ~/Projects
git init
git remote add dropbox file://$HOME/Dropbox/gitroot/research.git
git add testfile.txt
git commit -m "initial"
git push dropbox master
 
ssh anothercomputer
cd ~/Projects
git clone -o dropbox file://$HOME/Dropbox/gitroot/research.git
cd research
ls >> testfile.txt
git commit -m "just testing"
git push dropbox master
git pull dropbox master

For the first computer, once you fill the bare repo with some stuff, you can delete the folder and do a clone like how you did with the second computer.

• I have an OpenBSD server account (no root though)
• I don't want to run any additional daemon process or expose it via http
• I can download and compile source if it can be installed as a non root account
• Transport must be via SSH
• I don't need GUI tools, speed should be reasonable

Tried Mercurial, Darcs, Bazaar and Git. Fossil is also a great tool that provides wiki, version control and ticket management. Darcs is the easiest, but for some reason, extremely slow. Finally chose Git. Download and compile was easy. Read top 3 lines in the INSTALL file in source distribution for steps. Rest of the steps explain how I set it up. Note that this may not be the best possible Git workflow. Merely that it works for me. Note that I've installed git in ~/software/git.

If you are a fitness freak, don't bother. I am talking about 5km as a goal - if you routinely do 15km+, you might find this quite boring.

• Get a Unix/Linux machine that you've an account and that supports SSH.
• Create a directory, say /home/loginid/repository
• On your Windows machine, download pageant.exe and puttygen.exe (at a minimum) from PuTTy site.
• Start puttygen.exe, generate your private and public key pair. Save private key somewhere. C:\Documents and Settings\\.ssh\id_rsa is a good choice. Exit puttygen.exe.
• In your server, make a .ssh directory, create a new file called authorized_keys, paste the public key into that file without any line breaks.
• Start pageant.exe. Right click on the icon (terminal with a hat) on the system tray, add key and choose the private key file.
• Download and install Bazaar Windows version.
• Start it Bzr in command line.
• Create the remote repository like bzr init sftp://username@remote/home/loginid/repository
• Create a local directory, create a repository there too.
• Add some files to local repository.
• When you want to push it up to remote, do bzr push sftp://username@remote/home/loginid/repository

For more info, read Bazaar doc.

Why is it insecure? When you do a GET all the parameters are in the URL, in plain text. And the URL gets stamped in your browser history, web server access logs (we may be able to assume that the server is reasonably secure) and more scarily, in the logs of any proxy servers that are in the route.

In 1995, I got into a data warehouse project and all the ETL was through some bunch of shell utilities followed by sql*loader. This certainly would've helped!

Just a personal preference - I don't prefer using any of the Tortoise*GUIs. GUI as such is fairly nice, but I don't generally like installing shell extensions on Windows. Ideal solution for me would've been the ability for any of these to init a repository on a remote filesystem by SSH - couldn't find it out though.

assoc .otl=outliner
ftype outliner=c:\tools\vim\vim72\gvim.exe --remote-silent "%1"