The Linux Thread - The Autist's OS of Choice

You can edit your first post and quote this other post you replied to to avoid multiposting.

You can also delete the second post.

While you're scrolling towards the latest post in the thread, you can click the "+Quote" button under posts you want to reply to and in the end click "Insert quotes" in the post editor.
On mobile I have tried editing in quotes like the way this post has them, and for whatever reason it won't let me. Most of the time I am on the site I am using my phone. By the time I'm at my computer at night I'm on here. So it might be easier to insert a quote when editing a post on that.

On Alpine, it's bringing in qt-python libraries, wallpaper crap and abseil for some reason, Plus, it crashes now unless xwayland is explicitly turned off in the config if you don't have it installed now. It never did that before. But, even before that it bringing it's own dumb cursor software. I'm not sure if its just Alpine related because of musl or some other crap. Not that it matters because of how easy it was to switch to river.

You can also do the hypercode (quote=) quote here (/quote) to add quotes too. Old forum trick. Obviously, you need the "=" after the first quote bracket with the name, and put the quote in-between. Use [] instead of ().
Yeah, idk about Alpine. I imagine they aren't directly supported by vaxry, it's just being packaged by someone. But idk. I know on Arch it will put in qt if you install the hyprsomething qt application thing.

Arch is the only thing I run hyrprland on because it's the only os I use that hyrprland makes sense to have. A fast moving wm on a fast moving distro. Gentoo I just use dwm and that's it, and on other stuff it just depends.
 
Be also prepared to Google problems and getting frustrated because that particular problem has been around for a decade and the ten possible solutions all don't work.
Unironically one of the reasons why I'm considering Linux is because you can just ask a LLM for help instead of spending 50 hours dump diving into stack overflow threads with retarded shit solutions, each one with conflicting methods or having to read every manual of every library to use.
 
Last edited:
Unironically one of the reasons why I'm considering Linux is because you can just ask a LLM for help instead of spending 50 hours dump diving into stack overflow threads with retarded shit solutions, each one with conflicting methods or having to read every manual of every library to use.
The LLM is also just fed by the same search results and decades-old problems and unfixed bugs, but at least it's less likely to tell you that using Arch would solve your problems (what Arch users don't tell you is that they simply don't ever use their computers for anything but reinstalling and reconfiguring Arch, and the rest of their days they're cruising and bugchasing in public toilets).
 
The LLM is also just fed by the same search results and decades-old problems and unfixed bugs, but at least it's less likely to tell you that using Arch would solve your problems (what Arch users don't tell you is that they simply don't ever use their computers for anything but reinstalling and reconfiguring Arch, and the rest of their days they're cruising and bugchasing in public toilets).
tfw you daily drive arch no problem
 
I'm no fan of systemd, but that didn't stop me from replacing my fstab with systemd.mount files on my present Gentoo installation. Makes the .automount semantic for my network drives that much more straightforward, among other things.
 
  • Like
Reactions: SphinxItOver
Linux Mint 22.1 is out

Modernization of APT dependencies​

One of the major projects in Linux Mint 22.1 was a thorough review and modernization of APT dependencies. The goal was to clean up outdated components, rationalize, and create a streamlined, future-proof set of package management tools and libraries.
APT isn’t just a command-line utility; it’s a robust ecosystem of tools (like Synaptic, GDebi, and apturl) and libraries (such as aptdaemon and packagekit) that support Mint’s applications. Many of these tools, though functional, were built over a decade ago and are no longer maintained upstream. While Linux Mint, Ubuntu, and Debian have patched them over the years, their aging design and limited features created persistent issues and barriers to innovation.
To address this, Linux Mint transitioned to Aptkit and Captain:
  • Aptkit replaces aptdaemon, providing a streamlined library for package management operations with updated functionality.
  • Captain unifies the features of GDebi and apturl into a single, easy-to-use utility.
All the tools previously reliant on aptdaemon, synaptic or apturl now use these replacements.

Captain replaces Gdebi/apturl with better translations and less bugs
This transition has several benefits:

  • Better translations: Everything is now fully translated, eliminating longstanding localization issues.
  • Improved quality: By removing reliance on unmaintained components, Mint ensures fewer bugs and "paper cuts". Small bugs can be addressed, they're no longer considered as "upstream / wontfix".
  • Simplified architecture: Moving to Aptkit allowed the Software Sources to downgrade foreign packages graphically and no longer rely on a VTE. In the Update Manager, it empowered us to boost Wayland compatibility and modernize the multithreading and multiprocessing code, which were getting very old.
  • Easier development: Rather than constantly patching release after release (packagekit's inability to purge, aptdaemon's inability to remove essential orphans), we develop the features we need and rely on libraries that fully support what we need.


Foreign packages can be downgraded graphically
While these changes might be invisible to most users, they lay the groundwork for a smoother, more reliable experience and any new issues can now be addressed with ease. This modernization ensures that Linux Mint’s package management remains robust, user-friendly, and ready for the future.

Much improved package management, multithreading and multiprocessing in the Update Manager
These changes represent a significant step toward a smoother and more future-proof experience with the many tools which rely on package management.

Power Modes​

Choosing a power mode allows you to balance between power saving and performance optimization.
The following power modes are available on all computers:
  • Power-saver mode: Limits performance to conserve energy.
  • Balanced mode: Adjusts performance based on your needs.
On supported systems, an additional Performance mode is available. This mode maximizes performance at the cost of increased power consumption.
Power-saving modes reduce performance but can extend battery life, reduce heat generation, lower CPU frequency, and decrease fan noise. Note that the system may override user settings based on the selected mode to adjust display brightness or make temporary adjustments to further reduce power consumption or enhance performance.
In Cinnamon, you can select the power mode by navigating to Preferences → Power Management:

Power mode selection in the Cinnamon settings
Alternatively, you can select a power mode directly from the power applet:

Power mode selection in the power applet
In Xfce and MATE, power modes can be managed from the terminal.
To view the available power modes, run the following command: powerprofilesctl.
To switch between modes, use the following commands:
  • powerprofilesctl set power-saver to enable power-saver mode.
  • powerprofilesctl set balanced to enable balanced mode.
  • powerprofilesctl set performance to enable performance mode.

Night Light​

Night Light is a feature designed to reduce your exposure to blue light by warming up the color of your monitor. As you approach bedtime, it adjusts the screen to help reduce eyestrain, headaches, and improve sleep quality.
This feature is fully integrated into the Cinnamon desktop environment and it supports both Xorg and Wayland.
To enable Night Light, navigate to Settings → Night Light and toggle the option to activate it.

Night Light in Cinnamon
By default, Cinnamon automatically calculates your local sunrise and sunset times based on your system's timezone. During the day, the screen displays cooler, bluer tones, while at night, Night Light shifts the screen to warmer, redder tones.
If you prefer, you can switch to a manual schedule and set custom start and end times for when the feature is active.
You can also adjust the color temperature to control how warm or neutral you want the display to be during the night.

Cinnamon 6.4​

Linux Mint 22.1 ships with the latest version of Cinnamon, which introduces a brand new default theme, native dialogs, new features and much improved Wayland compatibility.

New default theme​

The default theme was redesigned with a modern aesthetic, characterized by smoother, rounded elements and darker tones that provide more contrast and depth. These changes are aimed at making the Cinnamon desktop visually appealing in all Linux distributions.

The rounder corners and refined contrasts allow the interface to feel less cluttered, offering a more relaxing and enjoyable user experience. The design adjustments align with trends in contemporary UI/UX design, offering a more polished and efficient interface while ensuring that Cinnamon retains its classic, approachable aesthetic.

Cleaner, modern dialogs​

The confirmation dialogs now feature a cleaner layout and clearly separated buttons.

The dialogs to end the session, kill a non-responsive application, authenticate with policykit, join a network, switch audio device, change the display settings, unlock a keyring were previously implemented in Gtk and some of them relied on system components which are not compatible with Wayland.

To improve compatibility and make the user experience more consistent, Cinnamon switched them to native dialogs, implemented in Clutter, just like the panel and the other desktop components.

On-Screen display elements were also redesigned to look cleaner and more modern than before.

Improved Wayland compatibility​

In Cinnamon 6.4, we've replaced the deprecated `policykit-1-gnome`, which had issues under Wayland, with native dialogs for better integration. As a result, all applications and features that require admin privileges are now fully functional in Cinnamon on Wayland.
This includes crucial features like:

  • System snapshots
  • Installing or updating software packages
  • System settings

Additionally, the Night Light feature and the color plugin have both been updated to fully support Wayland.

Other Cinnamon improvements​

New options include:

  • Notifications can now appear above fullscreen windows (new setting).
  • Nemo now has an option to disable auto-expanding of treeview columns during drag and drop.
  • GWL (Global Window List) now includes an option to always show windows from other monitors.

Other notable improvements include:

  • Simplified sound over-amplification settings for easier configuration.
  • Cleaner Alt-Tab behavior with no more arrows, cryptic title changes, and minimized windows now placed at the end by default.
  • Option to toggle password visibility in the screensaver dialog.
  • Nemo actions now support keyboard shortcuts for more efficient navigation.

Other improvements​

The Software Manager has been optimized for better speed, ensuring faster application browsing and installations.
The Bulky file manager now includes a useful feature for removing accents from file names, which is especially handy for international users managing large batches of files.
Thumbnails are now generated for .ora (OpenRaster) files, making it easier to browse graphic design projects and workflows.

Artwork improvements​

In the Mint-Y theme, Cinnamon looks darker, rounder and more modern than before.
Since "Maya" in 2012, every Linux Mint release has come with a fresh batch of desktop wallpapers. People love them, and new sets are always a highlight, but with over 20 collections now, finding the right one has gotten tricky.

"Wallpapers" features the best colorful desktop backgrounds
Starting with Linux Mint 22.1, wallpapers are moving to themed sets, making them easier to explore and more organized.
The first set is "Wallpapers," full of bold, colorful designs featuring cool abstract patterns and 3D shapes to give your desktop a vibrant new look!

Main components​

Linux Mint 22.1 features a Linux kernel 6.8 and an Ubuntu 24.04 package base.

LTS strategy​

Linux Mint 22.1 will receive security updates until 2029.
Until 2026, future versions of Linux Mint will use the same package base as Linux Mint 22.1, making it trivial for people to upgrade.
Until 2026, the development team won't start working on a new base and will be fully focused on this one.
 
On my Gentoo System, I've been experimenting in splitting out services based on my network interfaces and openrc profiles, and I want some feedback if there's a better way to do this:
loopback: sshd.lo (only listens to localhost, mostly unnecessary, for testing purposes)
ppp0: internet connection, unbound (DNS resolver, serves only localhost) wireguard-0 (for VPN)
LAN.vlan-100: unbound-net.vlan-100 (serves only this particular network, queries against localhost, depends only on the first unbound service) sshd.vlan-100 (ditto)
LAN.vlan-200: for local wifi, services likewise vlan-100
wireguard-0: likewise for above too

The advantage is that each service only listens to their specific area of jurisdiction and can function almost independent of each other.
I realized I had a problem when my network switch was dying, and the unbound server that normally serves the LAN freaked out about not being able to listen to the specific IP address, even if I forced it to start.
This way, I can at least access the internet even if the LAN part of the network is hosed due to a faulty switch without any effort to force things.
I specifically added rc_provide="!dns" so anything depending on DNS won't freak out if the LAN interfaces fail to start.
 
some spergery

None of this makes sense without a network diagram incl. a list of your adapters. Whatever you're doing is highly custom and probably only makes sense to your autistic mind. It also sounds like incredible overkill regardless. It also sounds to be a fun project, so don't take this as criticism or an attempt to dissuade you, just letting you know that you have communicated none of the relevant details for people to discuss it with you.
 
None of this makes sense without a network diagram incl. a list of your adapters. Whatever you're doing is highly custom and probably only makes sense to your autistic mind. It also sounds like incredible overkill regardless. It also sounds to be a fun project, so don't take this as criticism or an attempt to dissuade you, just letting you know that you have communicated none of the relevant details for people to discuss it with you.
Basically, I have many network interfaces for my LAN, via VLANs for different traffic grades and firewall rules, and another cable directly into the ISP modem.
Code:
[Internet Modem] --> [This gentoo machine] --> [Switch] --> [The rest of my LAN]
The switch to my LAN started failing, causing the network interface to fail to start, and all the cascading downstream services to fail to start due to service dependencies. My idea was autisticly splitting out services into where it specifically needs to go, instead of a single instance of a service (eg DNS server for the LAN) on all the interfaces. If the connection to the internet still works, I shouldn't need to fight the startup services to connect to whatever search engine on the internet to look up the issue just because the rest of the LAN failed.
I hope that makes better sense.

Edit:
This should be doable with whatever else init system your distro uses.
The cloned services are created as just symlinks in /etc/init.d:
Code:
/etc/init.d/unbound-net.wireguard-0 -> unbound
UNBOUND_BINARY="/usr/sbin/unbound"
UNBOUND_CONFFILE="/etc/unbound/unbound-net.wireguard-0.conf"
UNBOUND_SSDARGS="-x ${UNBOUND_BINARY}"
rc_need="unbound net.wireguard-0"
rc_provide="!dns"
net.wireguard-0 means the interface wireguard-0 is up, while "unbound" is the original instance now configured to only serve queries for the localhost.
Likewise /etc/unbound/unbound-net.wireguard-0.conf would set the interface specific configuration and query the main unbound instance to serve the LAN.
 
Last edited:
On my Gentoo System, I've been experimenting in splitting out services based on my network interfaces and openrc profiles, and I want some feedback if there's a better way to do this:
loopback: sshd.lo (only listens to localhost, mostly unnecessary, for testing purposes)
ppp0: internet connection, unbound (DNS resolver, serves only localhost) wireguard-0 (for VPN)
LAN.vlan-100: unbound-net.vlan-100 (serves only this particular network, queries against localhost, depends only on the first unbound service) sshd.vlan-100 (ditto)
LAN.vlan-200: for local wifi, services likewise vlan-100
wireguard-0: likewise for above too

The advantage is that each service only listens to their specific area of jurisdiction and can function almost independent of each other.
I realized I had a problem when my network switch was dying, and the unbound server that normally serves the LAN freaked out about not being able to listen to the specific IP address, even if I forced it to start.
This way, I can at least access the internet even if the LAN part of the network is hosed due to a faulty switch without any effort to force things.
I specifically added rc_provide="!dns" so anything depending on DNS won't freak out if the LAN interfaces fail to start.
The solution is to buy a decent wireless router, stick OpenWRT on it, and stop worrying about such things.

I've not yet seen a non-schizo use case for VLANs. And as for Unbound, just use your ISP's DNS server. They know where all your traffic is going anyway, so there's not much of a privacy issue.
 
I've not yet seen a non-schizo use case for VLANs
Hey.
I have 4.
Internal.
External untrusted guest access. Access points with an open network.
External semitrusted guest access. Access points with an encrypted network but I give to guests, etc. Laptops that customers send me to use goes here so they can get to the Internet but not scan my network.
Internal no-Internet. For webcams and other chinkshit I don't want phoning home.

I may be schizo, but I like to call it "Paranoid".
 
And as for Unbound, just use your ISP's DNS server. They know where all your traffic is going anyway, so there's not much of a privacy issue.
Its not so much a privacy issue, but I don't want a DNS fuckery. It's an annoying fuckery but still fuckery. I use DNSSEC and compare against Google/Cloudflare DoH time to time to make sure there's nothing strange going on. I'm sure they also know I use TOR occassionally.
The solution is to buy a decent wireless router, stick OpenWRT on it, and stop worrying about such things.
It's pretty freaking weird that you run all this traffic through your arch box, instead of a dedicated SOHO Router.
My PC was already connected directly to the modem for more than a decade, a good router costs money and time to research when I can just run some Linux commands and have whatever I want accomplished immediately. Now that I can afford some gear, I have just put in an SFP+ card on it for LAN cable consolidation, hence the move to VLANs and proper managed switches. Each of the network was previously separate cables to different devices (the wifi network was just a NAT router behind the LAN NAT). I would prefer my existing network configuration etc remain rather than redoing everything.
Are you using vlan tagging? How is the physical separation achieved?
Yeah, its tagged. Its now a single fiber cable (well, 2, since it's SFP). I was even thinking of consolidating the internet connection part of my cables to the modem, but now I see that it would cause a single point of failure if a switch dies.
 
Arch with USEFLAGS would be fucking perfect imo, I do not enjoy using emerge whatsoever. pacman is probably the best package manager available and it's usage is piss easy.

Idk, I could install Gentoo again but Arch just works for the most part.

I assume I could edit PKGBUILD's though eh?
 
  • Agree
Reactions: Marvin and 419
Back