I recommend the one-mail-per-file, and one-directory-per-folder, idea. It's not exactly, well, new - but it beats everything else by miles.
Yes, this means you keep your mail local. This is a good thing, as this means /under your control/.
grep? Yes, works. Easily.
glimpseindex? Yes, works. Easily.
Anything else? Yes, works. Easily.

I keep all my mail from 1998 onwards (when I switched from a certain commercial provider with a proprietary email system) in that way. And it Just Works.

('course, Gmail/MSNmailorwhateveritscalledtoday are out. Who cares. exmh (and mutt in a pinch) FTW.)

>Linus uses death threats?

Not exactly, but he did suggest certain people commit suicide:
"Modern PCs are horrible. ACPI is a complete design disaster in every way.
But we're kind of stuck with it. If any Intel people are listening to
this and you had anything to do with ACPI, shoot yourself now, before
you reproduce."

.. more long-lived, but they're also quite impractical in everyday use.

Look, for example, to the EU, which has â1/â2 coins and not notes, and ask the people how they like 'em. (Hint: they're nearly-universally loathed.)

If you're concerned about wallet theft - carry an obviously bulging one. In a back pocket. Stuffed full with receipts and not much else.

I was .. relieved .. of this wallet about 10 times now, always in overcrowded places (trains, subways, tramways, buses) and only once even noticed when it happened. Never lost the really thin one (passport, CC, cash) I keep in a front pocket, though.

And if it ain't gone, hey, you've got a lot of receipts to remind you all the places you've been ;)

A bit of network knowledge is essential, yes. Please don't forget IPv6 in the interview.

Though first of all I'd try and find out if the interviewee is interested in learning about new technologies, and if s/he appears to fit into your team - no matter how brilliant s/he is with Windows, if s/he's not fitting into your team you'll have a problem on your hands.

For the technical side:
Ask some question in the direction of AD, like "if group A is a member of group B, and group B is a member of group C, which then has group A as a member - is that legal in AD, what problems would you expect, how would you go about fixing it?".
Authentication: "please explain the concept of Kerberos to me".
Backup&restore: "how would you go about backing up a handful of servers, various versions, incl. at least 2 versions of Exchange and SQL Server, and how would you do a bare-metal restore"
Understanding: "explain the different RAID levels, and what their down-/up-sides are"
Automation: "how would you go about automating testing&roll-out of security patches (mind different Windows Server versions)"
Security 1: "if you had to expose SharePoint to the outside world, how would you secure access, and how would you do server hardening, same for Exchange with Outlook Web Access"
Security 2: "what would be the down-/up-sides of getting all our Windows machines on the network with 802.1x, how would you go about managing the certificates"
Security 3: "please explain Teredo, and how would you go about ensuring that there are no such tunnels to outside our network"
Understanding of basic technologies: "please explain SMTP, and why you need DNS for that", "how would you choose a Windows domain and how would you integrate it with our DNS setup"
Day-to-day operations: "How would you go about ensuring that Exchange services stay available, transparent for the users, even when applying patches or when some hardware dies"
Deeper understanding of Windows internals: "explain SysWoW64, and how it works so 32bit binaries get to their 32bit DLLs" (that's a real tricky one, and full of security-relevant pitfalls!) - go grab a copy of the "The WoW effect" paper, and make a hands-on test for finding a file with certain contents hidden in either System32 or SysWoW64.

1. invent a reason to withdraw lots a cash, and disseminate widely (like "spotted a really nice car/bike") via your usual channels (preferrably electronic or otherwise easilly accessible for surveillance)
2. withdraw cash, at least 5-figure amount in $ or â
3. let your social network (by which I mean real-life family and real-life friends, not F*book) know what's going on, and that you will be incommunicado, and not even watching news (so threats against family/friends are pointless for your adversaries), for at least half a year. Include co-workers/bosses/underlings/HR departments from 3 jobs ago. Physical letters, written in your own hand, not email. Include hand-written letter appointing someone you trust to look after your affairs.
4. invent an errand as an axcuse to get out of work in the middle of the day, and borrow someone's car/bike/bicycle, whatever your cow-orkers can provide
5. drive to a different nearby city, leave car where it'll be towed after a day or two. Preferrably crossing a border or two in the process. Leave the US or UK if your starting place is there. Changing continent is probably futile.
6. walk to someplace nearby. Yes, even you can hike for 10-20km. Preferrably along hiking paths in woods, along a river or somesuch, wherever there's not much chance of CCTV.
7. don some form of hat or baseball cap or so. Whatever's not too uncommon in your area. And sunglasses Stylish, not obviously for obscuring your face. If usually bearded, lose it. Change hairstyle somehow
8. use some public transport, as crowded as can be found, that doesn't require ID, and can be paid for in cash.
9. repeat 7. at least 5 times. Intersperse with walking (like from railway station X to bus station Y) and taxi trips. Get off PT through already-closing doors. Enter somewhere where multiple lines stop, enter throigh already-closing doors.
10. buy some hiking gear, A backpack here, a tent (not in a singal colour!) there, a camping stove elseplace, canned food etc.
11. you should now be equipped for a week of the great outdoors, and be someplace where there's really lots of woods around. Go hiking in a fashion it'll take you a week until you meet Big Civilization again, avoid towns and villages and as much human contact as possible.
12. walk into stores not located in the absolute outskirts of cities or tiny settlements and buy supplies. It's good if said stores are at least 2 days hiking away from your hiding area, and if they're in areas where pedestrians are not completely uncommon (like L.A.).
13. hike for a week to someplace else after a week of resting - your blisters will thank you for it.
14. always maintain as good personal hygiene as at all possible - both for medical as for appearances sake. Wash clothes and yourself in a stream (a bar of soap is sufficient. Keep one change of clothes decent, and use it only for trips in urban areas. You want to be taken for a random hiking person, not a trespassing homeless. Do not make use of unattended hiking houses (if such even exist in your area - they're common in mainland Europe), ever.
15. If caught by park rangers etc. whilst illegally camping, be friendly and just pay the fine

That 5-figure cash amount is good for a year of living outdoors if you're careful.

What Mozilla - and a couple others - are doing wrong is to break with the principle of least surprise. Another prime example were our friends from Redmond with Vista - pretty much everybody who had used Windows before absolutely hated it, and for good reason. Or take Ubuntu with Unity for similar stupidity.

This has been a huge problem for their userbase before their "rapid releases", but now it's much more obvious, because it breaks your workflow every couple weeks instead of once a year.

Then there's the completely ignorant "update first, THEN check if there's compatible addon-updates". Some people (me included) rely on those addons, and the decision to upgrade (and have those addons not working) or to stay with the old version a couple more days (thus keeping the addons functional) should be left in the hands of the user.

Plus (warning: pet peeve) not everyone thinks that all the world should look and behave like a fscking smartphone - I got a huge monitor here, a keyboard with 100+ physical keys and a real pointer device, and I want to use them.

And, last not least, there's the whole thing about FF being just a freaking TOOL, not a lifestyle - I understand that this might be hard for the developers to fathom, but for the userbase all those forced UI changes are about as interesting as having the gearlever in your car suddenly controlling your audio stuff, and the volume control being responsible for opening/closing the windows. We're not interested in having to google for a couple hours to be able to get going again just because the shop changed the oil.

It's called "staging".

F*ck comments. F*ck all the other interactive "web 2.0" sh*t. Do your Wordpress or whatever, then suck it out of the DB, convert to static HTML, and put it on the external webserver.

Problem (pretty much, well 99%) solved.