From 030adf23abcc8e6f3f28862b01f5e461cecc05d4 Mon Sep 17 00:00:00 2001 From: Jason Parker Date: Thu, 11 Sep 2008 15:33:29 +0000 Subject: Remove files that aren't used or are duplicated from dahdi-linux. Step 1 of cleanup. git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@4891 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- build_tools/genmodconf | 107 ----------------------------------------------- build_tools/genudevrules | 35 ---------------- dahdi.rules | 9 ---- 3 files changed, 151 deletions(-) delete mode 100755 build_tools/genmodconf delete mode 100755 build_tools/genudevrules delete mode 100644 dahdi.rules diff --git a/build_tools/genmodconf b/build_tools/genmodconf deleted file mode 100755 index b4d740b..0000000 --- a/build_tools/genmodconf +++ /dev/null @@ -1,107 +0,0 @@ -#!/bin/sh - -# this script makes an attempt to build a proper set of rules -# for loading the DAHDI modules and automatically running dahdi_cfg -# -# it accepts three parameters: -# the kernel major version being targeted (either linux24 or linux26) -# the root prefix to be used for finding/creating the files -# the list of module names being installed -# -# the process is as follows: -# -# for linux24, the file can be located either at /etc/modules.conf (combined -# with all other rules) or in /etc/modutils/dahdi (only the DAHDI rules) -# -# for linux26, the file can be located at /etc/modprobe.conf (combined with all -# other rules), /etc/modprobe.d/dahdi (DAHDI only) or /etc/modules.d/dahdi -# (DAHDI only) -# -# when the file is DAHDI rules only, then we don't preserve the existing -# contents of the file; the system administrator can put desired options and -# overrides in a separate file with a name that appears earlier in the sort -# order, so there is no need to edit the file produced by this script -# -# when the file is combined with all other rules, then we make a backup -# of it and remove all the old DAHDI rules we can find, replacing them with -# new ones -# -# in addition, for linux26, versions of module-init-tools 3.2.0 and later -# have the ability to pass module parameters specified on the modprobe command -# line to commands in 'install' rules, thus keeping them from being lost, so -# we try to determine what version is installed and take advantage of that - -if [ "${1}" = "linux24" ]; then - if [ -d ${2}/etc/modutils ]; then - target=${2}/etc/modutils/dahdi - elif [ -f ${2}/etc/modules.conf ]; then - target=${2}/etc/modules.conf - combined=1 - else - echo No suitable location for module rules can be found... exiting. - exit 1 - fi -elif [ "${1}" = "linux26" ]; then - toolver=`/sbin/modprobe --version 2>/dev/null| awk '{print $3}' | cut -d. -f2 | cut -d- -f1` - if [ ${toolver} -ge 2 ]; then - cmdopts=\$CMDLINE_OPTS - fi - if [ -d ${2}/etc/modprobe.d ]; then - target=${2}/etc/modprobe.d/dahdi - elif [ -d ${2}/etc/modules.d ]; then - target=${2}/etc/modules.d/dahdi - elif [ -f ${2}/etc/modprobe.conf ]; then - target=${2}/etc/modprobe.conf - combined=1 - elif [ -f ${2}/etc/conf.modules ]; then - target=${2}/etc/conf.modules - combined=1 - else - echo No suitable location for module rules can be found... exiting. - exit 1 - fi -else - echo Unknown kernel build version requested... exiting. - exit 1 -fi - -if [ -n "${combined}" ]; then - if [ -f ${target} ]; then - mv ${target} ${target}.bak - cat ${target}.bak | grep -v "alias char-major-250" | grep -v "alias char-major-196" > ${target} - fi -else - if [ -f ${target} ]; then - mv ${target} ${target}.bak - fi - echo "# automatically generated file; do not edit" > ${target} -fi - -echo Building ${target}... - -if [ "${1}" = "linux24" ]; then - for mod in ${3}; do - if ! grep -q "post-install ${mod} " ${target}; then - echo "post-install ${mod} /sbin/ztcfg" >> ${target} - fi - done -elif [ "${1}" = "linux26" ]; then - for mod in ${3}; do - if ! grep -q "install ${mod} " ${target}; then - echo "install ${mod} /sbin/modprobe --ignore-install ${mod} ${cmdopts} && /sbin/ztcfg" >> ${target} - fi - done -fi - -if [ -z "${combined}" ]; then - echo "***" - echo "*** WARNING:" - echo "*** If you had custom settings in ${target}," - echo "*** they have been moved to ${target}.bak." - echo "***" - echo "*** In the future, do not edit ${target}, but" - echo "*** instead put your changes in another file" - echo "*** in the same directory so that they will not" - echo "*** be overwritten by future DAHDI updates." - echo "***" -fi diff --git a/build_tools/genudevrules b/build_tools/genudevrules deleted file mode 100755 index c3081c9..0000000 --- a/build_tools/genudevrules +++ /dev/null @@ -1,35 +0,0 @@ -#!/bin/sh - -ver=`udevinfo -V | cut -f3 -d" "` - -if [ -z "${ver}" ]; then - # nobody has that old version, anyway. - ver=54 -fi - -# udev versions prior to 055 use a single '=' for matching key values -# udev versions 055 and later support '==' for that purpose, and versions -# beyond 092 will probably make it mandatory -# -# very old versions of udev required naming rules and permissions rules to be -# in separate files, but it's not clear at what version number that changed - -if [ ${ver} -gt 54 ]; then - match="==" -else - match="=" -fi - -cat <