Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site bu-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!bu-cs!root
From: root@bu-cs.UUCP (Barry Shein)
Newsgroups: net.eunice
Subject: Re: preventing case translation
Message-ID: <248@bu-cs.UUCP>
Date: Sat, 16-Mar-85 18:15:46 EST
Article-I.D.: bu-cs.248
Posted: Sat Mar 16 18:15:46 1985
Date-Received: Sun, 17-Mar-85 23:42:44 EST
References: <436@nbs-amrf.UUCP> <t4test.1359> <624@oddjob.UChicago.UUCP>, <212@lth.UUCP>
Organization: Boston Univ Comp. Sci.
Lines: 26


'ls *.o' or anything like that involving wild-cards is not
likely to ever work correctly from DCL. Remember that
the wildcard expansions are done by the SHELL in unix,
not the individual programs. In UNIX or EUNICE what 'ls'
really sees as a result of that command is quite literally:

	'ls a.o b.o c.o etc.'

Try (from EUNICE/UNIX) for example: 'ls "*.o"' (double quotes
as shown) and I think you will see what I mean [*.o: No such file or Directory]

	-Barry Shein, Boston University

P.S. It doesn't mean it *couldn't* be made to work, just that it won't
as you show it. A more plausible form would be:

	sh -c "ls *.o"

which would invoke the shell on the command and hence take care of
the wildcards. If you can run sh or csh from VMS than you could probably
write a satisfactory, simple DCL command file to take your commands
and produce that, how about:

	$ unix ls *.o
anyone? As I said, I dunno if you can get 'sh' started from VMS.