Date: Wed, 22 Apr 2015 15:43:25 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: freebsd-stable@freebsd.org Subject: Re: bsdinstall support for multiple kernels Message-ID: <20150422154325.GB48698@hub.FreeBSD.org> In-Reply-To: <20150422153300.GU1394@zxy.spb.ru> References: <20150422111334.GS1394@zxy.spb.ru> <20150422111844.GA31769@hub.FreeBSD.org> <20150422112822.GT1394@zxy.spb.ru> <20150422115559.GB31769@hub.FreeBSD.org> <20150422120706.GH9114@zxy.spb.ru> <20150422121037.GC31769@hub.FreeBSD.org> <20150422153300.GU1394@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--rS8CxjVDS/+yyDmU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 22, 2015 at 06:33:00PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Apr 22, 2015 at 12:10:37PM +0000, Glen Barber wrote:
>=20
> > On Wed, Apr 22, 2015 at 03:07:06PM +0300, Slawa Olhovchenkov wrote:
> > > On Wed, Apr 22, 2015 at 11:55:59AM +0000, Glen Barber wrote:
> > >=20
> > > > On Wed, Apr 22, 2015 at 02:28:22PM +0300, Slawa Olhovchenkov wrote:
> > > > > On Wed, Apr 22, 2015 at 11:18:44AM +0000, Glen Barber wrote:
> > > > > > > bsdinstall don't ask about kernel.VSTREAM and don't install k=
ernel.VSTREAM.
> > > > > > >=20
> > > > > > > What I miss?
> > > > > >=20
> > > > > > Currently, the installer only installs GENERIC.
> > > > > >=20
> > > > > > I have fixes for this in a projects branch, but it's not ready =
to merge
> > > > > > back to head just yet. (^/projects/release-install-debug if yo=
u're
> > > > > > interested.)
> > > > >=20
> > > > > I think also exist bug in scripts/make-manifest.sh:
> > > > >=20
> > > > > [...]
> > > > > eval: ${kernel....}: Bad substitution
> > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >=20
> > > > Yes, you are correct. This is also fixed in the projects branch.
> > >=20
> > > O, I see.
> > > Can you also patch release/Makefile?
> > >=20
> > > =3D=3D=3D
> > > .if !empty(TARGET:M${_V})
> > > OSRELEASE=3D ${TYPE}-${REVISION}-${BRANCH}-${TARGET}
> > > VOLUME_LABEL=3D ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGE=
T}
> > > .else
> > > OSRELEASE=3D ${TYPE}-${REVISION}-${BRANCH}-${TARGET}-${TARGET_AR=
CH}
> > > VOLUME_LABEL=3D ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGE=
T_ARCH}
> > > .endif
> > > =3D=3D=3D
> > >=20
> > > For BRANCH/REVISION like 10.1-RELEASE-p276179 label exceed limit:
> > > length(10_1_RELEASE_p281264_amd64_UEFIBO) =3D 33.
> > >=20
> >=20
> > I'm not sure there's much we really can do about this just yet. The
> > only solution I have for you at the moment is to set VOLUME_LABEL in
> > your build environment to exclude the patch version.
>=20
> Can you see to 'release.sh'?
> release.sh do 'make -C release release' w/o `make -C release clean`.
> As result don't rebuild images.
>=20
This is actually intentional, so a subsequent invocation of release.sh
does not clobber an existing build.
Glen
--rS8CxjVDS/+yyDmU
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVN8GdAAoJEAMUWKVHj+KTlroP/AwfAFsD5tnr3OP0S0yyFFWG
lM3+f5Vfh/Okf5ULAOdkN0EfpYkAsI4nq7G047aHFtubhsrYdFXzTuAJtJA2cP+/
mipyzmC/gEq6zo2uuZDEEBtwhDUmnBYb1K8fAO5pKEjhlDWMAVstKogz/GAzUBNy
kxBQBBuqy1HboVQuH/7ivgo65uA6kgWKEcwAIxrhm+RwEwGlQ8LCwNJNZjqjMRu7
sgN3Ylr0ew0Y2wxazFB4XE/mOxCQf5Dw2Bg/3L5hJS36hD1vyiQ47CwhhoDyeu3j
wqpUjsyF0c/XWBKW/Rdlgr+cUMUVVAfcNTWdWi4aD0sTMU3uVwQXpdDrrd1AJuzC
ZAi6/lde+2CnIQNGl4TJMNVkuV/A02yk9OKz4sYlwVo4btog3UPOjuvURa7mgG68
j+pCM0E1XXZuIjT/USk1kPoSxBX9/N5zff3vJU7NXDFOCssoA3ei5B3FbX+Km5ox
AZ0cBlhkkBqPE9vG+DvHn18LNqdjnP1WUMnyvb1vNZSacBbreMUMIPRHDxkPyml8
l0cIUTBw20i27o6jssaOpQYcMDH9ZX6/vOT7PdfB0dIbDN3duV+LbgV0KssmLrWv
TB0UN854cotPooxLjh0THcaba/zVmSKKVFX8vLPRGvcfM/W9PtqRiqYKHjQmJZsD
/5cPP+sFDjiGoOjcYT4L
=2Xz+
-----END PGP SIGNATURE-----
--rS8CxjVDS/+yyDmU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150422154325.GB48698>