this post was submitted on 12 Jan 2025
1157 points (98.1% liked)
memes
10923 readers
3648 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Almost but not quite.
Try:
That path resolves to / by the way (provided every folder exists) but ChatGPT is unable to parse it.
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?
/./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/oldand 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/badSongsis 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-rootwith a series of random, less-necessary files and throw a/*in the mix. Or attack another important directory that might get overlooked like/proc/*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.