The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
If the motherboard I'm buying has WiFi or Bluetooth integrated, those chips will be desoldered before use. All wireless protocols are optional, no exceptions.
Where on earth are you finding motherboards with the wifi soldiered on? They all have a removable module where you undo one screw and pop it out.
 
  • Agree
Reactions: seri0us
Where on earth are you finding motherboards with the wifi soldiered on? They all have a removable module where you undo one screw and pop it out.
uem0a1nm4hcc1.jpg
Even wireless amongst the normal soldered-on IO is usually removable too
 
Wireless is almost always removable as different modules are required in different countries due to differing spectrum laws.

And on the "How to make small Linux" there's also "Buildroot" which often gets used for embedded systems.
 
  • Agree
Reactions: analrapist
I lhink Dwm had a great philosophical, and design basis, but there were programs likw cwm that did it way better. That's usually the problem with suckless applications. There are just better ways of doing the same thing. Just make something that does one thing, and do it well enough you never have to worry about it again.

But I think the great thing about suckless stuff is how well they work in conjunction with cli applications (tmux, irc, w3m, mpv, lf, rsync etc) because of that simplistic design philosophy.

And,to be honest, dwm doesn't require patching. You can just play around with the keybinds in the config.h file, and make things to your liking.
One of biggest problems with software today is the obsession with accessibility and need to do any and everything.
Did it better philosophical, or some other aspect? It looks like it's a stacking window manager instead of a dynamic tiling window manager. Which is an important part of dwm for me. Not just the minimalism and suckless philosophy.

If you patched up dwm and configure it. You also never need to worry about it. I can patch it once. And you can just commit it to a GitHub repo, or back it up in whatever way you want. And on any install, you can pull thet repo down or copy it over. And you have that exact version of dwm (works for any suckless tool also). So to me because of the nature of changing the source code for this stuff. If anything it makes maintenance, and portability easier than anything else I've used.

And yeah, I do have an unpatched dwm I have been making myself use on one install. There a few reasons I wanted to make myself use it without patching that don't really matter here. I do think I prefer it patched to do things I like having. Like adding more layouts, adding scratch pads, adding gaps between windows (to me it's actually useful beyond just looking nice), having the mouse warp when changing windows with keybinds, which is actually the one thing I did let myself patch into the, no patch version.
 
  • Feels
Reactions: analrapist
And on the "How to make small Linux" there's also "Buildroot" which often gets used for embedded systems.
Important suggestion, IMO. Buildroot is substantially easier to hack on and use than Yocto. Yocto's designed for corporate, Buildroot for hackers.
 
And on the "How to make small Linux" there's also "Buildroot" which often gets used for embedded systems.
or if you truly are insane, you'd build the kernel, sysutils and bootloader yourself and shove them together on a virtual drive to make your own Linux distro.
I've done this, don't do this unless you really are insane. i did it because LFS didn't really teach me how a linux system fits together at a low level.
learning how the kernel and sysutils (in my case, busybox) work together symbiotically to achieve a functioning os taught me how it fit together at a low level, which is what i wanted to know.
 
or if you truly are insane, you'd build the kernel, sysutils and bootloader yourself and shove them together on a virtual drive to make your own Linux distro.
I've done this, don't do this unless you really are insane. i did it because LFS didn't really teach me how a linux system fits together at a low level.
learning how the kernel and sysutils (in my case, busybox) work together symbiotically to achieve a functioning os taught me how it fit together at a low level, which is what i wanted to know.
It's only fun when you fit it on a 1.44MB floppy.
My first 'router' was a 386 PC with a floppy drive only.
(My lawn, get off it, etc)
 
you forget to acknowledge the fact that as phones become more viable and popular, the younger generation has less and less use for a traditional desktop which i believe does end up cutting into the marketshare.
Very few of those people would have got a home pc before the advent of smart phones, so the actual impact is minimal.
 
FWIW I use fish with oh-my-fish.

I've been using fish for over 10 years now. I didn't realize it was written in Rust. Was it always written in rust? Back when I started using it, I'd often see stack crashes printed to the screen. It had some issues, but it never crashed out the terminal. The tab completion is really good, out of the box without any extensions. On most servers I just install it via ansible with no customization and it makes life so much easier.

Even wireless amongst the normal soldered-on IO is usually removable too

I was really surprised to learn this too. I was moving this motherboard from a prebuilt into a custom case years ago, and was trying to figure out what to do about, what I assumed was, a proprietary antenna. I was wondering if there were standard leads under the shield, took it off, and was surprised to just see a little PCI-E slot with a regular laptop Wi-Fi/Bluetooth adapter in it.

1733504947444.png
 

Attachments

  • 1733504947444.png
    1733504947444.png
    1 MB · Views: 28
Back