surprised you didn't suggest -exec rm -rf {} \; as an addon to the find....
Though, in the case of unusual issues, I tend to prefer going a bit deeper than most people, why not use the inode reference and delete it specifically by inode, though in this particular case, that should be drastically overkill.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I didn't suggest that because I don't see how it'd be any better than the original attempt - we've already established that rm -rf doesn't work if the directory contains some kind of self-reference. I'm not sure why the find came out with that output though, because it looks like it's reporting a lot of things that shouldn't be links.
I don't really know though, I'm just guessing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
surprised you didn't suggest -exec rm -rf {} \; as an addon to the find....
Though, in the case of unusual issues, I tend to prefer going a bit deeper than most people, why not use the inode reference and delete it specifically by inode, though in this particular case, that should be drastically overkill.
rm -rf ./.git should be sufficient.
I didn't suggest that because I don't see how it'd be any better than the original attempt - we've already established that
rm -rfdoesn't work if the directory contains some kind of self-reference. I'm not sure why thefindcame out with that output though, because it looks like it's reporting a lot of things that shouldn't be links.I don't really know though, I'm just guessing.