Sorry, this entry is only available in Deutsch.
Author Archives: patmuk
why I prefer mercurial over git
the safest file storage setup (using zfs)
I recently set up a file storage with the purpose of being super safe.
Here is what one needs to do and why:
Continue reading
How to upgrade Mac Pro 4.1 to 5.1 and run Apple’s Hardware Tests from a USB stick
I recently decided against building my own server from ordered parts and simply bought an older Mac Pro for a good value. It was roughly 200€ more than the build-it-yourself way, but therefor it can run OS X smoothly, which saves me time where I don’t need to babysit my machine.
Nevertheless, it can not go without a bit of hacking.
read on how to upgrade to 5.1 and run Apple’s Hardware Tests from an USB Stick
archive mails in iOS 7 using a gmail exchange push account
The behavior of the delete button changed in iOS 7: It no longer archives gmails but moves them to trash.
see how to restore the old behavior
xtend pass functions as parameters to other functions
In xtend everything is an expression. Thus you can pass a method to another method as a parameter in the following way:
Continue reading
The difference of xtend(2) dispatch and Java’s method override
The difference is single dispatch vs polymorphic dispatch. This theoretical concept becomes more clear with a comprehensive example:
Continue reading
How to Install mercurial (and maybe git) on a linux box without root privileges
If you happen to be on a linux box without root privileges you can nevertheless install the two very usefull distributed version control systems, git and mercurial:
Continue reading
secure gpg keys
I (re-)created gpg-keys.
Here my recommended steps:
1. First create one or more keys:
There are many tutorials, I recommend the one mentioned in my last post:
http://patrick.mukherjee.de/?p=151
2. List all keys:
gpg –list-secret-keys
now save each:
2. export the public-key as a text-file. This can be distributed without being afraid of mail-filtern, etc.:
gpg -ao pubKey_
where
3. The most important step: create a “revokation certificate”! So that you can revocate your published key at any time (maybe you forget the passphrase). This is only possible using the passphrase and the private key!
gpg -ao revokeCert_
4. Optionally save the private key in a ASCCII-file. The file is, of cause, encrypted using a passphrase. Store it very secure (you can even print it).
gpg -a –export-secret-keys
5. Now publish your key(s) to a key-server. It is sufficient to publish it to one server – the server distributes it to all other server.
gpg –send-keys
… while trying around I made a mistake and deleted my key prior revoking the key. Now the wrongly published keys are stored online for all eternety and will confuse people, who look for my key.
So, please, do not use these keys, as they do not exist anymore:
good gpg tutorial (in OS X)
http://www.robertsosinski.com/2008/02/18/working-with-pgp-and-mac-os-x/
Old, but still valid. Though now there is a GUI (in the installer https://www.gpgtools.org/installer/index.html) this command line tutorial explains the basics nice 🙂