similar to: libao on Debian

I have a test program that loads an AIFF or WAV file with libsndfile and plays then using libao. After running around in circles for a while, I found and fixed the problem, but I'm still confused as to why the solution works. Would someone please explain this to me so I don't trip over this again later in my project? I used sf_open_fd() to get a SNDFILE* pointer and an AF_INFO

Hello, I'm trying to make a function for using wine_get_unix_file_name in VB6 programs. Private Declare Function lstrcpyA Lib "kernel32.dll" (ByVal lpString1 As String, ByVal lpString2 As Long) As Long Public Declare Function GetProcessHeap Lib "kernel32" () As Long Public Declare Function HeapFree Lib "kernel32" (ByVal hHeap As Long, ByVal dwFlags As

Hi, I have a data.frame with many variables for which I am performing the mean by subgroup, for a pair of variables at a time, where one of them for each pair defines the subgroup. The subgroups in the x$cm1 are 0, 1 and 2. x ph1 cm1 0.2345 2 1.2222 1 2.0033 0 0.0000 2 1.0033 1 0.2345 0 1.2222 2 2.0033 0 0.0000 1 1.0033 2 > meanbygroup <- as.vector(with(x, by(x$ph1, x$cm1, mean)))

The HTB qdisc has a compile time option, HTB_HYSTERESIS, that trades accuracy of traffic classification for CPU time. These patches change hysteresis to be a runtime option under the control of "tc". The effects of HYSTERESIS on HTB''s accuracy are significant (see chapter 7, section 7.3.1, pp 69-70 in Jesper Brouer''s thesis: http://www.adsl-optimizer.dk/thesis/ ),

The HTB qdisc has a compile time option, HTB_HYSTERESIS, that trades accuracy of traffic classification for CPU time. These patches change hysteresis to be a runtime option under the control of "tc". The effects of HYSTERESIS on HTB''s accuracy are significant (see chapter 7, section 7.3.1, pp 69-70 in Jesper Brouer''s thesis: http://www.adsl-optimizer.dk/thesis/ ),

Hi Heikki, So libao is currently not maintained upstream. In the appropriate IRC channels I'm lead to believe that there are better libraries out there that should be used instead. If so many debian packages didn't link against it I would seriously consider dropping it all together. It doesn't sound like it's worth anyone's time maintaining libao properly upstream. I do have

I have been using OpenSSH for a while, and I would like to thank you for the great package. Here is a report of mysterious warning message lines, I get while I use OpenSSH. They don't seem to be serious, but annoying nevertheless. version: openssh-1.2.1pre27 OS Linux standard 2.2.14 #18 SMP Thu Jan 6 06:07:45 JST 2000 i586 unknown (compiled with gcc 2.95.2) Compiler gcc -v Reading

Dear WizaRds, I tried to construct a two-phase sampling design in Survey just the way I hoped understood in Vienna - I was wrong. I think I am too stupid to create the correct subset for phase 2. Phase1: Sample 1000 parts with 80 defective. Phase2: Sample 100 parts out of these 1000 with 15 defective. 0:ok, 1:defunct. The table below gives the conditional sampling values. Please help me:

Hi folks. If I have the following in my "data" event pH1 pH2 1 4.0 6.0 2 4.3 5.9 3 4.1 6.1 4 4.0 5.9 and on and on..... for about 400 events Is there a way I can get R to plot event vs. pH1 and event vs. pH2 and then do a loess or lowess line for each?? Thanks in advance David [[alternative HTML version deleted]]

Attached is the patch I've been using to fix the error message seen in the subject line. It seems (!) to have caused no problems with the previous openssh snapshot version openssh-SNAP-20001016, 2.3.0p1 and the latest snapshot (openssh-SNAP-20001114). The patch adds 3 lines to nchan.c in a switch stmt (line 100). It simply caters for the cases where the input channel state is

I have a simple cdr configured with the default tables, here is a row of a good cdr report calldate | clid | src | dst | dcontext | channel | ect ..... ect .... 2008-08-29 10:16:49 | "C. BOUTON" <40> | 40 | XXXXXXXXXXX | phonesystems | SIP/40-08776938 | ect ..... ect .... I have replaced the number by

Hello, In the following I tried 3 versions of an example in R help. Only the two first predict command work. After : library(splines) require(stats) 1) fm1 <- lm(weight ~ bs(height, df = 5), data = women) ht1 <- seq(57, 73, len = 200) ph1 <- predict(fm1, data.frame(height=ht1)) # OK plot(women, xlab = "Height (in)", ylab = "Weight (lb)") lines(ht1, ph1) 2)

Hi, A developper of MandrakeSoft needed for some reason to ameliorate ogg123 in a way: with the patch when you issue a Ctrl+Z (suspending the app) the dsp is freed. Ofcourse the app can still continue when SIGCONT is received. Apparently he chose to separate the actual code into more functions. Please note that this code uses local functions, it thus needs gcc to compile. -=-=-- ---

The Linux implementation of TCP sockets has a bug which causes shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write side of the socket has already been shut down. If you are using SSH port forwarding to tunnel HTTP through a firewall, nchan.c will tickle this bug once for every HTTP exchange. You will therefore get lots of useless, annoying error messages: channel 2:

I have a recurring graphics issue that I've not been able to resolve with R. If I make a series of regression estimates and then plot the estimated function for the regression lines over a scatter plot of the data, e.g., using a sequence of plot( ) and lines ( ) similar to those below

I know you're tired of hearing me complain about ogg123, but this time I noticed that some of the error messages are a bit inconsistant. Also, I noticed that some things (like "Error connecting to server") are fatal errors that kill ogg123, while I think they should simply go on to the next file in the list like "input not an Ogg Vorbis audio stream" does. Another problem

Dear friends: It's possible make a legend in the coplot output? My data are: "dados"<-structure (list ( Qu1 = c(1,2,3,4,5,6,7,8,3,2), Qu2 = c(3,4,5,6,7,8,9,9,6,3), Ku1 = structure (factor ( c(1,1,1,1,2,1,2,2,1,1),levels=1:2),.Label=c("Kmin","Kmax")), Ph1 = structure (factor (

As you are now probably aware, the portability team for openssh still has not fixed the hang-on-exit bug in the 2.9.9p2 release. Attached is a patch for 2.9.9p2 that fixes the hang-on-exit bug for Linux systems. It also adds a useful exit delay feature that has also not yet been incorporated into the main sources. For more information, see the SNFS (secure NFS) web page:

Markus, How's this patch? - a chan_wont_read()/chan_wont_write() API is added that is very much like chan_read_failed()/chan_write_failed(), but for the debug messages and chan_wont_*() don't ever call error() The 3.0.2p1 channel_pre_x11_open() uses chan_*_failed() but looks like it ought to use chan_wont_*() instead :) - forkoff() no longer fakes EOF for SSHv2 (still

The hang-on-exit bug still hasn't been fixed in OpenSSH-3.0p1... :-( Here again is the patch to fix this bug under Linux, updated for OpenSSH-3.0p1. This has been exhaustively tested for six months now. It also add an exit delay option that can be useful. The patch does not lead to data loss under Linux. Please see the Secure NFS page (SNFS) for further details: