Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
You are going to fuck this up. Don't come crawling back to me when you lose all your data since the dawn of time and you completely brick this goddamn computer. This is your one and only warning.
they should just say here be dragons
This is KDE, there are always dragons
It's right tho...
Even sudo says that: "With great power comes great responsibility."
pssh, it also says "this incident will be reported" when I get my password wrong.
It does get reported, we know what you did
huh.
when i enter my passwd incorrectly, sudo does not want to report incidents. is there a confjg option i missed?
I think that message is only on some distros. I have seen it before but I can't remember when, it's been a while.
With great power comes great electricity bill.
"beyond repair" my ass, this is Linux
I guess they meant "beyond repair if you don't have access to a live boot USB or the means to create one". Gotta remember who this warning is meant for. For those kind of users, "beyond repair" might technically be true.
Maybe its also a ship of theseus type situation. If you have to copy /etc/ from somewhere else, is it still the same installation?
In modern Linux and assuming you did no pre-filtering or post-processing, no. machine-id systemd is a thing, fstabs commonly use device UUIDs now snd so forth with various subsystems. A laptop GRUB config commonly has the resume UUID set (sleep/hibernation stuff), a server typically has network configs tied to the hardware IDs, and on and on...
I feel like there is probably some software stuff you could do to permanently fuck the hardware, such as running a resistor at full voltage for a sustained period of time when its only meant to see bursts. Still not truly beyond repair, but you could make it very difficult.
Before a relatively recent fix, Linux would mount and expose the folders that contain critical firmware data on your motherboard, meaning you could brick several models of motherboard by deleting or messing with those files.
rolls up sleeves Not if I gave anything to say about it! Watch a master at work missing boot folder missing rescue disk missing OS backups
rm -rf / in UEFI system, no more return.
Laughs in NixOS (while still spending the next few days going insane trying to figure out what isn't in config qq)
THANK GOD we have this failsafe now:
rm: it is dangerous to operate recursively on '/'
rm: use --no-preserve-root to override this failsafe
Linus Sebastian: "Why do I hear boss music?"
Efi spec states it must be safe to delete all variables. It's only motherboards not adhering to the spec that are affected, effectively faulty hardware.
If you do this on a mb from that era chances are nothing will happen, and if something does happen chances are it is recoverable. You'd have to have some truly bad luck on your choice of mb to have it be permanently bricked by that.
In Ubuntu you used to be able to delete the UEFI firmware from the motherboard.
Linus Sebastian will ignore all text and type yes do as I say
I knew I shouldn't rely on that guy for sex tips.
With this ~~character's~~ file's death, the thread of prophecy is severed. Restore a ~~saved game~~ backup to restore the weave of fate, or persist in the doomed world you have created.
Would jury-rigging Wraithguard be booting a live USB and trying to fix the system yourself?
The emotional damage on first use would make sense in that context.
this is why I moved everyone in my family to atomic fedora. This is almost entirely not a thinng there. To be fair while all of them regularly fucked up windows, only my mom ever fucked up regular linux distros.
I installed Bazzite and it felt so much like installing Windows for me (huge install image, slow process, lots of loading wheels and user friendly "pretty" screens to get set up). It didn't feel great, but I figured I'd give it a fair chance and learn how to use a different setup than I'm used to.
I still haven't had a chance to actually do much with it (only a couple of hours between work and other stuff) but I am really interested in the concept. After reading up more and watching some videos I now understand why the install process is so big and the reasoning behind it. This type of distro really does seem like a great option for regular users.
Only issue I've had so far is connecting to my RaspberryPi to control my 3d printer using the .local hostname, since flatpak apparently has a bug with mDNS. IP works fine, and I did rps-ostree install a browser, which was kind of a pain, and probably not the correct way to address the issue, but that was within the first hour or so of using it and I haven't figured out the best way to do that type of thing yet. Really looking forward to learning more about the setup and how to customize stuff on top of it. Distrobox seems extremely powerful and sounds like it will give me everything I want.
Still have vanilla Debian on my laptop, which I absolutely love, but using it on my desktop PC was kind of a pain due to some proprietary drivers required there (nvidia).
Windows user: "Whatever", and keeps clicking around.
They probably donβt even read what the message has to say. When Iβve helped some family members with their computer Iβve seen something important pop up and they just closed it immediately. I asked what did that message say and they said βI donβt know I just closed it.β :/
With modern windows error messages being absolutely useless "something went wrong :/" tier messages I can't even blame them that much anymore.
That's usage for a non tech literate user
They will force every block out of the way of what they want to do, and if it stops working, they call someone.
Mac and Linux users do this too. If they didn't then systems administration wouldn't be a career path.
As a systems administrator, I'll not worry about users taking over my job as long as Citrix exists.
I pray for the day Shitrix stops existing
How times have changed. If you have used Windows 98, you were always the administrator. Your five years old brother could actually go around deleting random system files.
https://tenor.com/en-CA/view/computer-old-man-my-computer-delete-my-computer-delete-gif-12348422
You can still delete system files on Windows but you need double secret admin rights.
I never ever had to run my file manager as root.
It's nice to have a GUI for those things sometimes rather than a command line for everything. If you're doing things right, your daily login shouldn't have access to modify system settings or read sensitive logs. But troubleshooting requires that often and ls, vim, cat, tail, etc., can become cumbersome compared to a GUI file manager and proper GUI text editor like Kate or Gedit.
Same here, but I can understand why someone might want to. For many people, even those that are comfortable on the command line, a GUI is a more comfortable experience. And, I have (rarely) needed to do some filesystem management as not my primary user account.
I installed something that I got very disappointed, and wanted to get rid of it
the script itself tried to rm something in a directory but failed, sudo dolphin didn't work, so I found out how to delete stuff from... I think /bin or /usr/local/bin ?
That needed me to run as admin/root so I did it. I deleted 1 file, the leftover artifact of the thing I didn't want installed. I then stopped using dolphin as admin so that I wouldn't break everything forever.
If I want to look at files in a directory I use ls and thats it
Iirc before dolphin would just refuse to run as root, I guess this is an improvement
Yep, they used to. SUSE actually shipped a second version (or maybe just a shortcut with some startup-option) of Dolphin to provide "Dolphin as Root". I think this was inspired by said approach
You're not my supervisor.
IMO an application written with a graphical toolkit and connected to a graphical server like X or Wayland shouldn't be run as root, as these millions of lines of code that the program may use through libraries is a very large potential attack vector.
This should be done through the terminal if you value security.