malak.ca — Server Hard Drive Upgrade

This is just a little note to mention that malak.ca has been down for the past 28 hours or so for an upgrade only planned as of a few days ago, when the site had been hanging for anywhere from a few hours to a few days, and diagnostics suggested that the hard drive may have been on its last legs.

A new 256-gig SSD was ordered and installed in the IBM ThinkCentre I claimed from a pile of computers to be shipped off for disposal in 2017 but only actually started using in 2020, with the intention of essentially setting up things as they were beforehand, with only an under-the-hood change of technology.

Here are a few highlights:

  • A backup of the blog database was created, and saved on an external drive;
  • The external drive, used as a backup for my other computers and the location of the static parts of my website, was separated from the machine, which was then powered down;
  • The old hard drive was physically removed;
  • The SSD was connected;
  • Fedora 34 workstation, which had been previously downloaded and installed on a USB key, was installed on the SSD yesterday evening (I’m currently still running on F33 for my desktop, laptop, and one of my worldcommunitygrid.org nodes)
    • The desktop for F34, on the core 2 duo, is faster, although some of that is due to the SSD, of course;
    • Interesting to see the dock moved from a vertical position on the left to a horizontal position at the bottom;
    • I find it interesting that at bootup, the activities screen appears to be the default;
  • This evening, the web server was installed;
    • Although we had planned to use php-fpm to separate permissions, but since this is a single domain box, we used a simple virtualhost;
  • MariaDB was installed;
  • The re-registration of my redirections for things like www.malak.ca with noip.com to account for the dynamic nature of my IP address was done;
  • The re-registration for my Let’sEncrypt was performed;
  • Various linux kung-fu tricks were performed, and magical linux incantations were uttered, and the setup was complete;
  • The external drive was reconnected;
  • The blog was restored from a backup.

The system is peppy, and this blog, which is hosted on the SSD instead of the external drive (as is the rest of malak.ca), loads somewhat more quickly.

As usual, great thanks go to my brother whose herculean efforts were at the core of the setup. Thank you!

Major changes to how PHP requests are handled in Fedora 33

(This post has an update 20210203 at the bottom.)

I run the www.malak.ca website and this blog on an old reclaimed computer using Fedora Linux. I used to use CentOS because of its long term stability, and in fact I still have a computer running CentOS running at full capacity as a computational node for the World Community Grid.

I have used Fedora on my desktops since 2008, and on my website server since at least 2018.

I have found CentOS very stable but, through my brother, somewhat limiting as each given version ages. My brother provides invaluable technical support and often does the heavy lifting on my servers and computers when it comes to, well, technical support and setup, for which I am very grateful. He has humoured me over the years in my use of CentOS, but has been frustrated with CentOS for years given its upstream source’s conservative development cycle and the difficulty in maintaining such systems over time.

In the meantime, over the years while using Fedora, I typically use a version for roughly its full lifecycle of 12 to 13 months, and I normally skip a version in the process. Previous to somewhat recent experiences, I would perform a full new install every year from a downloaded image; I was acting on advice from the Fedora website, increasingly old and out of date each time I performed a reinstall, to not use the dnf upgrade function on the grounds that it wasn’t ready yet. This further gave me reason for the occasional use of CentOS and its long term stability on some computers, which I might want to not want to bother reformatting yearly, let alone reinstall software. However, while I was performing another fresh install from Fedora 27 to Fedora 29 in the fall of 2018, I observed a command line upgrade of a Fedora system, and was intrigued. In the fall of 2019, when upgrading from Fedora 29 to Fedora 31, I used the command line upgrade path instead. (Here’s my archive.) This resolved, at least in my mind, my longtime concerns about the short lifespan of Fedora.

Unfortunately, this proved to be a matter of famous last words, since it was merely a convenience for upgrading, something that could be easily done on a weekday evening, instead of setting aside a Saturday afternoon and a (wholly pleasant) visit with my brother.

My most recent upgrade cycle of my server, from Fedora 31 to Fedora 33, was in and of itself as easy as it was on my laptop, desktop, and another box earlier this year. However, it proved to be effectively fatal for my website, since the web server was showing error 503 for PHP requests on the blog. Apparently, a PHP handling module, mod_php, used on my website, was deprecated in favour of php-fpm (here’s my archive). A mixed technical and somewhat editorialized discussion on this is on my brother’s blog. (Here’s my archive.)

For me, this isn’t so much an opportunity to complain; as I said, my brother did the real work in performing another iteration of setting up my website in April, 2020, only to do it once more in November, 2020, for which I’m grateful, under a fresh, baremetal install (which I performed.) Instead, the second comment to come to mind — initially, privately, and tongue-in-cheek! — after my gratitude that he would do the job yet again, was that my brother at least got to hone his skills on “the new method”.

After that, a few other things came to mind. As such, risking being a back-seat gratuitous commentator on the process:

  • It occurs to me that Fedora, while an excellent desktop operating system, arguably has risks associated with it as a medium-term and long-term server, given its mission to showcase and test new technologies as they are introduced while “old” technologies are deprecated;
    • And, since CentOS (and RHEL) grow old long enough before their 10 year EOL, but Fedora’s approximately 13 month lifespan is too short, how long is ideal?
  • The actual process itself of upgrading Fedora versions remains smooth, polished, and easy;
  • Could the upgrade process itself have included:
    • At least a warning that certain major changes were literally about to occur or were occurring?
    • An opt-out option for some changes?
    • Or involve as possible actually upgrading settings and/or other setups such that a neutral net effect on existing functions is effected, ie. change things properly, not just literally changing things without regard to any possible detriment to functions?
    • Or, make changes, but in separate, neutered files, and a notification that some potential conflicting changes have been made, requiring attention?
  • With regards to general version upgrading of my server, I should do some research into the new technologies to be installed before upgrading, so as to prepare for any major changes, just as any sysadmin should when upgrading versions to another of any long-term distribution such as CentOS, RHEL, Debian, Ubuntu LTS versions, or any other such system.

20210203 Update: It would seem that another victim of the change toward php-fpm was an inability to use the WordPress upgrade tool when it was time to change to v.5.6. It seems that using some file ownership settings on my machine, which facilitated my administration of the website on a larger scale than just WordPress, was at issue, and how php-fpm handles files and the required permissions, vs. the way mpm-itk and php-cgi would handle similar tasks.

And, at the same time, it seems to me that an additional question is raised, following my musing of “And, since CentOS (and RHEL) grow old long enough before their 10 year EOL, but Fedora’s approximately 13 month lifespan is too short, how long is ideal?”: The literal answer may well lie in “well that depends on individual packages and how they evolve over time, especially regarding the “real world” and other pressures which may shape the project’s evolution”, meaning that things may change more swiftly than Fedora’s 13 month lifespan, and others may outlive RHEL / CentOS’ (at least old) lifespan of ten years.

Which leads to my asking: “How to deal with change management?” and “How to choose a distro, and deal with change in a selected platform which has gone in a different direction from decisions leading to its original choice?”

Upgrades to Fedora 27 — what a breeze!

Over the past two weeks, I have upgraded two computers to Fedora 27 (from Fedora 25, having skipped Fedora 26 and enjoyed roughly a year’s worth of Fedora goodness).

The two computers are:

  • Dell desktop (main system):  Intel® Core™ i5-4460 CPU @ 3.20GHz — no Hyperthreading, 1 TB 7200 HD, 8gigs memory; screen upgraded separately to an Acer widescreen, and old screen relegated to a “new to me” computer setup as a node on the World Community Grid.
  • Acer laptop (secondary system): Intel® Core™ i7-5500U CPU @ 2.40GHz (Hyperthreaded), now 500gig SSD HD, 8 gigs memory.

Two of the equipment upgrades are the screen on the desktop, which is now a used Acer widescreen, and the laptop’s 5200RPM 1TB drive was upgraded to a 500gig SSD.  The laptop went from interminably slow to incredibly fast!  The comment from my brother:  “SSD’s are one of the few things that actually lives up to the hype.”  In my experience — under linux, anyway.  Under a corporate controlled windows box?  Well I’d say that my work computer, with an SSD, needs the SSD speed just not to be unusable!

The upgrades were incredibly easy this time, and fast, the new SSD installed on the laptop probably being the big factor.  In fact, I was able to do the basic install in about 15 minutes, and the rest of my list (made for Fedora 23, but the basic list is still valid) was easy to complete while on a business trip in the motel room during off hours.  In fact, one of the things that took a couple of days to realize:  Fedora has had difficulty with the UEFI on this machine in the past — it would install, and then not work, and I’d have to reinstall under legacy BIOS.  Note that I have a BIOS password, so perhaps in the past I just figured out how to make it persistent.  As for restoring the data, once home, I managed to easily copy all my data files from my desktop overnight.

As for the desktop, having just gone through the process a couple of days earlier with my laptop, I was able to easily update, and then re-transfer my data from the laptop overnight, as well as update my data backup on my home server.

The “big” thing this time?  The hardware upgrades.  The almost un-noticeable thing this time?  The installs, which were incredibly easy, quick, routine, and almost easily forgotten.  Sheesh, I’ve lost track of how many installs I’ve done over the years …

 

Fedora Linux spotted on 60 Minutes

Just watching 60 Minutes on CBS this evening, and the piece is on “hackers and cell phones”, air date 17 April 2016.

At one point, the reporter is calling, from Berlin, a person to whom she’d sent a cell phone. You see them switch to the hackers being interviewed for the piece, and their computer screen. On it, a command line shell with a bunch of code and output were displayed, and, whaddya know, in the upper left hand corner, there was a Fedora Linux logo. Offhand, because of the positioning of the logo, I’m guessing that they use XFCE.

Cool!

I’ve finally got a convert, sort of, to whom I’m giving a linux desktop!

In 2011 a new hire at work was assigned to join me on a few field jobs in order to expose them to the kinds of things we do at the office.

At the time, I enthusiastically told him about my use of linux. Suffice it to say his reaction was “What is this communist stuff anyway?!?!” Harrrummmpphh. “Red Hat is in line to have $1 billion with a big fat capital B in revenues this year alone. Doesn’t sound very communist to me at all.”

Back in mid-December of 2015 — after countless times of telling him about linux in the meantime, hopefully a bit more toned down — he sent me a message: “Here’s a modest budget; set me up, I’d be interested in trying it out.” I was practically beside myself in my pleasure.

I came back from the Christmas holidays and announced that I’d tracked down a used computer for free, and just needed to get it into my hot little hands. I explained that I wanted to give him a relatively risk free introduction. In the meantime, the computer in question, I’m told, proved to be dead and not usable. I’m promised another computer, and this week, when it looks like I’ll indeed be getting it in time for an install day this weekend, I further explained to my colleague: “The computer is probably about four or five years old but it’s supposed to be a dual core with 4 gigs of memory. It won’t be the best performing computer in the world, and some things it just won’t be able to do, at least not spectacularly, not because of linux, but because of the computer itself; however, it should still be good enough for videos, games, and day to day stuff, and you’ll be able to explore all the software available for it and see what can be done with linux, and you can add a few things like a bluetooth dongle if you like.”

He cautiously tells me all along that I’m building up anticipation; the caution suggests to me that he is mildly tongue-in-cheek meaning “of the disappointing variety”.

I then start asking him very specific questions, like what he wants as the computer name (I give him examples of current and past computer names I’ve used, and advise him to choose carefully since using the name of a pet or relative could backfire in case something goes wrong, and in the process of relating the experience to family or friends they may be confused or even become upset), the user name and password to use, the root password he wants, and things like which email client he uses at home. Pleased that he’ll be able to use a GMail interface, he begins to apparently genuinely say “Oh now you’re *really* building anticipation!” instead of the cautious insinuations from before.

Therefore in anticipation of the build this coming weekend, I put together this list of the main things I’ll need to install on his computer, especially since I’ll be helping my brother-in-the-know again with another desktop install, and try to get in some of his under the hood expertise at getting my server to be a bit more useful than a rarely used ftp server, a backup server for my data which depends on my remembering to back up my data on it, and consuming electricity.

So enjoy my list of things to do to loading a Fedora desktop very similar to how I use mine. And yes I know that there are plenty of things I *don’t* say, like “take this icon and place it third or fifth or last in the dock on the left on the activities screen” or, how to do “that”. 🙂

Installing Fedora 21 (Part II), 32 bits at a time

In Part I, I talked about installing Fedora 21 on a new Dell desktop, and promised a Part II, somewhat tongue-in-cheek. But wait folks, I was serious. 🙂

I have an Acer Aspire One which I received new out of the factory sealed box as a birthday present in 2009, and immediately converted it to linux after receiving it – Fedora 11, to be exact. It has used, as I recall, Fedora 11, 12, 14, 15, possibly 16, 17, and 19, all without any trouble. Well, ok, none that can’t be attributed to “whaddya expect out of a notebook vs. a full horsepower machine” and errors stemming from somewhere between the keyboard and the chair. ?

However, time is starting to march on with this machine, and while it was great under roughly 18 months of Fedora 19, it was clearly starting to slow down a bit, but … well, Fedora keeps releasing new versions, and, well, while CentOS 7, which is based on Fedora 19 and which I’d be happy to install on my netbook, unfortunately is only available under 64bit while my netbook is only 32bit. So my options were to either keep Fedora 19 unpatched, upgrade to Fedora 21 workstation, which I wanted to do, upgrade to Fedora 21 with XFCE, which would probably make it peppier, or explore other distros, which I don’t wish to do.

When Fedora 21 Workstation came out in December 2014, I downloaded the 32 bit version, and the fun began. Within a couple of minutes of booting up the live DVD and before the desktop loaded up, the machine went into hibernation. This didn’t feel right, but I hit a key and things came back to life. Then, within about a minute, the machine went into hibernation again. I hit a key again, got a minute of performance, and it hibernated again, ad nauseum, and ad infinitum, literally.

Despite this, I decided to continue with the F21 Workstation installation anyway, and I ended up babysitting the install, hitting a key to wake up the system every minute or so during the installation. On a single core atom processor running at 1.5 GHz, this took a good long while and a lot of keyboard wakeups. Finally, the system was installed, but it kept on hibernating after roughly a minute.

As a reference, I proceeded to install Fedora 21 XFCE Spin, and, except for hibernating once during the initial booting up of the liveDVD, it worked like a charm.

One solution I tried was to do a “yum install fedora-release-workstation” or somesuch from an installed XFCE spin, hoping to then do a “yum groupremove XFCE” and repeat “yum install fedora-release-workstation” just to reinstall any packages which may have gotten removed, but it bricked the install and I had to reinstall XFCE yet again.

For a variety of reasons which are now lost in the winds but which probably included having gone through the following suggestions from ask.fedoraproject.org, I managed to install and re-install the XFCE spin several times again after probably having reinstalled the Workstation a few times in between.

I went to ask.fedoraproject.org to ask for help (here’s my archive), and I got a few interesting responses.

The first response I got was:

“You can do tests and get logs without interference with systemd-inhibit – ie sudo systemd-inhibit bash. The system won’t suspend or hibernate until you end the process invoked with systemd-inhibit.” This didn’t work; hibernation continued as before.

The next response was “I’m just guessing, but it feels like the system thinks that the battery is almost empty and because of that does the right thing in that situation. I’m not sure which software component is handling this situation but anyway, there seems to be a bug that happens to manifest on your particular environment.” This could have been ruled out immediately – mostly – because at the time the battery was physically out of the machine when I tested, and I was running on mains electricity out of the wall. Nonetheless, I did check, with a fully charged battery in, to be sure I wasn’t being a fool; no such luck, under both cases, the machine kept on hibernating every minute or so.

All through this, I learned that at least one user with a Toshiba Satellite Pro without a CD player had this same problem, and worked just fine up till Fedora 20.

My “brother in the know” helped me with some research, and we found something: In the Arch Linux forums, the problem is described, and the user “Scimmia” comes up with the following workaround (here’s my archive):

“Try setting ‘HandleSuspendKey’ and ‘HandleLidSwitch’ to ignore in /etc/systemd/logind.conf” “Scimmia” further claims that this problem appears to be caused by systemd/logind. This all means that somewhere, signals are being sent out, rightly or wrongly or otherwise, that are being interpreted as “the clamshell lid is being closed, so it’s time to hibernate.”

To wit, my brother and I, after I’d installed Fedora 21 Workstation for the probably at least third time, then boot up an XFCE liveDVD (but do not install it), and through some of my brother’s linux kung-foo, he mounts the hard drive, using Thunar in the XFCE spin as a facilitator, and we edited the appropriate file.

… And Bingo was his name-OH. (Translation: Yup, that worked and the machine now works.)

Here are the instructions to correct the problem, at least for an Acer Aspire One, and which are also findable through ask.fedoraproject.org:

1) install F21 32bit workstation, by babysitting the system throughout the whole install to keep waking it up every minute or so (literally!)
2) reboot using a live-dvd that works on the system, such as the F21 XFCE live-DVD
3) mount the hard drive (not really sure specifically how my brother did it but using Thunar seemed to help out a lot)
4)open a terminal session and make sure the hard drive is mounted
5) edit the file /etc/systemd/logind.conf (such as using nano)
6) uncomment the settings for “HandleSuspendKey” and “HandleLidSwitch”
7) set the “HandleSuspendKey” and “HandleLidSwitch” options to “ignore”
8) save the file
9) reboot
10) enjoy

… and, it seems, my instructions, posted on ask.fedoraproject.org, helped at least one other user with an Acer Aspire one. I’m pleased. ?

Now, as for what I think of it … well I like F21 Workstation. On my laptop, it’s a slightly sluggish, but still working well.

Having to find multiple levels of internet access — oh, fun!

Disclaimer: I am musing on the challenges I faced while trying to secure reliable internet I required during a recent set of business trips, and the process of developing various solutions to these challenges. These challenges are, in a general fashion, typical of the routine logistical challenges I face when in-the-field, and no doubt of other field technicians. In no way am I trying to reflect negatively on my employer, who for the purposes of this entry shall remain nameless.

I was recently on a couple of business trips, depending on an iPad as a critical part of the execution of the contract. This trip was to a small city of 25,656 (according to Wikipedia), big enough to have plenty of internet access points, cell phones, and cell phone data. As far as I was concerned, in fact, I was in a mini-mini version of Montreal, home for me, to those who haven’t figured it out yet.

The way the iPad is set up, wifi internet access is required to transfer building plans needed to do the work to the iPad, and transfer back files and data collected from my field work. I have made no bones mentioning to some key people heading the overall project that this is a potential Achilles’ Heel to the execution of the project, since, at least in the overall project’s fringe locations sufficiently beyond population centres, internet access would be a spotty luxury at best. My trips were at least symbolically close enough to the edges, underlining the potential problem.

One of the first challenges I found was that the iPad didn’t seem to play well with the internet supplied in the motel (DataValet); although I did manage to get it to work once, it proved a bit too frustrating to get working reliably. A colleague confirmed that he’d had similar problems getting Apple products to connect to DataValet. I had no trouble getting my personal computer running Fedora 21 Workstation to work with DataValet: In fact, besides not recalling having trouble over the years connecting to wifi that wasn’t specific to Linux or Fedora, I would actually say that the experience was even easier than in the past, since the daily leases seemed to automatically renew, although it seemed to insinuate itself by a “convenient” automatic popup window. In parallel, my work Windows-based machine also worked flawlessly throughout with DataValet, although if I remember correctly, I may have had to occasionally open up a browser in order to renew the leases.

Add to this challenge, my employer’s local office didn’t seem to have wifi, or at least, assuming that it *was* there as a hidden network, my work computer didn’t automatically connect to the corporate wifi when not plugged in to the corporate network, which it normally does at my home office.

My first solution was to fulfill a purpose of my having asked for a company smart phone in 2014: Create a hot spot using the data plan on my work phone to do data transfers when not in a wifi zone that works well for the iPad. However, it seemed, between the picture-heavy data and the fact that the iPad seems to do automatic background backups when hooked up to internet — a feature to which I initially had a (negative) knee-jerk reaction that nonetheless actually was useful at one point and since — my phone appeared to run out of my data plan for the month, as evidenced by the sudden stop of internet connection through the phone while still operating just fine as a phone. Having quickly checked the phone’s data usage logs and determining that I’d certainly gotten to the neighbourhood of the limit I believed I had (2 gigs), I assumed that the phone’s contract had a limit set by my employer to turn off the data plans until the month rolls over in order to avoid overage charges. I later learned, upon my return home and standing in front of the IT tech responsible for the corporate cell phones, that the problem was presumed to be an unusual set of settings probably set by some esoteric app (of which I have have very few, esoteric or otherwise, on my work phone), or possibly a SIM card problem, which turned on off the phone’s data capabilities, and that in any case the company has no such policy to ask the cell service provider to turn off a phone’s data access when it reaches the limit of “included data” in the plan, until the rollover date. The lack of internet on the phone is “solved” by resetting the phone to factory settings; I should get instructions on how to do it in the future should I be faced with the problem again. 🙂

This led to a second solution: I used my personal phone to create a hotspot and consumed a bit of my personal data plan, which didn’t bother me too much, at least until it were to involve overage charges. Not that I checked, but based on the little amount of time I used it, I’m sure I never got into that area.

The next solution also created another challenge due to a flub on my part: My client finally gave wifi access to the iPad at her various locations; however, I should have requested that she also enable my work computer, since I had a secondary need for internet given that I developed a need to produce or modify extra plans several times once arriving at some sites, and as such a need to transfer the plans off the computer and onto the iPad.

Finally, I realized that when I have wired access, I had yet another solution available to me: I could set up my linux laptop to create a wifi hotspot. This was rather easy, at least under the current gnome version in Fedora 21 and I believe has been for quite a while under the gnome 3.0 series, and probably before too. Unfortunately, this was wasn’t a solution at the motel since it only had wifi and no wired access, and I didn’t have an external wifi receiver with a cord to provide the wired internet and free up the wifi card.

Here are some screenshots of how easy it is to setup a wifi hotspot under Gnome 3:

step 1

step 2

step 3

step 4

step 5

Feeling a bit curious along the lines of “shouldn’t this be relatively easy under Windows, too?”, I checked on my work computer, and while it seemed possible, and indeed my brother once did it for me with his Windows computer, it was not obvious at all; in fact, I gave up after about four or five click-throughs with little end in sight.

Hence, at the local office and having set up my laptop to create a local wifi hotspot, I’d created a mildly-amusing-to-me setup on my temporary desk, plugging in my personal laptop to the corporate network, running a hotspot using its wifi card, and using my work computer normally over wifi as well as doing data transfers from the iPad.

Back at home and at my home office, I mention my difficulties in getting internet access to my supervisor (who isn’t a computer techie type), who thought that creating a hotspot under Windows couldn’t be done, or at least he didn’t realize it could be.

Further discussing this with him, I explained the situation saying “I don’t mind trying to find other solutions — that *is* my job — but after not having two A Plans (the motel internet not working for the iPad, nor having wifi at the office), then suddenly not having a plan B (the company cell phone internet not working), having to depend on my personal phone’s data plan, then having to depend on the client’s internet access but not having enough access for all devices, and finally coming up with a part-time solution to replace one of the A-plans — using a second of my personal resources in the form of my personal laptop — there’s a problem here,” to which he agreed.

Jovially, he did however suggest that “in the next leg of your travels, I happen to know that if you can go to the local library, they have free wifi”. This made me realize that if necessary and if possible, I could also try the free wifi at the local Tim Hortons (a popular Canadian chain of coffee and doughnut shops), assuming that there is one in the remote town where I’ll be visiting next.

Which has me really thinking about the problem:

– not all the field techs in the company have smart phones with data plans, and as such not able to create a needed hotspot in order to enable the execution of a project;
– not all the field techs have personal smart phones with a data plan, nor should field techs in general be required to use their personal data plans, let alone go into overage charges, in order to enable the execution of a project;
– at least at first glance, it doesn’t seem to be a quick and easy thing to turn a windows machine into a hotspot in order to enable such work — and I don’t want to hear from the peanut gallery on this one, since I *know* that it *can* be done; my point is that at first glance, even a moderately savvy user such as myself shouldn’t have to say “It’s easy under Gnome 3, why isn’t it about as easy under Windows? Boy it’s a good thing that I had my personal laptop with me!” (On a side note, usually the stereotype is that “Windows is easy, and Mac easier, but isn’t Linux hard?” 🙂 )
– and, only a limited number of computer users are using Gnome 3, where it is easy to set up a hotspot if you either have a wired connection to the internet, or two wifi cards on your computer. (I’ll have to check with my brother, who uses XFCE on one of his laptops, which is on a technical level identical to mine, to see how easy it is under that desktop; obviously, it’s technically possible; I imagine it’s just a question of how easily different desktops enable the functionality.)

Which leads me back to the above-mentioned problem of “what do you do in remote, small villages where you don’t have a corporate office with wifi, motel / B&B internet access is spotty at best, there’s no cell phone coverage, and there are few if any public wifi spots like a restaurant or a public library?”

I just hope that the library’s free wifi isn’t provided by DataValet. 🙂

I’d say that Fedora has arrived!

Almost five years ago in March 2010, I stated “Ubuntu and Fedora LiveCDs — Ubuntu a clear winner!”

I’d burned two live CD’s — one of the current Fedora of the day, and one of the current Ubuntu of the day. I had wanted a group I belonged to to use one to reformat a virus-infected computer to use it again. Incidentally, they declined the honour, however that’s beyond my point: I didn’t want to give them (or anyone) the Fedora CD, while I thought that the Ubuntu CD was great out of the box, specifically including OpenOffice.org (now LibreOffice) and a cute little directory including a short video, a sample mortgage calculator, and two or three other little gems which really put the CD over the top for its immediate usefulness.

Well, I haven’t really used Live CD’s much since I’m not all that worried about having linux on the run, but at this point Fedora 21 seems to only be available by Live CD’s. But to wit, the experience with Fedora 21 seems to be quite the improvement in experience, according to at least two of my somewhere between the stated and implicit standards of comparison: The inclusion of (now) LibreOffice, what I considered a killer omission, and the ability to quickly and easily install many “productive” pieces of software through the new software installer. To be fair, at the time Fedora limited itself to CD’s and in its efforts to include as wide a base as possible for supposed widest mass appeal, Fedora was unable to include OpenOffice.org (or, as possible, any usable subset thereof) due to space restrictions, although it was able to include AbiWord.

Now, Fedora Workstation includes LibreOffice, and by typing into the search box in the “Activities Overview” (click on “Activities” on the upper left hand corner of the screen, or invoke it using the “hot corner” by bringing your cursor up there), the installed software that may help you, as well as a number of other pieces of software in the repositories which may help you, as indicated by a little shopping bag to the left of the proposed piece of software.

screenshot of proposed software

Well, I guess now I just need to find someone who needs to have their computer saved from viruses and spyware. 🙂

Installing Fedora 21 — Part I

Well, well, Fedora 21 Workstation came out in early December, 2014 to (at least my) great anticipation. It works great, and it’s a nice evolution in the Fedora desktop.

Initially, one of the biggest things that had me confused about it was wrapping my head around the hoopla: What’s the improvement? What’s the big deal? What has really come about to fill up the time between the release of Fedora 20 in December, 2013, and the release of Fedora 21 in December, 2014? Ok, tell me. “Uhhhh …” And so on.

Eventually I understood, or at least presumed, rightly or wrongly, that the biggest improvements for me would be under the hood and I wouldn’t really notice much, although I’d see the better and more intuitive software installation manager on the gui, and the polish, which I have. Apparently — for (one of) the main (now) Products, the Workstation — improvements would show up in the clearing of many bugs, general issues, and polish issues, and as well as choosing “best of breed” components (and in some cases, working with or even creating some upstream projects expressly to make desired components into the “best of their breed”, at least toward Fedora’s new vision). This would be instead of Fedora giving the impression (again, rightly or wrongly) of just “throwing together a bunch of packages and compiling them into a distribution” (admittedly, that worked rather well, and by working with upstream projects directly to fix bugs and contribute desired new functionality.) And finally, the dimensions of the windows have been changed such that in many places, the gray space and borders are smaller and thinner.

So after downloading and burning the 64-bit ISO (and concurrently, the 32-bit iso, the subject of Part II), and doing a full backup of my /home directory (including the hidden directories), I dived into the installation.

I had no trouble at all installing F21 on my NEW NEW NEW Dell Inspiron Dell i3847-5387BK PC (Intel Core i5-4460 / 1TB HDD / 8GB RAM / Intel HD Graphics / Windows 8.1). Firstly, nuking the Windows install was a great pleasure after having been pestered into first installing the Windows 8.1 which came with the computer. And that’s not including all the really annoying and really invasive questions the install asks, like full names, areas, and connecting to your (or signing up for) Windows Live or whatever account (which of course I don’t have).

The install was fairly easy (I suppose I’m not saying much given the several, several dozen linux installs I’ve done over the past eight plus years). In fact, the liveDVD — only because Fedora gave up on the size restrictions of CD’s for the live versions a few years ago, the image size was the order of 1.4 gigs (ok almost twice the size of a regular CD) — booted up rather quickly (faster than I’m accustomed to with the usually low-powered P4 single cores), and the first thing I saw was an option to either try out F21 Workstation or go directly to installation, all on top of Gnome Shell. I of course hotly jumped onto the install option, egged on by the annoying Windows install I’d just done (which, BTW, went flawlessly beyond the nuisances mentioned above, and fairly quickly.)

The biggest thing that was a bit confusing was discerning in Anaconda the checkbox that allowed me to free up all space on the hard drive, given that it seemed to be slightly below the screen and I needed to scroll down to it.

In the part of Anaconda that asks for location in order to set the time zone (and possibly / probably) set other regional default settings, Montreal — where I live — isn’t available. To me this is “a (minor) thing” since Montreal *used* to be available in the Anaconda locations list. The main cities in my time zone and “nearby” were Toronto and New York. I suppose that setting “New York” is generic enough, but in the presence of a long list of city names around the world spanning multiple time zones and with multiple redundancies per time zone, requiring someone from Montreal to indicate that their location is Toronto is downright near insulting — no Maple Laughs here! 🙂 Heck, I couldn’t even choose Ottawa had I wanted to, or choose to be equally insulted to indicate Quebec City — Go Habs Go! 🙂

Once the basic information was input, the installation was great and quick; so quick, in fact, I neglected to enter a computer name — easily fixed with a “hostname (addnamehere)” and “nano /etc/sysconfig/network” as root and editing things appropriately.

Interestingly, UEFI was not even a non-issue (ok so I do think that tin-foil hats are a legitimate fashion statement. 🙂 ) A quick check afterwards of the pre-boot menu options listed the following:

Boot Mode is to: UEFI
Secure Boot: ON
UEFI Boot: Fedora UEFI OS

How pleasing to see that Windows *isn’t* listed.

Now, beyond assuming that most linux distros pay the UEFI tax, err, registration fee, I wonder if Oracle pays it for Solaris, IBM for z/OS — I assume as much based on a cursory search for “IBM zos uefi” — or just about any other os developer working on intel architecture.

After that, the computer ran (and of course still runs) great. I even described it as “frighteningly fast”. The new software installer in F21 is quite helpful in suggesting software I want if it’s not already installed, and installs it quickly. The best part is that it’s seamlessly integrated with the activities screen where I can enter software I want to use in the search line, and most of the uninstalled software that I’d want is listed.

A few other command line installs were necessary though, to install (what my brother calls “your linux kung-fu”) some things like DenyHosts, some codecs, and so on.

However a there was one little problem with the settings. For one of the settings surrounding locations, I entered the likes of GB or UK for Great Britain / United Kingdom, so as to get settings with British spellings (again, Canadian English settings weren’t available). This had the result of setting the calendar applet at the top center of the screen to start weeks on Mondays. Now, I know that around the world this is gaining a certain traction for a variety of reasons, including ISO reasons, but this is incredibly confusing to one who is accustomed to calendars using Sundays as the first day of the week. (Yes, I know that this same argument, appropriately centred on Mondays, applies to those who use Mondays as the first day of the week.) This was finally fixed by setting the locales setting in /etc/default/locale to:

ANG=”en_CA.UTF-8″
LC_TIME=”en_CA.UTF-8″
LC_PAPER=”en_CA.UTF-8″
LC_MEASUREMENT=”en_CA.UTF-8″

Well this solution didn’t seem to be persistent, even if the file is. I ended up going into the “settings” / “region and language” option of the gui and setting both the language and region to, surprise, surprise, Canada.

Well this system is up and running, and works just like Fedora, surprise, surprise. My /home directory was restored with no trouble at all. And, while I was happy to have used Fedora 19 for a year and a half (as far as I’m concerned, Fedora heaven for me, getting an extra six months of system stability) I’m also glad to have updated to Fedora 21.

Upcoming: Part II — Installing Fedora 21, 32-bits at a time

I now have a Fedora Friend Finder!

In early 2011, I decided to go to a FudCon in Tempe, Arizona (here’s my archive). And here’s my blog summarizing my participation.

One of the things in the list of items to bring was a Fedora Friend Finder (archive, since the link disappeared), in other words an extension cord with multiple outlets / a power bar. This of course makes sense when you have a bunch of computer people gathering together, face to face: We still bring computers and as such we want to plug them in.

As you can see if you followed the link or checked my archive, the page featured a long power bar with 12 outlets, like the following:

12 outlet power strip

I of course had considered the power bar shown to be quite fanciful and even comical to the point of farce, and as such I assumed that someone had played around with The GIMP to produce the image.  However, the message was clear: I brought a four outlet power bar with a roll-up extension cord to FudCon Tempe, like the following:

cord caddy

During FudCon Tempe, I was mildly popular during the various “unconference” sessions and certainly made friends as a result of my power bar. In fact, during the “Lightning Talks” at the end of the “unconference” part, I was so popular that I had to turn people away who wanted to plug in, even after several other power bars had been plugged into mine.

Fast forward to this past week in 2014, and I’m shopping for supplies at a Canadian Tire for a job site I’m starting up, including electrical extension cords and power bars. What do I find? To my amazement, a 12 outlet power bar just like I’d seen on the Fedora Friend Finder web page. The person I was with was a bit bewildered by my fascination with it; to him, it was just a big power bar. It may have been odd, but it was just another power bar.

I wasn’t just fascinated; I was practically beside myself. Here I was in front of a real live example of the farcical prop I’d seen on a web page. Of course, I had to buy one.

Here’s a pic of it with eight personal pumps and one DryCal calibrator hooked up, charging the internal batteries:

my Fedora Friend Finder

I think it’s cool. It will probably eventually be used at home where I have my multiple computers and a big wide screen TV and PVR, where things are currently lit up like a Christmas tree, so to speak, with multiple power bars which are nonetheless underused given the multiple oversized adapters.

However, the temptation will be there to bring it out to any events at which not only would such a power bar be useful, but also to just brag on an “over the top” level and get incredulous looks along with a “may I plug in ?!?!?”