Source: http://stackoverflow.com/questions/248821/undoing-a-commit-in-tortoisesvn

I came  up with a super useful way to copy the clipboard from OS X straight to your iPad or iPhone!
Everything you need is free. Only pre-reqs are Dropbox and Automator. I've only tried this on Snow Leopard and I'm not sure if it works on Leopard. I use this to get URLs onto the iPad, notes and it even works pretty well if you need to copy a Wifi password without syncing to iTunes. Best thing about it is that the copy process is near instantaneous!

It's pretty simple and works like this:

1. Select text
2. Right click -> Copy to iPad (Dropbox)

See it in action:

Wooo! Now first, make sure you have Dropbox installed on both your Mac and iPad (Free)
Then we need to make a simple to make Automator service:

1. Open Automator.
2. Choose "Service".
3. Search for "Run Shell Script".
4. You want the /bin/bash shell (should be default option).
5. Type in the following:

cat > ~/Dropbox/Mac-Clipboard.txt

6. Save the Service.
7. Make sure it looks like this:



8. You're done!

Now all you ever need to do is right click on some text, pretty much anywhere, choose it from the menu we created. Since the clipboard's contents are normally very small (say less than 500kb) your upload to Dropbox should be pretty much instantaneous! When you open DropBox on your iPad, the copied text will be waiting.

After some more thinking about making this better I thought it would be good to do something like this for images using an RTF file format and a Python script. I abandoned the idea since Python doesn't have an RTF writer built-in so you would have to download it separately, make it, blah... blah... it was just getting too complicated. It's best to keep it simple and if you really want images, just copy them to  your Dropbox

If you liked this tip or think you can improve it in someway, be sure to leave a comment!

Scripts

1. Transmission: Transmission-NotifyCompletedTorrents (38)

A typical scenario is I'm SSH'ed into a remote server and I want to copy a file on my Mac, to the Remote machine I'm sshed into.

You can copy the "remote" file with this command:

scp -r brock@192.168.1.6:/remoteDirectory /localDirectory

Copy a local directory's contents /Volumes/src/ note the trailing slash, then place those contains inside /Volumes/des.

rsync -Pva /Volumes/src/ /Volumes/des

Update: Shell Scripts for QNAP BusyBox Linux

I recently acquired a QNAP TS-410 and thus far has been time consuming to setup. These things are great, but you can't just buy them, plug your drives in and have it working in 5 mins like an external drive...

The problem is not with the NAS itself, which with it's little low powered Marvell 800mhz Arm (FTW) processor, has been working great. Rather the unreliable nature of spinning mechanical hard drives *cough* *western digital* *cough*

The QNAP is setup as a RAID-5, because RAID-6 is just too much storage overhead and I would hate to build a raid 6 on an 800Mhz processor. The reported build time for a RAID-6 can be as much as 2.5 times longer than to build a RAID-5. Considering the ~25 hours to do the current setup, I think 75 hours would be totally unacceptable.

I bought three of those Western Digital 2TB Green Power drives (WD20EARS) primarily because they are low power, like the NAS. It took me about 5 hours to build the RAID, then another ~20 hours to syncronise the RAID, during which I could use the raid, but very slowly (~2MB write/sec). Drive bays 1 and 3 were running fine after the RAID finished, but the raid reported a "degraded state" and an issue with drive 2.

While rebuilding the RAID I found out you can actually increase the RAID build time, by giving more priority to the bild process with these commands to get the build speeds:

cat /proc/sys/dev/raid/speed_limit_max
200000
cat /proc/sys/dev/raid/speed_limit_min
1000

Changing the minimum build speed (in MB) can be achieved like so:

echo 50000 >/proc/sys/dev/raid/speed_limit_min

My advice is to run at max (makes the build and sync so much faster):

echo 200000 >/proc/sys/dev/raid/speed_limit_min

I soon discovered that the misbehaving drive had infact, 331 bad sectors. Yet the "smart" technology reported "Good". Yikes! ...and it was only 2 days old.

Still, i wasn't that surprised, I've bought many drives before that have died on me immediately or within the first six months of owning them (Samsung, Western Digital, Maxtor). I've never owned Seagate drives so I can't comment. I've heard others report bad Seagates, but in my experience I've never had as many go bad as those Maxtor 40-60GB Fireball drives, back in the day.

I got the WD drive replaced from the guys at PLE straight away with no questions asked. The RAID is now rebuilding and we shall see if all goes well.

Even with the issues so far, I am glad that I bought the QNAP (and not the Drobo) as I have the full power of Linux (without the hassle of setting it up). It's very cool being able to SSH into my NAS and configure things like RAID rebuild speed, renice processes (AFPD > SMBD) and it can even run BitTorrent and download stuff straight into itself. Drobo can't do that. Linux is very cool.

uname -a
Linux Axiom 2.6.30.6 #1 Tue Apr 27 02:45:06 CST 2010 armv5tel

Picture of my NAS (just warning you the file is big ~1MB

Update: I had the problem with the WD EARS sector 4k alignment:

fdisk -lu

Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *          63     1060289      530113+  83  Linux

/dev/sda2         1060290     2120579      530145   82  Linux swap / Solaris

/dev/sda3         2120580  3906011969  1951945695   83  Linux

/dev/sda4      3906011970  3907007999      498015   83  Linux
Device Boot      Start         End      Blocks   Id  System/dev/sda1   *          63     1060289      530113+  83  Linux/dev/sda2         1060290     2120579      530145   82  Linux swap / Solaris/dev/sda3      2120580  3906011969  1951945695   83  Linux/dev/sda4      3906011970  3907007999      498015   83  Linux

Now have to do a complete reinitialisation. See here for more info.

]]> http://brockwoolf.com/blog/building-a-qnap-ts410-raid-nas/feed 0 http://brockwoolf.com/blog/no-interfaces-available-in-wireshark-on-mac-osx http://brockwoolf.com/blog/no-interfaces-available-in-wireshark-on-mac-osx#comments Wed, 12 May 2010 11:04:52 +0000 Brock Woolf http://brockwoolf.com/blog/?p=842

Easy fix. You need to give Wireshark permission to access the network devices.

sudo chown {your account name} /dev/bpf*

Nayan Hajratwala over at Agile Shrugged managed to write a really great article describing how he got Subversion repos running on Mac OS X Server.

I got mine working on Mac OS X 10.5.8 but had to make a few different changes in order to get things working. His doesn't deal with multiple SVN repositories, only with a single one. This isn't ideal and I highly doubt anyone would go to the trouble of installing a SVN server and only ever need ONE svn repository.

I would suggest using /opt/repos/svn as the master path as the Open.collab.net developers recommend doing it this way on Mac OS X.

I'd be interested to know if you could make that an alias to an external drive with svn being a symbolic link inside the /opt/repos folder, which points to a location on an external volume like: /Volumes/External HD/svn. I will try this some day but if anyone knows if this actually works, please leave a comment.

Step 1 - Create a root SVN folder

Open Terminal.app:

sudo mkdir -p /opt/repos/svn

Step 2 - Create your SVN repository

sudo svnadmin create /opt/repos/svn/test
sudo chown -R www:www /opt/repos/svn

The second line makes Apache own this path and everything inside it including your new repo.

Step 3 – Configure the Apache web server via Server Admin

Server Admin is located in /Applications/Server/Server Admin.

1. Click Web in the Sidebar

2. Click Settings in the top bar

3. Select the Modules tab

4. Check the following modules:

authz_svn_module
dav_module
dav_fs_module
dav_svn_module

Step 4 – Enable WebDAV on your site

Reading comments, it seems that some people don't think you need this step. However for my configuration I'm pretty sure you do need to do this.

1. Click Sites in the top bar

2. Select your site

3. Click the WebDAV checkbox

Step 5 - Create a Realm

This will set up the OpenDirectory based security. We will be using Basic authentication only.

1. Select the Realms tab

2. Click “+” under the Realms box and enter the following:

Realm Name: svn_realm
Authentication: Basic
Location: /svn (Note: You have to change the dropdown to 'Location', not 'Folder').

3. Click “+” under the Users & Groups box, and drag/drop the users/groups that you want to give access to. Also be sure to give them read/write privileges...then press the Save button.

Step 6 – Tweak the Apache config file

There is no graphical UI to do this. So you need to use Terminal.app.

Edit the file under /etc/apache2/sites that corresponds to your site.

This should be a file starting with 000x.

In the <location "/svn"> section, add the following three lines:

DAV svn
SVNParentPath /opt/repos/svn
SVNListParentPath On

This is what mine looks like:

Step 7 – Restart the web server

You can do this from Server Admin ('Stop Web', then 'Start Web').

You should be able to access your repository at http://myserver/svn or locally at: http://localhost/svn

Be careful not to change any other settings in the Web portion of Server admin.

If you do it will change DAV svn to DAV Off again.

Free free to leave any comments and suggestions

Macports doesn't install ODE correctly either. Macports installs a PPC binary on your system (even if you have an Intel Mac). So here is the correct way to compile ODE on a Mac.

Download the ODE Source Code from Sourceforge.

Extract the source to a directory of your choosing (I use: /lib/ode-0.11.1)

Open a Terminal:

cd build
premake4 gmake --platform=universal32
cd gmake
make

At this point you need to add in some flags to the makefile in order to get this to build on Intel correctly. So open ode.make and change the following 2 lines:

cd ode-0.11.1/build/gmake
vim ode.make

You need to add -m32 to the CXXFLAGS, which you can do by adding it to the CPPFLAGS (which uses CXXFLAGS. Find the line starting with CPPFLAGS and change it to this:

CPPFLAGS  += -MMD -m32 $(DEFINES) $(INCLUDES)

You also need to add -m32 to LDFLAGS:

LDFLAGS   += -m32 -dynamiclib -flat_namespace -framework Carbon

Save and quit.

Build Release Libraries:

make config=releasesingledll

Build Debug Libraries:

make config=debugsingledll

This will build the libraries to here:

ode-0.11.1/lib/ReleaseSingleDLL/libode_single.dylib
ode-0.11.1/lib/DebugSingleDLL/libode_singled.dylib

So there you go. Enjoy using ODE!

Install Bullet (Download Link):

cd bullet-2.75/
cmake . -G "Unix Makefiles" -DBUILD_EXTRAS=on -DBUILD_DEMOS=on -DCMAKE_BUILD_TYPE=Debug
make

Pretty simple. The demos will be built to bullet-2.75/demos/ and the Bullet libs are built to bullet-2.75/src/