I have been using TWiki since 2002. I used to have binders before that, but searching through binders is a pain. TWiki provides version control automatically on all documents. Documents are kept in text files. You can use HTML tags plus TWiki's own markup language. There is no database backend so you don't have to worry about database corruption.

Subjects can be organised into "webs", which are colour-coded to make them visually distinct. Each web is a directory with its own internal structure, templates, etc.

I can upload binary files which are attached to the particular topic, so I can add screenshots, config files, router configuration files, executables, tgz files, PDFs, etc.

I use TWiki to track my projects, customers, network layouts, scripts, code, documentation, pictures, basically my entire life.

In response to the idea that my descendants will not be able to access this chronicle of my life, since TWiki is basically a bunch of folders with text files, as long as one browser that can be basic HTML and text survives, this information will be available.

To me, TWiki is my superpower. It has turned your average geek into a Guru, despite being over 50 years old and not able to remember anything from last week, I have a tool that allows me to recall commands I used in Windows 95/3.11, code snippets from the green screen era of System V UNIX, MS-DOS, Novell, OS/2 and C/PM.

Because TWiki supports HTML, I have built screens that allowed me to manage networks with hyperlinks to run VNC to connect to users' desktop PCs, phones, printers, PBXes, servers. I have code from hacking cellphones, databases, weird little one-off projects like swipe card interfaces. Code snippets in dBase, C, SQL, PHP, Informix, VisualBasic.

All searchable with regular expressions.

Blessed Ishtar, how does one live without a wiki? I literally can't remember life without it.

My Nokia 6230b just gave up the ghost this week. Loved that phone. It's fallen off my motorbike, hit the ground, broke into 4 pieces. I put them back together and it worked. So I bought me another Nokia. Let's see how long that one will last.

O5, huh?
I got me an X20 whose BIOS says 1999. It has a Pentium III 600MHz with a whopping 192MB RAM. Love the keyboard. I use it as my morning PC when I'm drinking my coffee upstairs looking out at the tropical forest around my home. I like old computers. Also got a Model M keyboard but my wife uses it now. I'll have to steal it back from her someday. She doesn't appreciate it.
I love my Dell Mini 9's but they're young still, from 2008. I take one on my bike with me. Rock solid. I got three of them, so by the magic of parts replacement, at least one should last a while.

My most important habit for system administration is to record things in my wiki. I have been maintaining it since 2002. Every shell script, procedure, config file, screenshot goes into it. All my daily personal logs (with timestamps) go into it. Network layouts, tips, tricks, shortcuts, links to tutorials, whatever.

It has become my personal superpower. There is nothing more important as a tool. If you are not using one, start today. I can't recommend it enough.

I concur. There are 2 mistakes I have made in the past. One is to fix something that people thought was impossible to fix. That sets you up as a godlike figure. People start to expect the impossible as a matter of course. The second is about not pacing myself. You have to establish an understanding with your employers/userbase that a request takes X amount of time, be it 2 days or a week. Once you have established that, you are giving yourself time to fix the ones that really take a week. The rest of the time you are giving yourself time to think about the job and prepare for problems to happen. You also have to establish habits like ACTUALLY taking an hour to eat lunch instead of eating at your desk. The important message to convey is that good system administration takes time.

Sad but true. The better you get at this job, the more weight you put on. What we need, is an augmented reality device that let us work while jogging. Or something ...

Uh, Slackware? Closest thing to SysV UNIX I've used. Doesn't get in your way when you want to do something. Rock solid stable. I've tried all the other distros and keep coming back to Slackware. Spent my 80s on UNIX, my 90s on Windows, now on Slackware on the Y2K era. Never looked back.

No, really, Slackware. Never mind it gets bad press from all the *buntu fanbois. Slackware does NOT get in your way. Hackable to the extreme. Comes with 5 different desktop environments, pick one. Don't like it, install something else. Slackware don't care. You can make it work YOUR way. No strange shit happening in the night while you sleep.

I often think people like *buntu coz it reminds them of how Windows behaved. *buntu keeps doing strange shit when you not looking. Slackware? Something not working, you got a hardware problem. This thing just works. Every day, all day, all night. Boring really. The good kind of boring. Like mainframe boring, Novell Netware boring, OS/2 boring, SysV boring. Damn thing just works, no hysterics.

And they don't go changing the initialization system on you, either. Same old boring init scripts we've been using since Adam was a boy. Get it here -> http://www.slackware.com./ See the boring website. This is the oldest distro around. Kernel version - 3.10.17-smp. Boring, no drama.

Want Gnome? Get it here -> http://www.droplinegnome.org/. Can't imagine why anybody would.

Thank me later.

I disagree.

What users are accustomed to, is a paradigm. Double-click on an icon to open it, click on the X in the upper right hand window to close a window, etc. Change that and they get confused. But as long as the new desktop obeys the same rules, they are ok.

XFCE by default, behaves according to that paradigm. So it is not difficult to transition users from XP to XFCE. I have done it. With the proverbial grey-haired, fussy, old biddy who complained for everything. Never complained about the new desktop. Just wanted to know how to save to a USB drive.
I've even put KDE for some users and they loved all the sexy desktop effects.

And oh yes, they've been using it for 3 years now and are quite comfortable with it. It all depends on how you approach the transition. In the end, it is not about the technology, it is about the people. If you take time with them and make them feel comfortable, it will work.

My experience is different. In my last job, I put down Slackware desktops to replace Windows XP. In conversation with the managing director, we were debating XFCE vs KDE. I wanted to use XFCE but he said, 'Give them the bling!'. So I put KDE in the Sales department and they loved it. I showed them all the sexy effects and they lapped it up. In the Accounts department, I put the XFCE desktop. In the end, XFCE was simpler for me. But the KDE users never complained. They loved it. Mind you, I did not try configuring it like XP. I just gave them the standard setup.

I would suggest using XFCE as the desktop. It's easy to transition users from XP to XFCE. The windows work the same. You can configure it for double-click or single-click to open icons, etc. Click on the X in the upper right hand corner to close Windows, etc.
As for the distro, I chose Slackware after experimenting with Linux Mint. I know it sounds counter-intuitive but it makes for a more stable environment becoz users can't just download and install stuff on their own. Slackware requires more work to install stuff and that's actually a good thing. It ensures that the working environment doesn't change without you being involved. Makes for a very controlled environment. Plus, Slackware is wicked fast even on crap machines.
The main headache is going to be stuff like incompatible printers. Stay away from Canon ImageRunners - no drivers. Use HP or Brother printers. HP has some multi-function machines that actually have web interfaces to do scanning.
For really necessary Windows applications, use a Virtual machine. You can have a desktop with both Windows and Linux icons on it at the same time using Virtualbox's seamless mode. My younger brother uses it all the time.
But, strategically, you should be promoting the web instead of the desktop. I'd hook people up with Gmail accounts and have them sharing documents and calendars across that. It's really more productive. Just my two cents.

All right, I am not disagreeing with you, but, in practice, how often does that occur?

I have transitioned five organisations to Google Apps/OpenOffice. They all have external partners in various parts of the world. People make do. They learn to send PDFs if formatting becomes an issue.

Listen, this is a problem even between versions of Microsoft Office, if I'm not mistaken. It's part of the reason the term 'forced upgrade' was invented. So, it's not just limited to Linux desktop environments. That was why there was this big controversy over the ODF standard in Europe.

And this is being worked out between organisations all the time. Nobody is so big that they don't need to compromise when dealing with external parties.

So, push come to shove, you could maintain a virtual machine somewhere for the express purpose of converting documents if need be. For 10 workstations, I don't see this as a problem. If the management wants to avoid upgrading the machines, they can work this out without too much of a fuss. It's a matter of talking it out, not a technical issue.

Last time I paid for this, it was US$25.00 per user per year. It may have changed.

But when you think that you don't have to

• maintain a file server
• do backups
• maintain an email server
• do any server updates
• worry about SPAM, viruses

Google Apps just makes sense.

It's possible to replace XP with Linux. I've done that in a company with non-technical users.

You just have to select your targets carefully.

If you want to replace Windows desktop applications with Linux desktop applications, you may be barking up the wrong tree. In this company, we replaced Microsoft Office applications with Google Apps. This takes time but it does work. Once you have people settled into Google Apps, the desktop becomes irrelevant. I changed people from XP to Slackware Linux desktops without any fuss. Yeah, Slackware, not Ubuntu. And they loved the speed of response.

If you sit back and think about it, the desktop without applications just provides operating system services like networking, printing, a graphical environment, etc. Once people get used to the paradigm of clicking on icons to open windows, clicking on the X in the corner to close the window, etc, one graphical environment is pretty much the same as the other.

Now there are always applications that can't be replaced. I would create a virtual machine to handle those applications. Virtualbox provides a remote desktop server for its virtual machines, so the users can use rdesktop to connect to the virtual machines.

I would go so far to say that you should think of replacing all Windows XP machines with either Linux machines or thin clients. Move the essential applications to a server running Terminal Services and have the users login onto that server if they need a Windows desktop. Windows Server 2003 looks and feels pretty much like Windows XP, so that transition would not be too unsettling. If the server is powerful enough, they should actually get a peformance boost from working off the server.

So, the end of support for Windows XP doesn't have to be traumatic. You have options - a cloud-based desktop like Google Apps, a Linux desktop, or a Terminal Services-provided desktop. All are doable, manageable, for 10 workstations.