HP t1000 T1500/T1510 Windows-based Terminal Network Installation Guide - Page 35

The version of NFS provided with Red Hat Linux 5.2, must be met

Get HP t1000 - Terminal Thin Client PC PDF manuals and user guides View all HP t1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

Configuring Terminal Start-Up Resources 21 The following four requirements are mandatory and must be met in the NFS configuration: Note IMPORTANT! If these requirements are not met, the terminals will not work in a network-boot environment. 1. The client root account map must be able to access the server root account (on Linux, this is called no_root_squash, and on SCO Openserver 5.05, set the NFS option to -anon=0). This is because the terminal executes certain software that (within the terminal environment) must be run as root, even when a user is logged in to the terminal. In UNIX, this is accomplished by making the programs set the superuser ID (suid) to root. If the NFS server remaps the ID to something other than root, the programs will run, but not as a root user. 2. The file system must support symbolic links. 3. The file system support must allow set-user ID programs to be stored (several Windows NT NFS implementations do not support this). 4. The file system must provide read/write access to the clients. Note The version of NFS provided with Red Hat Linux 5.2 has an inconsistency with versions in earlier releases. Normally, entries in the /etc/exports file should be of the form: /nwt/root (no_root_squash) For release Red Hat Linux 5.2, the default was changed from read/write to read-only, so the entry needs to be changed to: /nwt/root\ (rw,no_root_sqash,no_all_squash) for the system to behave correctly. Earlier and later versions of the NFS support will work properly with or without the explicit rw option.

  • 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
Configuring Terminal Start-Up Resources
21
The following four requirements are
mandatory
and
must be met
in the NFS
configuration:
Note
IMPORTANT
! If these requirements are not met, the
terminals will not work in a network-boot environment.
1.
The client root account map must be able to access the server root account (on
Linux, this is called
no_root_squash
, and on SCO Openserver 5.05, set the
NFS option to
-anon=0
). This is because the terminal executes certain
software that (within the terminal environment)
must
be run as root, even when
a user is logged in to the terminal. In UNIX, this is accomplished by making the
programs set the superuser ID (
suid
) to root. If the NFS server remaps the ID
to something other than root, the programs will run, but not as a root user.
2.
The file system must support symbolic links.
3.
The file system support must allow set-user ID programs to be stored (several
Windows NT NFS implementations do not support this).
4.
The file system must provide read/write access to the clients.
Note
The version of NFS provided with Red Hat Linux 5.2
has an inconsistency with versions in earlier releases.
Normally, entries in the
/etc/exports
file should be
of the form:
/nwt/root (no_root_squash)
For release Red Hat Linux 5.2, the default was
changed from read/write to read-only, so the entry
needs to be changed to:
/nwt/root\
(rw,no_root_sqash,no_all_squash)
for the system to behave correctly. Earlier and later
versions of the NFS support will work properly with or
without the explicit
rw
option.