similar to: scp.c: u_int64_t in bwlimit()

Here are a couple of patches against the CVS (Jan 22 18:41 PST) Some C++ comments found their way into ssh.h The no64.patch puts ifdefs around buffer_get_int64() now in bufaux.[c,h] -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net -------------- next part -------------- --- ssh.h.old Mon Jan 22 18:40:58 2001 +++ ssh.h Mon Jan 22 19:02:02 2001 @@ -25,8 +25,10 @@ # include

Here's a patch that should make predict.glm(..., type="response") retain the names. The change passes make check on our Opteron running SLES9. One simple test is: names(predict(glm(y ~ x, family=binomial, data=data.frame(y=c(1, 0, 1, 0), x=c(1, 1, 0, 0))), newdata=data.frame(x=c(0, 0.5, 1)), type="response")) which gives [1]

ssh won't compile on this platform log: gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c atomicio.c -o atomicio.o In file included from config.h:294, from bsd-misc.h:39, from includes.h:91,

configure appears to be setting things right: dragon:/var/src/openssh-1.2.1pre23> grep INTXX config.h #define HAVE_INTXX_T 1 /* #undef HAVE_U_INTXX_T */ #define HAVE_UINTXX_T 1 Marc G. Fournier marc.fournier at acadiau.ca Senior Systems Administrator Acadia University "These are my opinions, which are not necessarily shared

Hi, On RHEL 6.3 with gcc 4.4.6, a number of compiler warnings are emitted when building recent snapshots: These all seem to be harmless, but annoying. readpassphrase.c:127: warning: ignoring return value of ?write?, declared with attribute warn_unused_result readpassphrase.c:146: warning: ignoring return value of ?write?, declared with attribute warn_unused_result make[1]: Leaving directory

Josef''s fs_mark test fs_mark -d /mnt/btrfs-test -D 512 -t 16 -n 4096 -F -S0 on a 2GB single metadata fs leaves about 400Mb of metadata almost unused. This patch reduces metadata chunk allocations by considering the proper metadata chunk size of 200MB in should_alloc_chunk(), not the default 256MB which is set in __btrfs_alloc_chunk(). Signed-off-by: Itaru Kitayama

Henrik Bach wrote: } Hi John, } } configure still exits, when checking for uint64_t. I've attached a patch, } that properly will fix it. Either uint64_t or u_int64_t will succeed: } } Index: configure.ac } =================================================================== } RCS file: /var/cvs/llvm/llvm/autoconf/configure.ac,v } retrieving revision 1.106 } diff -u -r1.106 configure.ac } ---

This deadlock comes from xfstests 251. We''ll hold the chunk_mutex throughout the whole of a chunk allocation. But if we find that we''ve used up system chunk space, we need to allocate a new system chunk, but this will lead to a recursion of chunk allocation and end up with a deadlock on chunk_mutex. So instead we need to allocate the system chunk first if we find we''re

Hello all, Trying to get this piece of code to work on my data set. It is from http://www.itc.nl/personal/rossiter. logit.roc <- function(model, steps=100) { field.name <- attr(attr(terms(formula(model)), "factors"), "dimnames")[[1]][1] eval(parse(text=paste("tmp <- ", ifelse(class(model$data) == "data.frame", "model$data$",

Dear all, I get a strange error when I find polychoric correlations with the ML method, which I have been able to reproduce using randomly-generated data. What is wrong? I realize that the data that I generated randomly is a bit strange, but it is the only way that I duplicate the error message. > n<-100 > test.x<-rnorm(n, mean=0, sd=1) > test.c<-test.x + rnorm(n, mean=0,

I was wondering if there was something specific to the internal chacha20 cipher as opposed to OpenSSL implementation. I can't just change the block size because it breaks compatibility. I can do something like as a hack (though it would probably be better to do it with the compat function): if (strstr(enc->name, "chacha")) *max_blocks = (u_int64_t)1 << (16*2);

Hi, This is a second try to fix the long chain call lengths in netfilter. The difference with the previous patch is that I got rid of the extra argument. I somehow didn't see it could be done without using the 'int *ret2' argument. A comment on the number of arguments to nf_hook_slow: I don't think the number of arguments should be decreased. For the bridge-nf code, f.e., the

W dniu 21.06.2017 o?17:46, Macka pisze: > W dniu 20.06.2017 o?21:25, Timo Sirainen pisze: >> On 20 Jun 2017, at 15.49, Macka<dovecot at macka.pl> wrote: >>> Hi, >>> >>> I have problem with quota storage information in dovecot-2.2.29 (and >>> newer versions, too - 2.2.30.2). >>> I use FS quota backend. >> . >>> After

Reid, >Well, if it doesn't break anything else, I'd fix the header file. The >standard type name is supposed to uint64_t not u_int64_t. I would just >change the header file to define both of them, something like: > >typedef u_int64_t uint64_t; > >You could do that in /usr/include/types.h, I've tried it and it doesn't break anything, but ... >or we could

hi i have gone through the achieves but still could not get my bridge to suvive a reboot . please can anyone help me am using fedora core 2 -----Original message----- From: bridge-request@lists.osdl.org Date: Fri, 28 Jan 2005 03:08:06 +0100 To: bridge@lists.osdl.org Subject: Bridge Digest, Vol 17, Issue 25 > Send Bridge mailing list submissions to > bridge@lists.osdl.org > >

Hi Andrew Morton, The patch "[patch 05/22] ocfs2: lighten up allocate transaction" in mm tree is not the newest one, please drop it from mm tree. This patch V3 is newest, please replace it. Thanks. The issue scenario is as following: When fallocating a very large disk space for a small file, __ocfs2_extend_allocation attempts to get a very large transaction. For some journal

Well, if it doesn't break anything else, I'd fix the header file. The standard type name is supposed to uint64_t not u_int64_t. I would just change the header file to define both of them, something like: typedef u_int64_t uint64_t; You could do that in /usr/include/types.h, or we could add it to a header file in llvm/include/Config, ifdef'd for Interix. Reid. On Tue, 2004-08-31 at

Who takes action on this? >From: John Criswell <criswell at cs.uiuc.edu> >Date: Wed, 01 Sep 2004 15:16:53 -0500 > >Henrik Bach wrote: >>Reid, >> >>>Well, if it doesn't break anything else, I'd fix the header file. The >>>standard type name is supposed to uint64_t not u_int64_t. I would just >>>change the header file to define both

[cc'ed to exports at crypto.com. This patch contains no changes to cryptographic routines, it only changes how the package's configure script works] [I'm not subscribed to this list, please cc me on responses. Thanks] I noticed a minor configure problem in OpenSSH 2.9p2. Basically, configure will check sys/types.h for various "sized" prototypes, and then it separately

This patch adds all the missing commonly used UNIX attributes: st_dev, st_ino, st_nlink, st_rdev, st_blocks, st_blksize, st_ctime. In addition it extends st_atime and st_mtime to 64bits, and adds nanosecond resolution to all three timestamps. This is implemented as an extension to the ATTR message. This patch alone is sufficient for SSHFS to be able to use these attributes. The following two