Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!nic.MR.NET!eta!com50!mscunx!hawkmoon!det
From: det@hawkmoon.MN.ORG (Derek E. Terveer)
Newsgroups: comp.unix.xenix
Subject: Re: Weird File Names (Removing them)
Message-ID: <828@hawkmoon.MN.ORG>
Date: 26 Feb 89 10:53:43 GMT
References: <91@raider.MFEE.TN.US> <281@swusrgrp.UUCP> <167@usource.UUCP>
Organization: One of the Eternal Champions - Richfield, MN, 554232523, USA
Lines: 26

In article <167@usource.UUCP>, frankb@usource.UUCP (Frank Bicknell) writes:
> Safer would be:
>
>  		find . -inum inode -exec rm -i {} \;
>
> or use a fix program which does this only to the file in the
> current filesystem (where _is_ that source code?).

The newer OS equivalents for this command that is restricted to a single fs
would be:

		/* bsd -- don't cross(X) over to another device(DEV)
		 */

		find . -xdev -inum inode -exec rm {} \;

		/* sysv -- stay on own mounted fs
		 */

		find . -mount -inum inode -exec rm {} \;

-- 
Derek Terveer 	    det@hawkmoon.MN.ORG || ..!uunet!rosevax!elric!hawkmoon!det
		    w(612)681-6986   h(612)688-0667

"A proper king is crowned" -- Thomas B. Costain