BIND 4.9.3 resolver support for SunOS 4.x compatible shared libraries ===================================================================== This directory contains the makefile and scripts necessary to install the new 4.9.3 resolver into your existing SunOS-4.x compatible libc.so shared library binary. These procedures have been tested on SunOS-4.1.1_U1 (sun-3), SunOS-4.1.4, NetBSD-1.0, and NetBSD-1.1. They are very likely to work on OpenBSD, and may work on FreeBSD-2.x. Since BSDI's BSD/386 1.1 does not support shared libraries, don't try this there, but you may have some luck with BSDI's BSD/386 2.x. You should read through this whole file, *and* the relevant INSTALL file, BEFORE BEGINNING. I mean it. I really mean it. The shared library is the second most important part of a functional operating system (right next in line to the kernel itself). If you screw it up you will be very very unhappy and so will your users. As always you should have regular backups of everything. WARNING: For SunOS-4.x see README.SunOS before beginning. [Disclaimer: THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.] NOTES about this new release: 1. makeshlib can now rebuild shared libraries for either SunOS-4.x or 4.4BSDs that use the SunOS-4.x shared libraries. 2. makeshlib determines the system type automatically by what 'uname' returns. Make sure that 'uname' is in your path. (This shouldn't be a problem since it's in /usr/bin on both systems) 3. If the script can't find your shared library object files or you haven't built libresolv_pic.a, it will exit immediately, instead of failing on later commands. 4. The shared libraries are rebuilt in the current directory (and temporary directories underneath it), instead of in SHLIBDIR. NetBSD and other 4.4bsd's use /usr/lib for SHLIBDIR, and rebuilding them under /usr/lib did not seem like the appropriate place for this operation. 5. You have the option (by setting USELORDER at the top of the script) to dynamically generate an lorder-sparc file using lorder on a SunOS machine. Using Sun's lorder-sparc file may arguably reduce the amount of paging of the shared library code, and doesn't take as long. On the other hand, since it is generated from the list of object files that are actually present, you don't have to worry too much about the file getting out of order somehow. NetBSD and other 4.4bsds will always dynamically generate this list, as this is the method it uses when the system shared libraries are built, so unsetting this variable on a NetBSD machine has no effect. 6. Larry Wall's patch program is no longer require to make the modifications to the lorder-sparc file under SunOS if you use it or to the Makefile in /usr/lib/shlib.etc. A sed script will modify the lorder-sparc file, and the Makefile is no longer used. #ident "@(#)bind/shres/netbsd:$Name: $:$Id: README,v 8.1 1995/12/22 21:57:03 vixie Exp $"
BIND 4.9.3 shared library resolver SunOS specific details
---------------------------------------------------------
First off you should ensure the "Shlib Custom" package has been properly
installed. It populates the directory /usr/lib/shlib.etc with files,
the most important of which are libc_pic.a and libcs5_pic.a.
Install the appropriate "jumbo libc patch" for your SunOS version, if
you haven't already. Among other things, this includes fixes for some
bugs in the shared library building process. This will also include the
shared library build directory (/usr/lib/shlib.etc), which is useful if
the "Shlib Custom" package was not already installed.
At the time of this writing, the patch numbers and latest revisions of
the "international" versions of these patches were:
4.1.3: 100891-12
4.1.3_U1: 101558-06
4.1.4: 102545-02
Note that "international" means "has not installed the extra-cost 'US
Encryption Kit'", so most sites, even in the US, will need these
versions. If you have installed the "US Encryption Kit" you will need
to get the domestic versions.
As "recommended" patches, these patches are available for anonymous ftp
to all Sun customers, even those without support contracts, from
sunsolve1.sun.com in the /pub/patches directory.
Note: apparently the 4.1.4 jumbo libc patch is not "recommended" and is
therefore only available with a support contract. That's the bad news.
The good news is that the README claims it only fixes two bugs, and one
of them is in gethostbyname()--which this installation process replaces.
The other fix has something to do with NFS over slower links. The
fixes, as described in the patch README are:
1190985 --> gethostbyname() can trash an existing open file descriptor.
1197137 --> NFS server crashed w/ "Panic: Bad Trap" when NFS client do a
"find" over T1 link
So, if you have support, it's probably a good idea to install the
patched libc first in any case.
SunOS-4.1.1 for sun3 doesn't have an explicit known libc patch, though
upgrading to 4.1.1_U1 does replace the shared libraries, and it's highly
recommended that you do this upgrade if at all possible.
#ident "@(#)bind/shres/netbsd:$Name: $:$Id: README.SunOS,v 8.1 1995/12/22 21:57:03 vixie Exp $"
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.