Date: Wed, 26 Sep 2007 18:38:38 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-stable@freebsd.org Subject: Re: rm(1) bug, possibly serious Message-ID: <46FA991E.4090303@dial.pipex.com> In-Reply-To: <20070926171503.GC3062@dan.emsphone.com> References: <54db43990709251838q68bdba95iefefb43029761c34@mail.gmail.com> <200709261447.l8QElua3058752@lurza.secnetix.de> <20070926171503.GC3062@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote: >In the last episode (Sep 26), Oliver Fromme said: > > >>Bob Johnson wrote: >> >> > Maybe. But I expect that the behavior for "rm -rf .." is there so >> > that things don't get REALLY astonishing when you do "rm -rf *". >> >>The expansion of "*" does not include "." or "..". >> >> > >Under /bin/sh, ".*" does match "." and "..", so be careful :) > > > .??* is a standard workaround that works most of the time. Won't match .a .b etc but such antisocial files are the exception, one might hope. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FA991E.4090303>