|
|
KVM recommendations / Insights / Experience I've just been Googling about coding for the Mac [ again ] and came across this old blog that mentions using a KVM [ non - OS X - probably BSD or Linux - either would be fine ] to provide source code services. This is rather off patch coding topics, just wondered if any one here has experience of / insights about / recommendations or caveats to make. I thought it sounded like a really good idea. Nice way to organise one's code. The idea is to use the KVM to control a range of network connected devices, including computers and thus manage additional cheap and cheerful BSD or Linux based servers, amongst other things. Would love to do this with Mac Minis though :-)
|
You can pickup a pretty cheap 2 computer KVM for around 50 bucks, and use one input for your Mac and the other for a machine running multiple virtual machines. No sense in buying a bunch of computers for something that isn't very resource intensive.
Thanks for the feedback mattgolsen.
The KVM approach is beginning to appeal to me; affordable & flexible.
You may also want to look into using SynergyKM, a software based keyboard/mouse sharing solution. I use it across a WinXP machine, to a 27in iMac, to a MacPro and occasionally my Mac Book Pro. It can work over any TCP/IP connection, on any "leg" of the connection. So my setup goes from a Firewire cable, to a wired LAN connection, to wireless and then to another wireless connection.
Actually this brings up question regarding your original post. Does anyone use any sort of version control or anything similar for their QC comps?
Yes. Subversion.
However traditional diffs don't handle binary plists. I've tried using
plutilas a pre-commit script to convert binary plists to xml.. But the element order tends to be shuffled around with each save, so the diffs are full of static.I've been pondering creating a utility that would take an xml plist and reorder elements in a stable way, thus possibly rendering diffs useful.
Yeah version control is a problem I run into frequently with my stuff. I've got a main branch that I work on and a co-worker creates additional work that I integrate, but it can be a bit labor intensive to keep track of all the changes that either of us do. I honestly don't know much about the different flavors of version control, but it is something that I'm probably going to need to setup soonish, especially as our stuff grows.