From owner-freebsd-questions@FreeBSD.ORG Fri Nov 19 14:09:15 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B89116A4CE for ; Fri, 19 Nov 2004 14:09:15 +0000 (GMT) Received: from helium.webpack.hosteurope.de (helium.webpack.hosteurope.de [217.115.142.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7AF743D1D for ; Fri, 19 Nov 2004 14:09:14 +0000 (GMT) (envelope-from me@hexren.net) Received: by helium.webpack.hosteurope.de running Exim 4.34 using asmtp helo=hexren.steenbuck.net) id 1CV9Rp-0003Xn-9g; Fri, 19 Nov 2004 15:09:13 +0100 Date: Fri, 19 Nov 2004 15:09:12 +0100 From: Hexren X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <18815024894.20041119150912@hexren.net> To: Andy Firman In-Reply-To: <20041119133443.GA23820@akroteq.com> References: <20041119133443.GA23820@akroteq.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: can't get rid of this file with trailing backslash? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hexren List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 14:09:15 -0000 AF> I was editing my named.conf and somehow saved the file AF> with a trailing backslash and I can't get rid of it. AF> -rw-r--r-- 1 root bind 18314 Nov 18 11:35 named.conf AF> -rw-r--r-- 1 root bind 18314 Nov 18 11:07 named.conf.save.11-18 AF> -rw-r--r-- 1 root bind 17389 Nov 18 10:58 named.conf\ AF> -rw-r--r-- 1 bind bind 2602 May 25 17:28 named.root AF> I was using nano and have no clue how I did it. AF> If I rm named.conf\ it removes the named.conf. AF> So how do I get rid of named.conf\ ? AF> Andy --------------------------------------------- only shooting in the blue here but have you tried rm 'named.conf\' so as to instruct the sheel to ignore any special chars it sees. Or rm named.conf\\ (I seem to recall that you the backslash is the escape sequenze for the bash so escaping a backslash should lead to a literal backslash. *guessing* Hexren