I hate to say this but Linux software is not perfect. I know, I know, but nothing could possibly be wrong with openSUSE, right? Well, Linux and all the open source tools are created by people and since we are flawed, so are our creations. Sometimes, things can slip through the quality assurance process at openSUSE and however rare, they do happen.
One of my problems that has shown it’s ugly head is an issue with the wifi driver. Sometimes, for whatever reason, it cannot authenticate. Another situation is, sometimes, you may have an issue passing a device to a Virtual Machine and it doesn’t come back quite right.
In short, if you have a device on the PCI bus that needs to be removed and added again, there are some ways to do that. To get the PCI device ID, run:
Take note of whatever your troublesome device is from here.
echo "1" > /sys/bus/pci/devices/$NUMBER/reset
This should reset the device and have it behave, but as you may know from your experience in having used the original Nintendo Entertainment System, sometimes, it just isn’t good enough.
The sleep 2 is only necessary if you are copying and pasting into the terminal or creating a script. It is just a pause before it rescans the PCI bus. How I used it and I did create a script for this that I can invoke if I have problems.
Software isn’t perfect, I have historically had issues on more than one distribution with PCI devices requiring a reset. This method works with openSUSE Tumbleweed in the year 2019. If this should change, I will update this post.
NetRunner (19.08) is not one of those distributions I hear touting its uniqueness and wonders loudly on the Internet. As part of a two week challenge for BigDaddyLinux Live, I lassoed an ISO and took it for a spin on a VM. Some may argue that a VM doesn’t make for a good test experience and I would agree to that, sort of… This is not going to be a test of NetRunner’s performance on bare metal but rather, this is an impression of how the developers are answering the operating system question.
Bottom Line Up Front, NetRunner has a look of its own. The default software is refreshingly not minimal as that seems to be the talk of many Linux enthusiasts (I blame Arch for that). The included pieces of software makes for a great showcase of the various KDE applications. Personally, this is a good approach for most users. Those minimal installation folks should just learn to remove software using the package manager if that is such a huge issue. I am not keen on the default theme with the red cursor and the lack of a usable Dark NetRunner theme. Aside from that, it appears to be a good KDE Plasma experience and a fine showcase of the various applications a Linux user should try. This is my biased review of NetRunner as an openSUSE user.
The installation of NetRunner, like most of the Linux world is very straight forward and not problematic. Although, I realize that this is not a shared view among all users, this is my experience.
The bootloader gave some options so I wanted to play around with them. Unfortunately, the Memory test didn’t work for me but it was a neat idea.
Rather than continue to play around with these tools, I decided I would go ahead and unwrap this NetRunner present and see how it goes for me.
Essentially, a few moments later and the Desktop presented itself in all it’s KDE Plasma beauty. The default look is fine with me. Not my preference but I don’t expect every distribution to ship my preference, that would be silly and would undoubtedly make touring other distros incredibly boring.
The installation process uses the Calamares installer so it is incredibly easy to do. Thankfully, there isn’t any scavenger hunt required to initiate the installation. Once the installer has settled, select your Language and Location.
Next will be your keyboard layout and your partition scheme. I chose to erase the entire disk. It is interesting to note that the default Swap size is twice your RAM amount plus a little extra for good measure.
The last bit of using your noodle to get this set up is to set your user name and root password. Once complete, you are given a Summary and final sanity check before you commit to the installation.
The installation doesn’t take before it is finished which gives you a great opportunity to read the installation propaganda as you wait, or you can go do other things as I did and come back when it is done.
When you are done, feel free to reboot or hang out in the live session, whichever works for you. I wanted to see how quickly this would boot and I wanted to dig into it.
First Run and Impressions
The boot time was reasonable. Not lighting fast but reasonable and of the speed that I would have no complaints. Ultimately, I would rather it boot every time than boot occasionally really fast and leave you scratching your head when it doesn’t choose to boot.
The login screen or sometimes called “Display Manager” looked nice enough. I couldn’t put my finger on it but it made me feel like it was an older layout. That might be me and if we were in court, I would expect the other lawyer to object to that and strike it from the record.
The desktop does look nice, but I am not sure about that red cursor. It does bring back the happy smiles of the Amiga OS as it did back in the early 90s. The version of Plasma that shipped with NetRunner 19.08 is 5.14.5. A bit older as it was released in October of 2018 but not a bad version at all. It should also be noted that this is not an LTS version either.
The menu is the Application Dashboard. This is not my favorite menu system but that is easily changed. I do admit, it is a nice looking interface but it is just not for me. I don’t like menus that block out my desktop.
The game selection brought a smile to my face. I am glad to see Steam is installed by default. If you are into gaming, Steam is your portal to a wide selection of electric joy. I would have liked to have seen Lutris too but one out of two is not too bad. Excitingly, a game that I did forget about was BurgerSpace. It is a BurgerTime clone that I played on the Intellivision as a kid. Although, BurgerSpace doesn’t have the fun 8-bit music as the original, it was still fun to play… until I couldn’t get down the ladder…
I wanted to explore further the different applications. I found it interesting that there is a Skype client by default. The multimedia applications installed by default are some that I use. Handbrake and Kdenlive are two that I use with some frequency. There isn’t VLC but SMPlayer is available which is fine. The Web Camera application is Cheese which is also fine.
The Web applications section I thought was curious. Telegram was good to see but I scratched my head on the WhatsApp. I know that is used by many but the juxtaposition with having it alongside Hooktube seemed odd. Hooktube divorces you from the YouTube-ness of YouTube while WhatsApp is an application that will be collecting on you. It is easy enough to remove but I just thought it odd. I am sure that there is a valid reason for the selection, I just don’t know what that is.
The software package manager is very decent and I like the interface very much. It’s very clear on how to use, perhaps overwhelming for a new or less technical user but it is perfectly usable. I have found that there is this rather large section of the populous that doesn’t like to read and a wall of text can be overwhelming when there isn’t a giant “GO” or “NEXT” button to guide their eyes. When committing to updates, authentication is required. This is in contrast to what I am most accustomed in openSUSE.
What I found fascinating is that I found interesting is that it looked like the critical updates were not automatically included. Perhaps they were not selected or I had done something wrong but I would assume that these would be priority. I completed these updates and rebooted the system to take advantage of the new kernel and such.
The default NetRunner theme is too light for my liking. I went into the System Settings to correct this deficiency and unfortunately, I was met with less than stellar results. Somehow there seems to be something wedged in the theme engine that makes even the Breeze Dark theme unusable.
It didn’t seem to matter which dark theme I chose, NetRunner, changed the colors, Breeze Dark, use the Dark Color scheme, the result was the same in that it was not possible to read the text as any contrast was lost. For whatever reason, the desktop was not respecting my request.
This is basically a deal breaker for me. I do not like light themes… at all… and if I cannot allow my eyes to take a break from the light pollution, I am not a happy user. Just a mention, but I did notice that there was some reorganizing in the menu selection. Plasma Tweaks was an additional section that included all the visual tweaking settings. It seemed redundant and a silly call back to the Gnome Tweaks mess of applications.
There are some other interesting applications included in NetRunner that are worth looking into but I have already blathered on far too long about my first impressions.
What I Like
NetRunner does not do the rather common nonsense approach of not bundling software with their desktop environment. They have taken the time to include a nice and sensible selection of applications to get you going right out of the gate. Quite literally, after a short installation cycle, you can be up and running, creating, playing or doing very typical computer based tasks. The selection, although somewhat peculiar is a great showcase of applications.
The package manger, Synaptic, is frankly, one of my long time favorite package managers ever in Linux. It is the Debian staple of managing your packages and no Debian system should be without it. The fact that it is installed by default is a huge positive. As nice as the software centers are for discovery of applications, Synaptic just does the job better.
What I Don’t Like
The theme, something is wrong with the theme and how Plasma handles themes. I am sure I could correct it with enough time but that is a pretty significant annoyance. I would prefer NetRunner just use the standard Breeze themes and modify it to whatever would make it uniquely NetRunner with maybe a different shade of blue and the logos. Making the theme as such that I cannot read the text when switching it to a dark color scheme is a no go.
There isn’t a system control panel like you would find on the openSUSE or MX Linux distributions. I find YaST to be such an important tool for any system I set up. The KDE System Settings is great for user level settings but not the best for system wide settings, user management and the like. If I could wave the magic wand, I would like to seem more distributions use something like YaST, if not YaST itself on their distros for better system management.
The Software selection, although mostly great had me less than happy about having Skype and WhatsApp installed by default. This might make me sound like an old man yelling at kids to get off my lawn, but I have made it a point to push people away from such services and use them only if necessary. Having these installed by default don’t make me smile, I would much prefer to see other, less invasive applications in their place. Telegram was nice to see so there is that.
NetRunner is a distribution that is clearly focused squarely on it’s own goals and appearance. If you aren’t going to stray from what they have set in place, this will do nicely for you. The software selection is a great start as a sensible base of applications and also has some applications that should probably be removed
I am not exactly sure what I think of NetRunner. I like much of what they are trying to accomplish, I appreciate that they are doing their own thing and seemingly have a goal in mind of targeting a general user with this distribution. At the same time, I do not like some of their defaults and find some of there selection, not to my liking. Would I recommend NetRunner for someone to try? Yes, but it wouldn’t be the first I would recommend. It scores high on the ease of installation but low on the ability to cleanly customize it. It scores high on default software selection but bothers me that they have selected some other applications. Overall, it is a decent distribution and if you are not satisfied with your current experience, this is worth a try.
Would I switch from openSUSE to NetRunner? No, not a chance but I am glad NetRunner is out there and answering the software needs for many people.
This is nothing more than a placeholder post and an announcement of a somewhat embarrassing example of my poor video editing abilities. I previously created a blathering about getting the Commodore 64 on the Internet with IRC and step by step instructions but under the pressure of one person (see how easily I am swayed). I made a short video about the process.
Feel free to watch if it you wish and if you want more low quality, low budget productions, let me know. I just may get to it. I need more practice with Kdenlive.
I have been using BTRFS on all of my openSUSE machines without issue. In my quest to build a new multi-roll system to act as a server, workstation and occasional casual desktop use, I wanted to have a storage solution that was very fault tolerant and would allow me to expand my disk size with minimal effort. That is in both replacing individual drives with larger drives and potentially adding another controller card to have more drives.
ZFS is in the news as the new “hotness” for a file system and it does indeed have a lot of the really awesome features BTRFS provides, maybe more but support in Linux doesn’t appear to be as robust as BTRFS. Could my mind change in the future? Absolutely, but for now, until I get the stability of BTRFS on root, the snapshot system and the ease of flexibility in altering the array of storage, I will stick with BTRFS.
I have been looking at doing an upgrade to my monitor situation, for numerous reasons. The monitors I am using are of unequal resolution, size and aspect ratio, it has been fine but I am becoming less satisfied with its usability. This is especially true since I started to use some of the tiling techniques built into Plasma. I just happen to need more pixels. Looking at my available options, I became interested in one of these 1440p monitors. My issue is, I am not interested in a curved monitor. I think they look just a bit silly and I don’t stand directly in front of the computer all the time. Interestingly, it seems as though the curved screens are less expensive then their flat counterparts with the same resolution and frequency. Although I would prefer a flat screen, it is more economical and of better specifications to go with the curved model.
I’m not prepared to make a purchase today as I need to do some more research on the subject but I am now very much interested in a single 1440p monitor rather than my two cobbled, odd lots hanging above my laptop.
US military has been using 8-inch floppy disks in an antiquated ’70s computer to receive nuclear launch orders from the President. Now, the US strategic command has announced that it has replaced the drives with a “highly-secure solid state digital storage solution,” Lt. Col. Jason Rossi
The 8-inch floppy disks have been used in an ancient system called the Strategic Automated Command and Control System, or SACCS.
It’s used by US nuclear forces to send emergency action messages from command centers to field forces, and is unhackable precisely because it was created long before the internet existed. “You can’t hack something that doesn’t have an IP address.
Despite the age of the system, the Air Force is confident in its security and has a pretty good handle on maintaining it. By contrast, installing an all-new system isn’t as easy as it sounds. “You have to be able to certify that an adversary can’t take control of that weapon, that the weapon will be able to do what it’s supposed to do when you call on it,”
My U13 Logic chip is likely failing. I am sure it’s not the RAM as I am having an intermittent problem with my system. Sometimes I get a blank screen and sometimes some garbled mess of characters in a range of colors. Based on the likely causes, I am quite sure it is the 74LS257A Logic IC. That should cost me less than $1 for the part and around $10 on shipping.
I am late on the release of this podcast, not because I am fading out already, but because of life things. Regardless, I wanted to follow up on a BDLL from 19 October 2019. The discussion was about distro hopping, why Linux users distro hop. Often when people are new to Linux, they hop around and try new distributions. Some people like to jump around every time there is something new released.
Some Distros cater to some bits of hardware better than others. MX Linux on old hardware, openSUSE on newer hardware, Manjaro or Pop!_OS for gaming. Debian for obscure hardware. Ubuntu and its flavors for the mainstream.
I am not a distro hopper, embed myself, decided to stick around and help out to the best of my ability.
Between Mandrake / Mandriva fading and embedding into openSUSE I jumped around a bit. When I decided on openSUSE, I knew it wasn’t perfect, there were some issues but they were easily mitigated, I was most enamored with the friendly and helpful community along with the “ecosystem” of tools around openSUSE. The ease of installing software the graphical way and a pretty awesome wiki.
I mostly try out other distros to see what else is out there. Nothing ever seems to capture me like openSUSE. There are many good choices of Linux and I would probably be content elsewhere but nothing quite gives me the excitement that the green chameleon clad openSUSE provides.
Firefox has been updated to version 69.0.2 which contained a single fix for Linux-only crashes when changing the playback speed of YouTube videos. Fwupd shipped at version 1.3.1, that is a daemon that allows session software to update the firmware. It now allows for disabling of all plugins and added support for thunderbolt interfae for kernel safety checks. Gstreamer and many of it’s plugins were updated to version 1.16.1 which offered performance improvements. nodejs12, python-packaging and tcpdump were updated to address more than two dozen CVEs.
Plamsa 5.17.0 arrived with some significant changes to the new version. The release announcement says that this new version is as lightweight and thrifty with resources as ever before. Notably, the start-up scripts were converted from a slower Bash to a faster C++ and now run asynchronously, which means it can run several tasks simultaneously, instead of having to run them in sequence. KDE Applications 19.08.2 improved High-DPI support in Konsole and other applications. Many bug fixes in Kmail and saving messages directly to remote folders has been restored. Many other KDE applications received updates as well. e2fsprogs update 1.45.5 addressed a CVE where an attacker would have been able to corrupt an ext4 partition. Updates to gnutls, Nano and php7 were also included.
Mumble was finally updated to 1.3.0 after getting through the rigorous legal review of the SUSE lawyers and now those crazy lips are gone.
The Tumbleweed Snapshot reviewer gives 20191009 a moderate score of a 90; 20191011 a stable score of 92; 20191012 a stable score of 96; and 20191014 a moderate score of 82.
The Project Name Change Vote Continues
The discussion around changing the name of the project is still continuing in the mailing list. The vote has been extended out to the 7th of November, 2019. It has been decided to create a wiki page to consolidate the information. The keypoints can be summarized by the following:
For Keeping the project name
If the name is changed, we would lose brand reputation earned over the years.
Many members and other contributors are strongly attached to the current name.
Changing the name might give the impression that the relationship between SUSE and openSUSE is strained.
A lot of work will be required to rename domains, OBS projects and metadata, GitHub namespace, packages trademarks, etc.
Rebranding requires a tremendous amount of communication (and money) over years to establish the new brand name.
SUSE can transfer or license relevant trademarks to an openSUSE Foundation.
The relationship with SUSE is part of our marketing strategy, e.g. Leap/SLE’s shared codebase.
Changing the project name will make current openSUSE swag (T-shirts, mugs, stickers, etc) obsolete.
Reasons in favor of the name change
openSUSE is often typed and/or pronounced incorrectly (e.g. OpenSUSE, OpenSuSE etc). Watch how do you say SUSE?
The Free Software Foundation (FSF) complains about the looseness of the term “open”.
The distinction between openSUSE and SUSE can be confusing to people new to either brand. Some people have been known to shorten openSUSE to SUSE.
If the community thinks that the project benefits from a new name then this is the moment to change it, i.e. before registering a new legal structure (like a foundation).
My thoughts on this, the reasons for a name change seams superfluous. Although I understand the there is some confusion and how it is typed is often wrong, those do not outweigh the marketing strategy of the Leap/SLE’s shared codebase, the amount of work that would go into rebranding, renaming and making all the cool things I have today obsolete.
I think it is good that we the openSUSE community have this discussion. It has been good for me as I can reflect on my reasons I don’t care for it and rather than just make it an emotional and close-minded decision, I can look at the facts and make a rational decision to keep the name just as it is.
If the name changes, I won’t be upset, disappointed, yes, but not upset. It is the community and the technology that I like, the name is secondary.
I am not one to just toss something when it is broken. I want to give every piece of equipment a shot at another life whenever possible. Somethings do have to go to the big recycler in the sky but not without some kind of fight at my end.
I couple years back when I thrusted myself into the foray of “modern” gaming, I purchased two of these “Rock Candy” Gamepads from a local retailer. This was for my first Steam Game purchase, River City Ransom: Underground. They worked quite well but having kids with passion bubbles very near the surface, gamepads have a tendency to go flying or falling from time to time.
After some time of play, one had a fall too many and the plastic broke that held the batteries in place on one controller. Within a week, the other decided it would no longer turn on. Both controllers were put away into storage, until yesterday.
My oldest son asked if they could be fixed and I suggested that we could take the board from one and put it in the body of the other. He said he wanted to do it. I supplied some tools, provided just a bit of guidance and my 8 year old took the screw driver to task. I guided him on disassembly and used a magnetic bowl to hold the screws so didn’t roll away.
When he started to put it together, he asked how to do it, to which I gave the proper fatherly advice, “just like taking it apart, but in reverse!” Surprisingly, that was enough. I just made sure that the Left and Right Bumpers PCBs was correctly placed. He knew what screws went where and placed everything just right.
I double checked the screws to ensure that they were all snugged up properly, popped in some batteries and we were off to the races. There is only just a bit of confusion now as the blue controller now goes to the green dongle.
In another proud moment, my boy turned to a SNES emulator and played Super Mario All-Stars. Those old games are still fun to play today, even for the youth, which is a testament to the fun-gineering of yeaster-year
Technology is certainly a fun thing to play with but it is so much more fun to pass on the joy of owning your technology to your kids. The amount of confidence my boy has earned through this exercise is worth far more than the cost of both of the controllers. I am hoping this sparks a flame for a passion for technology, not just in using but in creating and imagining new ways to use technology. I am quite sure that his abilities that will far surpass my own.
There are many flavors of Linux, we call them distributions but in a way, I think “flavor” is a good word for it as some some are a sweet and delightful experience while with others a lingering, foul taste remains. Manjaro has not left a foul taste in any way. In full disclosure, I am not a fan of Arch based Linux distributions. I appreciate the idea of this one-step-removed Gentoo and for those that really like to get into the nitty-gritty bits Arch is good for that. My problem with Arch is the lack of quality assurance. The official repository on Arch Wiki describes the process of how core packages need to be signed off by developers before they are allowed to move from staging into the official repositories. With the rate at which packages come in, it is almost an impossibility that through manual testing software will continue to work well with other software as some dependencies may change. Admittedly, I don’t use it daily, outside of VMs for testing nor do I have a lot of software installed so this is not going to be a problem I am likely to experience.
Manjaro, from my less than professional opinion, is a slightly slower rolling Arch that seems to do more testing and the process, from what I understand, is similar. Developers have to approve the packages before they are moved into the official repositories. I also understand that there isn’t any automated QA to perform any testing so this is all reliant on user or community testing, which, seemingly, Manjaro is doing a good job of it.
This is my review of Manjaro with the Plasma Desktop. Bottom Line Up Front, this is quite possibly the safest and most stable route if you like the Arch model. In the time I ran it, I didn’t have any issues with it. The default Plasma Desktop is quite nice, and the default themes are also top notch. The graphical package manager works fantastically well and you do have Snap support right out of the gate. It’s truly a great experience. Was it good enough to push me from my precious openSUSE? No, but it has made for a contender and something about which to think.
The installation process was as smooth as room temperature butter and felt incredibly refined. The installation media greets with a very nicely themed boot loader to which the default option is to boot Manjaro. Very quickly you are brought into a live session where you can begin to do some exploration.
Since I was doing this in a VM, I did have some VM-isms, that made this look less than stellar, initially. Since I wanted to get to installation, straight away, I went right for that icon on the desktop. Nice to see that the icon was on the desktop, not hidden away giving you a scavenger hunt as your first objective for the installation. This is using the Calamares installer so it is incredibly straight forward and new-user approachable. You are initially asked for your language preference, then to set your location.
Your next objective in this installation is to select your keyboard layout. Then to set your partitions. My preference, for this installation was to Erase the disk and I didn’t add any Swap. Although, I recently learned that doing so is not the best idea for system stability.
You next step in this journey is to tell Majaro, who you are in the Users step. Here you will enter your name, your username, the name of your computer, set your user password and administrator password. Here you can set the system to log in automatically and to use the same password for the administrator account. The next step is a somewhat new entry into this process, as I’m told, but you can now select your Office Suite. The three options are: No Office Suite, LibreOffice, and FreeOffice.
I selected FreeOffice for two reasons, one, there was quite the hullabaloo about Manjaro offering it. I am personally quite happy with LibreOffice and I like my options there so this was the perfect opportunity to get some impressions of it.
Finally, you are presented the Installation Summary with a final Sanity Check before proceeding. I always appreciate the sanity check
Then the installation will commence, you can sit back or leave, whatever you want to do at this point. Alternatively, you can read the Manjaro propaganda and become acquainted with the world into which you are stepping.
Here is where I put the image that tells you to reboot… but… I didn’t take that snapshot.
First run and Impressions
Just like the live media version, the installed version of Plasma looks fantastic. Although, to be fair, it is a chore to make Plasma not look fantastic.
This time, however, I wanted to do some exploration of the Welcome and also leave it set to launch at start so that I can return to it on my next boot. My first stop was at the center column, bottom row, Applications.
This curious application, called Manjaro Application Maintenance was highly structured and very easy to get around and understand what is going on. For those that like the “minimal” installation. They can very easily go here and remove all the bits they don’t want.
Next on my agenda was to perform updates. In this case, they have a graphical tool so the graphical tool, I decided to use. Warnings are never a point of concern, really, as they are just that, warnings, a spot to slow down and read the situation.
Here there were some warnings about packages being installed before the dependency. It’s odd that the package manager wouldn’t just fix that and reorder how the packages are installed but perhaps it is some sort of circular dependency and this is the warning of that. The updates proceeded but with one slight hitch.
I was not able to do as instructed on here as when I did go to the virtual terminal, I was greeted with nothing, no prompt or anything of that nature. Not a big deal, I just waited until there was no activity from the virtual machine and I sent the power off signal to safely power the thing down.
Upon rebooting the VM with Manjaro, I was once again greeted with the splendidly polished Display Manger and a login prompt. I logged in and everything was as I expected it. I do want to say that having Yakuake installed by default is a fine addition to Plasma. A quick F12 presents a terminal drop down that just screams all kinds of nerdy wonderfulness.
I then wanted to see how the process of installing applications would go with Manjaro. Since I didn’t want to install anything that would pull down a lot of packages, I went for something small that I didn’t really need, KPatience, a Soliaire card game. After all, Windows 3.11 had something similar installed by default.
When you select to install an application you are prompted for you password. This is not the administrator password but the user password. Whether or not that is more or less secure than the root password, I don’t know, but I thought that was worth noting. I also appreciate the “Transaction Summary” given. How that is different than an Installation Summary, I am not sure. Maybe this is a better word for it as you can install and remove applications and those actions combined are “transactions.” Something to think about.
I did have to change the Application Launcher to the Application Menu because… I just happen to find the Menu more appealing.
That is very easily done, as in any Plasma desktop, by right-clicking on the menu icon and selecting, Show Alternatives.
Another noteworthy feature of Manjaro is the Kernel Notifications. I don’t completely know what all this means, what is an “unsupported kernel” and to only notify if running an unsupported kernel but I do understand notifying of a new LTS Kernel. If I were going to take my flag in this distribution, I would recommend becoming well acquainted with this too. I imagine this could very much be the difference between a reboot and run and a reboot and flop.
I also want to congratulate the Manjaro team on a job well done with the Dark Breath theme. Although, when I say it, I feel like I’m saying “Breeze” with a lisp, the Dark Breath theme is so nicely done that I could reach out and give an e-high-five on how it looks. Different then the Breeze but equally as nice.
The desktop and Manjaro specific tools all feel well orchestrated. Aside from my upgrade hiccup, which I want to stress is a hiccup, I was able to keep flying along. I do want to note that the only other time I have seen that screen was when updating a system with proprietary Nvidia drivers on a previous main driver. It was almost a welcome back to see that little notice.
Since I had to try FreeOffice out… though, without any office tasks to perform, I wanted to see how it looked and felt. Just on the surface because this is not a review of FreeOffice, just an impression. I was immediately impressed by the ease of picking your theme. Not only did you have the choice in dark or light themes, you also had a choice in the annoying ribbon layout or traditional and much more useful classic menus and toolbars.
The first application to click-around in this office suite was the word-processor called TextMaker. I really liked the presentation of it as it immediately gave me happy feelings. The ribbon layout was what you would expect but the part I didn’t care for was the additional menu bar of new, open, save, undo, redo, etc. I prefer the LibreOffice execution of that as it moves that inline with the File, Home, Insert, Layout etc… tabs. Not a big deal. I didn’t dig into it but I am sure that it is customizable to some degree.
The next application in this sweet suite of office tools is the spreadsheet application called PlanMaker. It has a similar feel as TextMaker and had the basic functions for which I would be using. I did find the ribbon a bit excessive on the screen real-estate but again, this is just an impression. I could very easily go back to the more efficient layout.
The last application in this suite is called simply Presentations and it also is about what I would expect. I didn’t create any presentations with it but the impressions by clicking about did give me the impression that I would be able to bore anybody with an unnecessary slide show.
The only thing I hadn’t checked yet was the file dialog. I must say, I did not like this. It was the only thing I didn’t like about FreeOffice on my tour of impressions. It was very 2002 in appearance and although I’m sure it is quite functional, it is not what I would consider modern. Although, the GTK dialog isn’t any better, so if we are comparing it to that I guess it’s fine. I would have preferred some sort of Plasma integration here so that it used the Plasma File Dialog.
Really, all applications and desktop environments should really use the Plasma file dialog, anything but that is a sore disappointment in user interface.
Overall, FreeOffice is nice, certainly very usable and has a nice polish to it. I don’t think I would replace LibreOffice with it as I do use the Draw and Math functions of that and I haven’t run into a compatibility issue in a long time. I am glad that Manjaro gave me the opportunity to kick the tires on it.
What I Like
I like the fact that Manjaro give the option, right out of the gate, to pick your office suite. I would haven’t ever tried anything other than LibreOffice had I not had the option. Although I have decided to continue to use LibreOffice, I appreciate being presented an alternative.
Pamac-CLI is a kind of shim to make Pacman not ridiculous. It converts all the nonsense commands of pacman into something that is human readable and intuitive. For example, to install a software package:
Breath Dark theme is well done. It give Manjaro Plasma edition a unique feel but just every so subtly. Also, green is a great color to go with if you are going to set a highlight color.
Default software selection is very satisfactory, so much so that I had to find some oddball thing to install just to go through the process. I still prefer to have VLC over other media players and Firefox over other web browsers. I like that they chose to include Konversation for IRC and Steam for games.
A nice surprise was to see that SUSE Imagewriter was included on the Manjaro installation for writing images to Removable media. Interestingly, not even openSUSE includes that by default.
What I Don’t Like
It fundamentally still uses Arch as the base and although pamac-cli is a nice shim to offset the nonsense that is pacman. I do prefer having sensible and intuitive terminal commands. There are too many to remember, I don’t have the patience to faff with the game of scrabble in command options.
The Plasma screen locker crash did bother me a bit as and I’m not sure where the blame is to be had for that. I don’t have an nvidia driver so maybe the issue was with the package resolver (ahem, Pacman) that didn’t order things properly. I don’t know.
Manjaro used Ext4 for the file system. That means, I don’t know how I would roll back a bad update. I think running a rolling distribution without that safeguard is asking for trouble. For this alone, I am much relieved that I have BTRFS on my root file system for snapshots. Should anything go wrong, rolling back is trivial.
Manjaro is a fine distribution but it has the one glaring shortcoming that is, it is Arch based. Since I have had such a bad taste in my mouth for Arch, I just wouldn’t consider using this. Perhaps, if my first experience with Arch was Manjaro, things would be different. Had I not ever messed with Pacman maybe I wouldn’t be so obstinate about it. Although, fundamentally, I am not real confident in the QA process of Manjaro or any Arch based distribution. I would be more inclined to trust it if it was built on something like the Open Build Service with openQA automating the testing process to knock out most of the rough edges along with user testing.
For me, I will stick with my openSUSE Tumbleweed with my snapshot rollback system, should the automated and human testing allow something to slip through that takes my system down or I muck about, I can always undo it and keep sailing.
Just because I am over biased about Arch, doesn’t mean you shouldn’t give Manjaro a try. It is certainly well done and the developers have a fantastic passion for the project. That passion alone is almost enough to nullify all my reservations about the project.
My 6th noodling might be my longest noodling yet. It started out a bit light but then after reading I just got a bit too excited. If you want to skip to the end where I do a little self-deprecation and ignore the meat of it, that is very understandable.
I took my kids to the symphony this past Sunday. It was hugely beneficial to have the kids experience a symphonic performance. It made for a pretty decent lesson about the benefits of working together. When the orchestral members were warming up before they begin the performance there is a cacophony of sounds and although individually, the instruments sound nice, together it sounds like a mess. When the performance started and the conductor did his conducting, keeping everyone on pace and on the “same sheet of music” as it were, you could listen and imagine the story of events in the mind’s eye. Everything from serious and intense melodies to whimsical light hearted tones. Although my kids could only manage to sit through an hour of the performance, there were lots of lessons to be extracted about the benefits of working together.
How this can be applied to the Linux community is as such. When we work together, in harmony with one another, we can make for some amazing results. Whether it is the latest Ubuntu MATE, the newest release of Plasma or helping someone through a tech question, by working together in a kind and respectful tone we can achieve great things. I am of the belief that all Linux is good Linux and by making any one aspect better, we make it all better, regardless of the flavor of Linux or desktop you choose.
Let’s make some beautiful music
Dell Latitude E6440 Caddy Drive Bay
My primary machine that I am using I didn’t choose lightly, I wanted a lot of flexibility in a fairly small package. Since I like to test things in VM, I wanted to have the option of a third hard drive. What I discovered is that it doesn’t seem to matter how much storage I have available, I seem to fill it up. I am starting to think that maybe I have a problem.
I do clean out my drives from time to time but I find that the more space I have, the sloppier I am about cleaning up the cruft. I am preparing to build a system with a heck of a lot more storage and after making my hard drive purchases, I realized, I may have purchased too small of drives. If this is the case, I think I have a strategy to compensate for this.
I did create a YouTube video of the ease of using the drive bay for additional storage as I knew it would be a short thing and provide me an opportunity to edit something together. A consequence of the additional drive has resulted in me rarely poping in the optical drive. Perhaps my needs for optical media is fading?
I recently change over all my cordless power tools to the DeWalt 20V max line. I do spend a lot of time outside of the cubicle doing non-cubicle activities and I have recorded much of it and scripted some things out to share my findings and reasoning from the perspective of a Linux Geek. Although power tools are not strictly a nerdy activity, there is a lot of nerdiness to be had. My specific high points of what I find is that the price per tool combined with the watt-hour of use per charge and number of charges per battery made it the best bang for your buck. The other main factor is the variety of tools I have available to me with this one battery platform. In an effort to simplify my life, this is what I have chosen and so far, it has exceeded my expectations.
BDLL Follow up
One of the things I like about BigDaddyLinux Live is the discussion we have on there. Some of it, I don’t have much to contribute as it is either outside my area of expertise or maybe I am still forming my opinions. There were two topics that really engaged me last Saturday. The first being developing on Linux and the second on virtual memory or in Linux called Swap.
On development, there is a lot of negativity towards Electron applications from some in the Linux community. In short, an Electron application is a cross platform thing that allows a developer to make an application for Linux, MacOS and Windows. One of those things is really cool and the other two, not as much. The benefit is, it is an easy way to maintain a single codebase and maximize the number of platforms that can reached.
The draw backs are that Electron is quite inefficient. The storage space it takes up is fairly extensive and the RAM usage is also weighty. With newer computers, this is not an issue. If you have 16 or 32 GiB of RAM this isn’t an issue, if you have 2 or 4 GiB of RAM this can be an issue.
A discussion that start on the Discourse and made its way into the show was about using Swap in Linux when there is so much RAM available in modern systems. The question is to Swap or not to Swap and how much Swap and what kind of Swap. I recommend watching BDLL from 05 October 2019 for the extended discussion or going to the BDLL Discourse for opinions outside of mine.
Swap reminds me a lot of the bank switching that was common on 8-bit computers of old except instead of keeping the data in a switchable bank, this is putting it on a hard drive or SSD. The issue I find with Swap is if you are really taxing your system, you can end up with having a lot of disk thrashing that can really bring your system down to a crawl.
For my primary machine, I have set aside 17 GiB of Swap space, just in case. I have used it on more than one occasion… maybe due to Electron apps and it has come in handy when I haven’t paid attention to memory usage when using Google Chrome. Swap space on the two Acer AspireOne netbooks I set up for my kids gets used pretty regularly. Whenever using the a web browser they do dip into the swap space often.
Since I’ve been using Linux now for quite some time, I have the space to spare and I do take advantage of the hibernate to disk (or SSD) function from time to time, I set my system up with a Swap partition. It is an old fashion and inflexible approach and I am okay with that. The benefits of a swap file are probably greater but since openSUSE makes it very easy set up a Swap partition and I know what I am getting with it. That is what I will stick with, for now.
openSUSE Leap to SLE
An often forgotten bit of openSUSE that makes is rather remarkable is how closely the Leap project is with the SLE project. One of my good E-friends, Mauro, who does the Linux thing as a profession, not a hobby and home-gamer like me was telling me how easy it is to move a client from an unsupported openSUSE Leap system to a SUSE Linux Enterprise support contract without disruption.
I know that this is not possible with CentOS and Red Hat but with Canonical’s Ubuntu it is essentially the same distribution. What I find interesting is the different executions of each of the distributions of integrating community based projects with commercial offerings. My preference here is the [open]SUSE model as it seems like a cleaner approach, though I see the benefits of the Canonical method too.
Many updates included gcc9 version 9.2.1, gcc8 version 8.3.1, gcc7 version 7.4.1, Plasma Framework 5.62.0, Plasma Workspace 5.16.5, Xorg-X11-server 1.20.5, Kernel 5.3.1 and several bug fixes around YaST and PulseAudio and a bug around not being able to duplex print with Okular.
The Tumbleweed Snapshot reviewer gives 20190923 a stable score of a 97; 20190925 a stable score of 98; 20190926 a stable score of 98; and 20190927 a moderate score of 83.
If you want to lock yourself on the latest Stable snapshot from the 26th of September:
tumbleweed switch --install 20190926
Project Name Change Vote
As of today, the polls are open for a name change on the project. I did cast my vote and after reading through the mailing list, there is a little bit if heat concerning the issue. Ultimately, the hope is that it is a clear in favor or not in favor of the name change. If it is closer to a 50-50 split, that can potentially be more problematic. I personally am hoping that we just keep the status quo. Although I do agree that some of the legal constraints with the relationship to SUSE can be problematic for end-user experience, things like codec installation and such. There are some benefits with the brand association, especially in respect to the SLE to Leap for those that are in the space of selling solutions.
The sixth openSUSE Asia Summit just concluded this past weekend. It took place at the Fakultas Teknik of the Universitas Udayana in Bali, Indonesia. There were a number of participants that traveled from 20 different nations around the world to join the students at the university. Students not only made their first contributions to open source technology but also volunteered with running the summit.
The Beta version of Plasma 5.17 was released with new features and improvements such as per-screen fractional scaling on Wayland and a new User Interface for configuring permissions of Thunderbolt devices and network statistics in KSysGuard. Due to increase in user privileges with this feature is being examined by the SUSE security team.
openQA found a few bugs with GIMP, some applications were mixing Kirigami and Qt Widgets that were breaking some keyboard shortcuts that were addressed and will be fixed in the final release of Plasma 5.17.
Leap 15.2 will see some major version upgrades of many components such as a new version of the Linux Kernel, Qt 5.12 LTS, Plasma 5.18 LTS and the latest KDE Frameworks and Applications. A full Wayland session that arrived in Tumbleweed a few weeks ago will be available in Leap 15.2. Testers are welcome to ensure the best user experience possible.
Qt 5.14 branch is still in early stages but the development teams have been busy integrating it into openSUSE builds. Bugs have been identified and most of them fixed so it is possible to build projects against Qt 5.14. One of the most user visible features is the implementation for scaling for HiDPI displays that was mostly rewritten and hardware acceleration for Qt Quick using a new abstraction layer. It can also take advantage of the Vulcan API.
This laptop of mine that I purchased just over two years ago has the ability to have 3 storage devices. I have previously described what I’ve done in it with an mSATA and the 2.5″ SSD. Between the two, I have 995 GiB of storage, 101 GiB for root using the mSATA and 894 GiB on the 2.5″ drive. That was fine and all for normal things, but VMs do require a lot of space and so a lot of space I needed. Although I do often use my optical drive, it’s not as often as I use VMs so I decided to get a caddy and install a third drive in this 14″ chassis laptop.
Here is a short video on how simple the process is… and another reason to play around with Kdenlive. In short, adding a hard drive is as simple as:
Insert the drive into the caddy
Secure the drive using the set-screws but be careful to not over tighten
remove optical drive from the computer and insert hard drive (SSD) caddy into bay
Bob’s your uncle
The main reason is, I need more space for virtual machines. I’m sure for normal people the two drives is more than adequate but I have to play. Most people would probably just clear out the old virtual machines after they were done but I am guilty of data hording and probably need to get that under control. I also don’t have much interest in wiping or possibly interfering with how my laptop is running as openSUSE Tumbleweed works so fantastically well on it.
My process is, I try out the Linux distribution virtually to obtain some general impressions, test out a few things, check the memory usage and so forth. If I find it exceptionally interesting or want to test a use case, I take it to the next level and put it on some hardware. I find it a more efficient use of my time to do my first round of testing virtually before I meddle with the metal.
It also doesn’t help that I am more likely to use Virt Manager with Qemu which uses Qcow2 drive images and they take up more space than VDI images from VirtualBox. Since I tend to get a better feel for the distribution using Virt Manager, especially with Gnome based desktops, I am more likely able to give them a fair shake. Consequently, I need more storage space.
Despite the fact this laptop is older, I can’t seem to find another comparable 14″ machine that has the drive flexibility that the Dell Latitude E6440 has. I do wish it had some kind of refresh to allow for a faster CPU with lower power utilization but that is just not the demands of typical users these days. For now, I will continue to use this laptop as I have intended. If I do another modification to this system, it will likely be to upgrade the CPU to the highest performing 35W TDP processor that is available.
I was able to get my Commodore 64 under its own power to access the IRC chat rooms, specifically the BigDaddyLinuxLive room where I was able to chat with such folks as Bill, Popey, Chris and another Allen. It is very satisfying experience. More on that here:
I recently had jury duty and the courthouse in my small-ish community, Windows 7 which is near end of life. For each bit of evidence, they used CDs and DVDs to store each individual item as evidence.
Building a Computer
I am building a computer for the first time in a very long time. I want to do it on a budget. I received some components at no cost to me, the case and motherboard so that drove the purchasing of the rest of the products.
Motherboard MSI 970A-G43
AMD FX-9590 CPU
Memory, 32 GiB DDR3 1866MHz
Video Card RX570
Storage 6x 2-TiB drives
1000 Watt Power Supply
Rather large case
All for about $350.00
More on this in the future.
Acer AspireOne Netbooks
Recently Set up two AspireOne Notebooks with openSUSE Tumbleweed using the Xfce environment. Initially one had had 1 GiB of RAM but an SSD, the other with 2 GiB of RAM and a slightly faster CPU but with a traditional hard drive.
Told after the fact two points of advice, whip the egg whites before you add the sugar, contrary to the directions and questioning whether or not there was any amount of egg yolk.
BDLL Follow Up
Manjaro is the current Distro Challenge… It’s Arch based so…
Eric Adams talked about how people can get “bug apathy” when they experience a problem on Linux or other open source software. know that I am guilty of that.
Bug reporting is something we Linux or free and open source software users should do. The vast majority of the software I don’t pay for, it’s open source and I believe that I have a social contract with these developers and maintainers to either help with the project or donate to it.
LibreOffice and openSUSE communities are having a joint conference next year in Nuremburg, German. For this special conference, they are having a logo competition. A logo is believed essential for the conference and they want to visualize both communities during this co-conference. LibreOffice will celebrate its 10-year anniversary and openSUSE will celebrate its 15-year anniversary during the conference.
There have been discussions about the “openSUSE Project logo & name change” that started in June 2019 on the openSUSE Project mailing list. The Election Committee received a request from the Board to conduct a vote whereby openSUSE members can indicate whether they are for or against the project name change.
The voting will start on Oct. 10 and end on Oct. 31, which will provide three weeks for members to vote. The result will be announced on Nov. 1.
The Commodore 64 was my first computer and as such, now holds a special place in my heart and probably forever more, or at least until I lose my mind completely. In all the years I had a C64, I never visited a BBS as I didn’t get that bit of tech until I got my Commodore Amiga 600. Due to the wonders of the Internet, and a global effort to keep these old machines relevant from guys like The 8-Bit Guy, Perifractic Retro Recipes, Retro Man Cave, Dan Wood, LGR and so many others, I was inspired to take the time to make my Commodore 64 more than just a stroll down vintage lane for me. I have seen others make use of it for writing and developing new games and such for it but how could I incorporate it into my life was the question. That answer, IRC, it must do IRC.
So, lets use the “scientific method” on this as I make my kids do it, so why not force myself to do the same.
Make use of my beloved Commodore 64, my first computer, in some practical way. I am going to use “practical” fast an loose for this. I have seen many examples of using the Commodore 64 in some sort of networked fashion but I wanted to see if I could have it serve a specific purpose. Chat on IRC, Connected through the Ethernet into my home network using it’s own power and capability.
I think I am able to get the Commodore 64 to access the IRC function on the Internet without having to telnet into another server as a bridge to make it happen. I also think this is going to be a bit of a headache and everything is going to fight me along the way.
Here is my list of “materials” in order to conduct this experiment.
This computer has a whopping 64K of memory to which, in it’s time was an extraordinary amount of memory, generally about 16 times that of its contemporaries at the time. If you know anything about the Commodore 64, nothing I am going to tell you here will be new. If you don’t know much about the commodore 64, this is a great video on YouTube with a great breakdown of the chip design.
Purchased from The Future Was 8-Bit, this is a fantastic device that came included with an 8 GiB SD Card filled with all kinds of goodness. It is a joy to use and makes for reliving the Commodore 64 history so much more enjoyable. Although, you don’t get to enjoy the warm purring the 1541 5¼” Floppy Drive, this is a more practical and sustainable solution. If you purchase newer software for the C64, they usually build it to be compatible with this device. It was a great deal and allowed me to be able to use the .d81 image Contiki OS image that will be described below.
This is a 10Mbit network card from icomp.de that comes form a rather long line of similarly designed devices. This is said to work with Contiki, Codenet and WarpCopy. The nice feature of this card is that it can be used as a stand alone or on a Carrier Card so that you can add this “feature” to another device like the MMC Replay or Chameleon. This will not work with a C128, SX-64 and very old C64 main boards. I don’t have a “very old” main board (just really old), so this works fine with my computer.
Wired Ethernet line
There really isn’t much to report here. I just made a cable and strung it from my router over to the Commodore 64. It is neat to see the flashing activity light when it’s running and doing it’s network activity.
Why a CRT? To be more genuine to the period in which it came from? No, it is because it is what I have and it should also be noted that this is an old SVGA, CAD monitor that I once used for such activities. Now it serves are more noble function as my “retro corner” display. I have a ViewSonic that converts the S-Video and Composite signals to SVGA.
Software package that is accessible from here on GitHub that comes in a few different builds. I used the .d81 image as that would eliminate the need to swap disks, or at least the risk of me screwing up the process of disk swapping should that become necessary.
Assemble the components, plug the computer into a working Ethernet line and attempt to get online to chat in an IRC room. The intent here is to use the Commodore 64 as the client, not to use any other machine as a spring board.
The results are mixed but I am going to break it down a bit so that you can replicate it and adjust the process to fit your situation.
Since I have the SD2IEC, I used the .d81 image and put it on the root directory of my SD Card that is in my SD2IEC. Why the root directory? Just to make it quicker to access it.
With the RR-Net MK3 installed in the cartridge port, the start screen is quite different, displaying information about the card. With the SD2IEC connected and the SD Card inserted, I loaded the drive management software which is a simple interface for navigating the contents of the drive. After all, it is 8 GiB of storage so the traditional methods are a bit cumbersome in this regard.
There are two applications that you have to run before you can begin doing the IRC you have to set up what is the “Ethernet device” and set the IP Addresses.
I am not sure if it is critical to do them in any particular order but I started with ETHCONFIG to set the Ethernet device.
Once it is set, all you can do is power cycle the machine to perform the next step. That means, enjoying the lackadaisical loading times of the Commodore 64. Even with an SD Card… not real fast.
Next was to run IPCONFIG to define the IP addresses of the Contiki OS. To navigate up and down in the fields, use the F5 and F7 keys. ENTER to select Save & Close
After this ready prompt, you will have to power cycle the machine once again to load the IRC application. The first run of this, I went for just IRC as opposed to IRC80 as that 80 means column and I like the C64 font.
When the application completes loading from the SD Card, you are the prompted for the IRC server and nickname. Using F5 and F7 to navigate up and down will take you to each of the fields and RETURN to Connect. I want to note here that you must write your IRC nickname in all lowercase and numbers. If you use any uppercase numbers, the IRC server will not be able to recognize the characters.
It will take just a bit but you will see the typical IRC “chatter” fly past on the screen.
Well… I wouldn’t say “fly past” for this. More like trot steadily through. To join a channel enter
/join #<room name here>
In my case, I decided to join the #bigdaddylinuxlive room because, why not? I know the people there, they are friendly and I knew that someone would get a kick out of it.
I made some observations that whatever you type into the prompt, whatever case it is, will be displayed as all uppercase.
I further compared it against what I see in comparison between the Qt based IRC application Konversation. How would it be displayed to “normal” or I guess, “modern” clients.
I was able to see that the Commodore 64 client could only send all lowercase characters, display it locally as Uppercase characters but be able to receive a mix of characters. I thought it all to be quite interesting.
I did test the 80 column mode of the IRC client. It did indeed work and was readable but but I have had it crash on me a few times. I can’t say as to why so I have decided to stick with the 40 column mode for now.
It should also be noted that the screen scrolling is quite a bit slower in this mode. Not terrible, just quite noticeable. The
The Commodore 64 is very much able to, under it’s own, power, unmodified with the additional components is able to access the Internet and perform communication in IRC chat rooms. It does work better in 40 column mode than it does 80 column but is very usable.
Getting online with the Commodore 64 to hang out in IRC chatrooms is really quite a satisfying experience. The fact that it is a computer from an age before the internet and when BBS systems were in their early stages, having the ability to plug an Ethernet line into it and with a little configuration was able to get onto the World Wide Web… of sorts, at least a part of it.
I am impressed that I am able to do this much with an unmodified Commodore 64. I am quite impressed that with 64 KiB of RAM, it is still a productive and usable tool. It is quite single purpose but absolutely useful.
I want to note that the web browser does work in this Contiki OS but not with HTTPS so that is out. It does make requests as you would expect and I think I just may revisit the rest of this on another blathering at some point in time.
Future plans, I really want to be able to telnet into a Linux machine with the Commodore 64, I have some other hardware and software I want to try out with this machine to see what other greatness can become of it.