Date: Mon, 23 Mar 2015 09:06:09 -0700 From: Devin Teske <dteske@FreeBSD.org> To: "Sergey V. Dyatko" <sergey.dyatko@gmail.com> Cc: Devin Teske <dteske@FreeBSD.org>, freebsd-current@freebsd.org Subject: Re: bsdinstall and current (possible stable) snapshots Message-ID: <5762F1B8-771F-469C-9B93-AB6477C1C90D@FreeBSD.org> In-Reply-To: <20150323084738.70f7db7b@laptop.minsk.domain> References: <20150323084738.70f7db7b@laptop.minsk.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mar 22, 2015, at 10:47 PM, Sergey V. Dyatko <sergey.dyatko@gmail.com> 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 ?
When I get some time I’ll have a look and see what I can do.
—
Cheers,
Devin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5762F1B8-771F-469C-9B93-AB6477C1C90D>