Yes, "wantonly" is spelled correctly here. I looked at it and immediately it felt wrong so this is for any like me who's only ever heard it said.
Also, broke my Codium install today, no idea how but it won't load debug values now, woo.
Yes, "wantonly" is spelled correctly here. I looked at it and immediately it felt wrong so this is for any like me who's only ever heard it said.
Also, broke my Codium install today, no idea how but it won't load debug values now, woo.
And also
Btw, downloading a CD (.iso) on the phone to boot it, because your Linux broke while you had no bootable thumbdrive around. Is something a lot of people here did sometime.
PSA: get a cheap thumb drive and install ventoy. You'll never regret it!
Plus you can technically still use it to store files if you make a directory in the ventoy dump partition.
I keep memtest86+, clonezilla, Ubuntu 24.04lts, gparted, and boot-repair on the drive.
maybe not ventoy specifically since it's full of binary blobs that are virtually unvettable
Yeah, I need to find a better way. Been trying to setup pxe boot in docker
I've got a binary blob right here π₯΅
Eh, good enough. Your Linux install also has binary blobs.
I never even thought of that - you then plug in your phone as a thumb drive? Makes sense.
I mean I'm not sure I could actually boot off of my phone as a USB drive. That would be an interesting concept.
Unlikely. The USB protocol requires one master and one or more slaves (or whatever less charged nomenclature you prefer). In all likelihood UEFI will blindly assume to be the master while Android and iOS require negotiation to figure out who's boss and what interface to present.
Although given UEFI it might be possible to patch that functionality in.
i had this feature when i installed ubports (ubuntu touch) on my phone in 2021.
much before that in 2013 my phone's stock rom had a 'driver install' mode that presents an iso file in the system partition to the computer as a virtual cdrom, i could swap out that file with a linux iso and it would boot
The USB protocol and UEFI aren't a problem, but Android/iOS might be. I've booted various PCs from a raspberry pi (USB-OTG), but the last time I tried to boot an iso from my android phone I couldn't get it to work. It's been a while so I can't remember exactly what the issue was.
My guess the issue is that phones don't just show up as simple drives, they rely on MTP support
That's what I was referring to with "which interface to present."
There's a tool, whose name I forget, which is included in Kali NetHunter to do just that. It does whatever trickery is needed to present the phone/tablet as a bootable thumb drive. It requires root and, to my dismay when I needed it, I never owned a device that was rootable to fully use NetHunter. It could do a lot of other cool stuff via USB too; phone as a Bad USB, Rubber Ducky, automated Windows login bypasses, etc.
It does, though with an app that exposes the iso.
Edit: Right, i thought it was EtchDroid. I think it was DriveDroid (with a broken cert)? There's also SimpleBoot now.
Just a couple days ago I needed a microsd to usb adapter. Couldn't find one, so I loaded the files to a memory with fat usb(I don't know what it's called) and usb c connections. Then connected the memory to my phone and on my phone I moved the files to the microsd card.
Not the same but similar vibes I think.
It's sad that several phones are removing the memory slot.
Fat USB is called USB A. The one you use for printers is USB B. Then there are mini-A, mini-B, micro-A, micro-B and USB 3.0 micro-B which are all different shapes physically. And USB A 3.0 has slightly different contacts from USB A 1.0/2.0
Anyway, that was when USB nomenclature was still simple. Don't google anything they did past version 3.0, for your own sanity. We're now down to mostly the USB C and A shapes, but USB 3.2 gen 1x1 is the same thing as USB 3.1 gen 1 is the same thing as USB 3.0.
USB 4 simplified things a bit, but now you can get things like Gen 4 asymmetric 3:1
I had that exact situation but simply went to the library to fix it. Modern phones scare me.
My computer configuration is best described as a construction of duct tape and chewing gum holding a house of cards in place
Tbh my server is getting a bit that way too, which is slightly more concerning
My partner would text me 'what did you do' when I had a day off and audiobookshelf stopped working. This is why I only tinker after midnight
Yeahβ¦ ive been meaning to get audiobookshelf setup, but it looked like a pain so itβs been sitting there untouched. That along with needing to migrate from Plex to Jellyfin, my projects pile up.
ABS is actually quite easy if you already have a library for audiobooks on Plex
Just install ABS on the same box and point it at the same folder and it will do most of the rest itself
Remote access is a bit of a pain though. I'm using tailscale for it. I wish there was a better, more universal (also free) 2fa solution out there but it just doesn't exist.
ABS is actually quite easy
Well yeah, you just depress the brake pedal
I got it up and running in about 10 minutes just yesterday, but that's probably because I had already spent a couple of days learning how to use quadlets and getting my remote access scheme figured out.
Does mTLS work with ABS? That's how I control access to many of my "exposed" services.
I just set it up with my Docker setup. Point it at the appropriate volumes and it pretty much goes. GUI tools for Docker help. I like Dockge.
Even with docker, things can get complicated. Like if you use *arr stack for your plex library, but you manually copied in some extra subtitle files, or tweaked the descriptions of some media. Now you have to find those customizations so you can migrate them to the jellyfin library
I also wait until my partner is asleep. It still doesn't make me 100% safe from the 'what did you do' texts, because sometimes I break things that I don't think to check. Worse, sometimes I break something so bad that I stay up until 6am trying to fix it, only to cook my brain and pass out without fully repairing what went wrong.
But it's still better than doing it during the day.
Sounds like a very similar situation to car mechanics
There's the German saying, that the shoemaker always has the worst shoes.
Is Spain we say that the blacksmith uses wooden spoons.
Wouldn't that mean something else?
The saying literally translates to "in the house of a blacksmith there are wooden spoons". In Poland we say "the shoemaker walks in shoes with holes". They all just means that people who build things as their job don't have the time to build those things for themselves.
I am a computer person. My philosophy is probably a common one, if it works donβt touch it.
I am an Arch user. My philosophy is probably just as common: if it works, I must fuck with it
It's a common philosophy practiced by everyone that says, "yeah, I probably shouldn't mess with this, it is working fine right now, but ... Maybe ...."
Well, we profess to follow it at least.
This is why you keep 2 computers. One that is dull and as stock as you can. And then you have that beater box to get stupid with. Drive the sum biotch right into that kernal panic at 100mph just for fun.
So therapeutic some days......
Mac and a half a dozen server homelab. Plex was a homelab test thatβs now βprodβ (family wonβt let me shut it off) so itβs in the prod environment outside of my homelab
My Mac is supposed to be the safe box too. I keep having to talk myself down from installing Asahi.
A good excuse to get another cheap box to crash and burn!
Fastest I ever got a kernel panic was ~50mph. There are photos.
I like Niri a lot. Plus the maintainer isn't an asshole.
That's why sway and river exist. They're actually stable.
Sway still struggling with screensharing (specifically window sharing) tho or atleast it was last time I yried it in february :(
Havenβt heard of them before tbh, from the replies Sway not be super stable. And river?
I have my (edit: RIVER) config for over a year and it's very reliable. It never broke on me apart from the misconfigurations which were my fault.
It also integrates well with Waybar and is compatible with other Wayland tools for wlroots.
But keep in mind that my config is relatively minimal.
my linux honeymoon has far gone. nowadays I just use fedora gnome and actually work on something that makes money.
No shame in that. I love sway/i3 because it force me to keep my screen tidy, but you are right that it takes time to get a decent config file.
Not everything has to be a poweruser wet dream and most Linux distro allows you to do 95% of the stuff you need through the GUI, so more power to you to customize your experience.
That would be true if the GUI worked correctly.
However, more often than not, some inner thing breaks, which means that the GUI just throws an error screen and tells you "good luck". So you have to search for that text in Google, and it will send you to an obscure forum where a guy said in 2014 that the solution for that problem is to run some random command in the terminal.
For example the "app store" GUI for Kubuntu never worked for me. It always stalls at some point or another. Meanwhile, running sudo apt upgrade worked flawlessly. Both operations should be doing the exact same thing under the hood.
Two times already, a relative that uses Manjaro but has no idea about Linux came to me for help because the "app store GUI" (which is a different one than in KDE) one day stopped working. The issue was to run some random key-relayed command.
Years later, I found out that apparently the Manjaro maintainers let their certificates expire MORE THAN ONCE. Which has to be fixed manually by the end user apparently. And they apparently didn't think of adding a notification in the GUI telling you about this. Which is bonkers. Not everyone reads all the news articles relating to their OS.
That would be true if the GUI worked correctly.
The GUI works correctly for the vast majority of the time.
And MacOS and Windows also have GUI bugs, but we are so used to using these OSes that we know the workarounds.
The difference with Linux is that depending on your desktop environment, you will have to learn a new workflow. On Windows and MacOS, you one desktop environment and that's it.
However, more often than not, some inner thing breaks, which means that the GUI just throws an error screen and tells you "good luck". So you have to search for that text in Google, and it will send you to an obscure forum where a guy said in 2014 that the solution for that problem is to run some random command in the terminal.
Happens with Windows too where you get an error code and then you have to registry entries to fix a bug. Again, same kind of issues with a different workflow.
For example the "app store" GUI for Kubuntu never worked for me. It always stalls at some point or another. Meanwhile, running
sudo apt upgradeworked flawlessly. Both operations should be doing the exact same thing under the hood
I've had lots of issues with Windows store where a software wouldn't install correctly and I had no way to install what I needed to. At least, with Linux, you have multiple way to install a software. The app store is just a GUI over the package manager.
Two times already, a relative that uses Manjaro but has no idea about Linux came to me for help because the "app store GUI" (which is a different one than in KDE) one day stopped working. The issue was to run some random key-relayed command.
I do the IT for work (small company, 4 employees) and the number of time I had to un-break something in Windows for no apparent reason is high. Bugs happen in any OS. Linux is no different.
Years later, I found out that apparently the Manjaro maintainers let their certificates expire MORE THAN ONCE. Which has to be fixed manually by the end user apparently. And they apparently didn't think of adding a notification in the GUI telling you about this. Which is bonkers. Not everyone reads all the news articles relating to their OS.
That's dumb and I agree with you, but that's not a Linux issue though, that's a Manjaro maintainers issue.
Most issues are a maintainers issue. Rarely is the issue in Linux itself. Most of the issues are in userland.
Yes. All OS have bugs, and yes, we are used to doing workarounds for windows too. But most of the time, that workaround is fishing for a setting in an obscure menu with a Windows7 UI. But it is still a GUI. If you read the labels of the buttons you can navigate the menus to reach the button you want to press.
I have never ever had to edit the registry to fix an issue. I have maybe edited the registry 10 times in my whole life, most of the time it was to customize beyond what the GUI offers, not to fix a bug. That's on my PC, I don't work in IT for a company. Maybe company management requires more extensive use of the registry.
The whole point of my comment is not that Linux breaks constantly while windows doesn't. Of course it's going to break more often, since there is an uncountable different Linux configurations, it's incredibly more complex than having 2-3 versions of windows to maintain.
The point is that you can fix most issues on windows with the GUI, while on Linux you have to use the terminal most of the times.
We also know those windows workarounds because GUIs are way more discoverable than terminal commands.
GUIs act like trees. If you don't care about the "personalization" branch of the menus, you just don't click on it.
Terminals act like lists. You do ls /usr/bin you'll just get shown hundreds of binaries. Which are not categorized in any way. Only when you know which binary solves your issue you can read the man and get something that hopefully resembles a tree, with headings of different levels.
I have never ever had to edit the registry to fix an issue. I have maybe edited the registry 10 times in my whole life, most of the time it was to customize beyond what the GUI offers, not to fix a bug. That's on my PC, I don't work in IT for a company. Maybe company management requires more extensive use of the registry.
I have edited the registry a lot when I last used Windows when I used it last a few years ago, and even had to do it for the other employees while maintaining their PC.
The whole point of my comment is not that Linux breaks constantly while windows doesn't. Of course it's going to break more often, since there is an uncountable different Linux configurations, it's incredibly more complex than having 2-3 versions of windows to maintain.
The point is that you can fix most issues on windows with the GUI, while on Linux you have to use the terminal most of the times.
And you can do the same with the GUI on Linux. However, since the GUI is mostly just a wrapper around Linux CLI cmds, it's a lot faster to fix issues from the terminal.
Linux was used mostly by power users a few years ago, and they tend to use the CLI a lot more. Thus the knowledge they have and share is the one they know, the CLI. Hell, when I have to use Windows, I will use thr CLI unless I absolutely have to use the GUI.
And that's the knowledge that is usually shared because regardless of which distro/desktop environment you use, the CLI is consistent across the distro.
But Linux has come a long way and many issues can be corrected through the GUI
top 93 comments