HP Visualize J5000 hp enterprise file system: planning and configuring hp DCE/ - Page 18

Compatibility Information and Installation, Requirements

Page 18 highlights

About HP DCE/9000 Enhanced DFS Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements This chapter describes the hardware, software, operating system, memory, and swap space requirements for HP DCE/9000 Enhanced DFS Version 3.0 on HP-UX 11.0. Enhanced DFS 3.0 Interoperability Enhanced DFS 3.0 clients and servers are completely interoperable with HP DCE/9000 Version 1.4x, 1.5.x, EFS 1.0, DFS 2.0, and 1.7 DFS clients and servers. Enhanced DFS 3.0 servers can "serve" HP DCE/9000 Version 1.4x and 1.7 DFS clients; conversely, HP DCE/9000 Version 1.4x and 1.7 DFS servers can serve Enhanced DFS 3.0 clients. NIS and Integrated Login Interoperability NIS, Integrated Login, and DCE/DFS should interoperate without any problems because they do not have any knowledge of one another. Both Integrated Login and NIS attempt to solve the problem of creating a common /etc/passwd and /etc/group file on multiple nodes. Integrated Login does this by using /opt/dce/bin/passwd_export to pull the contents of the DCE registry (basically the global /etc/passwd and /etc/group files) onto each node. NIS, on the other hand, gets the global /etc/passwd and /etc/group files through a hook in the getpwent() system call. DCE/DFS uses this functionality primarily to print a username and group when you perform an ls -l within DFS. The second function of Integrated Login, which NIS does not provide, is to obtain a user's DCE credentials when a user performs a standard UNIX login through telnet, ftp, CDE, and so on. If Integrated Login obtains the credentials successfully, the user accesses DFS in an authenticated manner, and without having to perform a dce_login. When DCE is not available, Integrated Login falls back to using the /etc/passwd file; upon successful login, the user does not have DCE credentials, gains unauthenticated access to DFS, and thus can only access entries with an any_other ACL entry. 18

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164

18
About HP DCE/9000 Enhanced DFS
Compatibility Information and Installation Requirements
Compatibility Information and Installation
Requirements
This chapter describes the hardware, software, operating system, memory,
and swap space requirements for HP DCE/9000 Enhanced DFS Version 3.0
on HP-UX 11.0.
Enhanced DFS 3.0 Interoperability
Enhanced DFS 3.0 clients and servers are completely interoperable with HP
DCE/9000 Version 1.4x, 1.5.x, EFS 1.0, DFS 2.0, and 1.7 DFS clients and
servers. Enhanced DFS 3.0 servers can "serve" HP DCE/9000 Version 1.4x
and 1.7 DFS clients; conversely, HP DCE/9000 Version 1.4x and 1.7 DFS
servers can serve Enhanced DFS 3.0 clients.
NIS and Integrated Login Interoperability
NIS, Integrated Login, and DCE/DFS should interoperate without any
problems because they do not have any knowledge of one another.
Both Integrated Login and NIS attempt to solve the problem of creating a
common
/etc/passwd
and
/etc/group
file on multiple nodes. Integrated
Login does this by using
/opt/dce/bin/passwd_export
to pull the contents of
the DCE registry (basically the
global /etc/passwd
and
/etc/group
files)
onto each node. NIS, on the other hand, gets the global
/etc/passwd
and
/etc/group
files through a hook in the
getpwent()
system call. DCE/DFS
uses this functionality primarily to print a username and group when you
perform an
ls -l
within DFS.
The second function of Integrated Login, which NIS does not provide, is to
obtain a user’s DCE credentials when a user performs a standard UNIX login
through
telnet
,
ftp
, CDE, and so on. If Integrated Login obtains the
credentials successfully, the user accesses DFS in an authenticated manner,
and without having to perform a
dce_login
. When DCE is not available,
Integrated Login falls back to using the
/etc/passwd
file; upon successful
login, the user does not have DCE credentials, gains unauthenticated access
to DFS, and thus can only access entries with an
any_other
ACL entry.