search for: ambigious

https://bugzilla.mindrot.org/show_bug.cgi?id=2532 Bug ID: 2532 Summary: MaxSessions config parameter name is highly ambigious Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: DarkTrick at out...

https://bugzilla.mindrot.org/show_bug.cgi?id=2531 Bug ID: 2531 Summary: MaxSessions config parameter name is highly ambigious Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: DarkTrick at out...

...t assume that UFO6 > > support included into UFO(4). > > > > Without this work, migrating a guest to a 3.18 kernel fails. > > > > This series eliminate the ambiguous NETIF_F_UFO. > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still > ambigious. I know it was used to keep compatibility for legacy guest. But > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and > gso type in vnet header looks sufficient? [...] The IPv6 fragmentation ID needs to be added to the vnet header, to do UFOv6 properly. If it wa...

...t assume that UFO6 > > support included into UFO(4). > > > > Without this work, migrating a guest to a 3.18 kernel fails. > > > > This series eliminate the ambiguous NETIF_F_UFO. > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still > ambigious. I know it was used to keep compatibility for legacy guest. But > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and > gso type in vnet header looks sufficient? [...] The IPv6 fragmentation ID needs to be added to the vnet header, to do UFOv6 properly. If it wa...

Hi , is it possible to calculate ld-measures D, D', r and perhaps corresponding p-values with r IF THE PHASE IS KNOWN? The genetics - package provides the LD function only for ambigious phase. Thank you very much Bettina Kulle

...bytes 1021.87 bytes/sec total size is 4728911 speedup is 617.03 rsync error: some files could not be transferred (code 23) at main.c(620) It would be MUCH better if the warning would indicate where the error was LOCAL or REMOTE and WHICH specific thing it had problems with. "." is VERY ambigious in this case since we're dealing with multiple directories both local and remote. Otherwise, everything gets uploaded properly contrary to the error message at the end. rsync version 2.5.6 protocol version 26 [snip] Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,...

...> > Without this work, migrating a guest to a 3.18 kernel fails. >> > > >> > >> > This series eliminate the ambiguous NETIF_F_UFO. >> > >> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is >> still >> > ambigious. I know it was used to keep compatibility for legacy >> guest. But >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio >> features and >> > gso type in vnet header looks sufficient? >> [...] >> >> The IPv6 fragmentation ID...

...> > Without this work, migrating a guest to a 3.18 kernel fails. >> > > >> > >> > This series eliminate the ambiguous NETIF_F_UFO. >> > >> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is >> still >> > ambigious. I know it was used to keep compatibility for legacy >> guest. But >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio >> features and >> > gso type in vnet header looks sufficient? >> [...] >> >> The IPv6 fragmentation ID...

...the archives the xts. vignitte , googled for an answer but couldn't find one so her it is: ? the Vignette states that xts "doesn't inforce the duplicate row requirement" but yet when I try to bring in tick stock data from a data frame as.xts it complains that the string is in an ambigious format. ? The date and time were in two separate columns I corrected that using excel and put them both in one column and saved the file as a text file in which the first column became similar to the example below.? tried to read the table directly, didn't work, I brought in the data as a data....

----- Original Message ----- > Now that UFO is split into v4 and v6 parts, we can bring > back v4 support without any trouble. > > Continue to handle legacy applications by selecting the > IPv6 fragment id but do not change the gso type. Thist > makes sure that two legacy VMs may still communicate. > > Based on original work from Ben Hutchings. > > Fixes:

----- Original Message ----- > Now that UFO is split into v4 and v6 parts, we can bring > back v4 support without any trouble. > > Continue to handle legacy applications by selecting the > IPv6 fragment id but do not change the gso type. Thist > makes sure that two legacy VMs may still communicate. > > Based on original work from Ben Hutchings. > > Fixes:

Hi, I happened to notice that linux.git uses plenty of btr and bts instructions (not btrl, btrw, btsl, btsw). For examples, see arch/x86/include/asm/bitops.h. LLVM barfs on these due to ambiguity, while GNU as is fine with them. Surely, there must be architectures where the w/l variant is unavailable? LLVM must support those architectures, no? Thanks.

On Wed, Jul 10, 2013 at 11:12 AM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Hi, > > I happened to notice that linux.git uses plenty of btr and bts > instructions (not btrl, btrw, btsl, btsw). For examples, see > arch/x86/include/asm/bitops.h. LLVM barfs on these due to ambiguity, > while GNU as is fine with them. Surely, there must be architectures > where

...We also continue to support legacy guests that assume that UFO6 > support included into UFO(4). > > Without this work, migrating a guest to a 3.18 kernel fails. > This series eliminate the ambiguous NETIF_F_UFO. But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still ambigious. I know it was used to keep compatibility for legacy guest. But what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and gso type in vnet header looks sufficient? With the series, we can't send UFOv6 packet but legacy guest can. How about fix the UFOv6 also in this seri...

...luded into UFO(4). > > > > > > Without this work, migrating a guest to a 3.18 kernel fails. > > > > > > > This series eliminate the ambiguous NETIF_F_UFO. > > > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still > > ambigious. I know it was used to keep compatibility for legacy guest. But > > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and > > gso type in vnet header looks sufficient? > [...] > > The IPv6 fragmentation ID needs to be added to the vnet header, to do...

...We also continue to support legacy guests that assume that UFO6 > support included into UFO(4). > > Without this work, migrating a guest to a 3.18 kernel fails. > This series eliminate the ambiguous NETIF_F_UFO. But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still ambigious. I know it was used to keep compatibility for legacy guest. But what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and gso type in vnet header looks sufficient? With the series, we can't send UFOv6 packet but legacy guest can. How about fix the UFOv6 also in this seri...

...luded into UFO(4). > > > > > > Without this work, migrating a guest to a 3.18 kernel fails. > > > > > > > This series eliminate the ambiguous NETIF_F_UFO. > > > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still > > ambigious. I know it was used to keep compatibility for legacy guest. But > > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and > > gso type in vnet header looks sufficient? > [...] > > The IPv6 fragmentation ID needs to be added to the vnet header, to do...

...gt; > > > > Without this work, migrating a guest to a 3.18 kernel fails. > >> > > > > This series eliminate the ambiguous NETIF_F_UFO. > >> > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is > >>still > >> > ambigious. I know it was used to keep compatibility for legacy guest. > >>But > >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio > >>features and > >> > gso type in vnet header looks sufficient? > >> [...] > >> The IPv6 fra...

...gt; > > > > Without this work, migrating a guest to a 3.18 kernel fails. > >> > > > > This series eliminate the ambiguous NETIF_F_UFO. > >> > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is > >>still > >> > ambigious. I know it was used to keep compatibility for legacy guest. > >>But > >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio > >>features and > >> > gso type in vnet header looks sufficient? > >> [...] > >> The IPv6 fra...

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).