FreeBSD_HEAD_i386 - Build #2185 - Fixed

2016-01-23 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #2185 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2185/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2185/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2185/console Change summaries: 294

FreeBSD_HEAD_i386 - Build #2184 - Failure

2016-01-23 Thread jenkins-admin
FreeBSD_HEAD_i386 - Build #2184 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2184/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2184/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2184/console Change summaries: 2

Re: HPN and None options in OpenSSH

2016-01-23 Thread Michael Sinatra
On 01/23/16 09:15, Kevin Oberman wrote: > Are you sure of this? I have not looked at the code, but my former > colleagues at the high performance research network ESnet claim at > http://fasterdata.es.net/data-transfer-tools/say-no-to-scp/ that the > internal buffers and effective window size hav

Re: HPN and None options in OpenSSH

2016-01-23 Thread Dag-Erling Smørgrav
Kevin Oberman writes: > Dag-Erling Smørgrav writes: > > Julian Elischer writes: > > > what is the internal window size in the new ssh? > > 64 kB. > Are you sure of this? Sorry, I was thinking of 6.6 (in stable/10). The buffer code in 7.1 supports dynamically-sized buffers with a hard limit of

[Bug 194744] [PATCH] allow to specify custom keymap when kbdmux used

2016-01-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 Oliver Pinter changed: What|Removed |Added Flags||mfc-stable10? -- You are receivin

Re: HPN and None options in OpenSSH

2016-01-23 Thread Kevin Oberman
On Sat, Jan 23, 2016 at 7:55 AM, Dag-Erling Smørgrav wrote: > Julian Elischer writes: > > what is the internal window size in the new ssh? > > 64 kB. > > DES > -- > Dag-Erling Smørgrav - d...@des.no Are you sure of this? I have not looked at the code, but my former colleagues at the high perfo

Re: HPN and None options in OpenSSH

2016-01-23 Thread Dag-Erling Smørgrav
Julian Elischer writes: > what is the internal window size in the new ssh? 64 kB. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: libcrypto.so.7 not found, needed (?) for X server

2016-01-23 Thread Thomas Mueller
> > root@amelia:~ # pkg info -f xserver > > Shared object "libssl.so.7" not found, required by "pkg" > > What happened here? Bug in new FreeBSD? > This is explained by the UPDATING entry of October 2015: > 20151030: > The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring >

Re: Too low PTHREAD_STACK_MIN value?

2016-01-23 Thread David Chisnall
On 23 Jan 2016, at 08:58, Maxim Sobolev wrote: > > For what it's worth, I agree with David. This looks like definite misuse of > the constant. If app X requires min size of stack of Y, it's fullish of it if > to expect our PTHREAD_STACK_MIN somehow accommodate that. It should be really > using

FreeBSD_HEAD_amd64_gcc4.9 - Build #1038 - Fixed

2016-01-23 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #1038 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1038/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1038/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1

Re: Too low PTHREAD_STACK_MIN value?

2016-01-23 Thread Maxim Sobolev
For what it's worth, I agree with David. This looks like definite misuse of the constant. If app X requires min size of stack of Y, it's fullish of it if to expect our PTHREAD_STACK_MIN somehow accommodate that. It should be really using MAX(PTHREAD_STACK_MIN, Y) to set its stack instead. Should be

Re: RCTL and VIMAGE for 11.0-RELEASE

2016-01-23 Thread Bjoern A. Zeeb
> On 23 Jan 2016, at 06:41 , Ernie Luzar wrote: > > Bjoern A. Zeeb wrote: >>> On 24 Aug 2015, at 19:08 , Mark Felder wrote: >>> >>> What is preventing RCTL from being enabled right now? Any known/serious >>> blockers? >> It’s enabled in GENERIC. >>> And the same for VIMAGE? I know there were i