Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!lll-winken!sun-barr!rutgers!mit-eddie!media-lab.media.mit.edu!lenox
From: lenox@media-lab.media.mit.edu.MEDIA.MIT.EDU (Lenox H. Brassell)
Newsgroups: comp.os.os2.misc
Subject: Re: Does anyone have unix utilities for OS/2
Summary: "CD C:." is what bites you
Message-ID: <5775@media-lab.media.mit.edu.MEDIA.MIT.EDU>
Date: 2 May 91 16:59:04 GMT
References: <2589@umriscc.isc.umr.edu> <72009@microsoft.UUCP> <5774@media-lab.media.mit.edu.MEDIA.MIT.EDU>
Organization: MIT Media Lab, Cambridge, MA
Lines: 19

In article <5774@media-lab.media.mit.edu.MEDIA.MIT.EDU>, lenox@media-lab.media.mit.edu.MEDIA.MIT.EDU (Lenox H. Brassell) writes:
> 
> It isn't unreasonable to want to, say, copy a bunch of files to "the
> current directory on drive C:", but there's no easy way to do this
> using the MKS Korn Shell.
> 

I haven't bothered using the MKS Korn Shell for a long time, and my
memory failed me.  "cp *.c C:." actually does do "the right thing".
But when you ask the Korn Shell to "CD C:.", it puts you into the root
of drive "C".  This is not an unreasonable thing to want to do,
either.  This, despite the fact that the underlying operating system
kept track of what "the current directory on drive C:" really meant.

It was particularly, uhm, "interesting" to me that all of the Toolkit .EXE
utilities interpreted "C:." to mean what I wanted it to mean, but that
the Korn Shell had a different interpretation.

--Lenox [lenox@media-lab.mit.edu]