Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!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: UN*X/DOS
Message-ID: <2685@mibte.UUCP>
Date: 8 Sep 88 12:06:43 GMT
References: <18509@neabbs.UUCP> <24516@bu-cs.BU.EDU> <31930@clyde.ATT.COM> <23064@wlbr.EATON.COM>
Organization: Michigan Bell Telephone Company
Lines: 30

In article <23064@wlbr.EATON.COM>, pete@wlbr.EATON.COM (Pete Lyall) writes:
> In article <2684@mibte.UUCP> jnj@mibte.UUCP (Jim Jackson) writes:
> -- 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
> -				
> 
> Eh? Someone slip a 'dir' command into Unix while I wasn't looking, or
> did your system administrator inadvertantly set up an alias between
> 'dir' and some flavor of 'ls'?
> 
> Pete
> 
> -- 
	You're right.  Seems this command was a local command that just
contains "ls -xFb $*".  But my point is still valid, 'type' exists on both
systems and yet have completely different uses.  Just be careful when trying
to improve either system by combining your favorite commands from the other.

				Jim Jackson