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.
Tumbleweed Snapshots 20190923 20190925 20190926 20190927
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.