Ooops

You just type ZZ… then the program assumes you fell asleep trying to exit and stops.

I’m still waiting for more distributions to include it to replace my old 3A+ home server.

Yes, you can. But the usual setup is to have a file system root that is nothing but subvolumes, which you can then use and mount basically as if they were independent partitions. But when you don’t create a root subvolume for your system root first, you install the system directly on the file system root alongside created subvolumes. This tends to get messy as strictly speaking the file system root is a subvolume, too. So now you have that with your system installed and all other subvolumes nested inside it.

That’s not a cat but quite obviously a rabbit.

No, that buried deep in the box with suppressed memories. So thank you for reminding me.

That’s probably the ugly method but as it’s my personal device I didn’t see a problem adding such things to /etc/environment

PS: You should be able to also set this when starting i3 with “QT_QPA_PLATFORMTHEME=qt5ct i3”…

That’s defintiely the wrong title.

No, it’s not the user catching Linux in trying to pretend user friendliness witht the terminal.

It’s Linux catching the user in still hating it when he gets the wanted user friendliness, for the sole reason of being conditioned to hate the terminal.

Of course not. There is a market for investing very little for some cheap malware and then putting it out there, waiting for the small amount of people (out of a billion of desptop users) falling for it. Also you go for the weakest link in defense, so scamming random desktop users is rarely a technical feat. It usually exploits the human, not the system.

But we also all know how money is actually distributed. So millions of random users being scammed for some money is still not the high reward scenario a server is. Much more work is invested there because the rewards are so much higher. And yet even then you often target people as the weak link. System security for a company is mainly user security. Teaching them to not fall for for scams as an entry way to the system. And there are a lot of professionals that basically made this their own social science of how I convey those things the best, how I enforce and regularly refresh those lessons, how to make people stick to best practices.

Are you trying to tell me this all happens in parallel to a technical server structure that actually isn’t that safe but rarely exploited because nobody could be bothered to check for vulnerabilities as it’s just Linux and the adoption rate is low?

The cruder the malware, the better your chances of running successfully in Wine.

Because throwing together some simple executable using inbuild windows functions is much easier than programming something well-build and hidden based on deeper system layers. So your random “I just encrypted all your files because you clicked this .exe, now send me bitcoin to get it back”-bullshit might work well on wine (which is why wine should be run as it’s own user with no priviledges to access anything but your Windows programs).

Also there is no incentive for companies to fix an exploit quickly. They will only release the fix with some scheduled update anyway or else people might notice that there was something worth fixing and that’s bad for your stock price.

Malware for desktop users is the low hanging fruit with little rewards. You just hear about it because it’s so rediculous easy.

The real money is on servers, so that’s were real money/work is invested to develop malware for much higher gains. How successful are they again?

Distrowatch’s source for popularity is how often the different distros are clicked on on their own homepage… which has the toplist featured prominantly on the start page.

So their ranking completely and utterly worthless, as it’s prone to manipulation and once you basically pushed your distro to the high spots it’s guaranteed to stay there as a rarely used but highly rated distro is of course attracting more clicks from people wanting to know what it’s actually about… see: MX Linux being on their #1 spot forever.

I could never get myself to using a track ball. An ergonomic mouse on the other hand…

I know they officially don’t. And I didn’t try to say that Sway was bad in any way or that it is their fault. I was just stating facts about state of it with NVIDIA graphics (that kept me -as a long-term i3 user- from switching to Wayland).

The Sway implementation (not Wayland as some DEs seem to run really smoothly) sadly is still completely hit or miss depending on your exact hardware setup. I have two device (both even with nvidia grphics *sigh*) and one of them is just a buggy and flickering mess.

Proper malware often still doesn’t run. Cheap executables to encrypt your stuff and so on the other hand work well.

Which is why wine should be run as its own unpriviledged user…

It builds the kernel module for your specific kernel. It’s not different from the nvidia package, that’s just the same thing pre-build for the default kernel (in fact if you install both nvidia-dkms will build the module locally, then realize the exact same thing it just build is already there and move on…).

You didn’t upgrade before installing. -y updates the package list to match the mirror, -u updates your system (and you should not use them separately, so if in doubt always use -yu).

So when you try to install (without synchronising the package list first) your system looks at it’s outdated package list, then requests files that are no longer on the mirror as they are already on a higher version.

There’s one caveat here: The UEFI specification doesn’t strictly require the ability to handle more than one EFI System Partition on a drive, so some simply don’t. So this “use a separate boot partition”-method might fail on some computers that just don’t recognize a second ESP on the same drive and only surely works with a whole separate drive for Linux.

Simplified version: SSDs or more precisely NAND flash memory has some technical quirks. You can’t just overwrite stuff like you do with magnetic hard drives. You have to actually delete things. Also you can usually only delete full physical blocks.

But data rarely fits neatly into physical blocks, so instantly deleting data would mean every time you delete something that partly resides in one block, you would need to save the data in that block you want to keep, wipe the whole thing then rewrite parts of it. That’s a lot of unnecessary stress on the hardware and also more work in teh writing and rewriting process.

So SSDs use a similiar approach as old magnetic hard drives. Blocks aren’t physical deleted but marked as no longer used. Which works well for hard drives where you can just overwrite data, but for SSDs this is also far from optimal as with every new write you want to commit you have to pre-check if this unused part of a block is already deleted and usuable or not? In the latter case you either need to do the “save some of it, wipe the block, rewrite” oparation you tried to avoid before or simply go on and try to find another actual free block to use. Which decreases performance obviously. And at some time you would have a lot of wasted half-full blocks and would need to organize your data to reclaim these

Enter TRIM… where periodically (usually when the system is idle anyway) the blocks that are marked as deleted are checked if there’s still used data in it (those are then copied to a completely free block and the whole block is wiped to free it up for the next write.

In layman’s terms it’s basically anolog to defragmenting a hard drive in the brackground. When the drive isn’t doing anything important it spends time rearranging data only partly using a physical block to wipe the whole thing and also to wipe blocks that are completely marked as deleted to keep everything neat and organized with fully used blocks and wiped blocks available for re-use.

PS: so-called continues TRIM is available also. That will basically do the whole “everytime a part in a block is marked as deleted write the other data to a new block an wipe the whole block”-routine in real-time… but after the regular writes are done to not clog up the system. But periodic TRIM is easier on the drive and usually sufficient.

PPS: TRIM is part of the drive’s set of commands. So all the data handling involved doesn’t need to be handled by the file system. You just issue the TRIM command to the drive and it handles everything internally.