Re: "rm" bug

[Paulo Nogueira]

  Hi,

I apologize for not sending the full error report;
what I get is the following (on a machine running
RedHat 9.0, not some prehistoric system):

$  \rm a b*
rm: No match.
$  \rm -f a b*
rm: No match.

OK, I got the right answer when I switched to "bash";
the wrong answer occurs in "tcsh", which is my usual
shell.

So, it seems it is a shell problem after all.
 I'll try sending the report to address@hidden

Kind regards


>      there seems to be a weird bug with the "rm" command, at least
>      with "rm (coreutils) 4.5.3".
>
> This is an quite old version of, the latest stable is 5.0.
>
>      Just try the following commands,
>
>         rm -i  a b*
>
>         rm -f  a b*
>
>     in a test directory containing a file named "a" and no file with a
>     name starting with "b".
>
> I don't know what the bug is supposed to be.  -f ignores non-existant
> files, so it doesn't print anything if some file doesn't exist.
> $ touch a
> $ rm -i a b*
> rm: remove empty file `a'? y
> rm: cannot lstat `b*': No such file or directory
> $ touch a
> $ rm -f a b*
> $