fl42v

@fl42v@lemmy.ml

This profile is from a federated server and may be incomplete. Browse more on the original instance.

What's (are) the funniest/stupidest way(s) you've broken your linux setup?

Tinkering is all fun and games, until it’s 4 am, your vision is blurry, and thinking straight becomes a non-option, or perhaps you just get overly confident, type something and press enter before considering the consequences of the command you’re about to execute… And then all you have is a kernel panic and one thought...

fl42v,

That’s an interesting way to distro hop for sure

fl42v,

Been there, and even without encryption: took me to reinstall a few times before I realized I can chroot again and repair 😅

fl42v,

Nah, that’s when the fun really starts! ;)

Well, on the upside, it definitely works better than coffee or energy drinks :D

Also, nice save with the last one!

fl42v, (edited )

Daaem, I guess the poor dude at the receiving end did not consider it particularly fun. Well, at least they had sbin working, so probably possible to recover without a live cd. Huh, guess who’s now spinning up a VM to check it out 🤣

Checked it out: on arch that results in inability to run tty on reboot, then you’re dropped into initramfs’s rescue shell where you can simply +x new_root’s /usr/bin/* and be back up and running

fl42v,

Oh, I just remembered another one or three. So, resizing the partitions. My install at the time had a swap partition that I didn’t need anymore. Should be simple, right? Remove the partition and the corresponding fstab entry, resize root, profit. Well, the superblock disagreed. Fortunately, I was lucky enough to be able to re-create the scheme as it was, and then take my time to read the wiki and do the procedure properly (e2fsck, resize2fs and all that stuff).

Some people I’ve met since, unfortunately, weren’t so lucky (as far as I remember, both tried to shrink and were past mkfs already) and had to reinstall. The moral is, one does simply mess with superblocks; read the wiki first!

fl42v,

Yeah, a very unfortunate one: probably, the most painful to recover from. I’d just reinstall, honesty 😅 At least with mine I could simply add the necessary stuff from chroot or pacstrap and not spend a metric ton of time tracking all the files with incorrect permissions

fl42v,

You can dump the permissions from the working system and restore them. Quite useful when working with archives that don’t support those attributes or when you run random stuff from the web 😁

fl42v,

Been there with sudo. Fortunately, su still works, as well as going to another tty and logging in as root. Well, as long as the root login is enabled; otherwise that old hack with init=/bin/bash may work, unless you’ve prohibited editing kernel cmdline in the boitloader or decided on efistub

fl42v,

You mean you’ve removed the service partitions used by windows and grown the main one into the freed space? Than yes, it’s not the way. 'Cause creating a new partition instead of growing the existing one shouldn’t have touched the latter at all :/

fl42v,

I mean, it’s simple, elegant, and destructive AF given the right circumstances. Basically a chaos grenade we didn’t realize existed

fl42v, (edited )

This has to be illegal. I mean, it’s basically suicide incitement (or whatever is the phrase for it)

This guy has a good take on linux companies, agree or disagree? (www.youtube.com)

Kent right here talks about how Linux related companies need to focus on putting their resources towards collaborating and helping big companies port their software and THEN introduce open source software to new users instead of remaking desktop environments, pushing companies away, and overall doing the same thing over and...

fl42v,

Meh, idk tf he says he understands. Like “make [ported adobe CC] popos-exclusive”: sure, big brain, how’s that supposed to work, exactly? Or “there are 3 desktops ppl GAF about”: riiiight, me along with other wm users aren’t ppl anymore, apparently.

The whole video pretty much boils down to “I don’t need X, hence nobody [«meaning the vast majority of ppl»] needs x”. By the same logic, the “vast majority” doesn’t need CC either, it’s mostly necessary for professional designers, etc 🤷

I mean it’s probably possible to choose the windows route and go “we make one steaming pile of garbage that kinda works everyone but perfectly - for nobody”, yet linux distros so far have been pro-choice and pro-customization. You want “just works”? Sure, go with X, Y, and Z distros. Wanna something specifically tailored for your workflow? You may start with the same and replace/modify stuff, but also I, J, and K are a great base to build your future setup from the ground up and avoid banging your head against the wall while figuring out what drugs their devs were on. And the same goes for DEs/WMs: gnome is, gnome also works, yet if you want to change it significantly, you’ll either have to mess with extensions or maintain a fork of a huge codebase you don’t fully understand and most of which you don’t exactly need. So, building from scratch may just be an easier solution.

Technically, you can also PR, yet it can easily be rejected, and then you’re back to forks.

fl42v,

Well, technically, you can kill both your dog and your children. With some consequences, that is. Humans are generally considered more valuable than dogs, hence the consequences are more severe.

Anyways, that’s f-d up.

fl42v,

As a former arch user, I advocate for both XD

fl42v,

I can only argue with metal body here: that’d vary on model-to-model basis. I’ve had a few thinkpads made of plastic, and they’re fine after a few drops here and there, and hinges are alive and well, also I’ve seen some (mostly new-ish) laptops made of literal aluminum foil that are bent AF; what’s even worse, one wasn’t even what they call unibody, i.e. the frame was sandwiched of aluminum shell and a piece of crappy plastic with heat inserts for screws → after like a year of normal usage those inserts literally broke off with the surrounding plastic.

The latter one was some ultrabook by HP. Namedropping here 'cause I have some personal issues with their products, so, frankly speaking, fuck them in particular :)

fl42v,

Wsl2? It’s a VM. As for wsl1… Not sure, mb smth wine-ish.

fl42v,

Yeah, I believe that won’t work. The tape is supposed to be blue

fl42v,

Not necessarily, I guess. They’re talking about a firmware upgrade of sorts, and, at least on the machines I own(ed), performing it didn’t reset user settings (which disabling the logo is)

fl42v,

More like reflashing entirely or just changing the image. Alternatively, you can often disable showing the.logo somewhere in the settings.

What’s known as resetting bios is more like removing the stuff saved in CMOS, AFAIK

fl42v,

Unless they find another way to escalate privileges… A bug, a random binary with suid, etc

fl42v, (edited )

Except when your drive is encrypted you can easily destroy its contents. Let’s say you’re DorkPirate1337 who happens to care about their opsec; you luksEncrypt your drive and have a simple script that runs when a specific USB key is disconnected, triggers luksErase, and then poweroffs. Voila, when the school principal snatches your unlocked laptop while you’re in the lib, all your pirated hentai becomes permanently unaccessible whether you give up the password or not. [Edit: the USB key is strapped to your wrist]

Note: luks uses 2 encryption keys, where one is randomly generated and encrypts the actual data, and the second one is given by the user and encrypts the first one; luksErase destroys the luks header containing that first key

fl42v, (edited )

Why declare a war over it? Just sudo sed -i ‘s/%wheel/$(whoami)/’ /etc/sudoers or smth like that

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #