Date: Mon, 23 Mar 2015 01:55:45 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: bsdinstall and current (possible stable) snapshots Message-ID: <550FAAE1.8060201@freebsd.org> In-Reply-To: <20150323085222.3aaea668@laptop.minsk.domain> References: <20150323084738.70f7db7b@laptop.minsk.domain> <20150323085222.3aaea668@laptop.minsk.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--JnRP18JBsI4IUTMlAkeWQE9DHMC1phK9P
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On 2015-03-23 01:52, Sergey V. Dyatko wrote:
> On Mon, 23 Mar 2015 08:47:38 +0300
> "Sergey V. Dyatko" <sergey.dyatko@gmail.com> wrote:=20
>=20
>> 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 ch=
ecksum
>> stage, bootonly doesn't contain base, kernel,etc distributions but it =
contain
>> manifest file.=20
>> On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz an=
d
>> 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=20
>>
>> I had to first put 10.1 then update it to HEAD :(
>>
>> What do you think ?
>>
>=20
> 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...
>=20
>=20
> --
> wbr, tiger
>=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o=
rg"
>=20
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.
--=20
Allan Jude
--JnRP18JBsI4IUTMlAkeWQE9DHMC1phK9P
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQIcBAEBAgAGBQJVD6rkAAoJEJrBFpNRJZKfQpsQAJiMZLg11iCQzKGDIgeOU+YW
Cfs+hwZLHeIBpG9/hDioCIGMfi/Vafchm7tUVQ+RZ1NLCuzbrNVl5ai8j/q/I19W
NyB1PoAdHF/scxHtM4jM+Aub5mNHus2+9REkE8EvsRqFThZUFtuRKCzuMG6AajId
5ROielqTU1uG9/5Ywd2YsbJw4RTnvSAYnEFwJcUhfzVciRulquNAr0gIqUq3kP+Z
63URa3L9VP8BkEoCHWfum14ocwUhQ+6ykWpNi7tlC3uaQp/T48SJ3oEOoQvVVMc/
V1aAgR1Kulw+SRk+P6p0zM3KfrHPAAdSZTBjKKQA0n1Z9DmWQra59gQXMoDfKIXl
h12OsJy1H6g/Np9TqwoCXTvsZC3tbpmsMFvSTq80h9zFd9gY082/3tS23D+mtbfl
l3LQOL2V/74bYpp/WtY9x3KXZNbAH4JXwj93ZF5iA7ko2emlO3JO2xvIstsHFZu1
uOfnjezjYCDF/CZJXN1i2gn4CYPGufMRT+iHiYN/n9hRW7YVPdCT3QCW8fMHE8Oe
cIeQobnJBB9PEFEJfnGnhwG3pitgs0ceQGN7Mvs3yhGR882X3hrCQ23m06eBNdhO
nqq1l2hhTPJ3YCZ5alyVBNneHrU8MpZ45uSnOOgvjWiBSUGTgP8U1trhjMylLrm6
yFJKlClt14hpD+5JXZ+3
=lAoA
-----END PGP SIGNATURE-----
--JnRP18JBsI4IUTMlAkeWQE9DHMC1phK9P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?550FAAE1.8060201>