Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!bellcore!faline!thumper!ulysses!gamma!mibte!jnj
From: jnj@mibte.UUCP (Jim Jackson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: More John Dvorak comments
Summary: UNIX dir command
Message-ID: <2684@mibte.UUCP>
Date: 6 Sep 88 16:34:59 GMT
References: <18509@neabbs.UUCP> <24516@bu-cs.BU.EDU> <31930@clyde.ATT.COM> <1185@plx.UUCP>
Organization: Michigan Bell Telephone Company
Lines: 14

> Why write script files? Seems to me that most *IX commands can be
> mapped nearly 1:1 with DOS (e.g. ls:dir, cp:copy). Simply create a 
> link to perform the mapping. To link a dir command to ls, for instance,
> simply become su and give the command "ln /usr/bin/ls /usr/bin/dir".
> From then on, typing "dir *" will list the current directory (sorted,
> even!),. the advantage of this approach is that no extra disk space
> is used for a script (though I *think* one inode may be used).
> 
	Be careful of which command names you use.  In the previous case
you would lose the use of the UN*X 'dir' command.

					Jim Jackson
					Michigan Bell