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
I would ask this in the other Linux thread but this one seems more active so I'm going to ask here. I've been running KDE neon for years now. I'm running the one based on ubuntu's 22.04 version. I fucked up snap a while ago trying to move it when I realized I didn't allocate enough space to /var and I was trying to get wine working recently when I ran into a problem that's pretty specific to the version of KDE neon I'm running. I'm trying to decide between updating KDE Neon to the latest version, switching back to Kubuntu or switching to OpenSUSE. I'm kind of sick of ubuntu's bullshit that only seems to get more annoying and worse every time I update and KDE Neon breaks ubuntu in random annoying ways that seem to change with every version.

I like KDE, i'm happy with the way it works and I don't want to fuck around with different desktop environments or spend an unreasonable amount of time fucking around with terminals to configure things. OpenSUSE seems to be fairly highly recommended as an out of the box KDE distro and it seems like it'll work alright for most of what I do on a computer.

The thing I'm not sure about is audio production. I've mostly stuck with Ubuntu for so long because of the kxstudio repositories. They make it very easy and straightforward to setup a full linux audio production environment which can be a massive pain in the ass otherwise.

How difficult is it to set up a working audio production environment in an arch based distro? I've read that openSUSE doesn't offer a real time kernel so that's already a bit of a hurdle. How much fucking around is it to get JACK, alsa and pulseaudio to work together?
 
Grub said:
I would ask this in the other Linux thread but this one seems more active so I'm going to ask here. I've been running KDE neon for years now. I'm running the one based on ubuntu's 22.04 version. I fucked up snap a while ago trying to move it when I realized I didn't allocate enough space to /var and I was trying to get wine working recently when I ran into a problem that's pretty specific to the version of KDE neon I'm running. I'm trying to decide between updating KDE Neon to the latest version, switching back to Kubuntu or switching to OpenSUSE. I'm kind of sick of ubuntu's bullshit that only seems to get more annoying and worse every time I update and KDE Neon breaks ubuntu in random annoying ways that seem to change with every version.

I like KDE, i'm happy with the way it works and I don't want to fuck around with different desktop environments or spend an unreasonable amount of time fucking around with terminals to configure things. OpenSUSE seems to be fairly highly recommended as an out of the box KDE distro and it seems like it'll work alright for most of what I do on a computer.

The thing I'm not sure about is audio production. I've mostly stuck with Ubuntu for so long because of the kxstudio repositories. They make it very easy and straightforward to setup a full linux audio production environment which can be a massive pain in the ass otherwise.

How difficult is it to set up a working audio production environment in an arch based distro? I've read that openSUSE doesn't offer a real time kernel so that's already a bit of a hurdle. How much fucking around is it to get JACK, alsa and pulseaudio to work together?
Click to expand...
I've heard SUSE's Zipper package manager is very slow in America because they don't have any mirrors over here, so that's something worth considering. Also from what you're saying Fedora is probably what you're looking for.
 
volatile puar said:
I've heard SUSE's Zipper package manager is very slow in America because they don't have any mirrors over here, so that's something worth considering. Also from what you're saying Fedora is probably what you're looking for.
Click to expand...
Is that all of north America or just America? I don't live in America. I've never really looked into fedora all that much to be honest. It always felt like a really corporate distro even back in the day. Is there some kind of RPM equivalent to kxstudio?

Edit:I should have googled better.

I found this for opensuse that looks promising
 
Last edited:
Dox .bashrc aliases

Bash: 
function emacs() {
    { command emacs --init-directory="$HOME/.emacs.d/" "$@" > /dev/null 2>&1 & } 2>/dev/null
    disown
}

alias emacsclient='emacsclient -c -a ""'
alias emacst='command emacs -nw --init-directory=$HOME/.emacs.d'

alias glst="eza --git --git-ignore --group-directories-first -T -L 3"
alias gcom='git commit -m '
alias gadd='git add '
alias glog='git log --oneline --graph --decorate'

alias resource='source ~/.bashrc && echo ".bashrc reloaded"'

alias clock='tty-clock -c -C 2 -b -s'
 
Grub said:
Is that all of north America or just America? I don't live in America. I've never really looked into fedora all that much to be honest. It always felt like a really corporate distro even back in the day. Is there some kind of RPM equivalent to kxstudio?

Edit:I should have googled better.

I found this for opensuse that looks promising
Click to expand...
OpenSUSE is to SUSE what Fedora is to Red Hat, but SUSE is worse than Red Hat, with OpenSUSE calling conservatives rotten flesh. Fedora is a rolling release distro like Arch and is known for being easy to use (even if they like to push things before they're ready so Red Hat can test them), which is why I recommended it.
 
ToroidalBoat said:
edit 1: Still chugging away at 1 MB per minute. That's like 2 CDs a day. Even when offline.
edit 2: Also, whatever these mysterious writes are, they may not show up in System Monitor.
edit 3: And whatever these mysterious writings are, they do not change the available space.
Click to expand...
Hard to say. What are you actually using on your computer.

Also maybe consider the system journal or logs. If they aren't just being kept in memory. I don't actually keep track of how much is being read and written daily or by the minute. So I don't know what is an actual reasonable amount. But everything is a file on Linux. So things are going to be reading. Things are going to be writing to caches. Storing things in files. Could even be something like graphics driver. Which could make sense.
 
Susanna said:
FAT has a single point of failure, the file allocation table. If a single bit goes wonky there, you could lose the entire thing.
I would recommend you use a modern journaling file system for your backup drive, these have redundancies, or even better a COW system with checksumming, since these can actually tell you if a file has become corrupted.
Click to expand...
It's more complicated. Recovery is easy if only the File Allocation Table is corrupted and the root directory still exists. It can be rebuilt with modern tools. (I remember FAT also has 2 copies of the table).

If only the root directory is destroyed but you still have FAT intact, it will be somewhat harder but still possible to recover because you know how the clusters are grouped. However you will lose the filenames, folder hierarchy and metadata.

If both FAT and Root Directory gets corrupted, it will be pretty difficult, but not impossible to retrieve data and use heuristics to detect a docx, pdf etc. It might be way way too hard to recover everything (like some txt files or fragmented files). You have to guess where the clusters end and begin for a file if the file has no header, and fragmentation makes it much more difficult.
 
Last edited:
Anti Snigger said:
Dox .bashrc aliases

Bash: 
function emacs() {
    { command emacs --init-directory="$HOME/.emacs.d/" "$@" > /dev/null 2>&1 & } 2>/dev/null
    disown
}

alias emacsclient='emacsclient -c -a ""'
alias emacst='command emacs -nw --init-directory=$HOME/.emacs.d'

alias glst="eza --git --git-ignore --group-directories-first -T -L 3"
alias gcom='git commit -m '
alias gadd='git add '
alias glog='git log --oneline --graph --decorate'

alias resource='source ~/.bashrc && echo ".bashrc reloaded"'

alias clock='tty-clock -c -C 2 -b -s'
Click to expand...
My favorite bash "alias" which is actually a function:
gacp() { git add . ; git commit -m "$*" ; git push ; }
 
volatile puar said:
OpenSUSE is to SUSE what Fedora is to Red Hat, but SUSE is worse than Red Hat, with OpenSUSE calling conservatives rotten flesh. Fedora is a rolling release distro like Arch and is known for being easy to use (even if they like to push things before they're ready so Red Hat can test them), which is why I recommended it.
Click to expand...
I always just assume every Linux distro has shitty politics but I'll look more into fedora.
 
I was tinkering around with a fingerprint reader and a yubikey that I 1000% don't need.

In my curiosity I began messing with the config for SDDM login so I could have it fingerprint unlock/yubikey unlock with the PW as a fallback. I ended up getting it stuck and locked out of my PC by having a bad config in the pam file. I panicked a bit but then realized I could save myself. I used a usb drive with Ubuntu live mode on it to get back to the machine then rooted into the other volume and updated it. Getting back into my main OS. I then got the config right so my stupid yubikey setup works as intended.

A victory for autism occurred this day boys.
 
ToroidalBoat said:
Right now it's just the Firefox browser (with caching disabled), Terminal, and the System Monitor. Maybe it's "swap" space? But then again I don't see much activity with it.
Click to expand...
Maybe try iotop, in normal mode it will give you a nice overview of how much writing is actually happening and in batch mode it will give you a detailed log of who read/wrote when. If it's actually Firefox that is writing shit, maybe try one of the privacy forks like Mullvad or Librewolf.
 
The Big Bad D said:
iotop
Click to expand...
Terminal didn't recognize it. Is this another thing I have to install?

Anyway is this some sort of logging thing? If it were then it should show up in System Monitor, but sometimes there's writes that don't show up in it. It's a steady 1 MB per minute constant writing that isn't changed by disconnecting from the 'net. It is more frustrating than the mysterious 20 MB downloads which turned out to be "Safe Browsing".
 
TJT said:
In my curiosity I began messing with the config for SDDM login so I could have it fingerprint unlock/yubikey unlock with the PW as a fallback. I ended up getting it stuck and locked out of my PC by having a bad config in the pam file
Click to expand...
Are you using systemd or another init? Just curious as to see because I've been having issues migrating PAM to mdev.
 
Anti Snigger said:
Dox .bashrc aliases
Click to expand...
Following in the same spirit:
Bash: 
alias tmux='tmux new-session -t '0' || tmux'
alias resource='unalias -a; source ~/.bashrc'

tty-clock
Click to expand...
You can do better* by being more UNIX-y:
Bash: 
watch --interval 1 --precise --color --no-title --no-wrap "date '+%H : %M : %S' | figlet -f Small"
*The reason this is better is because you can add whatever "widget" you want, easily, by mixing paste(1) into it.
 
agent_donkey said:
Following in the same spirit:
Bash: 
alias tmux='tmux new-session -t '0' || tmux'
alias resource='unalias -a; source ~/.bashrc'


You can do better* by being more UNIX-y:
Bash: 
watch --interval 1 --precise --color --no-title --no-wrap "date '+%H : %M : %S' | figlet -f Small"
*The reason this is better is because you can add whatever "widget" you want, easily, by mixing paste(1) into it.
Click to expand...
I like tty clock because it’s dead simple, in tilix I usually have it on top of htop off to the side
Also for whatever reason plasma makes the system clock literally 2 point font no matter what the setting so it’s my clock now
 
Darkholme's Dungeon said:
Are you using systemd or another init? Just curious as to see because I've been having issues migrating PAM to mdev.
Click to expand...
Systemd.

Something is still wrong with it though as SDDM appears to just not work sometimes? I login with the yubikey most of the time now but sometimes it's just nope. Use the PW, or the fingerprint reader. I suspect it has something to do with the services not starting or starting out of sync with the SDDM itself somehow. But it works okay enough that I don't really care at the moment.
 
TJT said:
Systemd.

Something is still wrong with it though as SDDM appears to just not work sometimes? I login with the yubikey most of the time now but sometimes it's just nope. Use the PW, or the fingerprint reader. I suspect it has something to do with the services not starting or starting out of sync with the SDDM itself somehow. But it works okay enough that I don't really care at the moment.
Click to expand...
 
Vesperus said:
Enjoy...
Click to expand...
Thanks. So looks like the biggest offender is some kind of logging, with "systemd-jornald" and "rsyslogd"...

There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?

Screenshot from 2025-06-23 05-35-00.webp
(Pic is thumbnail. Censored SSD name after "jbd2" and other personal info further down.)
 
You must log in or register to reply here.
Back
Top Bottom