Acorn Communicator Filestore Manager's Guide

More documents

Recommendations

Info

Logging on User identification (id) As far as FileStore is concerned, the people that use it are identified by their user identification when they log on. In this manual we abbreviate this to user id. Typically, each id owns a directory with the same name, contained within the root directory. The id used to log on tells FileStore which directory the user owns and thus which files they can use and change and where to put files they create. Thus, in the above example, the user EDP owns the directory named EDP and all that it contains. File ownership In general, users can use, change and delete any files that they own, but can only use files owned by someone else — they cannot change or delete them. (But see Security and access in Chapter 3.) Passwords When a user attempts to log on, FileStore checks for the user id they type in a file called the password file. This is a file created by FileStore but maintained by you that contains the user ids and passwords of all users that will be allowed to use FileStore. FileStore looks for the password file on its 'leftmost' disc. This is the hard disc, if one is being used, otherwise the disc in the lefthand drive if it is being used, otherwise the disc in the righthand drive. Mistaken password If the user id typed is not in the password file, users will receive the error message User not known. Try again. If the user id is in the password file but the user has not typed the password required to use that id, they will receive the error message wrong password. If the user id is in the password file and the user has typed the correct password, they will be logged on as that id. User directory FileStore will then look for the user directory corresponding to the id, again searching from the lefthand disc. If it finds the user directory, the user will be logged on to that disc with that as the current directory. If it doesn't find the correct user directory, the user will be left in the root directory ($) of the first disc searched. 6 2 THE FILESTORE MANAGER'S ROLE
The FileStore The FileStore manager should be responsible for regular tasks that govern the manager's role running and day-to-day use of FileStore. These tasks include starting up FileStore at the beginning of the day and shutting it down at the end, and also supervision and maintenance tasks such as managing disc space and sorting out operating problems. What follows is a brief description of these tasks, and suggestions for overcoming problems that might arise during the course of a typical working day. Security Once users start to put their work onto FileStore, security of information is likely to become an important issue. There are three main ways that you can maximise security: using passwords, restricting access to FileStore and taking regular copies of discs. Passwords and software access Once a person has successfully logged on as someone else, they have access to exactly the same facilities as the genuine user. If you wish to protect people's files from unwanted interference, it is essential that you make sure that users: — Use passwords. — Change their passwords regularly. —Use non-obvious passwords. — Don't tell others their passwords. — Don't leave a written record of their password lying about. The other main software security is by use of *ACCESS. When a user creates a file, other users will not be able to read or change it. However, the owner of the file may change this by using *ACCESS. For example, typing: *ACCESS text WR/WR would allow any user to read or alter the file named text. This is unlikely to cause any problems, unless users get into the habit of using *ACCESS indiscriminately. Physical access You should consider siting FileStore in a locked room, to prevent unauthorised access. 2 THE FILESTORE MANAGER'S ROLE 7
Page 1 and 2: Acorn Communicator Acorn= choice of
Page 3 and 4: Important: WARNING: THIS APPARATUS
Page 5 and 6: Appendix 1: INSTALLING FILESTORE 39
Page 7: 1 ABOUT THIS GUIDE Introduction Fil
Page 10 and 11: The 'root' directory In a simple sy
Page 14 and 15: `Insurance' The best 'insurance' ag
Page 16 and 17: that must be done while FileStore i
Page 18 and 19: Type: password! 4-i 1 (where passwo
Page 20 and 21: 5. This will return you to the main
Page 22 and 23: without letting FileStore know you
Page 24 and 25: If all the users are within shoutin
Page 26 and 27: and show the directory tree of the
Page 28 and 29: If you are copying a file: 4. Type
Page 30 and 31: To change your password: 1. Return
Page 32 and 33: 1. There should be three sets of ha
Page 34 and 35: (For example, if a user creates a f
Page 36 and 37: 3. Type: *DISCS This displays the t
Page 38 and 39: Examining discs To display a single
Page 40 and 41: Changing the FileStore has its own
Page 42 and 43: Changing the maximum number of user
Page 45 and 46: Appendix 1: INSTALLING FILESTORE Yo
Page 47 and 48: FileStore Discs The function of eac
Page 49 and 50: The function of each of these featu
Page 51 and 52: doing this now will help prevent pr
Page 53 and 54: 6. Log on as SYST. On your Communic
Page 55 and 56: 2. Open the access flap, then turn
Page 57 and 58: (This logs you on to FileStore in m
Page 59 and 60: 3. Turn FileStore on. 4. Select the
Page 61 and 62: 7. Log off by typing: *BYE Final st
Page 63:
If there are already printers on th
Page 66 and 67:
to 254, otherwise it should be set
Page 68 and 69:
Bad attribute A user has made a mis
Page 70 and 71:
FS error 29 Someone has managed to
Page 72 and 73:
One of the discs is badly corrupted
Page 74 and 75:
the *CAT command or NETMGR task's T
Page 76 and 77:
If you have more than one FileStore
Page 79 and 80:
Appendix 3: COMMAND SUMMARIES Some
Page 81:
Maintenance mode To use the mainten
Page 84 and 85:
log on the process of selecting a F
Page 86 and 87:
80 Appendix 5: ECONET SYSTEM RECORD
Page 89 and 90:
INDEX $.UTILS.SETT1ME 34 Backup —
Page 91 and 92:
Maintenance tasks 9-10 Role of mana
Page 96:
Acorn Computers Limited Fulbourn Ro
show all

Acorn Communicator Filestore Manager's Guide

Create successful ePaper yourself

Delete template?

Save as template?