home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!mimsy!afterlife!adm!amsaa-cleo!hagadorn
- From: hagadorn@amsaa-cleo.brl.mil (Thomas Hagadorn)
- Newsgroups: comp.unix.misc
- Subject: Re: Giles' (Manual) Mania (getting longuish)
- Message-ID: <8934@amsaa-cleo.brl.mil>
- Date: 10 Sep 92 19:31:39 GMT
- References: <1992Sep8.183712.18867@newshost.lanl.gov> <7269@charon.cwi.nl> <1992Sep9.192946.27394@newshost.lanl.gov>
- Organization: Army Materiel Systems Analysis Activity
- Lines: 28
-
- In article <1992Sep9.192946.27394@newshost.lanl.gov> jlg@cochiti.lanl.gov (Jim Giles) writes:
- >
- >Can you explain why I can't even write (even if I want to) a remote
- >`ls' command which lists files on a remote machine but which is
- >compatible with `ls': I can't say
- >
- > rls machine-id a*
- >
- >to find all files in my home directory on the remote machine whose
- >names begin with `a'. *THIS* would be consistent, but the UNIX
- >environment won't even *let* me do it. Why? They *CLAIM* it's for
- >consistency!! But, since that obviously *wasn't* a constraint in
- >the rest of the environment (and this is counter to consistency
- >anyway), this excuse is not valid.
-
- I must be missing something on this one. If your complaint is that you
- need to quote the file list to keep it from being expanded before the
- rsh on machine-id get the command line arguments, then with csh you can
- get around this with an alias. For example:
-
- alias rls 'set noglob; rsh \!:1 ls \!:2* ; unset noglob'
-
- rls machine-id a* will now give the same results as if one rlogin'd to
- machine-id and did ls a*. Please clarify if your complaint meant to
- imply something different.
-
- regards,
- Tom H.
-