- Any ANSI C compiler can be used - gcc is fine. Npasswd
should also build with non-ANSI compilers, but this is discouraged.
Do you expect to run these scripts and binaries on multiple machines? [n]
- Always answer n
Pathname where the private library files will reside?
- This is the install directory where npasswd and its ancillary
files will be placed.
The default is /usr/lib/npasswd.
### Found passwd files "/etc/passwd"
Change passwd file list? [n]
- Npasswd can search multiple local password files to find a user.
If you want to manipulate non-standard password files, specify them here.
### Found shadow files "/etc/shadow"
Change shadow file list? [n]
- Npasswd can search multiple local shadow files to find a user.
If you want to manipulate non-standard shadow files, specify them here.
Replace system programs? [y]
- If this option is selected, then Configure creates a list of
the programs in system bin directories which have "passwd",
"chfn"
or "chsh" in their names. You will be able to edit this list. The
initial installation will move these programs will be moved to the npasswd
install directory.
Activate the "paranoid" option [n]
- Activating the paranoid option will cause npasswd to
abort if the uid obtained via getpwnam(getlogin()) is not the same
as that returned by getuid(2). If you allow multiple login names
to have the same uid, DO NOT enable this option.
Password history file [/usr/lib/passwd/history]
-
If this system is a member of a cluster which shares a password file,
the history should be put on a file system that all cluster members
mount read/write, preferably with root access.
Refer to the password history section of the Npasswd Administration Guide.
If your system has symbolic links, it is a good idea to use a "build tree" to keep the source area clean. The BuildTree script will do this.
build-area is where you want to build npasswd
source-area is the directory where you unpacked the distribution.
mkdir build-area
cd build-area
sh source-area/bin/BuildTree source-area
Note about the build process
During build process some directories will be visited multiple times. This is because of the dependencies between various parts of the package.
Common make targets |
|
| help | See what package targets are available. |
|---|---|
| all | Build the default stuff, whatever that may be. Most all targets do make all in subdirectories. |
| depend | Update the C source dependencies. A modified Makefile is created which has the dependency information at the end. Most depend targets do make depend in subdirectories. |
| install | Install what is built in this directory. Most install targets do make install in subdirectories. |
| deinstall | Remove what is built in this directory. Most deinstall targets do make deinstall in subdirectories. |
| clean | Light debris removal. |
| realclean | Total cleanup of debris, object files and executables. |
Special make targetsThese targets alter the compile and load flags in Makefile.local, which is included by the Makefile. They also do recursive makes in subdirectories.(See the Support Guide for details) |
|
| debug-none | Build production executables. The -XD command line option is available for run-time debugging. |
| debug-dbx | Build production executables with source debugger support. |
| debug-files | Build debug-dbx executables which change files in the current directory. |
| debug-system | Build debug-system executables with many security and update checks
disabled.
These executables are insecure, partly non-functional and are NOT suitable for production. |
Major customizations can be done by running Configure. Some changes require modification of options.h. The file to edit is options_h.SH.
Follow this procedure:
edit options_h.SH # Change the source sh options_h.SH # Reconstruct the file make realclean # Remove objects and executables make # Rebuild with new options
Installing
Invoke make install in the top-level build directory.
- The install will create any needed directories.
- Dictionary hash files will be built. The word list distribution must have been unpacked into the dict directory first.
- Executables and ancillary files are placed in the install directory.
- If replace system programs was selected, the system password change utilities found by Configure will be saved and replaced with copies or links to the npasswd binary.
Removing
To reinstall the vendor password programs, run /restorefiles.
To reinstall the vendor programs and delete npasswd, do
make deinstallin the top build directory. If the replace vendor programs option was not enabled, the system utilities are not affected by the removal process.
Build and install summary
The procedure to build, install and setup npasswd:
gzip --stdout npasswd-dist.gz | tar xpfv - # Unpack npasswd cd dict gzip --stdout npasswd-words.gz | tar xpfv - # Unpack word lists cd .. Configure # Answer the questions make # Build everything make install # Install everything /history_admin load < /dev/null # Make history database
Top
Home
Document id @(#) BuildInstall.html 1.15
Version 1.15
Last modified 07/20/98
Clyde Hoover
Academic Computing Services and Instructional Technology Services
The University of Texas at Austin
Copyright 1998, The University of Texas at Austin. All rights reserved.