search for: datamods

when i compile zaptel make linux26 make install i got these errors: make[1]: Leaving directory `/usr/src/zaptel-1.4/wct4xxp' make -C datamods clean make[1]: Entering directory `/usr/src/zaptel-1.4/datamods' make -C /lib/modules/2.4.27-3-386/build SUBDIRS=/usr/src/zaptel-1.4/datamods clean make[2]: Entering directory `/usr/src/kernel-headers-2.4.27-3-386' make: *** arch/i386/boot: No such file or directory. Stop. make: Entering a...

...tory `/usr/src/zaptel-1.4.9.2/menuselect' make[2]: Entering directory `/usr/src/zaptel-1.4.9.2/menuselect' make[2]: `menuselect' is up to date. make[2]: Leaving directory `/usr/src/zaptel-1.4.9.2/menuselect' make[1]: Leaving directory `/usr/src/zaptel-1.4.9.2/menuselect' make -C datamods datamods make: *** datamods: No such file or directory. Stop. make: *** [data] Error 2 Adding datamods to SUBDIR_MODULES in top level Makefile make: CC [M] /usr/src/zaptel-1.4.9.2/kernel/datamods/hdlc_fr.o /usr/src/zaptel-1.4.9.2/kernel/datamods/hdlc_fr.c: In function `fr_lmi_send': /usr/...

Se ha borrado un adjunto en formato HTML... URL: <https://stat.ethz.ch/pipermail/r-help-es/attachments/20120614/518ed68f/attachment.html>

Dear list, I've set up an RPM repository with several asterisk-related RPMs that I think contain some improvements upon what are already out there. The first goal is to be able to build an Asterisk + FreePBX system on CentOS 5 with the EPEL repo enabled; in our environment, where all our systems are under configuration management, either an appliance-type solution or a manual

Dear list-members I am new to R and a statistics beginner. I really like the ease with which I can extract and manipulate data in R, and would like to use it primarily. I've been learning by checking analyses that have already been run in SAS. In an experiment with Y being a response variable, and group a 2-level between-subject factor, and time a 5-level within-subject factor. 2

...channels Shaun Ruffell (1): zonedata: Ensure all zones have a default DAHDI_TONE_DIALRECALL. Tzafrir Cohen (2): xpp_fxloader: rename variable: default_law -> law xpp: astribank_hexload: allow empty span specs The diffstat from the dahdi-linux v2.9.2 release: drivers/dahdi/datamods/hdlc_fr.c | 15 ++++++++++++-- drivers/dahdi/datamods/hdlc_generic.c | 5 +++++ drivers/dahdi/firmware/Makefile | 5 ++++- drivers/dahdi/voicebus/voicebus_net.c | 6 ++++++ drivers/dahdi/wctc4xxp/base.c | 6 ++++++ drivers/dahdi/wcte13xp-base.c | 4 ++++ drivers/dahd...

...channels Shaun Ruffell (1): zonedata: Ensure all zones have a default DAHDI_TONE_DIALRECALL. Tzafrir Cohen (2): xpp_fxloader: rename variable: default_law -> law xpp: astribank_hexload: allow empty span specs The diffstat from the dahdi-linux v2.9.2 release: drivers/dahdi/datamods/hdlc_fr.c | 15 ++++++++++++-- drivers/dahdi/datamods/hdlc_generic.c | 5 +++++ drivers/dahdi/firmware/Makefile | 5 ++++- drivers/dahdi/voicebus/voicebus_net.c | 6 ++++++ drivers/dahdi/wctc4xxp/base.c | 6 ++++++ drivers/dahdi/wcte13xp-base.c | 4 ++++ drivers/dahd...

lme() and gls() models from the nlme package are all crashing with R.3.4.0. Identical code ran correctly, without error in R 3.3.3 and earlier versions. The behavior is easily demonstrated using one of the examples form the lme() help file, along with two simple variants. I have commented the errors generated by these calls, as well as the lines of code generating them, in the code example below.

I am trying to fit a B-spline regression model with a corStruct using gls. I am using bs() and specifying the knots myself. If I make the knots data-dependent, this works but has undesirable side-effects. I prefer to reference an auxilliary variable "knots" in my model formula. It should not be part of the data frame, as it is a vector of a different length. How can this be done? The

Dear R-helpers; While using gnls() to fit a function > Gbht0t.gnls <- gnls(h2 ~ Rht(b0, b1, b2, h1,t1, t2), data=gbht10, + params=list(b0 + b1 + b2 ~ Sisp -1), start=c(strssb0,strssb1,strssb2)) I encountered an error: "Error in model.frame(formula, rownames, variables, varnames, extras, extranames, : invalid variable type " Rht is a defined function to be

Does anyone know where I can get a list of ADSI functions.. Example *70 (No Call Waiting), Flash = Flash, Hold = ??? Thank you, -gcc

Dear all, I've stumbled a similar issue with the package cluster when compiling the 3.4.0 version with the settings of Fedora RPM specs. Compiling R with the default setting of configure yields a version that works for cluster... and nlme. I did not find the exact option that was the cause of this issue but I'm willing to help. Erwan PS: This is the reason why R is

...enerate .depends if there's no libusb The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 121 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...enerate .depends if there's no libusb The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 121 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...busb Makefile: A typo in a comment The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 135 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...busb Makefile: A typo in a comment The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 135 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...busb Makefile: A typo in a comment The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 135 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...busb Makefile: A typo in a comment The diffstat from the dahdi-linux v2.9.1 release: build_tools/install_firmware | 14 +- drivers/dahdi/dahdi-base.c | 135 +- drivers/dahdi/dahdi_transcode.c | 3 +- drivers/dahdi/datamods/syncppp.c | 1 + drivers/dahdi/firmware/Makefile | 31 +- .../oct612x/include/oct6100api/oct6100_apiud.h | 2 +- drivers/dahdi/oct612x/oct612x-user.c | 19 +- drivers/dahdi/pciradio.c | 28 +- drivers/...

...xxp.ko wctdm.ko wctdm24xxp.ko wcte11xp.ko wcusb.ko zaptel.ko ztd-eth.ko ztd-loc.ko ztdummy.ko ztdynamic.ko zttranscode.ko; do \ rm -f /lib/modules/2.6.8-2-386/extra/$x ; \ done; \ make -C /usr/src/linux SUBDIRS=/usr/src/zaptel-1.4.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install; \ if [ -f datamods/syncppp.ko ]; then \ make -C datamods install; \ else \ rm -f /lib/modules/2.6.8-2-386/misc/{hdlc_*,syncppp}.ko; \ fi make[1]: Entering directory `/usr/src/kernel-source-2.6.8' INSTALL /usr/src/zaptel-1.4.0/pciradio.ko INSTALL /usr/src/zaptel-1.4.0/tor2.ko INSTALL /usr/src/zaptel-1.4.0/...