When was the last time you paid close attention to warnings in a partition Management program? You don't remember? I'm going to tell you beautiful story. Jerry has his data on an SSD. Being the power user is Jerry totally disregarded the fact that he had to make a backup of his data. Jerry wanted to use a partition management program like the one I have included in the photograph I've just made.

He took a few precautions, made sure that he wasn't any browser, made sure that he wasn't on the internet, hell he even plugged out his internet router.

One thing Jerry did not anticipate was a catastrophic failure of a piece of critical hardware in his beautiful computer.
His gorgeous AMD processor had damage, heat damage

TSC = unstable
His GPU integrated in his CPU also had heat damage. When he makes certain simple moves, like moving a window, the GPU goes haywire, sends bad data to the CPU with the unstable TSC and everything cascades down, resulting in a beautiful green screen which Jerry had seen hundreds to thousands of times. These screens usually occurred only when Jerry had opened a browser. Jerry figured he was safe since he had not opened a browser since this session of the Operating System had started

**Wrong**

In the middle of operation that I have just described in the photograph in fact at the beginning within just the second minute of the operation that needs two to three hours, the machine did not crash to green screen, it terminated his Xsession effectively destroying his partition editor.

Jerry was flabbergasted something he had not anticipated

All his data was lost

Since he was not running ZFS, there was no way that he could restore or roll back a snapshot

^Z

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #gPartEd #xFace #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper #gufw

I've encountered an annoying problem

A critical shared Library that's used by FFMpeg and of course also used by MPlayer was not in the installation. It was an odd because even a remove reinstall of FFMpeg didn't fix the problem.

Since I'm in no mood to install a development environment from the command line to compile FFMpeg from scratch I just wiped the KDE distro and started all over.

While I was busy with the new installation so I was on the live ISO FFMPEG worked just fine and the library was there working perfectly.

You can already guess what happened when I booted into the new installation.

FFMPEG was installed by default by the distribution, since VLC is installed by default, but the shared library was missing!

¡WTF!

Then I encountered even more bugs, privilege escalation errors!

These bugs and errors have nothing to do with KDE!

They have to do with problems with the distribution from the perspective of my maintainer. It is my task to see if I can reproduce the problems after I fix them by hand if that does not take too much time and effort.

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper #gufw

I also encountered another problem; I can immediately tell you that it's not a KDE specific problem but it popped up in konsole.

The subject is fonts and the section is point size. The monitors I use are not of a small resolution. In fact an ideal IPS LED panel layout for me would be an 8K panel two 4K panels flanking it and two 1080p ultra ultra wide panels at a left and right of those.

With such a setup I can monitor different machines at the glance and control them with ease.

Even on my 1080p Ultra Ultra wide panel the default Point sizes for fonts are too small. On a scratch KDE based MX Linux installation, the following problem was repeated twice in Konsole.

The first time I changed font point sizes, closed konsole. When I reopened konsole the fixed with font, was replaced with one that appended spaces behind every couple of letters.

This rendered konsole unusable for work.

Changing the fonts Point sizes to the defaults again did not fix the problem.
Sinds that installation was Vanilla and didn't have enough space for home and root on one partition to actually Play with KDE, I wiped it and started again.

This time I deliberately did not change the point sizes even though it was hard to read. I then copied over some configuration directories from my other installation to this One, none of them related to anything KDE wise or any fonts directory. When I rebooted that installation The problem occurred for the second Time.

As with the wallpaper issue, I immediately converted that energy of irritation to something positive. I troubleshooted the font problem for a short while and when I couldn't isolate it I did a simple thing. I created a couple of other accounts on the same KDE installation to see if I could repeat the error.

That reproduction step is vital before a bug report is created. The other accounts were also residing on my other xFace MX Linux installations, which means I could simply copy them over to the other home partition where KDE was looking at.

In the other accounts I could not repeat the error.

That means a bug report is worthless because repeatability is crucial. Since the usage of a terminal in the K Desktop Environment is important, I changed my strategy and simply installed the xFace Four terminal in KDE. In the end that was a nice move since I know all the keyboard shortcuts of the terminal by hand they are in muscle memory and they have been there for years.

As a bonus I also installed other good shells in MX KDE the hashtags tell you which.

Right now I have a KDE installation in which I can actually work based upon the MX Linux KDE variant

I shall link a couple of photographs in a few minutes

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper

There's one thing I had not done in a long time which is install a distribution of my choice with a full KDE desktop manager. I haven't done that in more than 2 decades. KDE has been wonderful at it's infancy and KDE is still wonderful now.

Since MX Linux is my distribution of choice, it's logical that I installed the KDE version of that distribution even if it's just for a test drive.

I've allocated just 20 gigs for KDE which means it's tight with space but it's still usable for a test run.

One tool I immediately missed was gparted the powerful gnome UI, which puts the precision of partition manipulation at your fingertips, without the chances of making costly mistakes if you don't pay enough attention or are not affluent enough with the commands in your favorite shell.

I missed that tool during the installation of mxKDE because I needed to add partitiond before the installation could proceed I just left Blank Space on an SSD.

Apart from that I can tell you from the initial view that KDE has not just matured, advanced and elevated itself. KDE has become so lightweight in resource usage that it can complete with very Light Desktop managers.

You can still edit your widgets up to & icons almost the pixel. The things that I love about KDE from decades ago are still there and are even more powerful.

Since I started to use KDE when GPU usage on the desktop was not even a thing, you can imagine how fast the DE is now and a period where GPU usage is normal for everything.

Out of the box KDE is already fantastic. Go and see what KDE can be for you, by installing it yourself

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming

To make sure that everything starts up normally even when regular things are done, which should not influence the procedure, I left my ghostBSD installation alone for about a day

I inserted the external HDD in the tray, at the exact location where I had installed the Operating System, rebooted that MiniPC and fired up ghostBSD. A couple of nice things occur when you install ghostBSD instead of going flat with just freeBSD.

Configuration parameters for my HDMI IPS LED panel Zero was always added flawlessly since that is the display which I look at at boot

My secondary display which is connected to a mini DisplayPort (Zero) and then goes from mini DisplayPort to HDMI with an Active cable with circuitry in it, at the HDMI end, is automatically detected in the freeBSD configuration provided by the ghostBSD team.

That is a tremendously good feature which pleasantly surprised me.

Another BSD user told me here, that in the regular freeBSD installation you have to go and figure that out yourself, which is fine but not something I intended to do at this point.

Here are some images I just shot of the login screens with both IPS LED panels enabled

.🖋️ #bash #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #AskFediverse #WTF

@izder456

I am an individual who often does things in many fields, especially computing, in a weird and unexpected way. That's why I'm one of the efficient bèta testers for many different software programs which started in the days of the Waffle BBS's somewhere in the 90s of the last Century and still goes on to these days.
Going to the absolute beginning I even started to bèta test software on the Casio FX-700p; then I moved to the Commodore C64, the C128 where I debugged CPM software, then I moved on to the 286 PS2, the machine was loaded with the 287 Mathematics Co-processor, essential for running CAD software.

The reason for my specific booting of the SSD, the starter SSD, on the USB tray, a dual slot device, is because I currently have not made any specific space free for the operating system.

I miss going to my beautiful boxyBSD system which resides on the boxyBSD Network.

The reasons for that are somewhere in another thread, but it comes down to the fact that my brain dead ISP doesn't give us any IPv6 addresses from the get-go, while we pay them through the Nose for a puny 10MBit Connection on a obsolete xDSL router.

So I just went to one of my machines, a AMD MíniPC with 32GB RAM, didn't find any space where the operating system wanted to install on my resident m.2 SSD (no space due to Sound Engineering Audio projects) and my resident SATA SSD, for identical reasons.

In the end space was made on a SATA SSD which floats on my different SATA trays which are dual port.

I shrunk a partition and made 8GB free, which the installer divided in 7.1GB and 407+MB for Swap.

I immediately have to say that the installer teaches you what doesn't work and give you hints on where you can go and look for the reasons why.

I have an MBR SATA HDD, where I wanted to install the operating system.
The installer immediately warned me that I would get a non-bootable situation and it was right it didn't tell why but that's not important.

The SATA SSD was already converted from MBR to GPT, where of course it lost all data but that was unimportant, since it was scratch data. gPartEd warned me about the data loss

The semi-automatic installation liked the fact that the SSD was GPT, partitioned and happily did it's magic creating the file systems.

When after the installation, I powered down the tray and inserted a HDD in the open slot, not moving the SATA SSD, the FreeBSD boot environment told me that it could not find the boot partition.

For me that was a WTF moment since the SSD wasn't moved.

🖋️ #bash #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #AskFediverse