grep unable to cope with paths starting with root but missing drive letter

[Lewis Rosenthal]

Grepping seems to fail when the path begins with "/" or "\":

[j:\]grep enabled \etc\yum\repos.d\*
grep.exe: \etc\yum\repos.d\*: No such file or directory

However:

[j:\]grep enabled j:\etc\yum\repos.d\*
j:\etc\yum\repos.d\netlabs-exp-2rosenthals.repo:enabled=0
j:\etc\yum\repos.d\netlabs-exp.repo:enabled=0
j:\etc\yum\repos.d\netlabs-rel-2rosenthals.repo:enabled=0
j:\etc\yum\repos.d\netlabs-rel.repo:enabled=0

works, as well as relative paths.

FYI: grep-2.10-2.oc00.i386

[Silvan Scherrer]

fixed in r1697

[Lewis Rosenthal]

Sorry, but grep-2.25-1.oc00.pentium4 still produces the same complaint and the same results (when adding the drive letter). Tested with and without slashes. Did not test i686, however.

[Silvan Scherrer]

do you have a pathrewriter rule for /etc enabled? As then it doesn't work. As /etc if first redirected to the rewriting part and then searched for files. Which most likely doesn't work.

[Lewis Rosenthal]

You are exactly right, my friend, and I do not know why I didn't think of that before.

Testing against my Mozilla profile directory, without a drive letter specified but logged onto the same volume, grep works as expected, now, as do things like:

[c:\]grep VIRTUAL /config.sys
REM VIRTUALADDRESSLIMIT=1536
REM VIRTUALADDRESSLIMIT=1802
VIRTUALADDRESSLIMIT=2048
REM VIRTUALADDRESSLIMIT=2304

Thanks for the reminder.