User Tools
luser
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| luser [2015-12-29 16:24] – [Directories and files] victor | luser [2016-03-05 16:42] (current) – [LOCK] victor | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== A Luser' | ====== A Luser' | ||
| + | < | ||
| Disclaimer: I write this as friendly advice to new users of ITS, and the term " | Disclaimer: I write this as friendly advice to new users of ITS, and the term " | ||
| + | </ | ||
| ===== ITS is an open system ===== | ===== ITS is an open system ===== | ||
| Line 26: | Line 26: | ||
| - | * Don't overwrite files in other directories than your own. If you do it anyway, please let someone know so they can perhaps do something about it. ({{emacs_init|Here}} is a piece of TECO for your EMACS init file to help against involuntary disasters.) | + | * Don't overwrite files in other directories than your own. If you do it anyway, please let someone know so they can perhaps do something about it. ([[emacs_init|Here]] is a piece of TECO for your EMACS init file to help against involuntary disasters.) |
| * Please try to shut the system down nicely if you have to, instead of crashing it (or its host system). This minimizes the risk of filesystem breakage. | * Please try to shut the system down nicely if you have to, instead of crashing it (or its host system). This minimizes the risk of filesystem breakage. | ||
| Line 41: | Line 41: | ||
| * < | * < | ||
| * The key marked < | * The key marked < | ||
| + | |||
| + | If your connection is lost and you connect again, your old job (set of processes) is probably still around. | ||
| + | * Sometimes ITS detects your disconnection, | ||
| + | * Sometimes ITS doesn' | ||
| + | |||
| ===== Some commands ===== | ===== Some commands ===== | ||
| Line 67: | Line 72: | ||
| :: lists the files in the default directory. Also try '': | :: lists the files in the default directory. Also try '': | ||
| - | + | More commands: | |
| - | * For a fun introduction to more commands, read [[hactrn|The HACTRN]] by Guy L. Steele. | + | * For a fun introduction to more commands, read [[http:// |
| * For a gentle introduction to more commands, read {{AI_WP_235.pdf|Getting Started Computing at the AI Lab}} especially chapter 6. | * For a gentle introduction to more commands, read {{AI_WP_235.pdf|Getting Started Computing at the AI Lab}} especially chapter 6. | ||
| * For a serious introduction to DDT/HACTRN, read the [[http:// | * For a serious introduction to DDT/HACTRN, read the [[http:// | ||
| - | * For historical information, | + | * For historical information, |
| ===== Directories and files ===== | ===== Directories and files ===== | ||
| Line 78: | Line 83: | ||
| File names have four components. Each can be up to six characters. | File names have four components. Each can be up to six characters. | ||
| - | * | + | * |
| - | * | + | * |
| * " | * " | ||
| - | * " | + | * " |
| Example: " | Example: " | ||
| Sometimes filenames are shown in another order, as DIR; DEV: FN1 FN2. | Sometimes filenames are shown in another order, as DIR; DEV: FN1 FN2. | ||
| About file versions: | About file versions: | ||
| - | * If you //write// a file FOO >, you create the next version of FOO. If FOO 41 exists, you create FOO 42. | + | * If you //write// a file '' |
| - | * If you //read// a file FOO >, you read the latest version (or largest version number). | + | * If you //read// a file '' |
| * The FN2 "<" | * The FN2 "<" | ||
| - | * So you may need to clean up once in a while, e.g. by using the H command in DIRED (in EMACS). | + | * So you may need to clean up once in a while, e.g. by using the <key>H</ |
| Line 99: | Line 104: | ||
| The program used for (among other things) shutting down the system cleanly. | The program used for (among other things) shutting down the system cleanly. | ||
| - | * Type :LOCK to start it, and it prompts you with _ (underscore). | + | * |
| - | * To schedule a shutdown, give the command nDOWN, where n is the number of minutes to wait (minimum 5). | + | * To schedule a shutdown, give the command |
| - | * You are now asked if you really want the system to go down. Answer y if you really do. | + | * You are now asked if you really want the system to go down. Answer |
| - | * You are then asked to enter a brief message to users, ended by ^C. Please do. | + | * You are then asked to enter a brief message to users, ended by <key>^C</ |
| The system will start shutting down when either the n minutes have passed, or all users have logged out. (Please do not quit KLH10 or shut down the host system until ITS has shut down completely, which is visible on its console or by observing the CPU usage of kn10-ks going up towards 100%.) | The system will start shutting down when either the n minutes have passed, or all users have logged out. (Please do not quit KLH10 or shut down the host system until ITS has shut down completely, which is visible on its console or by observing the CPU usage of kn10-ks going up towards 100%.) | ||
| Line 108: | Line 113: | ||
| To cancel a shutdown, use the REVIVE command of LOCK. | To cancel a shutdown, use the REVIVE command of LOCK. | ||
| - | From HUMOR; | + | ==== DSKUSE ==== |
| + | '': | ||
| + | shows how full your current directory is. | ||
| + | '': | ||
| + | shows how full the HACK; directory is. | ||
| + | |||
| + | ==== PRUFD ==== | ||
| + | '': | ||
| + | PRints the User File Directories, | ||
| + | ===== Footnotes ===== | ||
| + | |||
| + | ==== Lusers ==== | ||
| + | |||
| + | |||
| + | From '' | ||
| + | |||
| + | ?? LUSER | ||
| + | :: See USER. !! | ||
| + | ?? USER n. | ||
| + | :: A programmer who will believe anything you tell him. One who asks questions. Identified at MIT with " | ||
| + | |||
| + | [Note by GLS: I don't agree with RF's definition at all. Basically, there are two classes of people who work with a program: there are implementors (hackers) and users (losers). The users are looked down on by hackers to a mild degree because they don't understand the full ramifications of the system in all its glory. (A few users who do are known as real winners.) It is true that users ask questions (of necessity). Very often they are annoying or downright stupid.] | ||
| + | |||
| + | ==== Alice' | ||
| + | (See [[http:// | ||
| - | LUSER | + | You can hack anything you want, with TECO and DDT.\\ |
| - | See USER. | + | You can hack anything you want, with TECO and DDT.\\ |
| - | USER n. | + | $U in and begin to hack.\\ |
| - | A programmer who will believe | + | Twiddle bits in a core dump and write 'em back.\\ |
| - | [Note by GLS: I don't agree with RF's definition at all. Basically, there are two classes of people who work with a program: there are implementors (hackers) | + | You can hack anything you want, with TECO and DDT.\\ |
| + | (But be careful typing <RET>)\\ | ||
| + | With TECO and DDT! | ||
luser.1451402664.txt.gz · Last modified: by victor
Page Tools
