renzev

@renzev@lemmy.world

Dieses Profil is von einem föderierten Server und möglicherweise unvollständig. Auf der Original-Instanz anzeigen

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

Ooh, I've never heard of bcachefs, sounds exciting! I see it supports encryption natively, which btrfs doesn't. Pretty cool!

Personally I've never had any issues with btrfs, but I did start using it only a couple years ago, when it was already stable. Makes sense that you'd stick with zfs tho, if that's what you're used to.

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

I find myself inventing new curses for those who screwed things up with these overblown, over complex, minimally functional abominations

Gosh, tell me about it. I once tried writing a custom wifi signal strength indicator app that got its information from network-manager. Apparently the only way to programmatically communicate with network-manager is through dbus, which is just terrible. Scarce to no documentation, poor support for any language other than C/C++, and once you do get it working, it's the most disgusting and overly verbose code you've ever seen, just to query the status of the wifi card. Could've exposed the API through raw unix sockets or something, but nope, they had to reinvent the wheel on that one as well.

Just give me vi and the basic configuration files and let me get on with it!

I'll take this opportunity to shill for Void Linux, it sounds like exactly what you're describing. I've been a happy user for like 5 years now. I particularly like how nothing ever breaks, because there's not much to break on such a minimal system.

...well, actually, a few things did break over the years, but most of those were due to user error haha.

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

Thanks! Memes as education material / propaganda FTW

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

I can think of a single instance where a Redhat-ism is better

I don't know if it would be accurate to call it a redhat-ism, but btrfs is pretty amazing. Transparent compression? Copy-on-write? Yes please! I've been using it for so long now that it's spoiled me lol. Whenever I'm on an ext4 system I have to keep reminding myself that copying a huge file or directory will... you know... actually copy it instead of just making reflinks

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

I'd do away with network-manager on a stationary system too, but I'm on a laptop, and unless there's some trick I don't know about, configuring wifi by hand for every new network I come across sounds like a bit of a pain. Especially for corporate/institution network that use fancy things like PEAP

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

Thanks! I love this format so much. I can't find it now, but one of my favourite memes in this genre was something like this:

STOP DOING

  • Tasks were never meant to be completed
  • Years of working, but there's STILL MORE SHIT TO DO
  • Wanted to get some work done anyway, for a laugh? We had a tool for that: it was called SIMULATION GAMES
  • "Please let me sacrifice a third of my life to justify my existence. Please let me spend eight hours a day working just to be able to do it again the next day" - statements dreamt up by the utterly deranged

Look at what people have been demanding our respect for all this time, with all the schedules and todo lists we have built for them:

These are REAL things done by REAL people

<Pictures of gmail, microsoft outlook, and some TODO list app>

They have played us for absolute fools

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

What I really don't understand is why distro maintainers feel the need to actually go along with these changes. Like, sure, if this predictable interface naming thing worked as intended, I can definitely see how it can be useful for server administrators. You could just hardcode the automatic interface names instead of assigning them manually in /etc/mactab. But why would the rest of us ever need this? Most personal machines have at most one wifi card and one ethernet device, so wlan0 and eth0 are perfectly predictable. And even if you have multiple wifi or ethernet adapters, your networking is probably handled by network-manager, so you never actually have to put interface names into config files. Why force enterprise-grade bloat on users who just want a simple desktop experience?

renzev OP , (Bearbeitet ) an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

No, the "old scheme" is the one that assigns wlan0, wlan1, eth0, eth1, and so on by default. I would say these names are pretty usable.

The part you quoted is what you need to do if you specifically need to be sure that a specific card gets a specifc name 100% of the time. You don't have to bother with it unless you have a reason to.

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

"reddit makes a linux distro" would be hilarious and terrifying

renzev OP , an linuxmemes in Props to Alpine and Kali for disabling this bullshit out of the box

Thanks, glad you like it! I spent quite some time re-making the template from scratch in inkscape, because the original meme din't have enough space for the text

renzev , (Bearbeitet ) an linuxmemes in We are not the same

Oh man are we sharing mpd scripts? I have this one that lets me search through music directory and add anything to the play queue (so I can add a single track or an entire album or whatever):

#!/bin/bash

MUSIC_DIR=$(grep -m 1 -E '^\s*music_directory\s+' "$XDG_CONFIG_HOME/mpd/mpd.conf" | awk '{printf $2}' | tr -d \" | tr -d \')
MUSIC_DIR="${MUSIC_DIR/#\~/$HOME}"

cd "$MUSIC_DIR"
CHOICE="$(find . | cut -c 3- | dmenu)" || exit 1;

mpc insert "$CHOICE"
mpc play

There's also this one that lets me save the currently playing song to a playlist of my choice. It's good if I'm listening to a new album or a new artist and suddenly think "yeah, this song really fits with the mood of X playlist":

#!/bin/bash

MUSIC_DIR=$(grep -m 1 -E '^\s*playlist_directory\s+' "$XDG_CONFIG_HOME/mpd/mpd.conf" | awk '{printf $2}' | tr -d \" | tr -d \')

choice="$(mpc lsplaylists | dmenu)" || { echo "No choice." ; exit 1; }
MUSIC_DIR="${MUSIC_DIR/#\~/$HOME}"

mpc current -f '%file%' >> "$MUSIC_DIR/$choice.m3u"

Here's my script to shuffle play an existing playlist as well:

#!/bin/sh

choice="$(mpc lsplaylists | dmenu)"
mpc clear
sleep 0.1
mpc load "$choice"
sleep 0.1
mpc shuffle
sleep 0.1
mpc play

The sleeps are to prevent Cantata (graphical mpd client) from shitting itself if I run this script while it's open. Also notice mpc shuffle instead of mpc random on. It shuffles the current playlist, but keeps the linear play order, so that I can add songs to play right after the current one.

renzev , an linuxmemes in Don't try this at /home

So switching to a slower wifi AP causes packets destined for outside of your network to not be dropped? That sounds like one of those cursed issues that's a complete nightmare to track down lol. Maybe the faster speed of the 5.8ghz network is causing your router to get overwhelmed or something? Does the same issue happen if you connect via ethernet? I don't really know what else can cause this, I hope you can get it fixed!

renzev OP , an linuxmemes in Debian used to be so good. What happened!?

No idea why busybox is needed. Is this is your emergency boot environment like initramfs?

I cannot for the life of me find the particular fix I followed, but I swear it was a missing symlink to busybox. Not in initramfs, but in the full booted environment. That's why I was so confused haha. I can't find anything about it right now, so maybe I'm misremembering something...

renzev OP , an linuxmemes in Debian used to be so good. What happened!?

Flatpak is awesome, I love it so much. It lets users pick a distro based on the unique features that distro provides, without having to worry about whether their favourite apps are packaged. Since you're considering switching to debian+flatpak, here is a list of pitfalls I've run into in flatpak so far, maybe this can save you some troubleshooting:

  • You need to have a thing called an "xdg dekstop portal" installed. Otherwise filepickers will be broken. On Debian this should be a dependency of flatpak, so it should be installed by default tho.
  • If you're manually restarting Xorg without using a display manager, make sure the xdg desktop portal process doesn't get started twice. Otherwise it will be broken
  • As far as I understand, there's no way to use xdg desktop portal to forward an entire directory through to a flatpak'd app, unless the app itself asks specifically for a directory. So stuff like opening a .html file that references a .css file in the same directory with a flatpak'd browser will be broken, unless you manually make an exception using Flatseal or flatpak override.
  • Make sure your root filesystem is mounted with "shared" propagation, otherwise umount commands won't propagate into flatpak's sandbox, and drives will get stuck in a weird state where they're mounted in some namespaces, but not others. This should be the default in Debian tho.
  • If flatpak'd Firefox has ugly bitmap fonts, follow this workaround

Anyway, this is just my experience running Flatapk in Void, hopefully it works smoother for you on Debian.

renzev , an linuxmemes in Don't try this at /home

Gentoo seems fun, I wanna try it some day. I would also recommend Void if you're looking for a distro with a boring old binary package manager (it's what I use on my laptop). Although the package list in Void is rather barren, I would recommend installing Flatpak to help fill in the gaps for some of the missing packages. There's also Alpine if you wanna go balls deep into the minimalism rabbithole. What makes Alpine so difficult is that it's a musl libc distro, so anything that needs glibc (i.e. any "serious" gui application) needs to run through a compatibility layer like gcompat or flatpak. Void is available in both glibc and musl libc flavours.

The community aspect can definitely be a big hurdle. Most of the time if you search for something like "<description of your issue> ubuntu", you can more or less blindly copy-paste the commands from the first result and it will work. With niche distros, you have to be able to interpolate instructions aimed at other distros and actually understand what you're doing. That why I would never recommend a non-systemd distro to someone who's new to linux.

By the way, what's your network issue? I'm no expert, but maybe I can try to help?

  • Alle
  • Abonniert
  • Moderiert
  • Favoriten
  • •
  • random
  • haupteingang
  • Alle Magazine
    •