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.
Re-adding Fedora to your EFI boot menu if you (like me) have the audacity to disconnect your hard drive
I'm now running Fedora 19, but this happened when I was still running Fedora 18 with UEFI on my HP Pavilion g6-2210us.
The Fedora installation created an entry in the laptop's EFI boot menu for Fedora 18. But when I disconnected the hard drive, replaced it with another for some testing, then reconnected the original drive, Fedora was no longer in the EFI menu.
I was still able to boot Fedora by navigating to it via the "boot from EFI file" function in the UEFI menu, so I knew where the bodies (i.e. Fedora's EFI partition) were buried.
(Click the image for a full-size look at my admittedly vanilla Fedora 19 Xfce desktop)
Update: A preliminary test revealed that my fedup problems were networking-related. I'll try again with my home network tonight.
Further update: My home network was amenable to fedup. It wasn't pretty; the fedup process needs work. But it did work, and not only do I have a working Fedora 19 installation, I now have the AMD Catalyst 13.6 beta video driver via RPM Fusion, and my 3D acceleration problems with my new AMD APU have been solved.
Even further update: With the AMD Catalyst 13.6 beta video driver from RPM Fusion, I'm lacking the small lines on either side of my application windows, but I do have 3D acceleration, and -- more importantly -- for the first time in Linux on this laptop, I now have working suspend/resume, which you'll have to pry from my cold, dead hands.
A still further update: This bug report appears to address the lack of those small lines on the sides of windows.
Here I begin.
After a shaky start with Fedora's fedup update tool to bring my Fedora 18 with Xfce system to Fedora 19, I did manage to successfully upgrade my HP Pavilion g6-2210us (with AMD A4-4300M APU, which features AMD Radeon HD 7420G graphics).
After a curl error on my work network, I started the process on my much slower home network, quickly bypassed the error and started on the slow process of downloading 1,800+ packages.
The AMD Catalyst 13.6 proprietary video driver will support the latest AMD APUs -- and I really need it
Given that my still-shiny, still-new HP Pavilion G6-2210-us laptop with an AMD A4-4300M APU that features AMD Radeon HD 7420G graphics is not well-supported in Linux's current open-source Radeon driver, I've been looking to AMD's proprietary Catalyst video driver for help.
I've tried the current version -- 13.4. X won't even start.
That's because my APU is so new, even the Catalyst driver doesn't support it.
But help is on the way. Version 13.6 of Catalyst does support the Radeon HD 7420G, according to the release notes.
This doesn't happen all the time. But it did today.
I'm stuck using Citrix. Maybe Citrix isn't crap (though it's certainly looking like it), but the application I'm using over Citrix is -- I repeat, IS -- crap.
I'm in Fedora 18, and it starts dying on me.
So I reboot into Windows 8. "Maybe it'll work better in the desktop operating system that isn't the playground of hackers and libre-everything partisans."
I start up Windows 8. I start my Citrix app.
It won't run at all in Windows. It won't even run badly. Nothing. Fucking nothing.
Back to Fedora. I just have to start a new session periodically to keep the Citrix over-the-wire goodness flowing.
Maybe this is a Windows 8 issue (because it runs reliably yet crappy in Windows 7). Maybe it's a Firefox-in-Windows issue.
All I know is I can hobble along in Linux but not Windows.
My shared-hosting provider moved my account to a new machine, and along with all that newness came a new ssh key.
FileZilla figured it out right away and asked me if I wanted to accept the new key. (I did.)
But when trying to open an sftp connection in Thunar or Nautilus, I got a "Host key verification failed" error.
The solution was easy to find.
All I had to do was go to the .ssh folder in my home directory (/home/steven/.ssh for me; /home/your_account/.ssh for you) and get rid of the "old" ssh key from the old server.
I tried to re-connect to my shared-hosting account via sftp, the system asked me to accept the new ssh key, I did so, and now I'm back in sftp with this account via the Thunar file manager in Xfce.
One of the features of the Ode blogging system's links in post titles in the default Logic theme is that they lead not to the individual entry page but to the portion of the page including all of the relevant day's posts that includes the entry whose link is being clicked.
That's a complicated way of saying that the title links look like this:
http://stevenrosenberg.net/blog/2013/06/11/#2013_0611_hostgator
I wanted to see how the blog would work when clicking on the title of a post leads to a page that just includes that individual post itself.
By that, I mean this:
http://stevenrosenberg.net/blog/web_hosting/2013_0611_hostgator
That is the same result you'd get by clicking the Permalink tag at the bottom of each entry.
It was as easy as copying the permalink tag and replacing the original title tag in the page.html file in my current version of Ode's Logic theme.
It's a small change. Not a big deal at all. But it's so easy to do in Ode. Just about every part of the system is a text file that most users can understand and modify. So I figured I'd do it and see how it worked.
HostGator emailed me recently about moving my shared-hosting account to a new server and a new version of the CentOS Linux distribution.
The move happened. Everything seems to be working. There were some changes in my DNS servers, but nothing broke. I had to change the URL I use to access my webmail over ssl.
I do have a new ssh key, which my FTP client prompted me to accept. And so I did.
Since everything is working, I haven't checked the DNS servers on my domains.
I give HostGator a whole lot of credit here because the only thing I had to change was my browser bookmark for accessing my secure webmail.
I don't remember which version of CentOS I was using before, but now it's 6.4. The version of Perl (5.8.8) didn't seem to change. PHP is up to 5.3.24. My OwnCloud test site works.
So I guess it was just the matter of retiring old hardware and bringing up new on the part of HostGator. They kept me informed, and all is well.
It didn't take me days to figure it out, but getting this Fedora 18 system to recognize and actually print on my el-cheapo HP LaserJet 1020 should have been a whole lot easier than it turned out to be.
The system "recognized" the printer as soon as I plugged it in. I already had the hplip package installed, which I thought would help. Drivers were installed for me.
But as soon as I tried to print, nothing happened.
I raised a bug in Fedora over 3.9.x kernels that won't boot under EFI on my HP Pavilion g6-2210us laptop.
The latest patched kernel works for me. Thanks, Fedora users and developers!
Ubuntu's SABDFL ("self-appointed benevolent dictator for life," as he's known) Mark Shuttleworth just added comment No. 1834 to Ubuntu's Bug No. 1 -- "Microsoft Has a Majority Market Share" -- and closed the bug.
Sure, Ubuntu might have played a small part in knocking off Microsoft Windows as the dominant operating system for computing devices, but as Shuttleworth admits -- and I give him a whole lot of credit for doing so, it's more the move (especially in the consumer space) away from desktop/laptops to mobile and tablet devices running iOS and Android that has pushed Microsoft to the sidelines.
Coincidentally, I've also been thinking about Ubuntu's Bug No. 1 myself lately, and like SABDFL figuring that it should be closed.