Now wonder, which one is will be preferred by people who aren't tech savvy.
linuxmemes
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now. Β
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 fork-bomb your computer.
I never deleted my root system with rm but I did dd go sda instead of sdb and ended up losing my data.
I like the windows delete philosophy of asking me before I delete something.
I fucking hate the windows delete philosophy of telling me I don't have access after I said yes.
I'm this close to daily driving as Sadmin
Every time I see I've of these memes my mind goes straight to infomercials.
gio trash
This works for those of us in GNOME and GNOME-derived places.
Seems like KDE doesn't have anything quite so simple. A quick web search suggests the correct command is kioclientN move filename trash:/
where N is the version number of kioclient. Very verbose. Worthy of a shell alias
.
Then there's stuff like bashtrash. Or just write a small function, without full XDG compliance and all the edge cases.
One drive has a trash for the trash. Iβm still not convinced those files are gone after the 2nd empty, I think they just donβt show the other trash cans
It's trash cans all the way down.
The cloud is just someone else's trash can
You know what they say, one man's trash...
Is another ones treature
Is another's CLOUD βοΈπ€
backups / btrfs snapshots
Btrfs snapshots/subvolumes can now also be deleted with rm. It's no longer necessary to use 'btrfs subvolume delete'
If you're going for cli, windows also can do rm -r -Force
-confirm:$false
Or just do Shift Delete in Explorer.
You can do that?
Yes. Place finger on key and press lightly downward. ;)
Use the --force Luke
the linux-file-deletion is used as a example for good software design. It has a very simple interface with little room for error while doing exactly what the caller intended.
In John Ousterhout's "software design philosophy" a chapter is called "define errors out of existence". In windows "delete" is defined as "the file is gone from the HDD". So it must wait for all processes to release that file. In Linux "unlink" is defined as "the file can't be accessed anymore". So the file is gone from the filesystem immediately and existing file-handles from other processes will life on.
The trade-off here is: "more errors for the caller of delete" vs "more errors due to filehandles to dead files". And as it turns out, the former creates issues for both developers and for users, while the later creates virtually no errors in practice.
Yes, the file itself (so the data and inode) is not gone as long as the handles live on. Only the reference is gone. You canstill recover the file. https://superuser.com/questions/283102/how-to-recover-deleted-file-if-it-is-still-opened-by-some-process#600743
doing exactly what the caller intended.
No, no. Exactly what the user told it to do. Not what they intended. There's a difference.
Machines will always do what you tell them to do, as long as you do what they say.
do what they say
Exactly type rm -rf /
instead of rm -rf ./
and you ducked up. Well you messed up a long time ago by having privileges to delete everything, but then again, you are human, some mistakes will be made.
Don't modern versions of rm block calling on / unless you pass a separate flag?
Deleting the current directory via ./
seems contrived since you would just use .
or more likely the directory name from outside the directory. What does happen is rm -rf ${FOO}/
while ${FOO}
is an empty string.
Not sure if you're referencing the Steam incident, but Steam did exactly that: https://www.theregister.com/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/
yup, did that one on a server at work. had to go cap in hand to my manager to get him to fix it
Even so, .
and /
are right next to each other so it's a likely typo. You might press enter before you catch it.
Left side: I regularly go bowling with the demon core
Right side: I have read the demon coreβs wiki 314 times
The windows shell has really gone downhill in recent years, with spontaneous file locks and random hangs
It's always the AV...