Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.EDU.AU!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!news.sprintlink.net!news.seanet.com!news.seanet.com!michaelv
From: michaelv@MindBender.HeadCandy.com (Michael L. VanLoon)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: Re: netbsd 1.0A source
Date: 31 Oct 1995 08:20:31 GMT
Organization: HeadCandy Associates... Sweets for the lobes.
Lines: 76
Message-ID: <MICHAELV.95Oct31002034@MindBender.HeadCandy.com>
References: <95Oct27.221010edt.9375@marvin.cdf.toronto.edu>
<MICHAELV.95Oct28233633@MindBender.HeadCandy.com>
<jdd.815088275@cdf.toronto.edu>
NNTP-Posting-Host: mindbender.seanet.com
In-reply-to: jdd@cdf.toronto.edu's message of Mon, 30 Oct 1995 21:24:35 GMT
In article <jdd.815088275@cdf.toronto.edu> jdd@cdf.toronto.edu (John DiMarco) writes:
michaelv@MindBender.HeadCandy.com (Michael L. VanLoon) writes:
>In article <95Oct27.221010edt.9375@marvin.cdf.toronto.edu> jdd@cdf.toronto.edu (John DiMarco) writes:
>On the other hand, you could go at it from the other direction. A
>fairly recent (unofficial) binary snapshot is available on
>ftp.wasabi.com. It should match closely the current sources.
That's a more reasonable option than pretending that the NetBSD-Current
sources correspond to the 1.0A binary release (six months out of date is
worse than one month), but I noticed the release on ftp.wasabi.com has the
same problem as 1.0A: the sources used to generate the release are not made
available. Surely it cannot be too much trouble to tar up and release the
sources at the same time a binary release is cut?
Not an unreasonable request. But, also not as necessary, since recent
sources and recent binary snapshots are usually close enough in
functionality that you can get to one with the other.
In any case, since the only sources that seem to be available are 1.0
and Current (Oct 30th), I'll have to decide whether or not to run 1.0
or compile a copy of Current.
The better scenario I find (and, indeed, the only way I'll bother
upgrading from 1.0 to current) is to:
1) Get the latest source tarballs I can find, download them, untar
them.
2) Download the most recent binary snapshot I can find.
3) Create a new config file for the kernel I will want when I
upgrade (the current sources use "new" config, whereas 1.0 used
"old" config -- there are some syntactical differences in the
kernel config files).
4) Back up the old binaries to a safe but accessible place (if you
have enough disk space). Move the new kernel into place, but
leave the old kernel in the root partition so you can boot it
if necessary.
5) Reboot with the new kernel in place, giving basic
functionality. In the most crude situations, you may only be
able to come up in single-user mode. (I had to build my new
kernel in single-user mode, but was able to come up multi-user
with my newly-built kernel.)
6) Untar the new binaries over the old ones. Reboot with the new
kernel again.
7) Build your new custom kernel. Reboot. (Repeat if necessary.)
8) If you were successful, you're up and running on current. Now
just rebuild the rest of the system. Don't forget to "make
install" /usr/src/include and /usr/src/share/mk first.
9) If everything went down in a mountain of flames, move your old
kernel and binaries back in place and try again some other
time.
Note that this is MUCH easier than trying to do a compile-only upgrade
(which, at this point, is almost impossible).
Also note that for emergency purposes, I have a statically linked copy
of gzip and tar in my /root/bin directory.
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Michael L. VanLoon michaelv@HeadCandy.com
--< Free your mind and your machine -- NetBSD free un*x >--
NetBSD working ports: 386+PC, Mac 68k, Amiga, HP300, Sun3, Sun4,
DEC PMAX (MIPS), DEC Alpha, PC532
NetBSD ports in progress: VAX, Atari 68k, others...
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -