Date: Fri, 6 May 2005 12:11:10 -0700
Reply-To: "Terjeson, Mark (IM&R)" <Mterjeson@RUSSELL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Terjeson, Mark (IM&R)" <Mterjeson@RUSSELL.COM>
Subject: Re: Call System in UNIX
Content-Type: text/plain; charset="us-ascii"
Hi David and All,
Yep, #1 was me, and making the same initial troubleshooting inquiry.
I had to send a chuckle back to Michael that, even though I had to ask
for troubleshooting purposes, I too have an ll set up for myself... :o)
For those using unix and wondering what we are talking about regarding
aliases, normally ll is not a unix command, however users can make their
own in their Bourne/C/Korn shells in the startup file such as .cshrc or
.kshrc, etc. You can make them in a couple ways: 1) make your own
script
file and make sure it is in your path, 2) make your own executable and
make sure it is in your path, 3) check out the "alias" command, or 4)
add into your .kshrc (or other startup file depending on the shell you
have in use) the defining of a script function, such as:
ll()
{
echo "`pwd`:"
ls -ilsa $*
}
which, since it is in your shell environment, you do not need to worry
about having something found in your path, and it will be there until
you log off. The $* allows for the passing of additional flags or file
specs, etc., just as if you sent them to the ls command (which
eventually
it really is).
Hope this is helpful.
Mark Terjeson
Senior Programmer Analyst, IM&R
Russell Investment Group
Russell
Global Leaders in Multi-Manager Investing
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
David L. Cassell
Sent: Friday, May 06, 2005 10:50 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Call System in UNIX
Michael Raithel <michaelraithel@WESTAT.COM> wrote:
> Two persons responding to this thread have mused about the "ll"
(el-el)
> Unix command:
>
> > Are you sure your command ll shouldn't be ls?
>
> > [2] What is 'll' supposed to do? cat the files together?
>
> Though I don't believe that ll is in the "Official Unix Command
> Dictionary", I have found it to be a very common "alias" for the "ls
-l"
> command at Unix sites where I have worked. It is so common that I was
> miffed when we migrated to a Unix box here (some time ago) and it
> wouldn't work by default. I needed to actually do some work for a
> change and set up an alias, myself.
Yep, #2 was me. I was trying to suggest, in my usual subtle way (where
'subtle' is defined as 'less impact than a two-train collision') that
perhaps the poster was using his own alias and there was no way for
anyone to know exactly what *his* 'll' was likely to do. It might be
'ls -l', but it might not...
David
--
David Cassell, CSC
Cassell.David@epa.gov
Senior computing specialist
mathematical statistician