search for: compatiblity

Not sure which list this should go to, so I'll include both. When I SSH from a 2.9.9p2 client to a OpenSSH 2.1.1 server, it often hangs at this point. It will hang there for days on end. If I open up 9 xterms and run that command, 2-3 will login. I have no problems using ssh1 (commercial). And openssh has no problems logging into newer servers > 2.1.1. Anyone know why this might be?

> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of bob netherton > > You can, with recv, override any property in the sending stream that can > be > set from the command line (ie, a writable). > > # zfs send repo/support at cpu-0412 | zfs recv -o version=4 repo/test > cannot receive: cannot override received

Just thought you'd like to know that SP1 for Windows XP breaks romaing profiles up to and including 2.2.5. This has been confirmed by MIT at the following link: http://web.mit.edu/swrt/winxp/ See the section "Software Compatiblity Test Matix/Testing SP1" We have found this to be the case as well.... I'm cross-posting this to samba-technical as well....we will work on some traces for you guys.... Some (maybe) helpful messages when logging on are: "The data area passed to a system call is too small" &q...

...Name: Sigbert Klinke Version: 2.1.1 OS: Suse Linux 10.0 (Full DVD) Submission from: (NULL) (141.20.100.252) Suse 10.0 installs only a Fortran 95 compiler with g77 compability mode. Using this leads in "configure" to an abortion with problems about "FPICFLAGS". Deinstalling g77 compatiblity mode, using f2c, compiles R. But after calling R() the program shows its entrance message and then hangs up, using 100% of the processor capacity. What finally works on my computer was setting a softlink from /usr/bin/g77 to gfortran such that the fortran 95 compiler was used directly during the R...

First a hint for those who try to compile newest Samba in HPUX 8.0x with HP's ANSI C compiler: You get this message: Compiling util.c cc: "smb.h", line 1598: error 1590: "share_mode_entry" is not a typedef name. cc: "smb.h", line 1598: error 1573: Type of "<<<NULL_SYMBOL>>>" is undefined. *** Error code 1 Somehow HP's compiler

https://bugzilla.samba.org/show_bug.cgi?id=10532 Summary: Rsync fails with older version. Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: r.e.wolff at bitwizard.nl

...the .ll file would not barf. I don't think I would be able to > reproduce this without a lot of work, so I'm just leaving this as an > anecdote. Well, I can only speak for myself, but in my two recent IR changes (cmpxchg failure orderings and cmpxchg weak"), I preserved bitcode compatiblity but not .ll. In both cases I was adding extra information to the instruction, which meant the bitcode reading section just had to insert a sensible default if that field wasn't present. In the first case, I could have kept IR compatibility, but the second (r210903) would have been rather diffi...

...on for this: sample.data.frame <- function(x,size,replace=FALSE,prob=NULL) # no auto-dispatch; sample is not a generic function { x[sample(nrow(x),size,replace,prob),] } Would it be a bad idea for this to be the standard behavior for sample? There is always, of course, the backwards-compatiblity argument. Is sample in fact used in practice to select random columns? I realize it is hard to quantify that, but perhaps there is some wisdom in the community about that. -s [[alternative HTML version deleted]]

...ly way to workaround this is to fallback to Macro() and write macro-contexts in AEL with the stack limit implications of them so I'm proposing to add to asterisk.conf configuration the ability to invoke stdexten using AELSub() so stdexten can be again be written in AEL mantaining real backward compatiblity as it did the fact that you are able to fallback to Macro. ;stdexten = gosub ; How to invoke the extensions.conf stdexten. ; macro - Invoke the stdexten using a macro as ; done by legacy Asterisk versions. ; aelsub - Invoke the stdexten sutbroutine using AELSub ; when stdexten i...

...ase a couple of weeks ago, I would like to ask: a) is RedHat likely to choose to backport the fix to 1.6 or will it adopt 1.7 or leave as is until 5.7 or later as it has done with BIND? b) will Centos and/or SL follow RH exactly or will their approaches differ? IOW, how far does the "binary compatiblity" policy extend? kind regards/ldv

...ponses as they''re being written to the socket, but that should be fixable transparently to us[4]. Support for the hardly used, hardly documented[2] embedded command-line switches in rackup config (.ru) files is is also broken under Rubinius. The recently-released Rack 1.2.1 introduced no compatiblity issues[3] in core Unicorn. We remain compatible with all Rack releases starting with 0.9.1 (and possibly before). [1] tested with Rubinius upstream commit cf4a5a759234faa3f7d8a92d68fa89d8c5048f72 [2] lets avoid the Dueling Banjos effect here :x [3] actually, Rack 1.2.1 is broken under 1.8.6. [4]...

...fset after that to place checksum */ > + __le16 rsc_ext_num_dupacks; /* num of duplicated acks */ dupacks -> dup_acks ? Also wouldn't it be cleaner to have an rsc struct? And "num" is kind of extraneous, right? So how about we group the fields: union { /* Unnamed struct for compatiblity. */ struct { csum_start csum_offset }; struct { virtio16 start; virtio16 offset; } csum; struct { le16 packets; le16 dup_acks; } rsc; }; what do you think? > + }; > __virtio16 num_buffers; /* Number of merged rx buffers */ > }; > -- > 2.17.1

...0x00000000 0x00000000 0xfeefdead 0x0199d518 0x199d500: 0x00000000 0x00000000 0x00000000 0x00000000 0x199d510: 0x00000000 0x00000000 0xfeefdead 0x0199d538 (gdb) Does anyone know issues with OpenSSL or OpenSSH above versions ? Is there any compatiblity issue ? Can someone share their knowledge ? Thank you, __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/

...lient-alike library, and when it thinks it is linking to c-client, it could instead link to the libdovecot-c-client-alike. This might be convenient if you want to limit how much of a public API is presented by the current "dovecot.so" that gets installed in e.g. /usr/lib/dovecot/. The compatiblity shim could have a small API, and if you don't want provide ABI guarantees within dovecot.so, the shim could dlopen() dovecot.so rather than link to it. 2. Use of Dovecot shared library within alpine, embedding the imapd Right now, the mail client "alpine" embeds a copy of the UW I...

...ill be enough to enable patches to land in Mesa. An official submit to linux-firmware will happen once we agree on the final firmware format and the kernel code is good to go. For now, please consider these branches as work-in-progress and do not distribute them or embed them anywhere to avoid compatiblity issues. Also update both together I as will heavily rebase in the next few days. So while we have still some work ahead, this at least unlocks a very unpleasant situation for everyone, and we will take further steps to keep improving it. Please test, hack Mesa, and comment on the kernel code s...

Please excuse a wee bit of cross posting here. It seems that the questions list may not be the appropriate place for this as I've found a number of unanswered posts involving this topic. My FreeBSD workstations are setup with pam_ldap to a centralized openldap server for authentication. This works perfectly for native FreeBSD applications. What I'm running into an issue with are Linux

--- Makefile.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.in b/Makefile.in index 304d96cd..47e04c02 100644 --- a/Makefile.in +++ b/Makefile.in @@ -353,7 +353,7 @@ depend-rebuild: rm -f config.h touch config.h makedepend -w1000 -Y. -f .depend *.c 2>/dev/null - (head -2 .depend; tail +3 .depend | sort) >.depend.tmp + (head -n 2 .depend; tail -n +3

...laptop without external LCD/CRT, beryl is working fine, but when I boot it with the external, it recognice fine the external LCD and don't want to allow beryl run. What beryl says: === BEGIN === $ beryl --test-only ************************************************************** * Beryl system compatiblity check * ************************************************************** Detected xserver : AIGLX Checking Display :0.0 ... Checking for XComposite extension : passed (v0.3) Checking for XDamage extension : pa...

...happen mostly within QEMU. User is currently required to enable it but it's pretty lightweight. OTOH vfio migration generally requires actual device-specific work, and only works when hosts are mostly identical. When they aren't it's easy to blame the user, but tools for checking host compatiblity are currently non-existent. Upper layer management will also have to learn about host and device compatibility wrt migration. At the moment they can't even figure it out wrt software versions of vhost in kernel and dpdk so I won't hold my breath for all of this happening quickly. -- MST

Hi, I'm trying to migrate from maildir to mdbox while preserving the pop3 UIDL (and the imap UID). The problem is, for maildir we use (for compatiblity with qpopper): pop3_uidl_format = %f Problem is, as soon as I convert that to mdbox, then whenever a client issues the UIDL command via a POP connection, the connection is closed and this error is displayed in the log: Error: UIDL: File name not found (pop3_uidl_format=%f not supported by stor...