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
Like what?
With Arch, the TUI installer already sets up seatd, dbus, and the XDG_DIR environment variables necessary to run Wayland. You can just install and run any Wayland environment without extra steps. Void however, and many other non-systemd distros, require tinkering with config files. Even if you're not using X, it's not difficult, but it can be annoying to do this repeatedly with multiple computers. Arch also doesn't separate dev packages. Separate packages can be annoying because they add an unnecessary extra step when building stuff locally. Void, for example, has strange names for packages like "MangoHud" (which is case sensitive) or "gst-plugins-bad1" (which doesn't make any sense. why have a 1?). Most distros don't do that, but having to track down the correct package names can be a pain since it is less intuitive. Additionally, systemd's service activation is much more straight forward than, say, runit or OpenRC, as it uses essentially the same command for running and starting services.
 
With Arch, the TUI installer already sets up seatd, dbus, and the XDG_DIR environment variables necessary to run Wayland. You can just install and run any Wayland environment without extra steps. Void however, and many other non-systemd distros, require tinkering with config files. Even if you're not using X, it's not difficult, but it can be annoying to do this repeatedly with multiple computers. Arch also doesn't separate dev packages. Separate packages can be annoying because they add an unnecessary extra step when building stuff locally. Void, for example, has strange names for packages like "MangoHud" (which is case sensitive) or "gst-plugins-bad1" (which doesn't make any sense. why have a 1?). Most distros don't do that, but having to track down the correct package names can be a pain since it is less intuitive. Additionally, systemd's service activation is much more straight forward than, say, runit or OpenRC, as it uses essentially the same command for running and starting services.
The dev package thing is a bit of a different criticism. Which I also find annoying for any of the distros that do that. Void alpine, and from what I remember Debian.

For setting up Wayland environment stuff. It really depends. It depends on the distro, what you are trying to run, and if you are using a display manager also. On how much is going to be set up out of the box by just installing the packages.

But really. I don't tend to use the archinstall script. Because I like having a bit more control than that gives. So in the end setting up arch for me, and setting up something like void, or any of the others. End up being essentially the same.

The commands being different. Idk that just doesn't really bother me. There are front ends for sv and some other stuff on void. I didn't really use them but they get rid of that. On open-rc I haven't even looked into it. Because rc-update rc-service and rc-status are pretty simple to use. Well there technically is rc-config that's a part of eselect on Gentoo. But it gives deprecation warnings when you use it. Not sure why they chose to deprecate it. Because it does solve that criticism for people that don't like them being separate commands.
 
Are those distros compatible with systemd unit files so installing stuff that's outside of distro maintained repos tends to work? I'd like to try S6 but my current setup justworks™

View attachment 7630838
Why the fuck would anything be compatible with systemd pollution?

The good people at Devuan have done sterling work maintaining packages that restore normal functionality to what Debian Linux has been broken into.

You don't need to install any system daemons that aren't covered by Devuan and its init scripts. Even if you did, I'm sure there are probably several tools for converting Lennart Poettring's .service and .timer cumrags into a normal init script if you must insist on installing other shit.
 
"gst-plugins-bad1" (which doesn't make any sense. why have a 1?)
That's the gstreamer plugins from the 1.x series. Debian and Fedora also put a "1" or "1.0" in the package name. Arch's choice to just call it "gst-plugins-bad" is admittedly smarter because the "1" is there to distinguish the new series from the 0.x one, which most distros don't even package anymore.
Arch also doesn't separate dev packages. Separate packages can be annoying because they add an unnecessary extra step when building stuff locally.The decline in personal violence is usually attributed to harsher punishment and the longer-term effects of cultural conditioning. It may also be, however, that this new cultural environment selected against propensities for violence.
Automatic install of dev packages can be added to any package manager with a one line shell function.
strange names for packages like "MangoHud" (which is case sensitive)
That's not a design choice I'd have made. But the search function is case-insensitive, so this isn't really an obstacle to discovery.
 
Last edited:
I've tried Void and have had nothing but issues with the touchpad firmware deciding not to load after reboots, or the internet randomly going out. I don't think it's a hardware issue since it never happened on Alpine. Non-systemds distros almost always have manual intervention quirks systemd distros don't have, and that can waste a lot of unnecessary time.

Speaking of edge cases, I'm also surprised no one has mentioned Devuan.
Void is kinda what gentoo was originally. I will never stop giving them shit over loosing control of their infrastructure cause the team lead just DFE'd (after having a nervous breakdown one day while being shitfaced drunk), and loosing their original domain by letting it lapse. Mainly because it was way too funny to be true.

They also don't support RISC-V(:_(
r Void Users,

We have a problem. In the last few months people have been complaining about the lack of management capabilities in the Void Core Team. We have been aware of the problem, and it’s time to explain the situation.

The current project leader has disappeared. We have had no contact with him since the end of January, and no meaningful contact for well over a year. This itself would be concerning, on its own but no threat to the project.

The problem is that we currently have no ability to manage some of Void’s central resources. In the past, they were managed exclusively by the former project leader. Namely:

  • The Void Linux Github Organisation.
  • The IRC Channels.
  • The domains.
We would like to warn people of a domain name that is no longer under Void Linux control. voidlinux.eu lapsed in its original registration, and was purchased by an unknown 3rd party before Void Linux could regain ownership. At this time, please assume that anything involving voidlinux.eu is not related to Void Linux, and should be considered potentially malicious. Of course, if the person who owns the domain now would like to transfer it to our control, we’d be grateful, and will update voidlinux.org to indicate if this happens.

Our official domain is VoidLinux.org.
 
okay i have a retarded question. how do i flash an iso onto a usb drive in linux? i know theres a way to do it without using etcher which i saw you all clowning on.

i ran cp <iso> /dev/<disk> and nothing happened. i unplugged and plugged back in the usb and now it shows it as bootable. okay i guess

i also find it weird that i needed to use root to flash the usb when what i read online said i shouldnt need to. without root it just kicked me out and said permission denied.

anyway. i have been having relatively few issues on linux and been managing to figure shit out. i did have to boot a live usb and chroot into my disk to fix my kernel once. the longer i use this shit the more i hate windows.
 
Last edited:
okay i have a retarded question. how do i flash an iso onto a usb drive in linux? i know theres a way to do it without using etcher which i saw you all clowning on.

i ran cp <iso> /dev/<disk> and nothing happened. i unplugged and plugged back in the usb and now it shows it as bootable. okay i guess

i also find it weird that i needed to use root to flash the usb when what i read online said i shouldnt need to. without root it just kicked me out and said permission denied.

anyway. i have been having relatively few issues on linux and been managing to figure shit out. i did have to boot a live usb and chroot into my disk to fix my kernel once. the longer i use this shit the more i hate windows.
You use dd. BE VERY CAREFUL. We don't unofficially call it disk destroyer for nothing. I've never seen cp working for making a boot ISO but I guess some iso files it will work, maybe? You could also install ventoy to the USB if you want to just cp many iso files on there and get to choose from them at boot time, works most of the time but some systems don't like it so beware of that. I am used to needing root/sudo to interact with block devices so not sure who said you don't need it?

Code:
sudo dd if=/path/to/your.iso of=/dev/sdX bs=4M status=progress && sync

 
Last edited:
You use dd. BE VERY CAREFUL. We don't unofficially call it disk destroyer for nothing. I've never seen cp working for making a boot ISO but I guess some iso files it will work, maybe? You could also install ventoy to the USB if you want to just cp many iso files on there and get to choose from them at boot time, works most of the time but some systems don't like it so beware of that. I am used to needing root/sudo to interact with block devices so not sure who said you don't need it?

Code:
sudo dd if=/path/to/your.iso of=/dev/sdX bs=4M status=progress && sync


Bash:
sudo sh -c 'cat $ISO_FILE > /dev/$TARGET_DRIVE'

I did this to prepare an AntiX ISO and it worked like a charm, obviously take caution with targeting any drive.
 
You use dd. BE VERY CAREFUL. We don't unofficially call it disk destroyer for nothing. I've never seen cp working for making a boot ISO but I guess some iso files it will work, maybe? You could also install ventoy to the USB if you want to just cp many iso files on there and get to choose from them at boot time, works most of the time but some systems don't like it so beware of that. I am used to needing root/sudo to interact with block devices so not sure who said you don't need it?

Code:
sudo dd if=/path/to/your.iso of=/dev/sdX bs=4M status=progress && sync

when i googled it i saw DD but was looking around for other options as well because of the disc destroyer thing.


this is what i was reading for the cp command and not needing root. partition manager shows that using CP did partition things correctly and such. IDK. if it works it works i guess. I am preparing to install bazzite on a gpd win 4.
 
when i googled it i saw DD but was looking around for other options as well because of the disc destroyer thing.


this is what i was reading for the cp command and not needing root. partition manager shows that using CP did partition things correctly and such. IDK. if it works it works i guess. I am preparing to install bazzite on a gpd win 4.
I just checked. That shit does work. Although it needed sudo. Guess I was just a retard when I got started using Linux, probably tried to always copy to the partition like sda1 and everyone always said to use dd instead. Nice.
 
when i googled it i saw DD but was looking around for other options as well because of the disc destroyer thing.


this is what i was reading for the cp command and not needing root. partition manager shows that using CP did partition things correctly and such. IDK. if it works it works i guess. I am preparing to install bazzite on a gpd win 4.
I'm not sure I've ever seen a device end up as owned by plugdev, maybe a thing on one of those 37 Linux OSes I don't use. But dd and cp and everything else does basically the same thing. dd just gives you more information and control. Always remember the "sync" before unplugging if using cp or dd or cat or..... Also, for the truly paranoid you can also use "eject /dev/sdX" to make sure everything is flushed to the drive.
 
I just checked. That shit does work. Although it needed sudo. Guess I was just a retard when I got started using Linux, probably tried to always copy to the partition like sda1 and everyone always said to use dd instead. Nice.
glad my retarded ass could open you up to new possibilities
 
Bazzite's July 2025 update (archived) replaced KDE Discover with Bazaar (archived), a GNOME/GTK4 Flatpak app store that had its first pre-release two weeks ago.
View attachment 7631694
To say the software is premature is an understatement: among many issues, there's no way to filter searches by category, no Permissions section, not even an Updates tab! But it has a Downloads chart :wow:
View attachment 7631751
Some people (archived) are pissed at Ublue's "break it, update it!" method (they did it with Bluefin too), switching apps and uninstalling old ones they were used to. I'm pretty pissed too. If this keeps up, I'm switching distros. I don't need a wannabe Microsoft doing shit like this.
Bazzite is downstream from Fedora. Whatever brain parasite Fedora suffers from is going to affect your user experience. Fedora's thing is making you a beta tester for the latest Red Hat bullshit, so this is par for the course.

okay i have a retarded question. how do i flash an iso onto a usb drive in linux? i know theres a way to do it without using etcher which i saw you all clowning on.

i ran cp <iso> /dev/<disk> and nothing happened. i unplugged and plugged back in the usb and now it shows it as bootable. okay i guess

i also find it weird that i needed to use root to flash the usb when what i read online said i shouldnt need to. without root it just kicked me out and said permission denied.

anyway. i have been having relatively few issues on linux and been managing to figure shit out. i did have to boot a live usb and chroot into my disk to fix my kernel once. the longer i use this shit the more i hate windows.
USB drives, much like the drives your computer uses for storage, are located in /dev/ as /dev/sd*. The disk destroyer part of dd comes from people accidentally putting the wrong sd* part when using the tool, losing all your shit is just one letter away.

I'd recommend Ventoy. You only need to flash the USB drive once and then it's mounting the drive as usual and transferring ISO images over as files. It's nice to have a multi-OS USB stick for troubleshooting Windows, Linux, etc. Ventoy has its own installation utility, refer to the docs. Still the same danger of :lossmanjack:, so carefully read through what lsblk tells you.
 
okay i have a retarded question. how do i flash an iso onto a usb drive in linux? i know theres a way to do it without using etcher which i saw you all clowning on.

i ran cp <iso> /dev/<disk> and nothing happened. i unplugged and plugged back in the usb and now it shows it as bootable. okay i guess

i also find it weird that i needed to use root to flash the usb when what i read online said i shouldnt need to. without root it just kicked me out and said permission denied.

anyway. i have been having relatively few issues on linux and been managing to figure shit out. i did have to boot a live usb and chroot into my disk to fix my kernel once. the longer i use this shit the more i hate windows.
BalenaEtcher is the easier one if you don't have mintiso or mintusb or whatever it's called
 
this sounds interesting. ive managed to get it working just with kernel commands but with ventoy i could have my endeavouros live usb and other installers on one drive.
Ventoy is great. As I mentioned above you'll sometimes get the odd system that doesn't like it and refuses to boot media from it but the advantage of just slinging 5 isos on there and forgetting about it far outweigh that one rare issue.
 
Back
Top Bottom