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
Can someone recommend me a good audio player? Something roughly in line with Foobar2000. Both graphical and terminal are a OK.
I like ncmpcpp.
This isn't as simple as grub launching with RO instead of RW, is it?
According to the forums its bug in fsck.fat. Not sure if it really is a bug or not, but changing the flags to 0 0 helped and now it mounts normally. Weird.
 
Apparently I'm a fucking bot, saar and that AI filter stopped me from reading it on my phone :( Fucking smug troonime avatar.
We discussed this a few weeks ago in the OSS community thread, you can completely bypass it by changing your useragent to something that does not look like a real browser lmfao.
 
I have to ask, do you use some weird voice to text to write your posts? You could delete half your stops and convert the other to commas and it'd be way less of a pain to parse.
On the one you replied to. I definitely hit space twice on accident on my phone, and it put a period in front of than him.


No, I didn't forget, I think I set up something wrong about the LVM or maybe I forgot to include the xfs module in the kernel, or something. Will find out today.
It probably was something dumb like this. I do really recommend installing the bin kernel like @Frederica Bernkastel said. Besides just getting through the install a little quicker. You can use that to check which modules are loaded after you are booted into your system. Then you can use that list of modules to automatically configure a kernel config, that disables everything except the modules you need. It makes slimming down the kernel super simple.

The only other thing I can think of is possibly an issue with your initramfs if you are using initramfs. (or you forgot to enable the grub useflag, set the right grub_platform use flag, or didn't enable the initramfs use flag) Or if you aren't using initramfs you need to make sure you build the modules for your filesystem, and the kind of drive you are using into the kernel. Instead of building them as modules. Or maybe not installing xfsprogs.
 
There is fooyin, which seems to be pretty close to foobar2000.
View attachment 7873537
View attachment 7873536
Does it have support for foobar2000 plugins? Cuz it kinda ceases to make sense when it has to rely on it's own plugin system. Kinda how Double Commander has more or less parity with Total Commander plugins making it a very robust tool that not only copies TC, but also leverages it's plugin system that's half the reason people use it. Same goes for foobar2000, if it doesn't have the plugin interoperability it's more or less useless for people who are looking for a foobar alternative on Linux.
 
Does it have support for foobar2000 plugins? Cuz it kinda ceases to make sense when it has to rely on it's own plugin system. Kinda how Double Commander has more or less parity with Total Commander plugins making it a very robust tool that not only copies TC, but also leverages it's plugin system that's half the reason people use it. Same goes for foobar2000, if it doesn't have the plugin interoperability it's more or less useless for people who are looking for a foobar alternative on Linux.
I tried fooyin only once a while back, so I can't really help you. But now that I'm on Gentoo, I'll give it another shot.
In the meantime @Yandex Captcha Solver probably can give more infos on the plugin system.
 

I feel like lunduke is stretching a bit with this one. It's not like the multilib thing (even that story in reality probably wouldn't have ended up like he implied it would).

I think its probably a good idea to plan how 32 bit will be phased out at some point. And it makes sense that developers don't want to spend their time and energy solving the 2038 problem. Not even because 32 bit will eventually be phased out. But because it's already obsolete, and in the future it will become even more obsolete.

But most importantly he answers his own questions in this. Besides all of that. Why drop support for the thing that is being used by fewer people all the time that is no longer being added to new systems (it's not like they are dropping support now anyway), while there are modules that aren't going to be dropped that don't have maintainers? Hmmmm, doesn't take a genius to figure that one out.
 
Last edited:
I'm just surprised there isn't a popularized retro exclusive Linux distribution for 32-bit and older hardware. If there really is a market for it, people should make one.
 
Last edited:
I think its probably a good idea to plan how 32 bit will be phased out at some point. And it makes sense that developers don't want to spend their time and energy solving the 2038 problem.
Microsoft just hard yoinked 32-bit with the release of Windows 11 and no one even noticed since WoW64 is such a solid compatibility layer that most people were running 64-bit Windows and didn't even consider that the 32-bit part is just a compatibility layer, all the old games just werk.

You only really want to worry about 64-bit Linux being able to flawlessly run 32-bit software under a similar subsystem, since actively used 32-bit only hardware is like a percentage of a percentage. Like, pre-2003 hardware. Prehistoric fossils. Even the oldest x86-64 CPU's like the Athlon 64 are basically useless for running modern software in any realistic scenario. The handful of schizophrenics still using those won't matter when it's time to fully ditch 32-bit Linux, and they'll definitely make their own little fork backporting all the kernel changes to 32-bit.
 
Not even because 32 bit will eventually be phased out. But because it's already obsolete, and in the future it will become even more obsolete.

As long as they stick with not breaking old userlands then it’s already completely obsolete. People who need old i686 or older hardware going can and should run an embedded extended LTS kernel with support for all modern hardware stripped right out. People who need 32-bit distros can just run them under an x86_64 kernel. Problem (mostly) sorted.

But if kernel developers plan to remove 32-bit backwards compatibility from their x86_64 platform support (it has always been a configurable option in make menuconfig, after all) to complete the phase out of legacy code paths, then there needs to be a decent userland way to handle it (i.e. as performant as the existing way) implemented long before support is ever ripped out,

Anything less than that and we’ll see Win32 binaries (under Wine) outliving native Linux ones on an operating system which is designed to run entire chroots of coexisting userlands, and that would be a huge travesty. Even when we have source code available, quite a bit of decent software which no longer sees updates is platform-specific.

The whole Year 2038 problem is mostly a nothingburger for most legacy 32-bit software running on 64-bit systems, as one can just hook the appropriate calls in userspace (LD_PRELOAD of some simple userland libraries is a wonderful thing) to add a fixed negative offset to them. Sure, affected legacy applications will show incorrect date/time info on things like internal file pickers, but the time would continue to be accurately reflected on the actual filesystem and within modern, compliant software,

What we all really need to be thinking about is keeping modern libraries working across both i686 and x86_64 so that older applications can remain usable (e.g. if we don’t have 32-bit NVIDIA driver libraries all of a sudden, then we will lose access to our older video games)
 

Watching this. I feel like it really made it obvious why I can stand watching lunduke (besides the fact he is the only person that covers some stories).

It's because I hate the people he talks about SOO much more. Than him. When he talks about these people he seems like a so much more bearable.

Until he makes another video saying we need to strip away Internet privacy to stop the heckin trolls.
my only real gripe with lunduke is if you follow software development at all and learn basic facts about how these companies operate, lunduke's positions sound completely out of left field, like he hasn't worked a day in the industry.
since he claims to have decades of experience in the industry, this makes it come across as he's putting his agenda first before the truth, and i think he purposefully misleads his audience.
after so many videos where they left me doubting his sincerity, i had to unsub.
 
As long as they stick with not breaking old userlands then it’s already completely obsolete. People who need old i686 or older hardware going can and should run an embedded extended LTS kernel with support for all modern hardware stripped right out. People who need 32-bit distros can just run them under an x86_64 kernel. Problem (mostly) sorted.
They generally have been pretty good about not breaking userland, or at least trying to not break it. I would be talking out of my ass, if I gave any speculation on what they are actually going to do. But I imagine 32 bit emulation and the ability to run native 32 bit programs on 64 bit kernels isn't going anywhere even as it gets phased out.

And if worse comes to worse. I think an option that makes sense is just using an older kernel. I really don't see why running a kernel that's a few years old on some super old 32 bit hardware would be a big deal, if it comes to that.

my only real gripe with lunduke is if you follow software development at all and learn basic facts about how these companies operate, lunduke's positions sound completely out of left field, like he hasn't worked a day in the industry.
since he claims to have decades of experience in the industry, this makes it come across as he's putting his agenda first before the truth, and i think he purposefully misleads his audience.
after so many videos where they left me doubting his sincerity, i had to unsub.
Yeah, I 100% agree. Over time watching his videos, he's lost most of his credibility to me. The problem is. There are times where he does break stories, or he is the only one that covers them. Or he does, from what I can tell give honest coverage. But then he will cover something you can tell he is completely full of shit.

Then he will out a video like this. That I actually like.


Lunduke is really a mixed bag.
 
I complained about riverwm breaking too much with updates a while ago, and it looks like the dev made a fork in response to that.
How much better off would I be using a tiling WM instead of Xfce? (And I say this as a user, at various points, of tmux, ranger, Vim, Neovim and Emacs ... I actually worry that the WM might end up getting in the way of those like Xfce already did)
 
How much better off would I be using a tiling WM instead of Xfce? (And I say this as a user, at various points, of tmux, ranger, Vim, Neovim and Emacs ... I actually worry that the WM might end up getting in the way of those like Xfce already did)

It all depends on how much you care about keyboard usage being prioritized over the mouse, the layout of your windows, etc. The i3 window manager is one of the more accessible tiling window managers, though you do have to manually select which direction you want the windows to spawn: aside the currently focused window and below the currently focused window. The default configuration file for i3 should suffice if you really don't care to deal with messing around so much. In my opinion, i3 handles the mouse just as well as the keyboard out of the box while others you have to go out of your way to find a balance.
 
Back
Top Bottom