Compaq T1500 - Windows-based Terminals - 72 MB RAM, Руководство по установке

Страница: 35 / 74

Configuring Terminal Start-Up Resources
21 21 21 21
The following four requirements are
mandatory and must be met must be met must be met must be met in the NFS
configuration:
Note Note Note Note
IMPORTANT
IMPORTANT IMPORTANT
IMPORTANT! If these requirements are not met, the
terminals will not work in a network-boot environment.
1. 1. 1. 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. 2. 2. 2. The file system must support symbolic links.
3.
3. 3.
3. The file system support must allow set-user ID programs to be stored (several
Windows NT NFS implementations do not support this).
4.
4. 4.
4. The file system must provide read/write access to the clients.
Note
Note Note
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.