Re: update strategies

[Aristedes Maniatis]

OK. This is where I get confused. I thought that the point of putting these applications into the base FreeBSD distribution was that they need to be tightly integrated into the OS. I understand that this is critical for basic system tools like "adduser". It appears this makes it important to build the whole distribution together (buildworld) and not get one tool out of sync with the rest.

But if this is not the case, and we are supposed to build portions of the /usr/src/ without rebuilding the whole thing, why aren't these tools in /usr/ports?

I'm new here, so I'm not telling you how to suck eggs. Perhaps there are historical reasons for this hierarchy. But I want to make sure I do the right thing. Is this the safest approach:

* install ports for named, ssh, etc.
* disable the base FreeBSD distributions of these tools
* use cvsup to update these tools whenever I need to because of security/bugs/features
* use cvsup to update base FreeBSD (src-all) for each tagged release (every 3 months or sooner in case of problems). Or less often if the update doesn't look important. Then buildworld to build a consistent FreeBSD release.


Cheers
Ari Maniatis



On Sunday, December 8, 2002, at 12:40 PM, David Magda wrote:

You don't have to rebuild world:

# cd /usr/src/usr.sbin/named
# make
# make install

should work fine. The resultant binary after the 'make' is in the
/usr/obj hierachy.

-------------------------->
ish group pty ltd
7 Darghan St Glebe 2037 Australia
phone +61 2 9660 1400   fax +61 2 9660 7400
http www.ish.com.au | email [EMAIL PROTECTED]
PGP fingerprint 08 57 20 4B 80 69 59 E2  A9 BF 2D 48 C2 20 0C C8


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message