[App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4

pete M petem001 at hotmail.com
Thu Sep 11 13:43:29 UTC 2014


Thanks Tim. this will help a lot..

My searching skills are usely not bad, But I dont have any good luck on the archive site..



From: Tim Sawyer 
Sent: Wednesday, September 10, 2014 11:11 PM
To: pete M 
Cc: Bob ; APP RPT 
Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4

Is this what you were thinking of?

  From: Jim Duuuude <telesistant at hotmail.com>

  Subject: [App_rpt-users] "Official" "fixed" DAHDI patches

  Date: March 25, 2014 at 11:32:09 AM PDT

  To: app_rpt mailing list <app_rpt-users at ohnosec.org>, "mike at glaserelectronics.com" <mike at glaserelectronics.com>


  After much lamenting this morning, I have come up with what I feel comfortable
  as a "working" DAHDI patch set. This is useful if you are wanting to "roll your own"
  app_rpt system (perhaps on some non-(Centos 5.X 32 bit) platform).

  If you take any of the distros of DAHDI 2.5.1 or newer, and apply these patches,
  it should "work".

  This patch set may be obtained from:

  https://allstarlink.org/fixed-dahdi-patches.tar.gz

  or from SVN at:

  http://svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/trunk/fixed-dahdi-patches/?root=svn



--
Tim
:wq

On Sep 10, 2014, at 11:12 AM, pete M <petem001 at hotmail.com> wrote:


  Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember..  

  If it would be installed at least up to a point. I would be able to do it.. 

  I just dont know how to tell the compiler not to compile that part and go on..





------------------------------------------------------------------------------
  From: kk6ecm at gmail.com
  Date: Wed, 10 Sep 2014 09:15:13 -0700
  To: app_rpt-users at ohnosec.org
  Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4


  Couple of thoughts. I've not been able to load using ssh.  Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around.

  As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~}

  Thanks, 
  Bob
  kk6ecm

  Sent from iPad 


  On Sep 10, 2014, at 8:30 AM, pete M <petem001 at hotmail.com> wrote:


    OK, did I asked a question that CAN’T be answered? Or did I asked the wrong way?
    If I did I am sorry.. And I gave my apology to every one I could have offended..
    But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do..
    Like just point me the pathway.. I will try to do it on my own..
    Thanks
    On Sep 9, 2014, at 11:13 AM, pete M <petem001 at hotmail.com> wrote:


      I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that..

      I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy..



      From: kk6ecm
      Sent: Tuesday, September 09, 2014 1:40 PM
      To: APP RPT
      Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4

      I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. 

      Thanks, 
      Bob
      kk6ecm

      Sent from iPad 


      On Sep 9, 2014, at 8:27 AM, pete M <petem001 at hotmail.com> wrote:


        Ok will try that..

        thanks!


        From: Bob
        Sent: Tuesday, September 09, 2014 10:55 AM
        To: 'APP RPT'
        Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4

        I’ve done this several times without issue. Here are the steps I used.


        Load CentOS 5.10 downloaded from CentOS website
        No features, tools only, no desktop (competes with Asterisk)
        Set ssh /etc/ssh/sshd_config
        Run "setup" at comand line and disable firewall
        vi /etc/rc.d/acidrepo
           http://dl.allstarlink.org
        Execute portion of ks.cfg, each line at a time
        cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig
        cat <<EOF >>/etc/rc.d/rc.local


        cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh


        chmod 755 /etc/rc.d/phase1.sh


        /etc/rc.d/phase1.sh
        Auto reboot after phase1.sh executed
        phase2.sh runs automatically to completion


        Bob
        kk6ecm



------------------------------------------------------------------------

        From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M
        Sent: Tuesday, September 09, 2014 7:00 AM
        To: APP RPT
        Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4


        Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada..


        I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling.


        here is the out put from the script


        sh phase2.sh
        ****** Phase 2 post install ******
        Getting asterisk install script from http://dl.allstarlink.org../.
        Getting files.tar.gz from http://dl.allstarlink.org../.
        ****** Asterisk Installation ******
        /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found
        Unpacking files.tar.gz...
        Compiling Zaptel...
        checking for gcc... gcc
        checking for C compiler default output file name... a.out
        checking whether the C compiler works... yes
        checking whether we are cross compiling... no
        checking for suffix of executables...
        checking for suffix of object files... o
        checking whether we are using the GNU C compiler... yes
        checking whether gcc accepts -g... yes
        checking for gcc option to accept ISO C89... none needed
        checking how to run the C preprocessor... gcc -E
        checking for a BSD-compatible install... /usr/bin/install -c
        checking whether ln -s works... yes
        checking for GNU make... make
        checking for grep... /bin/grep
        checking for sh... /bin/sh
        checking for ln... /bin/ln
        checking for wget... /usr/bin/wget
        checking for grep that handles long lines and -e... (cached) /bin/grep
        checking for egrep... /bin/grep -E
        checking for ANSI C header files... yes
        checking for sys/types.h... yes
        checking for sys/stat.h... yes
        checking for stdlib.h... yes
        checking for string.h... yes
        checking for memory.h... yes
        checking for strings.h... yes
        checking for inttypes.h... yes
        checking for stdint.h... yes
        checking for unistd.h... yes
        checking for initscr in -lcurses... no
        checking for initscr in -lncurses... no
        checking for newtBell in -lnewt... no
        checking for usb_init in -lusb... no
        configure: creating ./config.status
        config.status: creating build_tools/menuselect-deps
        config.status: creating makeopts
        config.status: creating build_tools/make_firmware_object
        configure: *** Zaptel build successfully configured ***
        make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect'
        checking build system type... i686-pc-linux-gnu
        checking host system type... i686-pc-linux-gnu
        checking for gcc... gcc
        checking for C compiler default output file name... a.out
        checking whether the C compiler works... yes
        checking whether we are cross compiling... no
        checking for suffix of executables...
        checking for suffix of object files... o
        checking whether we are using the GNU C compiler... yes
        checking whether gcc accepts -g... yes
        checking for gcc option to accept ANSI C... none needed
        checking for GNU make... make
        checking for asprintf... yes
        checking for getloadavg... yes
        checking for setenv... yes
        checking for strcasestr... yes
        checking for strndup... yes
        checking for strnlen... yes
        checking for strsep... yes
        checking for strtoq... yes
        checking for unsetenv... yes
        checking for vasprintf... yes
        checking how to run the C preprocessor... gcc -E
        checking for egrep... grep -E
        checking for ANSI C header files... yes
        checking for sys/types.h... yes
        checking for sys/stat.h... yes
        checking for stdlib.h... yes
        checking for string.h... yes
        checking for memory.h... yes
        checking for strings.h... yes
        checking for inttypes.h... yes
        checking for stdint.h... yes
        checking for unistd.h... yes
        checking for initscr in -lcurses... no
        checking for initscr in -lncurses... no
        checking for pkg-config... No
        configure: creating ./config.status
        config.status: creating makeopts
        config.status: creating autoconfig.h
        configure: configuring in mxml
        configure: running /bin/sh './configure' --prefix=/usr/local  'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=.
        checking for gcc... gcc
        checking for C compiler default output file name... a.out
        checking whether the C compiler works... yes
        checking whether we are cross compiling... no
        checking for suffix of executables...
        checking for suffix of object files... o
        checking whether we are using the GNU C compiler... yes
        checking whether gcc accepts -g... yes
        checking for gcc option to accept ANSI C... none needed
        checking for g++... no
        checking for c++... no
        checking for gpp... no
        checking for aCC... no
        checking for CC... no
        checking for cxx... no
        checking for cc++... no
        checking for cl... no
        checking for FCC... no
        checking for KCC... no
        checking for RCC... no
        checking for xlC_r... no
        checking for xlC... no
        checking whether we are using the GNU C++ compiler... no
        checking whether g++ accepts -g... no
        checking for a BSD-compatible install... /usr/bin/install -c
        checking for ranlib... ranlib
        checking for ar... /usr/bin/ar
        checking for cp... /bin/cp
        checking for ln... /bin/ln
        checking for mkdir... /bin/mkdir
        checking for nroff... /usr/bin/nroff
        checking for rm... /bin/rm
        checking for strdup... yes
        checking for vsnprintf... yes
        configure: creating ./config.status
        config.status: creating Makefile
        config.status: creating mxml.list
        config.status: creating mxml.pc
        config.status: creating config.h
        configure: Menuselect build configuration successfully completed
        make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'
        make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect'
        make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect'
        gcc -g -c -D_GNU_SOURCE -Wall    -c -o menuselect.o menuselect.c
        gcc -g -c -D_GNU_SOURCE -Wall    -c -o strcompat.o strcompat.c
        gcc -g -c -D_GNU_SOURCE -Wall    -c -o menuselect_stub.o menuselect_stub.c
        make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml'
        gcc -O -Wall   -c mxml-attr.c
        gcc -O -Wall   -c mxml-entity.c
        gcc -O -Wall   -c mxml-file.c
        gcc -O -Wall   -c mxml-index.c
        gcc -O -Wall   -c mxml-node.c
        gcc -O -Wall   -c mxml-search.c
        gcc -O -Wall   -c mxml-set.c
        gcc -O -Wall   -c mxml-private.c
        gcc -O -Wall   -c mxml-string.c
        /bin/rm -f libmxml.a
        /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o
        a - mxml-attr.o
        a - mxml-entity.o
        a - mxml-file.o
        a - mxml-index.o
        a - mxml-node.o
        a - mxml-search.o
        a - mxml-set.o
        a - mxml-private.o
        a - mxml-string.o
        ranlib libmxml.a
        make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml'
        gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a
        make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'
        make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'
        Generating input for menuselect ...


        ***********************************************************
          The existing menuselect.makeopts file did not specify
          that 'zttool' should not be included.  However, either some
          dependencies for this module were not found or a
          conflict exists.


          Either run 'make menuselect' or remove the existing
          menuselect.makeopts file to resolve this issue.
        ***********************************************************


        make: *** [menuselect.makeopts] Error 255
        Failure: Unable to compile Zaptel 2
        Fatal error: Unable to install Asterisk!
        [root at node rc.d]#


        I dont know where to go from there..


        Anyone care to help a bit?





------------------------------------------------------------------------
        _______________________________________________
        App_rpt-users mailing list
        App_rpt-users at ohnosec.org
        http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

        To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
        You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

--------------------------------------------------------------------------
      _______________________________________________
      App_rpt-users mailing list
      App_rpt-users at ohnosec.org
      http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

      To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
      You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.


----------------------------------------------------------------------------
    _______________________________________________
    App_rpt-users mailing list
    App_rpt-users at ohnosec.org
    http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

    To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
    You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
    _______________________________________________
    App_rpt-users mailing list
    App_rpt-users at ohnosec.org
    http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

    To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
    You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

  _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
  _______________________________________________
  App_rpt-users mailing list
  App_rpt-users at ohnosec.org
  http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

  To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
  You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140911/80811476/attachment.html>


More information about the App_rpt-users mailing list