From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.botz.org (thalamus.botz.org [207.210.96.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.botz.org", Issuer "mail.botz.org" (not verified)) by huchra.bufferbloat.net (Postfix) with ESMTPS id C50F321F20F for ; Thu, 7 Nov 2013 02:48:23 -0800 (PST) Received: from [127.0.0.1] (syzygy.botz.org [127.0.0.1]) (authenticated bits=0) by mail.botz.org (8.13.8/8.13.8) with ESMTP id rA7AsdkT012312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Nov 2013 05:54:41 -0500 DomainKey-Signature: a=rsa-sha1; s=thaldk; d=botz.org; c=simple; q=dns; b=YAlFi4+j48crwa9S+n3VVia1zVinlcLQgve6Rp1mjl2C/nsndeLJgpvRBWXiy35ZO xBq7P/UpXFbEzVuRyUFaw== DKIM-Signature: a=rsa-sha1; c=simple/simple; d=botz.org; s=thalamus; t=1383821683; bh=fz3iOr3LtwVfsPXHP52zucMSnrk=; h=Message-ID:Date: From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:X-Scanned-By; b=lHvGqmDzRVmQ QMLynFqtXrbZ1RsXdb349mE3o7x5rzBHPPBYiJTH7d/2IWNv0evah+6nG5sXcA5uQ63 ISxiQ1x/uD+i6RRwaQdPwnOYDpcqjn0gHBXap8VOrTOZv/O3gAEYfy/uqmHg5vCy4lD sURHubZp0uLx4yCOzFD+Hgmmc= Message-ID: <527B6FE6.2060702@botz.org> Date: Thu, 07 Nov 2013 07:48:06 -0300 From: Juergen Botz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Dave Taht References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.62 on 207.210.96.137 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt 3.10.17-6 released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 10:48:24 -0000 On 11/01/2013 11:17 PM, Dave Taht wrote: > - no sysupgrade fix Exactly what is the problem with this? I'm asking because looking back over the archive, "sysupgrade -n" was said to broken since 3.10.3 (July 27th), but I used the GUI to upgrade to a few versions after that without problems and the GUI uses sysupgrade, right? :j