Sorry but I hate Dell laptops.
The business laptops that I have worked with over the years all had issues that were just a nightmare to deal with. That it is the wireless chipset that would get the laptop to crash because we were using Fortinet software to the latest bluetooth adventures.
I have been trying to get my apple wireless keyboard and trackpad to work with the work provided Latitude E6410 to no avail. I have read one site after another about the apple drivers that you need to extract from the boot camp material and how people resolved different issues. I have tried many times over the months and nothing ever worked. Different version of the drivers or different sequence of installation of the components.
Today, I decided that I did not trust the built-in bluetooth because other people at work were having issues with bluetooth headsets.
I disabled the bluetooth in the bios and plugged in my $5 tiny dongle I purchased months ago over the Internet. Very generic bluetooth dongle.
Tadam! Everything works now. I am using my keyboard and trackpad to post this.
All these months wasted on the below standard components that are in these Dell laptops. I am not surprised and I have one more reason to hate this Dell hardware. How can they sell so many with all these issues?
Found this great article on how to hack your way to do a SVN dump from a remote repo. I had never use the svnsync command but this allows you to make the remote repo a local one and you can easily use it to create your dump file. Very useful when you have lost admin access to the original server and you need to migrate to a new SVN server.
Quick command list:
- svnadmin create temprepo
- echo ‘#!/bin/sh’ > temprepo/hooks/pre-revprop-change
- chmod +x temprepo/hooks/pre-revprop-change
- svnsync init file://temprepo https://server/svn/origrepo
- svnsync sync temprepo
- svnadmin dump temprepo > dumpfile
Copy the dump file over to the new SVN server and on it:
- svnadmin load reponame < dumpfile
A quick word of warning because the UUID will change with this process so doing “svn sw” on existing working copy might prove to be challenging.
I had some problems installing the Cisco VPN client 4.8 on my Slackware 12.0 workstation so I searched a bit on the net and fond a page that had almost everything to the t: http://blog.360.yahoo.com/blog-.WURHFYwdq8.zfEosWC6j8jQ?p=55. A few very small differences that are due to the fact that the kernel has changed a bit more since this doc. So here are the very quick steps:
- cd /usr/src/linux/
- make menuconfig – and check that everything is good
- make bzImage
- cd include/linux
- ln -s autoconf.h config.h
- cd /whereever/vpnclient/
- perl -p -i -e ‘s/CHECKSUM_HW/CHECKSUM_COMPLETE/g’ interceptor.c – to replace references of CHECKSUM_HW with CHECKSUM_COMPLETE; there are only 2 to fix
- perl -p -i -e ‘s/skb_checksum_help(.*)/skb_checksum_help(skb)/g’ interceptor.c – to replace the 5 references to skb_checksum_help() with the proper parameters
- ./vpn_install – to install the Cisco VPN client
If you have a different experience don’t hesitate to let me know how it works for you.