>> > This is the best thing to try first - although I have seen some things
>> > that even this won't work on.
>> >
>> > Chris
>>
>> Such as what?
>
>WHOA!
>
>This is my chnace to present my most stupid mistake:
>
>[EMAIL PROTECTED]:/tmp# cat /dev/null > -i
>[EMAIL PROTECTED]:/tmp# rm -i
>rm: too
On 26 Apr 1998, Ben Pfaff wrote:
>This works for any filename which the kernel can recognize (that is,
>any filename except one with a '/' in it. If you have one of THOSE,
>good luck.
>
> Hint: `debugfs'. (If you do have one with a /.)
is there a FAQ which has all these various sol
This works for any filename which the kernel can recognize (that is,
any filename except one with a '/' in it. If you have one of THOSE,
good luck.
Hint: `debugfs'. (If you do have one with a /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
int main()
{
unlink("-i");
}
This works for any filename which the kernel can recognize (that is,
any filename except one with a '/' in it. If you have one of THOSE,
good luck.
Carl
--
[EMAIL PROTECTED]
The sun's not eternal
That's why there's the blu
[EMAIL PROTECTED]:/tmp# cat /dev/null > -i
[EMAIL PROTECTED]:/tmp# rm -i
rm: too few arguments
Try `rm --help' for more information.
[...]
It took me some time to deal with it. There is a trick. I'll leave it as an
exercise to the reader. Hint: It is possible with rm. ;)
rm -- -i
On Sun, Apr 26, 1998 at 11:40:01PM +0200, Marcus Brinkmann wrote:
> On Sun, Apr 26, 1998 at 11:44:55PM +0800, The Thought Assassin wrote:
> > On Sun, 26 Apr 1998, Chris wrote:
> > > On Sun, 26 Apr 1998, The Thought Assassin wrote:
> > > > the backslash is the shell's delimiting character, and the s
On Sun, Apr 26, 1998 at 11:44:55PM +0800, The Thought Assassin wrote:
> On Sun, 26 Apr 1998, Chris wrote:
> > On Sun, 26 Apr 1998, The Thought Assassin wrote:
> > > the backslash is the shell's delimiting character, and the shell will not
> > > try to expand anything directly after a backslash.
> >
On Sun, 26 Apr 1998, The Thought Assassin wrote:
> On Sun, 26 Apr 1998, Chris wrote:
> > On Sun, 26 Apr 1998, The Thought Assassin wrote:
> > > the backslash is the shell's delimiting character, and the shell will not
> > > try to expand anything directly after a backslash.
> > This is the best
On Sun, 26 Apr 1998, Chris wrote:
> On Sun, 26 Apr 1998, The Thought Assassin wrote:
> > the backslash is the shell's delimiting character, and the shell will not
> > try to expand anything directly after a backslash.
> This is the best thing to try first - although I have seen some things
> that e
-BEGIN PGP SIGNED MESSAGE-
On Sun, 26 Apr 1998, Thomas J. Malloy wrote:
> I was moving a file and intended to type " mv thefile.tar.gz ~/ " so
> that it would be moved to my home directory, but by mistake I typed
> " mv thefile.tar.gz /~ ". Now I have a 800k file named
On Sun, 26 Apr 1998, The Thought Assassin wrote:
> On Sun, 26 Apr 1998, Thomas J. Malloy wrote:
> > " mv thefile.tar.gz /~ ". Now I have a 800k file named ~ on / . I
> > tried to "mv ~ normalfilename" and this does create a normal file, but
> > the ~ file still exists. If I try to "rm
On Sun, 26 Apr 1998, Thomas J. Malloy wrote:
> " mv thefile.tar.gz /~ ". Now I have a 800k file named ~ on / . I
> tried to "mv ~ normalfilename" and this does create a normal file, but
> the ~ file still exists. If I try to "rm ~ " the system thinks I want
> to delete my home director
Most of these silly character files (and we have ALL done it) can be
dealt w/ using "./". This causes it to not be looked at. so rm ./~
says look in . and remove the file ~. No expansion performed. I used
this technique to test this e-mail. Try `touch ./~`, then `rm ./~`.
Works like a champ.
13 matches
Mail list logo
