A little while ago I found an image of a car (specifically a GTO) on the back of an old Maxtor hard drive PCB. I just recently had a chance to take some high res pictures.
Click the above image to see a high resolution image of the full drive.
I recently got a new 24 inch iMac and needed a way to share my keyboard and mouse between Mac OS X 10.5 (Leopard) and Windows XP. Synergy does exactly that. Setting up a Synergy server under XP was simple, but the Mac client was a little more tricky.
Apparently there is a bug in Synergy 1.3.1 with OS X 10.5. When you try to start Synergy (client or server) as a daemon under OS X 10.5 it crashes. Below is a workaround which starts the Synergy client at boot in the foreground (-f) through launchd. Put this file in /Library/LaunchAgents/net.sourceforge.synergy2.plist (needs root privileges):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>net.sourceforge.synergy2</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/synergyc</string>
<string>-f</string>
<string>-1</string>
<string>--name</string>
<string>imaczomg</string>
<string>--debug</string>
<string>WARNING</string>
<string>deathstar</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
Here is what the argument string will look like:
/usr/local/bin/synergyc -f -1 –name imaczomg –debug WARNING deathstar
/usr/local/bin/synergyc - the path to your synergy client binary
-f - run in the foregorund
-1 - do not restart on error (launchd will do this for us)
imaczomg - the name (or IP) of your mac client
–debug WARNING - won’t log every time the mouse moves off the screen
deathstar - the name (or IP) of your server
If you are running a Synergy server on OS X 10.5 please look here.
I came across this blog:
http://meta.ath0.com/2003/11/04/my-top-ten-reasons-why-redhat-sucks/
While the author of this blog has some very valid points, some or outdated or unproven.
RPM. If you think RPM is a reasonable piece of software design, I can only assume you’ve never used Portage, APT or BSD ports. I still have to keep a “cheat sheet” of the bizarre invocations necessary to make RPM perform basic tasks. Then there’s the fact that you can’t just install an RPM; no, you need to find the right RPM for your specific version of RedHat, assuming one exists. And if that’s a pain for you, imagine what a pain it is for developers.
The author is right. RPMs are simply horrible to work with. There are some real show stopper bugs that RPM developers simply refuse to fix. Additionally, the Red Hat repositiories are far smaller than most free distros.
Shoddy workmanship. RPM was discovered to be broken in 2002; it would regularly corrupt its own databases and lock up in such a way that it couldn’t be killed. In spite of that, RedHat went and made two major releases with a broken RPM.
Here is another example of a MAJOR bug. The comments on the bug report are a real joy to read. As a result of the bug report, a developer was fired.
As a network administrator, I use Microsoft Remote Desktop (Terminal Services) on a daily basis. In Windows XP, the Remote Desktop shortcut is buried deep within the Start Menu. Additionally, Microsoft recently updated their Remote Desktop client. As part of this change, they moved the shortcut.
Previously it was located here:
Start->All Programs->Accessories->Communications->Remote Desktop
Per the new version is it:
Start->All Programs->Accessories->Remote Desktop Connection
I find this way a lot easier:
Start->Run->mstsc
“mstsc” stands for Microsoft Terminal Services Client. Sure, you could create a desktop shortcut, but when working with multiple workstations that becomes a hassle.