Many of my traditional blog post live on this site, but a great majority of my social-style posts can be found on my much-busier microbloging site at updates.passthejoe.net. It's busier because my BlogPoster "microblogging" script generates short, Twitter-style posts from the Linux or Windows (or anywhere you can run Ruby with too many Gems) command line, uploads them to the web server and send them out on my Twitter and Mastodon feeds.
I used to post to this blog via scripts and Unix/Linux utilities (curl and Unison) that helped me mirror the files locally and on the server. Since this site recently moved hosts, none of that is set up. I'm just using SFTP and SSH to write posts and manage the site.
Disqus comments are not live just yet because I'm not sure about what I'm going to do for the domain on this site. I'll probably restore the old domain at first just to have some continuity, but for now I like using the "free" domain from this site's new host, NearlyFreeSpeech.net.
Just a quick note that I changed my /etc/apt/sources.list to pull updates for Debian Wheezy from a more local "secondary" mirror rather than the primary Debian mirror for the U.S.
I'm not sure whether or not this site at the closer-than-not University of Southern California will be faster than Debian's primary U.S. mirror, but I'd like to think I'm taking just that much pressure off of Debian's primary infrastructure by using this secondary mirror.
So how did I find the new mirror? They're all right here.
Here's my sources.list before:
deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free
deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
And after:
deb http://mirrors.usc.edu/pub/linux/distributions/debian/ wheezy main contrib non-free
deb-src http://mirrors.usc.edu/pub/linux/distributions/debian/ wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
No big deal.
Debian developer Ingo Juergensmann reports that addition of a 'leap second' to clocks made apps that include Firefox consume all the CPU on the system.
That sounds like as good an explanation as any for my troubles yesterday with both Iceweasel/Firefox and Google Chrome both pegging my two CPU cores at various times, especially since I didn't reboot the system, which was in suspend overnight.
I'm on my second day of intense use of my Debian Wheezy (aka Testing) system, which I upgraded from Squeeze (aka Stable) on Friday.
While I'm getting the hang of GNOME Shell, with its "hot corner" mousing technique, creation of virtual desktops as needed, plus the overall newness of transitioning from GNOME 2.30 to 3.4.2, today I decided to work in the GNOME Classic desktop as opposed to the full GNOME Shell.
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.