On 2015-03-23 01:52, Sergey V. Dyatko wrote:
> On Mon, 23 Mar 2015 08:47:38 +0300
> "Sergey V. Dyatko" <sergey.dya...@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 ?
>>
>
> 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
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> I have worked around this by doing: mount -t tmpfs tmpfs /usr/freebsd-dist This hides the MANIFEST file shipped on the bootonly image, and when there is no local MANIFEST to compare it, it fetches one from FTP along with the dist files, and just works. I am unsure what the best way to handle this properly is though. -- Allan Jude
signature.asc
Description: OpenPGP digital signature
