*BSD News Article 80931


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!news.cc.nctu.edu.tw!spring.edu.tw!howland.erols.net!EU.net!news2.EUnet.fr!newsbr.eunet.fr!usenet
From: fgm@osinet.fr (Frederic MARAND)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: dummy question
Date: Wed, 16 Oct 1996 21:41:01 GMT
Organization: Groupe SEDI / Agorus SA / OSI SARL /
Lines: 20
Message-ID: <543o1d$pe0@newsbr.eunet.fr>
References: <53mfdu$1iv@wa4phy.async.com>
NNTP-Posting-Host: 193.107.196.155
X-Newsreader: Forte Free Agent 1.0.82

sam@wa4phy.async.com (S.W. Drinkard) wrote:


>Ok, I'm not exactly a newbie, but I created a file with a filename of
>"--remove-files" due to a blunder of the fingers.  SysV would let me 
>remove it in quotes, or by matching a wildcard patern.  I tried every
>combination of rm/mv/whatever short of the 45-cal pistol.  How does 
>*bsd do it?
Apart from the obvious rm ./--file  some mentioned, and which should
work, a solution existed on SunOS 4, and that was using the
little-known command unlink, which passes its argument(s ?) straight
to an unlink() syscall. That worked, and if *BSD has it too, it should
work too.

By the way, the symetrical link command allowed a (super)user to
create links to anything, including cyclic graphs in the file system
tree that fsck could not remove, and so on. Does it also exist on *BSD
?