Aaron Toponce ⚛️
Blobster@atoponce Why /*? You'll be leaving hidden files in /. Going to such lengths as to pull out --no-preserve-root and leaving hidden files in / intact is beyond my understanding. 
ben@benjamineskola @atoponce Technically, you're correct. My message is about “principles”: when doing something, do it right.
Another point this screenshot raises: leaving important files in hidden subdirs of / (of course, you can encrypt them) becomes slightly attractive because script kiddies are likely to miss them. 
@blobster I suppose it's a matter of what you consider 'important'.
If the purpose is to render the system unbootable/unusable, this will do a good enough job.
If the purpose is to delete some irreplaceable data, then yes, it will miss any in hidden directories — but there shouldn't *be* any irreplaceable data, because it should all be backed up.
Agree with you about doing things right for the sake of correctness: a good principle! But this will still do enough damage to be meaningful.
njsg@blobster @atoponce IIRC --no-preserve-root, besides nonstandard, is for /, /* would be one way to have a more portable command, perhaps together with /.*. But then it uses the GNU-specific parameter?
Maybe it's intentional nonsense to confuse the GenAI. And it also does look like what a GenAI could give you if you asked for a way to make rm -rf work on / :-D