Though my track record with in-place upgrades of Linux/Unix systems is far from positive, I decided to do just that with my long-running (since late 2010) Debian Squeeze laptop today.
It went surprisingly well -- and by that I mean I'm using a fully upgraded Debian Wheezy laptop to create this post in Nautilus via sftp.
My Debian Squeeze system has been swapping a lot lately. I think web browsers -- mostly Google Chrome -- are to blame. I'm not sure switching entirely to Firefox will solve the problem. Web browsers eat resources.
To speed things up, I decided to reduce my "swappiness" to see how that affects system performance.
It's been a very long time since I've done it, so I Googled "swappiness in Debian," and came across my own entry from 2010 when I was running Ubuntu 10.04. I got my information from the Ubuntu community Swap FAQ, and you can too.
I followed the recipe on my Debian Squeeze system, changing swappiness from the default of 60 to 10 so the system will use swap less often.
So far, so good.
The next day: This is totally working. After six or so hours of my usual workload, I'm only using 1.2 MB of swap. Nice!
The next week: After a full day of computing, with lots of Google Chrome windows and tabs open all day (I barely used Firefox/Iceweasel today), doing some photo edits but no video editing, I'm using 1.4 GB of RAM and 24.8 MB of swap. I'd say the experiment in changing swappiness is a success.
The more interesting bits this month include a controversy over duplication between the Debian Multimedia archive and Debian proper.
Stefano suggests that what package belongs where be worked out, or that Debian Multimedia shed its Debian name and move on.
I finally got Iceweasel 13 installed out of the Mozilla Debian APT archive on my Debian Squeeze system. For at least a week I've been stuck on Iceweasel/Firefox 12 due to dependency issues. dWhile a Debian Forums article didn't provide the exact solution to my problem, it did give me a clue:
I did that, and I got the new Iceweasel/Firefox as well as the needed dependencies, and thus far nothing appears to be broken.
So how do I do this in WordPress? I'm looking into child themes (I confess that I've -- horror of horrors -- modified the main theme in a WordPress blog), but I need EXTRA theming. What I need is the ability to tap the blog database for custom HTML output that includes only the elements I want with accompanying HTML so I can display that output on other sites.
It's so easy to do this in Ode and Movable Type. Why is it so hard (or seemingly so) in WordPress?
I know it's easy. You pick up your smartphone. You click the Twitter icon (or Facebook, if that's your poison).
Then you lay it out in 140- (or 500-odd) character bursts. Or you talk about the sandwich you're eating.
There's nothing wrong with that. Except that your words now live on some social network. Not on your own hard drive or server. Not even on a WordPress.com blog from which you can extract every post to archive and reuse as you please.
These are the social networks on which I have accounts.
But I won't be posting directly on any of them.