Obligatory XKCD
need to be more creative with aliasing than “ls”
… but
cdis a built-in-1 accuracy point ( ◞ ﹏ ◟)
linux 4.5-rc5 had efivarfs fixed to prevent “rm -rf /” bricking uefi motherboards – so maybe someone can try it out? :]
This is one of the reasons I’ve disabled uefi by default with the
noefikernel parameter, the other reason being the LogoFAIL exploit: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Disable_UEFI_variable_access
It would be pretty useless if cd was a child process that changed its own directory, only to return to bash and be back where you started.
No problem, just tab complete your way around the filesystem.
What filesystem?
deleted by creator
I am immune to /dev/sda for I only have nvme
I love the nvme partition naming. Looking at you nvme1n1p3
/dev/nvme1s²2s²2p⁶3s²3p⁶4s²3d¹⁰4p²
deleted by creator
Eh? Idk if I agree. My original comment was entirely a joke based on the fact that the literal argument of=/dev/sda has no affect on my system but to address your actual point. I personally don’t find nvme naming any more confusing than SCSI. /dev/nvme0n1 is only one char away from /dev/nvme1n1 just like sda vs sdb. Additionally if you understand how the kernel comes up with those names they make a lot of sense. The first number is the controller, the second is the namespace or drive attached to that controller, the 3rd if present is the partition on the given drive. It is entirely possible to have a controller with more than one namespace. That aside aside…I think there is a genuine benefit to be argued for having USB drives, which are SCSI and fall into sdX naming separate from system drives as I dd far more USB media than system media. Making it a lot harder to screw my system up when trying to poke a flash drive.
That might make it even more dangerous, because you get used to flash to usb sticks on “/dev/sda”. And when you then use a device with a built-in sata drive, you might forget checking in a hurry.
Happened to me a once or twice. I am now only using bmap tools for this.
echo $PATHAnd
aliasto be sure.bash: echo: command not foundbash: alias: command not foundechoandaliasare both shell commands. If the shell is running (which it obviously still is), those commands should still work, as it does not involve reading data from disk, but from memory.Edit: I just noticed the picture said
cdwas not found, which is also a shell built-in. So, I don’t know.Why would somebody lie on the internet?
Just tested it in a container. The original screenshot is wrong:
(╯°□°）╯︵ ┻━┻
Switch your calculator with a computer. Try again.
deleted by creator
Empty
$PATH.You should all just use an immutable distro. Problemo solved-o.
/s
This isn’t programming, just someone who sucks at bash.
How else are you going to open your files in nano to do the programming on the prod server?
what’s a nano?
The beginner (and better) version of vim?
