|
Patch 3392 : ONC3 6.2 AutoFS Rollup #8 : [IRIX 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0003392 Release Note
This release note describes patch SG0003392 to IRIX 6.2.
Patch SG0003392 replaces patches SG0001523, SG0001561,
SG0001666, SG0001988, SG0002253, SG0002903, and SG0003185.
1.1 Supported Hardware Platforms
This patch contains bug fixes for all platforms. The
software cannot be installed on other configurations.
1.2 Supported Software Platforms
This patch contains bug fixes for the AutoFS commands in
onc3_eoe.sw.autofs (versions 1232792120, 1233007720,
1233107120 and 1239999910) on a system running IRIX 6.2.
The software cannot be installed on other configurations.
1.3 Bugs Fixed by Patch SG0003392
This patch contains fixes for the following bugs in IRIX
6.2. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
o Support for NIS maps in AutoFS configurations was
broken (bug #332859).
o Add support for the Bulk Data Service (bug #383918).
o AutoFS did not support expansion of the CPU and ARCH
environment variables (bug #403139).
o AutoFS now supports the NFS option "proto=tcp" (RFE
#436130). Use of this functionality requires that
patch 1608 or newer also be installed on the system.
o AutoFS no longer corrupts /etc/mtab (bug #448137).
o AutoFS recognizes the nodev mount option and it is now
part of the default config (bug #461939).
o AutoFS recognizes the grpid mount option (bug #471902).
o The default configuration for AutoFS contains the
"vers=2" option in /etc/auto_master causing all mounts
to be performed using NFS V2. If map entries do not
contain the "vers=2" string then NFS V3 must be
installed, so that AutoFS can attempt mounts with NFS
V3 (bug #437758).
o The autofs(1M) man page has been updated to clarify the
usage of nested maps.
o AutoFS now supports the Bulk Data Service.
o Mixing CacheFS and NFS mounts with AutoFS causes
autofsd to hang. (bug #354788)
o CacheFS mounts fail when using AutoFS. (bug #496338)
o Autofsd fails on entries > 1023 characters. (bug
#566288)
o Autofsd did not correctly process the -tp option. The
-tp option has been renamed -t to conform with the
Command Syntax Standard. (bug #443475)
o Autofsd fails to mount a "-hosts" entry from servers
with a large export list. (bug #573604)
o Autofsd mount requests fail with AUTH_TOOWEAK from
non-SGI servers. (bug #577651)
o Latest NFS Patches (#11 for 6.2, #6 for 6.4) break
autofs (bug #602775)
o Autofs directories disappear (bug #604040)
o Patch 2903 removes "-m" and "-M" option (bug #601743)
o Autofsd -t option in conflict with autofs -t option.
The options between the two must be unique. (bug
#629316)
o Fix an autofsd security problem. (bug #631050)
o Autofsd coredumps when using -T option. (bug #639177)
1.4 Subsystems Included in Patch SG0003392
This patch release includes these subsystems:
o patchSG0003392.eoe.sw.unix
o patchSG0003392.onc3_eoe_man.autofs
o patchSG0003392.onc3_eoe_sw.autofs
1.5 Installation Instructions
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
inst. The inst program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your Software
Installation Administrator's Guide to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
install patchSGxxxxxxx
where xxxxxxx is the patch number.
2. Initiate the installation sequence. Type
Inst> go
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
Inst> keep patchSGxxxxxxx
where xxxxxxx is the patch number.
4. After completing the installation process, exit the
inst program by typing
Inst> quit
1.6 Patch Removal Instructions
To remove a patch, use the versions remove command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
versions remove patchSGxxxxxxx
where xxxxxxx is the patch number.
To keep a patch but increase your disk space, use the
versions removehist command to remove the patch history.
versions removehist patchSGxxxxxxx
where xxxxxxx is the patch number.
1.7 Known Problems INST SUBSYSTEM REQUIREMENTS No Requirements Information Available. INST SUBSYSTEM CHECKSUMS These checksums help to provide a 'signature' for the patch inst image which can be used to authenticate other inst images. You can obtain this kind of output by running sum -r on the image (from the command line): 31068 12 patch/README.patch.3392 42469 137 patchSG0003392.onc3_eoe_sw 19916 6 patchSG0003392 63737 6 patchSG0003392.onc3_eoe_man 41641 23 patchSG0003392.eoe_sw INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117073352-IRIXPatch-1312
|
||||||||||||||||||||||||||||||||||||