The Linux Thread - The Autist's OS of Choice

[Frederica Bernkastel]

Part of me still feels the urge to distro hop over to a RHEL clone like Rocky Linux, but on the flip side

In some ways, hopping a lot can introduce you to new software you'll love if you're new to Linux, I don't think would love the terminal, or vim keybinds, as much as I do now if I didn't fiddle around a bit when I was new to Linux. If you can, you could also get a cheap thinkpad to test stuff on, and use ventoy for booting into multiple Linux ISOs.

 

[GNU Abyss]

Part of me still feels the urge to distro hop over to a RHEL clone like Rocky Linux, but on the flip side, I'm a bit too comfortable on Mint MATE to go through the headache of switching. I've already got an assload of stuff set up just the way I like it on this Mint install. Maybe I'll fiddle with an external hard drive again, but honestly... I'd rather save that for when I have a proper second machine to test things on. For now, enjoy this Neofetch screenshot.

If you want to simply test out a distro, all you need is a virtual machine. Figure out how QEMU and it's libvirt based UI interfaces work. I've done VM work on a shitty laptop with <8 GB of RAM, they're very convenient.

 

[analrapist]

Figure out how QEMU and it's libvirt based UI interfaces work.

You can do it all with the CLI too. libvirt did nothing but piss me off and I couldn't take QEMU seriously until I started learning the CLI. VirtualBox is another option that may be more streamlined for a lot of users if you must have graphical interfaces.

If you wanna test distroes even faster AND you're hosting on a systemd distro AND you're testing a systemd distro AND you like the CLI, give systemd-nspawn a try. It works marvelously, and saves even the little overhead that KVM introduces. nspawn is the single systemd feature I like most.

 

[Betonhaus]

You can do it all with the CLI too. libvirt did nothing but piss me off and I couldn't take QEMU seriously until I started learning the CLI. VirtualBox is another option that may be more streamlined for a lot of users if you must have graphical interfaces.

VirtualBox will be much slower though as it's a more abstracted type of virtualization. Libvirt can take advantage of your CPU's hypervisor abilities to run the VM at the same speed as your host os which dramatically improves the speed of the VM.

 

[Betonhaus]

They're both type 2 hypervisors, lackwit. Practically, libvirt is more performant because of KVM, but the difference is surely not "much slower".

Libvirt is type 1 because it functions on a much lower level in the kernel

 

[analrapist]

Because of contemporary developments, type 1 and 2 are not as differentiable as they used to be. Classical definition was that Type 1 was Bare Metal virtualization, which KVM is absolutely not. "much slower" because of type is not founded in reality, and is completely spurious to the discussion, because the point of contention was bad UI choices by libvirt shit and that there might be UI that is preferable elsewhere. There are a lot of reports that VirtualBox was faster because it had better/more-reliable hardware passthrough. This ought to be a "type 1" sort of thing, but again, today's debate seems to be about which hardware gets the passthrough.

Regardless, this discussion would be improved immensely by objective measurement, which there appears to be a sore lack of.

 

[prollyanotherlurker]

https://trac.ffmpeg.org/wiki/Concatenate

$ for f in GRMN*.MP4 ; do echo "file '$f'" >> mylist.txt; done
$ ffmpeg -f concat -safe 0 -i mylist.txt -c copy output.mp4

should generate output.mp4

truly the best linux using analyst-therapist out there.

 

[The Big Bad D]

VirtualBox will be much slower though as it's a more abstracted type of virtualization. Libvirt can take advantage of your CPU's hypervisor abilities to run the VM at the same speed as your host os which dramatically improves the speed of the VM.

There's a KVM backend for VirtualBox though: https://github.com/cyberus-technology/virtualbox-kvm

 

[Betonhaus]

There's a KVM backend for VirtualBox though: https://github.com/cyberus-technology/virtualbox-kvm

ah my mistake then.

 

[TheDataHorder]

Figure out how QEMU and it's libvirt based UI interfaces work. I've done VM work on a shitty laptop with <8 GB of RAM, they're very convenient.

I've worked with the QEMU/libvirt/KVM combo in the past and it's very powerful if you know what you're doing. The only downside is that, by nature, they're very complex to work with.
QEMU's cli in particular has caused me trouble since its very picky about its parameters. If managed by libvirt then its fine, but its a pain if you're trying to do something libvirt doesn't support properly. (Architectures other then x86 are often where it falls apart.)
hell even gui options to manage this are limited, the only one under active development is Virt-Manager and its terrible. there is a qt one, but its no longer being worked on saddly.
if there was a good gui to help rangle QEMU's complexity then my god that would change so much.

 

[Battlefield42]

Nevermind I got it. Thank you analrapist!

Lol

 

[Aljam]

sddm refuses to work after a nvidia update. I always have to go to tty3 on boot and start plasma after logging in. it's a pain in the ass and even system suspend is broken breaking network access after wake. fucking hybrid graphics smh tbh fam

 

[prollyanotherlurker]

Display manager users lose again.

 

[Betonhaus]

KDE users lose again. Cinnamon ftw

 

[Jang Joo]

You guys are running desktops?

 

[Betonhaus]

You guys are running desktops?

View attachment 7160847

only losers use tablets.

also elinks shits the bed on kiwiflare so you're full of shit

although carbonyl almost works so fancy that

 

[Frederica Bernkastel]

although carbonyl almost works so fancy that

One of the benefits of terminal browsers is they condition you not to rely on the internet for social interaction and consumerism.. Carbonyl loading KF is more a negative than a positive in that regard.

 

[Miller]

sddm refuses to work after a nvidia update. I always have to go to tty3 on boot and start plasma after logging in. it's a pain in the ass and even system suspend is broken breaking network access after wake. fucking hybrid graphics smh tbh fam

Apparently KDE wants to get rid of SDDM and make their own thing, like Gnome with GDM.

 

[Betonhaus]

Apparently KDE wants to get rid of SDDM and make their own thing, like Gnome with GDM.

It would be nice if they added native fingerprint unlock, and possibly even PIN unlock.

 

[Catter]

Apparently KDE wants to get rid of SDDM and make their own thing, like Gnome with GDM.

they should call it KDDM