I know just the audience for this

[email protected]

Having it concat the string may bypass some of the safeguards as it's only looking at parts of the fork.

String Concatenation in Bash [6 Methods] - LinuxSimply

Explore the article to learn the methods of bash string concatenation and enhance the script flexibility and functionality efficiently.

LinuxSimply (linuxsimply.com)

[email protected]

Why would it be running with sudo perms?

[email protected]

Is this considered chaotic neutral

[email protected]

Magic, thank you.

[email protected]

So it doesn't run into permission errors

[email protected]

The fact that some of you don’t get this is satire is what’s really funny.

[email protected]

Skynet's existence is contingent on the Terminator movies remaining profitable, so Dark Fate's performance might have averted Judgment Day.

lurch (he/him)

Sounds like reddit was part of the training data

[email protected]

Yeah, that's what I meant with folders.

I'm sure you could make it more general by traversing through /usr/libs and back.

lurch (he/him)

when you're in a chroot and you want to wipe only that whole part. you can't format the chroot, because it's just a subtree of the filesystem you want to keep.

[email protected]

How does this work? I tried to cd with … in bash and it doesn’t seem to work. And what would be the point of the single dots in there?

[email protected]

I’m going to start doing this on all posts

[email protected]

This will be the next SQL injection from the PHP days when they can’t bind parameters.

[email protected]

Ok I was thinking of a chroot env as being the only possible use case for this command.

[email protected]

/./ would apply to the current directory, and /../ would move into the parent directory. I imagine the idea is to start in a deeply nested directory, /home/user/Documents/old and begin either maintaining the directory (in a sense doing something like '–0' or reverting to a more basal directory (alla '–1'). The branch moving into ~/Music/badSongs is probably a way of trying to disguise the intent of parsing /.././.././.././.. to root and then /* to glob all root directories.

I imagine if for some reason ChatGPT was running Zsh or something that supports that kind of augmented Bash syntax it would work, but realistically it likely would fail.

I think someone might have better luck by attempting to rm - rf --no-preserve-root with a series of random, less-necessary files and throw a /* in the mix. Or attack another important directory that might get overlooked like /proc/*

[email protected]

They just pushed some weird stuff. But .. in /, will still be /, so as long as you do enough .. per directory, you'll end up there.

[email protected]

"I am sorry you're going through a hard time, but I'm sorry I cannot blow my brains out"

[email protected]

GPT was super useful for me getting into programming with very basic, core shit that it basically couldn't get wrong. But now that I'm learning how to actually program in C it is practically useless. It makes so many mistakes so often

[email protected]

Better to just use rm -rf ~/*. No need for sudo to destroy the most valuable data (the user's own files).

zkfcfbzr

Just noting that I gave it a shot. It ran the code with no errors or anything. Nothing really happened that was visible on my end though. The only iffy thing was that one of its replies a few messages later stopped generating half-way through - but otherwise it seems normal, and all of its replies since then were also fine.