From owner-freebsd-hackers@FreeBSD.ORG Thu May 5 11:53:49 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FAAE16A4D3 for ; Thu, 5 May 2005 11:53:49 +0000 (GMT) Received: from smtp2.dnainternet.net (smtp2.dnainternet.net [62.240.72.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEEFA43D3F for ; Thu, 5 May 2005 11:53:48 +0000 (GMT) (envelope-from erik.u@dnainternet.net) Received: from b-184-46.dsl.kpy.customers.dnainternet.fi ([212.149.184.46]:59923smtp2.dnainternet.net with ESMTP id S1228777AbVEELxs (ORCPT ); Thu, 5 May 2005 14:53:48 +0300 Message-ID: <427A094B.8040009@dnainternet.net> Date: Thu, 05 May 2005 14:53:47 +0300 From: Erik Udo User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050430) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <427A014D.6020809@dnainternet.net> <20050505114206.GA86050@freebie.xs4all.nl> <59863.192.168.1.20.1115293567.squirrel@webmail.thilelli.net> In-Reply-To: <59863.192.168.1.20.1115293567.squirrel@webmail.thilelli.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: req: New feature to rm? Remove file by the inode number X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 11:53:49 -0000 Julien Gabel wrote: >>>I couldn't find a way to remove files that had scandic/non-printable >>>letters, then i remembered ls showed inode number of the file. Is it >>>possible to remove the file by the inode number? It would be a >>>useful feature :) >>> >>>I bet there is a way to remove those files, but only >>>third party programs came to my mind. > > > I think the -inum option of the find(1) utility can do the trick. > After trying clri, maybe find(1) is a better way :). I can imagine what would happen when i would use clri on wrong slice :)