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.
I'm surprised that the Fedora documentation for working with GRUB 2 doesn't address rebuilding GRUB 2 entries for EFI booting.
They do address it, but they get it wrong.
The grub2-mkconfig instructions for both BIOS and UEFI systems are the same. The problem is that this instruction will only build the BIOS entries. The UEFI entries won't be rebuilt.
Once you have your changes set in /etc/default/grub, here is how to rebuild the GRUB 2 entries for BIOS and UEFI systems?
# grub2-mkconfig -o /boot/grub2/grub.cfg
# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
It is perfectly OK to do both of these commands (using root, hence the # prompt, or with sudo), but you do need the one that matches your booting method (BIOS for older systems, optionally UEFI for newer systems).
The only reason I figured this out is because I poked around quite a bit when having dual-booting issues. Someone should fix the Fedora GRUB page. I'm a Fedora member and could probably make the fix myself, but I'm not 100 percent sure what I'm doing here is the absolute best method because my GRUB bootlines after doing this look different then they do when the system (either yum or dnf) does a kernel update.
I needed to use LibreOffice today. It's not something that happens very often. I almost always write or edit in a text editor, web form or Google Docs. But today I opened up LibreOffice.
I wanted to use "automatic" spell-checking in LibreOffice, which you invoke with shift-F7. But it didn't work.
I looked at my default "language," which was U.S. English. There was no little blue check next to it that indicated it had a dictionary. I checked my packages. I wasn't missing English.
It turns out there's a hack that gets spell-checking working and gives me the red squiggly lines under my misspelled words (that's the way I like to do it.
I found the answer in LibreOffice's "Ask LibreOffice" forum (which uses the same software as Ask Fedora).
Here is the fix from that helpful post:
Under Tools -> Options -> Language Settings: Writing Aids, the list of available language modules showed almost everything set. I unchecked and then re-checked "Hunspell SpellChecker" and "Libhyphen Hyphenator" and hit OK. (I strongly suspect that the hunspell was the significant checkbox). Then, when I go back to Language and look at the default language settings, the "English (USA)" entry has the ABC✔ by it, and now spell checking is working.
Best guess is that some results of invoking something from hunspell is saved by libreoffice and that with updating versions, the cached output is no longer valid. Re-invoking (when re-checking the checkbox) refreshes the cached data and now everything is all better.
It sure worked for me.