Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

postinstall(8) [netbsd man page]

POSTINSTALL(8)						    BSD System Manager's Manual 					    POSTINSTALL(8)

NAME
postinstall -- check and fix installation after system upgrades SYNOPSIS
postinstall [-a arch] [-d destdir] [-m machine] [-s {srcdir | tgzdir | tgzfile}] operation [item [...]] DESCRIPTION
The postinstall utility performs post-installation checks and/or fixes on a system's configuration files. It is especially useful after sys- tem upgrades, e.g. after updating from NetBSD 1.6.2 to NetBSD 2.0. The items to check or fix are divided in two groups: enabled by default and disabled by default. The latter are items that are dangerous for some reason, for example because they remove files which may be still in use. If no items are provided, the default checks or fixes are applied. Those which are disabled by default must be provided explicitly. Supported options: -a arch MACHINE_ARCH. Defaults to machine of the host operating system. -d destdir Destination directory to check. Defaults to /. -m machine MACHINE. Defaults to machine of the host operating system. -s {srcdir | tgzdir | tgzfile} The location of the reference files, or the NetBSD source files used to create the reference files. This may be speci- fied in one of three ways: -s srcdir The top level directory of the NetBSD source tree. By default this is /usr/src. -s tgzdir A directory in which reference files have been extracted from a binary distribution of NetBSD. The files that are distributed in the ``etc.tgz'' set file must be present. The files that are distributed in the ``xetc.tgz'' set file are optional. -s tgzfile The location of a set file (or ``tgz file'') such as ``etc.tgz'' or ``xetc.tgz'' from a binary distribu- tion of NetBSD. Each set file is a compressed archive containing reference files, which will be extracted to the temproot directory. Multiple -s options may be used to specify multiple set files. The ``etc.tgz'' set file must be specified. The ``xetc.tgz'' set file is optional. The operation argument may be one of: check Perform post-installation checks on items. diff [diff(1) options] Similar to check, but also show the differences between the files. fix Apply fixes that check determines need to be applied. Not all items can be automatically fixed by postinstall, and in some cases an error will be reported, after which manual intervention will be required. Conflicts between existing files in the target file system and new files from the NetBSD distribution are resolved by replac- ing the existing file with the new file; there is no attempt to merge the files. See etcupdate(8) for an alternative update method that is able to merge files. help Display a short help. list List available items, showing if they are enabled or disabled by default. usage Same as help. EXIT STATUS
The postinstall utility exits 0 on success, and >0 if an error occurs or a problem was found. SEE ALSO
etcupdate(8) HISTORY
The postinstall utility first appeared in NetBSD 1.6. In NetBSD 4.0, the -s tgzfile option was added. In NetBSD 5.0, the ability to specify multiple colon-separated files with a single -s option was deprecated. BSD
October 4, 2008 BSD

Check Out this Related Man Page

COMPAT_SUNOS(8) 					    BSD System Manager's Manual 					   COMPAT_SUNOS(8)

NAME
compat_sunos -- setup procedure for m68k, sparc and sparc64 architectures DESCRIPTION
NetBSD/sparc64, NetBSD/sparc and some of the NetBSD/m68k architectures can run SunOS executables. Most executables will work. The exceptions include programs that use the SunOS kvm library, and various system calls, ioctl()'s, or kernel semantics that are difficult to emulate. The number of reasons why a program might fail to work is (thankfully) longer than the number of programs that fail to run. Static executables will normally run without any extra setup. This procedure details the directories and files that must be set up to allow dynamically linked executables to work. The files you need are on your SunOS machine. You need to worry about the legal issues of ensuring that you have a right to use the required files on your machine. On your NetBSD machine, do the following: 1. mkdir -p /emul/sunos/usr/lib /emul/sunos/usr/5lib 2. cp SunOS:/usr/lib/lib*.so.*.* NetBSD:/emul/sunos/usr/lib 3. cp SunOS:/usr/5lib/lib*.so.*.* NetBSD:/emul/sunos/usr/5lib 4. cp SunOS:/usr/lib/ld.so NetBSD:/emul/sunos/usr/lib/ld.so 5. If you ever expect to use YP, you will want to create a link: ln -s /var/run/ypbind.lock /etc/ypbind.lock Alternatively, you can use an NFS mount to accomplish the same effect. On your NetBSD machine, do the following: 1. mkdir -p /emul/sunos/usr 2. mount SunOS:/usr /emul/sunos/usr This will place the SunOS libraries on your NetBSD machine in a location where the SunOS compatibility code will look for first, where they do not conflict with the standard libraries. NOTES
When using compat_sunos on NetBSD/sparc64, the COMPAT_NETBSD32 option must also be used. BUGS
A list of things which fail to work in compatibility mode should be here. SunOS executables can not handle directory offset cookies > 32 bits. Should such an offset occur, you will see the message ``sunos_getdents: dir offset too large for emulated program''. Currently, this can only happen on NFS mounted filesystems, mounted from servers that return offsets with information in the upper 32 bits. These errors should rarely happen, but can be avoided by mounting this filesystem with offset translation enabled. See the -X option to mount_nfs(8). The -2 option to mount_nfs(8) will also have the desired effect, but is less preferable. The NetBSD/sparc64 support is less complete than the other ports. BSD
February 3, 2001 BSD
Man Page