Subject: Re: Suggested addition to build.sh
To: None <tech-toolchain@netbsd.org>
From: gabriel rosenkoetter <gr@eclipsed.net>
List: tech-toolchain
Date: 04/12/2002 13:24:01
--qyHYMwAXsHLOQihY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Apr 12, 2002 at 12:00:52PM +0100, David Brownlee wrote:
> How about an option to build a generic kernel into $DESTDIR?
> (Standard warnings about installing into /)
>=20
> It could be used on its own, or as part of a -d build.
>=20
> This is prompted by a question on the sparc list from someone
> who had a 1.5.x sparc box, and wanted to upgrade to -current.
>=20
> Just looking for the simplest answer to give to them :)
Shouldn't they really ./build.sh -R <something>, then install as
appropriate?
Something like:
- install new kernel from ${RELEASEDIR}/binar/kernel/netbsd-GENERIC.gz
- boot -s
- cd / ; for i in ${RELEASEDIR}/binary/sets/{base,comp,games,man,misc,text}=
.tgz
do pax -r -pe -z -f $i ; done
- update /etc by hand, if necessary (and it will be going from 1.5-release
to 1.5-current)
- reboot (or just log out; but things like IPF get unpleasant about
their ioctls if you don't reboot)
I mean, isn't taking something from $DESTDIR into a working system
actually *harder* than unpacking a release, especially for the
unitiated?
--=20
gabriel rosenkoetter
gr@eclipsed.net
--qyHYMwAXsHLOQihY
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjy3GDEACgkQ9ehacAz5CRp9lQCfSeBnRRXTH1q4ZhOHgXsIbEgW
HzYAn2N1LsTs2mer8LoM8QKoVVhKilo0
=AnK1
-----END PGP SIGNATURE-----
--qyHYMwAXsHLOQihY--