« June 2007 | Main | September 2007 »
July 27, 2007
Solve your samba problems in Feisty Fawn
sudo vim /etc/samba/smb.conf
search for a line that has 'msdfs proxy' and comment it out
sudo /etc/init.d/samba restart
you're welcome
Posted by dottie at 7:22 PM | Comments (0) | TrackBack
July 17, 2007
solo SCRUM scrap?
It seems Microsoft has developed a tool to allow you to implement SCRUM. Is that my little project finished?
possibly... I have to give it a gander yet....
The little guy (well...) gets crushed again!
Posted by dottie at 8:17 PM | Comments (0) | TrackBack
July 15, 2007
What are you doing for the next 6 months?
Justice Grey has publicly committed to reading 27 developer books in the next 6 months
It's a big undertaking and the question has been asked - when will he get the time to do some programming?
I guess he has some funding!
Anyway, at first glance, the books I would like to get from his list are:
- Beyond Code - Setty
- Refactoring: Improving the Design of Existing Code - Fowler
- Pragmatic Programmer - Andrew Hunt
I would have to research the rest of the list a bit but I think definitely an algorithm book, more patterns books and more UML will be in my near-future reading list.
It's strange that once you start learning about all this stuff you actually want to learn more - since I started grokking OO and patterns my view of programming has changed immensely. I am actually looking forward to the future and previously hairy application analysis have been simplified.
Looking forward to the next 6 months - the first three are being taken up by my first professional coding role and the following three - who knows!
Looking forward to the positive uncertainty.
Posted by dottie at 2:37 PM | Comments (2) | TrackBack
July 14, 2007
TortoiseSVN for Linux
Please!
Someone write a decent SVN client for Linux!
Posted by dottie at 10:08 PM | Comments (0) | TrackBack
Multiple identity crisis - selecting a different identity when using ssh for different tasks to the same server
If, like me, you have to connect to a linux server to get a console and the same server to access subversion then you might hit a snag. Accessing the server as normal with ssh wll result in a console connection - but if you use the same identity it won't be possible to access subversion - and vice versa.
The key is to use the config file of your local ssh installation. I'll presume here that you have your ssh setup to allow you to connect to your server and use the console.
I'll describe how to setup a new identity that will allow you to connect to subversion using the same identity on your local machine. This is for a linux machine. If you use Windows the situation is much easier - just use puTTY and load up the public key files with your saved profiles.
It took me a while to figure out but its fairly straightforward when you get it all together.
From your local machine ssh into the server as normal. Then go to the .ssh folder in your home directory (it will be hidden normally - to see it in a listing type ls -la)
cd ~/.ssh
Then first off, generate a new rsa key:
ssh-keygen -f yournewidentity
Don't forget to add a passkey, and don't forget the passkey!
The you will need to add this to your authorized_keys file. Before you do that though, make a backup of your file:
cp authorized_keys authorized_keys_backup
ok, now you can mess up all you want and you will still be able to restore your file and log in normally
cat yournewidentity.pub >> authorized_keys
Now edit the file (you can also use vi, nano or whatever takes your fancy)
vim authorized_keys
you will see the contents of the public key file of your new identity at the bottom of the file. Copy and paste this at the start of the newly-cat'd public key file content (leaving a space between the end of the command below and the start of the public key file content. (You may need to remove the spaces after each comma - I had to put them in here to allow the full command display properly)
command="svnserve -t -r /path/to/your/svn/repository --tunnel-user=your_normal_console_login_username", no-port-forwarding, no-agent-forwarding, no-X11-forwarding, no-pty
All that should be on one line in your authorized_keys file with the contents of the public-key on the same line. Save the file and exit the editor.
What you have done is to tell the server that when you log in and provide it with the new key, it will open a pipe to svnserver instead of logging you in to the console. Sweet!
Nearly there now, we just have to configure your local machine. But first you will have to get the private key of your new identity from the server to your local machine - FTP is the obvious answer.
When you have copied the key to your machine you will have to change the permission of the file:
chmod 600 yournewidentity
Once you have copied over the private key, on your local machine, edit the ~/.ssh/config file.
Add the following:
Host dummy_subversion_hostname
HostName server_hostname_or_IP
IdentityFile ~/.ssh/yournewidentity
Port 22
The Port is only necessary if you have configured your SSH server to listen on a different port. Save and exit and you are nearly done!
Now try and connect to your subversion server
svn info svn+ssh://dummy_subversion_hostname
SSH should ask to store the host key and then you should be prompted for your passkey and then subversion should cough up some info.
You are done.
p.s. Another alternative, and probably safer, is to generate the keyfile on your local machine and then copy only the public key to your server, leaving the privte key file secure on your machine.
Posted by dottie at 8:51 PM | Comments (0) | TrackBack
SCRUM solo - still vapour...
I've been readin up a bit on the SCRUM process and I think it might be possible to build a tool that forces you to look at your project from different viewpoints in order to set your goals and report to yourself successfully and possibly even help with rationalising the development process.
If you have a task which is constantly going over deadline then the system can focus on that and ask questions to help you frame your thoughts on the task objectively.
Then key to the system would be the developer - they have to want to use the system and be comfortable thinking outside their daily concerns.
I just might work dammit!
Now, more study...
Posted by dottie at 12:49 PM | Comments (0) | TrackBack
Meet the stack of books that has kept me busy for the last while
Not even a quarter of the way through this monster...
The list from top to bottom:
- C.J. Date - Database in depth (status : skimmed)
- Mike Gunderloy - From Coder to Developer (status : half way through)
- Onion & Brown - Essential ASP.NET 2.0 (status : halfway through)
- LIberty and Hurwitz - Programming ASP.NET (status : reference)
- MCTS - .NET Framework 2.0 Training kits (status : cracked)
- Cwalina & Abrams - Framework design guidelines (status : dipping)
- Onion - Essential ASP (status : half-read)
- Fowler - Patterns of Enterprise Application Architecture (status : bits read and lots browsed
The best books of the lot are: the two Onion books, Gunderloy, and Fowler.
And this doesn't include the Ruby books I want to get my head around too!
Posted by dottie at 12:46 PM | Comments (0) | TrackBack