Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Usher
--- On Thu, 5/17/12, Jason Hellenthal wrote: > > That is not the standard "key mismatch" error that you > assumed it was.  Look at it again - it is saying that > we do have a key for this server of type DSA, but the client > is receiving one of type RSA, etc. > > > > The keys are the same - th

Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Usher
--- On Thu, 5/17/12, Garrett Cooper wrote: > > ... but I'm afraid that changing that line in > myproposal.h BACK TO ssh-dss,ssh-rsa does not solve the > problem.  I did indeed make that change to > myproposal.h, manually, and then build the openssh-portable > port, but the behavior persists. >

Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Usher
--- On Thu, 5/17/12, Jason Hellenthal wrote: > On Thu, May 17, 2012 at 02:17:03PM -0700, Jason Usher > wrote: > > I have some old 6.x FreeBSD systems that need their > OpenSSH upgraded. > > > > Everything goes just fine, but when I am done, existing > clients are now presented with this messag

Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Hellenthal
On Thu, May 17, 2012 at 04:26:38PM -0700, Jason Usher wrote: > > > --- On Thu, 5/17/12, Jason Hellenthal wrote: > > > > That is not the standard "key mismatch" error that you > > assumed it was.? Look at it again - it is saying that > > we do have a key for this server of type DSA, but the cl

Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Hellenthal
On Thu, May 17, 2012 at 04:06:11PM -0700, Jason Usher wrote: > > > --- On Thu, 5/17/12, Jason Hellenthal wrote: > > > On Thu, May 17, 2012 at 02:17:03PM -0700, Jason Usher > > wrote: > > > I have some old 6.x FreeBSD systems that need their > > OpenSSH upgraded. > > > > > > Everything goes j

Re: Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Hellenthal
On Thu, May 17, 2012 at 02:17:03PM -0700, Jason Usher wrote: > I have some old 6.x FreeBSD systems that need their OpenSSH upgraded. > > Everything goes just fine, but when I am done, existing clients are now > presented with this message: > > > WARNING: DSA key found for host hostname > in /

Need to revert behavior of OpenSSH to the old key order ...

2012-05-17 Thread Jason Usher
I have some old 6.x FreeBSD systems that need their OpenSSH upgraded. Everything goes just fine, but when I am done, existing clients are now presented with this message: WARNING: DSA key found for host hostname in /root/.ssh/known_hosts:12 DSA key fingerprint 4c:29:4b:6e:b8:6b:fa:49... Th

Re: ARM + CACHE_LINE_SIZE + DMA

2012-05-17 Thread Ian Lepore
On Thu, 2012-05-17 at 15:20 +0200, Svatopluk Kraus wrote: > Hi, > > I'm working on DMA bus implementation for ARM11mpcore platform. I've > looked at implementation in ARM tree, but IMHO it only works with some > assumptions. There is a problem with DMA on memory block which is not > aligned on CAC

Re: ARM + CACHE_LINE_SIZE + DMA

2012-05-17 Thread Mark Tinguely
On Thu, May 17, 2012 at 8:20 AM, Svatopluk Kraus wrote: > Hi, > > I'm working on DMA bus implementation for ARM11mpcore platform. I've > looked at implementation in ARM tree, but IMHO it only works with some > assumptions. There is a problem with DMA on memory block which is not > aligned on CACHE

Re: GSoC Project: EFI on amd64/i386

2012-05-17 Thread Eric McCorkle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/08/12 13:35, Eric McCorkle wrote: > Hello everyone, > > I'm going to be working on EFI boot support on the amd64/i386 > platforms as a GSoC project. The idea is to allow booting from > EFI (as opposed to legacy BIOS) on these platforms, so tha

Re: GSoC Project: EFI on amd64/i386

2012-05-17 Thread Eric McCorkle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/17/12 10:36, John Baldwin wrote: >> Do the kernel and modules actually do anything that depends on >> being in a contiguous space in some way (ie some relocation >> trick)? Because it seems like it shouldn't really matter >> otherwise. > > The

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread John Baldwin
On Wednesday, May 16, 2012 10:00:33 am Mateusz Guzik wrote: > Are you going to support textdumps? > > I would like to note that some machines have swap space only for > textdumps, so I think you should support these. > > ddb is equiped with a lot of cool commands that show various important > deb

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread John Baldwin
On Tuesday, May 15, 2012 5:30:20 pm tza...@it.teithe.gr wrote: > Hello Community, > > I have the project "Automated Kernel Crash Reporting System" for this > GSoC and I would like to discuss my plans about it before starting the > coding on May 21. > > I have created a page in the FreeBSD Wik

Re: GSoC Project: EFI on amd64/i386

2012-05-17 Thread John Baldwin
On Wednesday, May 16, 2012 9:24:54 am Eric McCorkle wrote: > On 05/15/12 11:44, John Baldwin wrote: > > The i386 kernel assumes it starts out with a flat 32-bit mode with > > the kernel loaded into a contiguous memory region at a fixed > > physical address. If we need a relocatable kernel (as Marc

Re: new panic in cpu_reset() with WITNESS

2012-05-17 Thread Attilio Rao
2012/5/17, Andriy Gapon : > on 25/01/2012 23:52 Andriy Gapon said the following: >> on 24/01/2012 14:32 Gleb Smirnoff said the following: >>> Yes, now: >>> >>> Rebooting... >>> lock order reversal: >>> 1st 0x80937140 smp rendezvous (smp rendezvous) @ >>> /usr/src/head/sys/kern/kern_shutdow

Re: GSoC Project: EFI on amd64/i386

2012-05-17 Thread Eric McCorkle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/16/12 01:32, Andrey V. Elsukov wrote: > As i see we already have sys/boot/efi/libefi/efipart.c that uses > EFI BLOCK_IO_PROTOCOL to make "part" devsw. EFI BLOCK_IO_PROTOCOL > provides access to each disk and partition. AFAIK it supports only > G

ARM + CACHE_LINE_SIZE + DMA

2012-05-17 Thread Svatopluk Kraus
Hi, I'm working on DMA bus implementation for ARM11mpcore platform. I've looked at implementation in ARM tree, but IMHO it only works with some assumptions. There is a problem with DMA on memory block which is not aligned on CACHE_LINE_SIZE (start and end) if memory is not coherent. Let's have a

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread Mateusz Guzik
On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote: > Quoting Mateusz Guzik : > > >On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@it.teithe.gr wrote: > >>Hello Community, > >> > >>I have the project "Automated Kernel Crash Reporting System" for > >>this GSoC and I would like to

Re: new panic in cpu_reset() with WITNESS

2012-05-17 Thread Andriy Gapon
on 25/01/2012 23:52 Andriy Gapon said the following: > on 24/01/2012 14:32 Gleb Smirnoff said the following: >> Yes, now: >> >> Rebooting... >> lock order reversal: >> 1st 0x80937140 smp rendezvous (smp rendezvous) @ >> /usr/src/head/sys/kern/kern_shutdown.c:542 >> 2nd 0xfe0001f5d838

Re: High-res Timers

2012-05-17 Thread Bruce Evans
On Wed, 16 May 2012, Jason Hellenthal wrote: Does anyone have a quick list of high-resolution timer functions? Both user-land and kernel-land? It would be greatly appreciated (doing some performance timing for applications). clocks(7) - various system timers getitimer(2), setitimer(2) - get/se

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread Jeremie Le Hen
On Wed, May 16, 2012 at 02:45:24PM +0300, tza...@it.teithe.gr wrote: > > In this case Apache is a good choice. I would however recommend using > > www/nginx and PHP in FastCGI mode (FPM option in lang/php5 port). This > > is a preffered setup for almost all Russian highloaded websites. > > At the b