Date: Sat, 31 Mar 2007 15:00:45 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-questions@freebsd.org Subject: Re: deleting file '--preserve-permissions' Message-ID: <460EE81D.3080009@u.washington.edu> In-Reply-To: <460EE543.5080104@u.washington.edu> References: <1794.212.25.54.147.1175369763.squirrel@mail.uni-svishtov.bg> <6.0.0.22.2.20070331151239.02578380@mail.computinginnovations.com> <460EE543.5080104@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: > Derek Ragona wrote: >> try: >> rm -i * >> >> only answer y to the one you want deleted. >> >> -Derek >> >> >> At 02:36 PM 3/31/2007, lalev@uni-svishtov.bg wrote: >>> I've made mistake with tar. Something like >>> >>> tar cvfz --preserve-permissions home.tgz * >>> >>> or >>> >>> tar cvfz --preserve-permissions * home.tgz >>> >>> As result I have a file with name '--preserve-permissions'. >>> It seems that it's not easy to delete this file. >>> >>> rm '--preserve-permissions' >>> >>> does not give the desired result. >>> What should I do :-) > rm -- '--perserve-permissions'. -- tells getopt to stop searching and > the single quotes are a double bonus because it doesn't interpret the > string contents beforehand, but instead passes it on as a straight > string. > > Try: rm "--perserve-permissions" and rm '--perserve-permissions', in > that order to just see what happens ;).. > > -Garrett Haha. Forgot that the single quotes version won't work by itself. It's basically for cases when there are shell sensitive characters inside a string, when compared to the double quotes. The first solution with -- will work though, guaranteed :). -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?460EE81D.3080009>