*BSD News Article 24969


Return to BSD News archive

Xref: sserve comp.os.386bsd.misc:1721 comp.os.386bsd.questions:7428
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!ogicse!emory!europa.eng.gtefsd.com!library.ucla.edu!agate!fsa.ca!deraadt
From: deraadt@fsa.ca (Theo de Raadt)
Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions
Subject: Re: Updating to current
Message-ID: <DERAADT.93Dec13222523@newt.fsa.ca>
Date: 14 Dec 93 06:25:23 GMT
Article-I.D.: newt.DERAADT.93Dec13222523
References: <2ej7v4INN75v@flop.engr.orst.edu> <2ejfcj$d09@homer.cs.mcgill.ca>
Organization: little lizard city
Lines: 26
NNTP-Posting-Host: newt.fsa.ca
In-reply-to: storm@cs.mcgill.ca's message of 14 Dec 1993 04:28:03 GMT

In article <2ejfcj$d09@homer.cs.mcgill.ca> storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
   I work with NetBSD, so I will describe this for NetBSD-current.

Marc's description of the process is excellent. Of course, as he notes,
a week from now it might be different... this is an active source tree,
and if you want to track it does take a bit of pain.

I do one thing different from Marc: I compile everything STATIC --
that's right, no shared libraries. I don't bother with them at the
moment, and hey, someone should insure that static executables
continue to work :-)

If you want to have an easier time you can continue to build your
system with static libraries. This is actually quite a bit easier, and
*everything* compiles cleanly. You do not lose any functionality, just
a bit of disk space. I've got a 4G of disk at home so ... what's a few
megs between friends?

Just a few hours ago I did the following (actually, I first did a few
preliminaries that Marc describes very well)

    # make clean && make obj && make && make install && reboot

And the machine did reboot after rebuilding everything correctly.
--
This space not left unintentionally unblank.		deraadt@fsa.ca