--B4IIlcmfBL/1gGOG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.12.16 15:48:20 -0800, Jeremy C. Reed wrote:
| The INSTALL docs talk briefly about doing an upgrade using sysinst.
|=20
| It also says "The upgrade to NetBSD2.1 is a binary upgrade; it can be=20
| quite difficult to update the system from an earlier version by=20
| recompiling from source, primarily due to interdependencies in the variou=
s=20
| components."
|=20
| That doesn't seem true.

Maybe it was in the past.

| I have done many source upgrades (such as using=20
| src/build.sh). It is normal. Could this sentence (from=20
| src/distrib/notes/common/upgrade) be made more clear or precise as to whe=
n=20
| the source based upgrade doesn't work??
|=20
| I am looking for docs for manually doing upgrade via binary sets without=
=20
| using sysinst, such as
| - retrieve tarballs
| - backup kernel
| - extract kernel

  - reboot using new kernel
  - extract libs and other sets

| - extract etc set to somewhere other than etc
| - use postinstall
| - use etcupdate

[ommitted]

| - reboot
|=20
| I saw basic steps in the "Tracking NetBSD-current" webpage but it is not=
=20
| specific to doing an upgrade for official release.
| I also didn't see any mention of this is NetBSD Guide nor elsewhere in=20
| htdocs.

I was hoping to integrate some decent information into the NetBSD
guide about building the system and crossbuilding but then I
thought twice and began more inclined in doing the BUILDING man
page. I prefer to have a man page than a web page.

|=20
| Can someone point me to the docs for this?
|=20
| (I have done the upgrade many times, but now was loking for docs on=20
| postinstall in particular and then realized that all the documentation fo=
r=20
| binary upgrades appear to be missing.)

Not me..

| Do we have a "todo" list for the NetBSD Guide?

No, I don't think so.

|=20
| This reminds me ... probably the Documentation/current parts can be made=
=20
| less specific to just -current and this merged into Guide. And point to=
=20
| that URL instead of having different docs to maintain.

That was (my) the plan.

| Same thing for INSTALL documentation. Maybe should simplify this. Take ou=
t=20
| parts and merge into Guide and then point to Guide as needed for more=20
| details.

I think everything that makes sense should go to the guide. It's a
very organized documented and searching for something is a lot easier
than searching the netbsd.org webiste, unfortunately.

		-- Rui Paulo

--B4IIlcmfBL/1gGOG
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDo1n1ZPqyxs9FH4QRAuXFAKCDY5rFEPrKloUfsSnTDVJqLkkWggCfRwc2
8nLlF4k7JK236QkmX0R8Ibc=
=jfYh
-----END PGP SIGNATURE-----

--B4IIlcmfBL/1gGOG--