From owner-freebsd-current@FreeBSD.ORG Mon Mar 23 05:53:51 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C1901DE; Mon, 23 Mar 2015 05:53:51 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBA34AC; Mon, 23 Mar 2015 05:53:50 +0000 (UTC) Received: by wibgn9 with SMTP id gn9so51399086wib.1; Sun, 22 Mar 2015 22:53:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=f1xbXFRHFcMZu+0ScFYTevAKWBSBGt8cYY4Uxmn+2so=; b=dLS8iSe2Aeb2XKSS7C1TCvx5AmfiouOPBPuBN1pJmxDTo+U2R3nGQR8FlC/ZWa6aSS 6CM8OhsiZzwqgNCnnIRHqCV5PKVP7jkQowTzczwRnQ7TwiaHeIdLQfAQjb199RnF0GVk ashR58LH7IdQmbjUq5OvO/NhJbHjfsOQmqbVVB7QLnM1P8GEsHfRP+zg+U8Vt8bNv7Ut rv9otnC74sEcXDADK9qveHOK8YJtxpdM4kR1cjRhmjSYf/Zx/rxWbHDRyChBHG+MKRIQ LYdz9sPAacjmpVkyojVlcyYJRGEIpi+Kvt027S/dd7vp5jCGWydtcEcRJjtysXMKTpe5 E0Lw== X-Received: by 10.180.83.195 with SMTP id s3mr16671888wiy.54.1427090029474; Sun, 22 Mar 2015 22:53:49 -0700 (PDT) Received: from laptop.minsk.domain (minsk.nivalnetwork.com. [86.57.144.74]) by mx.google.com with ESMTPSA id lb6sm17815568wjb.22.2015.03.22.22.53.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Mar 2015 22:53:48 -0700 (PDT) Date: Mon, 23 Mar 2015 08:52:22 +0300 From: "Sergey V. Dyatko" To: dteske@freebsd.org Subject: Re: bsdinstall and current (possible stable) snapshots Message-ID: <20150323085222.3aaea668@laptop.minsk.domain> In-Reply-To: <20150323084738.70f7db7b@laptop.minsk.domain> References: <20150323084738.70f7db7b@laptop.minsk.domain> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 05:53:51 -0000 On Mon, 23 Mar 2015 08:47:38 +0300 "Sergey V. Dyatko" wrote: > Hi Devin, > > Recently I'm trying to install FreeBSD CURRENT from bootonly image > ( FreeBSD-11.0-CURRENT-amd64-20150302-r279514-bootonly.iso) > on IBM HS22 blade via bladecenter's kvm but I faced with problem on checksum > stage, bootonly doesn't contain base, kernel,etc distributions but it contain > manifest file. > On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz and > MANIFEST, sha256 sums from _local_ manifest doesn't match sha256 sums for > fetched files. I suppose it will be fine with RELEASE bootonly iso but not > with stable/current. > there is 2 ways how we can handle it: > 1) download remote MANIFEST if spotted checksum mismatch and trying to use it > 2) allow user to continue installation with 'broken' distributions > > I had to first put 10.1 then update it to HEAD :( > > What do you think ? > replying to myself :) possible way. #3: distribution filenames must contain svn revision. On checksum stage we can easy check does local MANIFEST actual or we must use remote file... -- wbr, tiger