1768
|
1
|
|
2
|
|
3 profile profile
|
|
4
|
|
5
|
|
6 FILE
|
|
7
|
|
8 /DD/SYS/profile
|
|
9 ./<homedir>/<user>/profile
|
|
10
|
|
11 SUMMARY:
|
|
12
|
|
13 Pseudo-environment variables file for the CoCo.
|
|
14
|
|
15 DESCRIPTION:
|
|
16
|
|
17
|
|
18 Since OS-9 Level 2 on the CoCo does not yet have true environment
|
|
19 variables, UUCPbb attempts to emulates them. The file 'profile'
|
|
20 contains the system and user's environment variables.
|
|
21
|
|
22 The file /DD/SYS/profile contains the system default values.
|
|
23 Each user can also set some of the environment variables by
|
|
24 creating a file 'profile' in their root home (login) directory.
|
|
25
|
|
26 If the user's profile exists, it will override the system
|
|
27 profile. If it doesn't the system defaults are used.
|
|
28
|
|
29 The file consists of one declaration per line with the format:
|
|
30
|
|
31 variable=value
|
|
32
|
|
33 There can be no space between on either '='. At present, the UUCP
|
|
34 package only supports the variables: TERM, HOME, MAIL, SHELL, and
|
|
35 EDITOR. For example:
|
|
36
|
|
37 TERM=coco3
|
|
38 HOME=/dd/usr
|
|
39 MAIL=/h1/spool/mail
|
|
40 EDITOR=ved
|
|
41 SHELL=shell+
|
|
42
|
|
43 In the case of SHELL, the value 'shell+' is suggested when
|
|
44 referring to Shell+ v2.1 or later; while 'shell' refers to the
|
|
45 original Microware Shell. Programs will have to internally figure
|
|
46 how to make use of the shell environment if the system uses both
|
|
47 Shell+ and the MW Shell or another shell.
|
|
48
|
|
49 The user is allowed only to change the variables TERM, EDITOR and
|
|
50 SHELL in their profile. The variables HOME and MAIL are reserved
|
|
51 only for /DD/SYS/profile. If they appear in the user's profile,
|
|
52 they are ignored. If HOME is not defined in the system profile,
|
|
53 getenv() will use the password to try and determine the HOME
|
|
54 environment of the user.
|
|
55
|
|
56
|
|
57
|
|
58
|
|
59
|
|
60
|
|
61
|
|
62
|
|
63
|
|
64
|
|
65
|
|
66
|