The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
more convenient than reinstalling Debian each version
Are you retarded? In what world is searching-and-replacing a distro name, running apt-get update && apt-get upgrade && apt-get distupgrade more 'inconvenient' than just having shit break at random at any point?
 
It's taken me too long to realise that "<application_name>&" in the terminal launches an app without the terminal defaulting to listen to mode. I feel so dumb.
The program is run in the background of that shell, you can bring it back to the foreground using fg. If you have multiple backgrounded processes, you can select which one bring back to the "foreground" by listing them with jobs. As I type this I realize I've never backgrounded more than 3 things at once, ever.
 
The program is run in the background of that shell, you can bring it back to the foreground using fg. If you have multiple backgrounded processes, you can select which one bring back to the "foreground" by listing them with jobs. As I type this I realize I've never backgrounded more than 3 things at once, ever.

So & makes the process run in bg of the shell? Let's say I use the shell to open most apps, then use it with nVim to program, won't nVim's performance be impacted by the apps because they're shell-bound?
 
Rolling release is more convenient than reinstalling Debian each version.
i'm not sure its that, especially since on most systems you can run upgrade, and don't have to reinstall. but its certainly nice not having a borked version of kde that has 1 extremely specific and unfixable bug for the next 4 years each update.
 
Maybe Debian has never been retarded, but last year when I upgraded Lubuntu from 23.10 to 24.04 it ended up bricking my fucking kernel and I had to boot into USB to back some stuff up on my main drive before reinstalling the entire OS from scratch. I'm still too lazy to try out another distro for now, but I'm not trusting Canonical to never make things harder than they need to be again.
 
i'm not sure its that, especially since on most systems you can run upgrade, and don't have to reinstall. but its certainly nice not having a borked version of kde that has 1 extremely specific and unfixable bug for the next 4 years each update.
Correction, I was on MX Linux. Docs say: "If you are using MX Linux and want to move from its Debian 11 (Bullseye) base to Debian 12 (Bookworm), a full reinstall is highly recommended and is the official advice from the MX Linux team. There is no officially supported in-place upgrade path for this major base change, and attempting to upgrade in place can lead to significant issues or a broken system"
So maybe this is an advantage to use vanilla Debian over MX.
 
Maybe Debian has never been retarded
No, Debian has always been retarded, it's just less retarded than most, because it's been one of the longest running, most successful distroes. But that also means it's retarded in its own ways. And then Arch is retarded because Arch isn't like Debian to be more like upstream. Using Debian is being able to make almost anything work for advice. But always, always: Retarded in what ways? That's how you figure out what distro you like: it's retarded in ways you don't mind.

I've dist-upgraded every Debian version since etch. The only time I've ever had issues was running sid, during a time of big change, and randomly not updating for months.
 
Correction, I was on MX Linux. Docs say: "If you are using MX Linux and want to move from its Debian 11 (Bullseye) base to Debian 12 (Bookworm), a full reinstall is highly recommended and is the official advice from the MX Linux team. There is no officially supported in-place upgrade path for this major base change, and attempting to upgrade in place can lead to significant issues or a broken system"
So maybe this is an advantage to use vanilla Debian over MX.
Or Devuan, which has many of the advantages of MX, but is perfectly fine with being upgraded normally.
 
I use FreeBSD as a couple of fileshares. I really like it. Haven't tried using it as a desktop.

I spun two some VMs to simulate the 4chan pdf vulnerability, and I hated it. I hated everything about it.

Mind you, most of the hate was because of the Yotsuba stack with ancient php, ghostscript running in the same process as the upload-and-execute-to-shell parser, and the fact it was FBSD 10.x, and ghostscript was ~9.x. 4chan was the perfect honeypot for script kiddies for a decade - accidentally -.

I haven't used it properly, let's say that much.
 
Who exactly was talking about a retarded normie strawman? Not me.
And I pointed out how automount sometimes just fails, either down to the distro not even including it or it failing for bizarre reasons.

Both of these things bother me immensely based on my own usage across the past 20 years. It makes basic file tasks with external drives annoying.

So yeah it was pretty fucking dumb.
just general advice for you. and anyone that doesn't know. This is something I've learned just because I do use external storage, usb's external drives, and have multiple internal drives.

If you want it to just work. You will need to make sure a few things are installed. Obviously your file manager of choice. Then you will want udisks2, and also gvfs. At least if you are using a gtk based file manager. for kde based or qt stuff, idk, since I mostly use gtk stuff. But you will almost certainly need udisks2, and it likely will either tell you somewhere if you need something else, or pull it in automatically. If you are using thunar, it will have thunar-volman which like the name suggests is a plugin for it, that manages volumes. You can adjust your settings with that. Others will have their own way. but if you have those programs it should take care of it.

if you have those, also polkit and a polkit agent helps too because you will likely need authentication for mounting certain drives (like internal drives) in a gui, but that depends on what you are doing.

@khaine I use FreeBSD as a couple of fileshares. I really like it. Haven't tried using it as a desktop.
I think the use case you have been using it for is probably the right way to use freebsd. On the desktop. Overall just sticking to linux. At least for now, is my general advice.

There might be some people, with specific hardware that is covered well. That happen to only use software on the desktop that's covered well also. But when you start to do anything a bit outside of that. It starts to become a real pain. In general, I just find it to be a worse experience than linux.

And they have the linux compatibility layer, But to me, it seems a bit iffy. When I used it. It had all kinds of random issues. And was just a headache. So if something you happen to use, is supported through that. I recommend just not bothering.

Some day, in the future. Freebsd at least, might make some advances in the desktop space. The problem, from what I've seen. Is while people might like the idea of how the bsd's do things. Like having a cohesive kernel and userland. Not having a "bloated" kernel. Sticking more to the unix philosophy. Those things in some ways are actually why it just doesn't work as well as linux right now. Also the license.

Linux has a lot of companies, hardware, and software contributing code to it. Getting drivers into the kernel. And that means almost any hardware is going to be supported. Obviously not everything, but a ton of stuff. And as a desktop users. That is something really appealing.

The unix philosophy gets in the way, because it means if something isn't portable, they won't add it, or at least their will be a lot of objections to it. Some things that will let you get better performance, or more convenience for users. That would need to be written for how the freebsd kernel does things. Like an init system for the freebsd kernel. I'm not a huge fan of systemd (not because it doesn't work well though), but it did bring things that make peoples lives easier, and is able to do a lot of things in the background that make developers lives easier. But systemd is very much not portable. Which is something that has stopped freebsd from moving towards some kind of their own more advanced init system with hooks for its kernel. At least from my understanding, and hearing talks from people.

Then the license. the agpl, Over time really gave linux a huge advantage over the bsd's . Them having their more permissive license let companies. Like famously apple ( from what I understand it used a lot of freebsd code for macos), and getting very little back as a thank you (they did at least hire some of the devs, though you could say they took the best devs, who were no longer working on freebsd). Meanwhile, you have android coming from linux. But because the gpl requires the code used from it also be open source. It ended up getting a lot of help back from the companies that ended up relying on linux over the years.

Along with the license. Because Linus ended up being willing to support any hardware he could. And accept code from companies, it has given Linux a huge advantage.

I'm sure there are a lot of other things that ended up leading to it too, but this is all I'm willing to type about something no one asked for.
 
Last edited:
Obviously your file manager of choice. Then you will want udisks2, and also gvfs. At least if you are using a gtk based file manager. for kde based or qt stuff, idk, since I mostly use gtk stuff.
The KDE alternative to gvfs would be kio. It is a hard dependency of both Plasma and Dolphin so the core package is impossible to miss. But there's other parts of it that are optional that provide useful functionality (such as elevating Dolphin to root, using mobile devices, etc) that may need to be installed manually.
Screenshot from the Gentoo packages list but it should be about the same in other distros too.
1747986988204.webp
I will say that disk management in KDE "Just Works", everything mounted through Dolphin was in a standard place (/run/media/<username>). It is not something I would consider broken.
 
I will say that disk management in KDE "Just Works", everything mounted through Dolphin was in a standard place (/run/media/<username>). It is not something I would consider broken
it's probably using udisks2 along with kio then. Since that's where it automatically mounts things. in /run/media/.

which is actually the reason I've moved away from udisk2. Because as far as I can tell, it actually won't let you pick anywhere else to mount things. Also because I don't use gui file managers much anymore. So not having that does really cause me any extra headache. It lets me use other options for rootless device mounting that let me mount drives wherever I would like.
 
Lutris is currently unable to install game launchers. The launcher installs then opens to do its install and then fails. For EA App I can get to the login screen before it closes. Battle.net wont even get to the login screen.

edit: idk how i did it but i managed to do it. another W for me on linux. fuck you microsoft
 
Last edited:
One of the first things I do on a new Linux Desktop/Laptop is disable media mounting as 95% of the time I put in a stick or sd card is to "dd" something to it so I can move the stick to something else to boot it. The rest of the time I understand the horribly complex "mount" command.
 
So & makes the process run in bg of the shell? Let's say I use the shell to open most apps, then use it with nVim to program, won't nVim's performance be impacted by the apps because they're shell-bound?
No, the processes don't impact the performance of the shell itself. But if you kill that shell it kills those processes too.
 
Lutris is currently unable to install game launchers. The launcher installs then opens to do its install and then fails. For EA App I can get to the login screen before it closes. Battle.net wont even get to the login screen.

edit: idk how i did it but i managed to do it. another W for me on linux. fuck you microsoft
Try adding the exe Lutis installed to Steam as a Non-Steam Game and then running it with Proton. Worked for me with Ubisoft Connect.
 
Back
Top Bottom