B-TR3E

No arguments, just downvotes… I almost suspect some participants do not even understand what might be wrong with “you are sudo”? I also bet you don’t have the right idea what the difference between effective UIDs might be depending if you’re using “su”, “su -i” , "su - " sudo or “sudo su”. The differences are not exactly subtile and I dare to say admins on unixoids who don’t know them are basically talking heads without an idea what they’re actually talking about.

Your terminal at boot. That would be TECTONIX or VT100 when your good old VAX has made a boo-boo once more? But I wouldn’t know where to fill any Chinese contact spray (“sudo su”, “Fu Manchu”…) in there. Or do you by any means mean your .bashrc? You know, before sucessfully shooting your own foot you’d need how to load and unlock.

OMG. There’s literally more ignorance and bullshit than words in that sentence. It is so wrong that not even the opposite is true. I hope that was sarcasm - in which case I draw my hat because it would be a true peace of art.
Before voting me down, be sure to

man environ

• and be sure you’ve understood at least what the environment variables do. If that is too hard for you, at least find out what the difference between a binary and a UID might be.

You’ve got to be a damn idiot jumping over his own shadow to get that done. How would you even do that? Running

chown -R root.root
```   over directories or mount points? Deleting files in /dev or /run and recreating them using "touch" without looking up ownerships before? I wrote "touch" because anyone proceeding to "mknod" would at least have read *some* man pages.  BTW, you'd need su for that rather than sudo.

This wouldn’t do anything. Sudo is white magick while su is the devil’s work, so they cancel out each other. I know, because I’ve read Harry Potter, seen “War Games” and am a social net Linux expert.

Some people think before they type. They also do not think mindlessly typing “sudo” before every fucking line in bash is a valid substitute for knowing what they do. Many of them have been doing so for decades on HPUX, Solaris, BSDs and IRIX on their own and other people’s/companies machines, not just on their single bedroom machine.

rm -rf is always right. No matter where. Supposed, of course, you are root.

No discussion. I am root! I am always right!

As a mint Enlightenment user I can only sneer at these plebes.

Technically, you’re still downloading it, even if your package manager does it for you. And, tbh, even on Debian stable it needs some user action (including a visit to Mozilla’s site) to get an actual version of Firefox and rolling upgrades installed instead of the LTS version.

Having a backup is not enough. Having an actual backup is better but still not enough. Having a tested recovery procedure is not trivial but usually is enough. I have not yet experienced the case when even that fails and I hope I never will.

I didn’t take it personally but installing core software packages from websites instead of using your distro’s package manager is the worst possible practice. Absolutely nothing that should be recommended publically without anyone with a clue protesting. I don’t really believe the “DKMS doesn’t work for any situation” argument either, tbh. Either there is a miodule matching your kernel, compiler and glibc then DKMS will just work or there isn’t. In the latter case you better believe in your distro’s maintainers’ descisions or you really know what you’re doing - and the fact that you’re overriding package management in a production environment tells me that you don’t. Better someone on the internets is telling you than your boss, believe me.

Yes, but the problem is that it’s not that hard to wipe your personal files incidentially. An operating system can be replaced easily without deleting your /home partition (you did create an extra /home partition, did you?) but your personal stuff not so much.
And that’s why there’s three things you should never forget:

• have a backup
• have an automated backup (or you’ll end up having no backup at all)
• have a tested way to restore from backup

Just argue against that fact, blame me of incompetence, know it all better, I’ll just laugh at you because you will as sure as the sun rises in the morning remember my words. Three times if you’re missing a single one of these three. Don’t ask why I am so definitely sure about that - let’s say it was a three step learning process…

You should know how dkms works or get a job that suits you better. That’s an amazing level of incompetence for someone in a professional position.

There’s no gambling envolved. You’re either smart enough to just boot from a live image (“smart” extending to “have a bootable image at hand or have a way to create one”) in which case it’s not gambling - or you’ve got not only a band hand but also no clue how to play it. In which case you shouldn’t have gambled in the first time.

Hehehe, that’s what I call the “Diving Bell Approach”. Either remote via serial console over IP or local when greeted by the dreaded

GRUB:>

prompt. Which means you really fucked up your boot sequence. Ususally happens with multi-disk machines and complex LVM/RAID setups. Which escalates the plain “fuck up” to “real fuck up” state. You’d better have a second machine or a printout of GRUB’s excessive documentation with the hard to find but essential parts highlighted. There are ways to find the partition to boot and even ways to “manually” boot the right kernel, initrd-image and get the latter to mount the right root partition - even if it’s on encrypted LVM, but be sure to have enough oxygen, keep your decompression times and have enough batteries for your flashlight…

Reboot from live image if you really need to.

[3] Wait for it to die for no good reason

No, that’s where they come from. Back in the good old days they used to end up in kettles stirred by members of primitive tribes wearing chef hats. Nowadays they are probably getting composted.

The word is “H E R E T I C”.

Right. Debian is the Roman Catholicism among the Linuces.