Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!library.ucla.edu!europa.eng.gtefsd.com!MathWorks.Com!news.duke.edu!convex!cs.utexas.edu!geraldo.cc.utexas.edu!dopey.cc.utexas.edu!not-for-mail From: vax@dopey.cc.utexas.edu (Vax) Newsgroups: comp.os.386bsd.questions Subject: [NetBSD] Help me sup(1) to -current! Date: 30 Jun 1994 02:35:45 -0500 Organization: The University of Texas - Austin Lines: 24 Message-ID: <2utskh$dpp@dopey.cc.utexas.edu> NNTP-Posting-Host: dopey.cc.utexas.edu There is nothing in any of the FAQs about how one should sup(1) to -current, as far as I can tell. As a 386BSD-0.1 -> pk -> NetBSD-0.[89] user, I know there are a few pitfalls in upgrading your OS. As I understand it, new binaries may not work with old kernels, and so forth, so; How (exactly) do I go about upgrading? What is the stability of -current? My first guess would be: 1) get and compile sup 2) get floppies, and kernel, and new binaries (can this be done in one swell foop?) 2.5) copy those floppies (for recovery purposes) 3) reboot and cross fingers 4) get sources for kernel, libs, include files, gcc/gas/ in that order (more or less) 5) recompile 6) get sources for other progs; recompile Will new kernels run old binaries? PS: If you know a NetBSD-0.9 archive maintainer, have them mail me regarding a fixit-style disk I made for recovering damaged systems from /dev/st -- Protect our endangered bandwidth - reply by email. NO BIG SIGS! VaX#n8 vax@ccwf.cc.utexas.edu - Don't blame me if the finger daemon is down