× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks, Barbara - I guess this suppresses the expansion of wildcards, eh? I forgot about that in a Unix-style setting.

Vern

At 09:49 AM 12/15/2003 -0500, you wrote:
Vern Hamberg wrote:
>
> I don't know if this has happened to anyone else, but it was a little
> messy. Somehow we got a file in the root (/) of our system, named *.* -
> perhaps as the destination of some kind of copy command.
>
> Anyway, when clicking, in Ops Nav, on the "root" share we have, only that
> "file" showed up. Of course, if I did a WRKLNK '/*.*', all the files with a
> period somewhere in the name appeared, including this one.
>
> In QShell, ls ??? (for 3-character names) displayed this file, as well as
> the directories with 3-letter names, such as "tmp" and "usr", and their
> subtrees - fortunately there is not much in these right now.
>

In QSH, use the back-slash to escape the special characters.

> ls \*\.\*

*.*

$
> cat \*\.\*


abc

$
> rm \*\.\*


$
> ls \*\.\*
ls: 001-2113 Error found getting information for object *.*. No such
path or


directory.

$



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.