| Line | Revision | Contents |
| 1 | 1 | =============================================================================== |
| 2 | FSP client version 0.0-h (pre-alpha) | |
| 3 | ------------------------------------------------------------------------------- | |
| 4 | ||
| 5 | This software is copyright 1992, 1993 Philip G. Richards, All | |
| 6 | Rights Reserved. Any copies that are made of this code MUST keep an | |
| 7 | unmodified copy of this notice within a file called README in the | |
| 8 | same directory as the source code. This is a PRE-ALPHA release -- | |
| 9 | I would prefer that the code does not get posted to Usenet, thank-you | |
| 10 | very much :-) | |
| 11 | ||
| 12 | THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY. | |
| 13 | ||
| 14 | The author will accept no responsibility for any use or misuse of the | |
| 15 | software, nor for any consequences produced by using it. In other | |
| 16 | words, if it deletes all your files, don't blame me -- by using | |
| 17 | it, you are accepting responsibility and liability. (It will not, | |
| 18 | however, intentionally delete them -- it will have been an error.) | |
| 19 | ||
| 20 | The author can be contacted (currently) as <pgr@prg.oxford.ac.uk>. | |
| 21 | ||
| 22 | =============================================================================== | |
| 23 | ||
| 24 | ************************************************************************** | |
| 25 | *** Note: I have written the *program* called `fsp' -- I have *** | |
| 26 | *** *not* written the entire FSP package. Questions about *** | |
| 27 | *** the server and the like should be sent to Wen-King Su *** | |
| 28 | *** <wen-king@vlsi.cs.caltech.edu> -- or the new maintainer of the *** | |
| 29 | *** code Joseph_Traub@seismo.soar.cs.cmu.edu. *** | |
| 30 | ************************************************************************** | |
| 31 | ||
| 32 | ||
| 33 | ---------------- What the client can do --------------------------------------- | |
| 34 | There is a help command; not a very good one, but it does tell you the | |
| 35 | commands. Type `help' to get a list of all commands; to get a brief | |
| 36 | description of a command, type `help name' (`name' being the command); | |
| 37 | to get brief help on all commands type `help all' (warning: there are | |
| 38 | 46 commands). | |
| 39 | ||
| 40 | See the manual page fsp(1) for a somewhat longer description... | |
| 41 | ||
| 42 | Note for versions since 0.0-g: the command `cat', `get', `du', and | |
| 43 | `tar' can all take a `-r' flag -- this causes the commands to process | |
| 44 | subdirectories as well as files. e.g., `du' will give the disk usage of | |
| 45 | the current directory; `du -r' will give the disk usage of the current | |
| 46 | directory and _all_ subdirectories (resursively). The `timeout' command | |
| 47 | causes communications to return an error code if the timeout occurs; | |
| 48 | this means that: | |
| 49 | ||
| 50 | timeout 30 | |
| 51 | pro | |
| 52 | iferror exit | |
| 53 | ||
| 54 | is a good way of determining whether a remote site is alive or not when | |
| 55 | writing scripts. The `ver' should only return an error if the timeout | |
| 56 | occurs -- however, pre-2.6.3 servers return version strings as an error | |
| 57 | which messes up that usage... | |
| 58 | ||
| 59 | Macro's are, for want of a better word, stupid. Until parameter | |
| 60 | variables are allowed, they can not do very much. Common ones (and | |
| 61 | user set up options) should be defined in the file ~/.fsprc (i.e., .fsprc | |
| 62 | in your home directory). This filename can be changed by setting the | |
| 63 | environment variable FSPRC. An example .fsprc is supplied in the file | |
| 64 | `fsprc' in this directory. | |
| 65 | ||
| 66 | It is also now possible to have commands like: | |
| 67 | ls -l | less | |
| 68 | Anything after the first `|' symbol is fed the output of the builtin | |
| 69 | command... | |
| 70 | ||
| 71 | rehash may need a little explanation -- when you do an ls, the directory | |
| 72 | information is fetched to the local end and stays there (thanks to | |
| 73 | the original authors stuff); if you want to check if anything has been | |
| 74 | updated since you did an ls of a directory, then you must rehash first. | |
| 75 | The client is now a bit more intelligent than it used to be (i.e., pre | |
| 76 | `d' release); it will automatically mark directories as out-of-date if | |
| 77 | it knows that it has modified them (e.g., by put, or mkdir or whatever). | |
| 78 | It's the wrong command name, but it brings back fond memories of csh... | |
| 79 | It may sound like a disadvantage -- in fact it is an enormous benefit | |
| 80 | having it work this way... *much* faster. | |
| 81 | ||
| 82 | All the commands which have a f<name> equivalent in the original | |
| 83 | distribution behave as before; well, pretty much. | |
| 84 | ||
| 85 | Oh, one last thing -- command lines can't have continuations...\ | |
| 86 | yet :-) | |
| 87 | ||
| 88 | ------------------------------------------------------------------------------- | |
| 89 | ||
| 90 | If you use it and like it, mail me. I need the encouragement :-) If you | |
| 91 | use it and don't like it, mail me. I need bringing back down to earth... | |
| 92 | ||
| 93 | Basically, even though it is pre-alpha, I would still like to know | |
| 94 | whether people like it or not... just don't complain too loud when it | |
| 95 | doesn't work right :-) | |
| 96 | ||
| 97 | enjoy, | |
| 98 | pihl <pgr@prg.oxford.ac.uk> |
Loggerhead is a web-based interface for Bazaar branches