From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.44]) by ur; Fri May 13 01:45:21 EDT 2016
Received: from mars.jitaku.localdomain (101-141-39-171f1.osk3.eonet.ne.jp [101.141.39.171])
	by mailmsa11.mozu.eo.k-opti.ad.jp  with ESMTP id u4D5jGbG027104
	for <9front@9front.org>; Fri, 13 May 2016 14:45:16 +0900
To: 9front@9front.org
Subject:  Re: [9front] sysupdate for amd64 system
Date: Fri, 13 May 2016 14:45:15 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <2966fc98d58d8c8ff4e23500d17ac01f@mars.jitaku.localdomain>
In-Reply-To: <7b6488587196bb8a0169c034b49d4f07@mars.jitaku.localdomain>
References: <7b6488587196bb8a0169c034b49d4f07@mars.jitaku.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: deep-learning-scale service DOM persistence enhancement method 

> 2) above was done on 386 termnal, however I got an error when amd64 terminal:
> 
> abort: '/mnt/web/0/body' 0 No status bad DH parameters: /mnt/web/0/body

This doesn't occur this time... 
Now, sysupdate for kokamoto user works fine on adm64 terminal.
I don't know why?

Kenji