Relevant BUGIDs:

Purpose of commit: cleanup

Commit summary:
---------------

Remove wrong/unsused files

diff --git a/modules/README b/modules/README
deleted file mode 100644 (file)
index 73d3cf0..0000000
--- a/modules/README
+++ /dev/null
@@ -1,55 +0,0 @@
-This directory contains the modules.
-
-If you want to reserve a module name please email <pam-list@redhat.com>
-and announce its name. Andrew Morgan, <morgan@linux.kernel.org>, will
-add it to the Makefile in the next release of Linux-PAM.
-
-As of Linux-PAM-0.40 modules can optionally conform to the static
-modules conventions.
-
-This file was updated for Linux-PAM-0.53.
-
-The conventions are as follows:
-
-There are only 6 functions that a module may declare as "public" they
-fall into 4 managment groups as follows:
-
-       functions                                       Management group
-       ------------------------------------------      ----------------
-       pam_sm_authenticate, pam_sm_setcred,            PAM_SM_AUTH
-       pam_sm_acct_mgmt,                               PAM_SM_ACCOUNT
-       pam_sm_open_session, pam_sm_close_session,      PAM_SM_SESSION
-       pam_sm_chauthtok                                PAM_SM_PASSWORD
-
-If a module contains definitions for any of the above functions, it
-must supply definitions for all of the functions in the corresponding
-management group.
-
-The header file that defines the ANSI prototypes for these functions
-is <security/pam_modules.h> . In the case that the module wishes to
-offer the functions of a given managment group, it must #define
-PAM_SM_XXX, where XXX is one of the above four tokens. These
-definitions must occur *prior* to the 
-#include <security/pam_modules.h> line.
-
-The pam_sm_... functions should be defined to be of type 'PAM_EXTERN int'.
-
-In the case that a module is being compiled with PAM_STATIC #define'd
-it should also define a globally accessible structure
-_"NAME"_modstruct containing references to each of the functions
-defined by the module. (this structure is defined in
-<security/pam_modules.h>.  "NAME" is the title of the module
-(eg. "pam_deny")
-
-If a module wants to be included in the static libpam.a its Makefile
-should execute "register_static" with appropriate arguments (in this
-directory).
-
-[
-For SIMPLE working examples, see
-
-       ./modules/pam_deny/* and ./modules/pam_rootok/* 
-.]
-
-Andrew Morgan
-96/11/10

diff --git a/modules/register_static b/modules/register_static
deleted file mode 100755 (executable)
index f3aebb6..0000000
--- a/modules/register_static
+++ /dev/null
@@ -1,49 +0,0 @@
-#!/bin/sh
-
-if [ `basename $PWD` != "modules" ]; then
-       echo "$0 must be run from the .../modules directory"
-       exit 1
-fi
-
-merge_line ()
-{
-       if [ $# != 3 ]; then
-               echo "usage: merge_line token filename 'new line'"
-       fi
-       if [ -f $2 ]; then
-# remove any existing entry...
-               grep -v "$1" $2 > tmp.$2
-               rm -f $2
-               mv {tmp.,}$2
-       fi
-       cat << EOT >> $2
-$3
-EOT
-
-}
-
-
-if [ $# -ne 2 ]; then
-
-       cat << EOT 2>&1
-$0:    this script takes TWO arguments:
-       the 'alphanumeric label' of the module and the location of
-       its object file from the .../modules/ directory
-EOT
-       exit 1
-
-else
-       echo "
- *> registering static module: $1 ($2) <*
-"
-       merge_line "$1" _static_module_list "\
-extern struct pam_module _$1_modstruct;"
-
-       merge_line "$1" _static_module_entry "    &_$1_modstruct,"
-       if [ -n "$2" ]; then
-               merge_line "$2" _static_module_objects "../modules/$2"
-       fi
-
-fi
-
-exit 0