installing trusted patches

[Ilmar S. Habibulin]

On 14 Mar 2002, Jeff Heath wrote:

> please point me in the direction of some directions?
You need not to use patches. ACLs are in the base -current distribution.
So you can grab them from freebsd cvs. And CAPs, MAC and audit are in p4
repository, here is the instraction how to get them via cvsup:


As many of you know, we've migrated most of the new TrustedBSD development
to the FreeBSD Project's Perforce repository.  Perforce is a commercial
source code revision control product, made available for free use to the
Open Source community, which makes possible the tracking of a central
"moving target" source distribution while maintaining local version
control, something that CVS did not permit and substantially hampered
progress.  The FreeBSD Project continues to use CVS as it's primary
version control system, and that's where the "official" tree is, but the
use of P4 allows side projects to work much more effectively.

The TrustedBSD source code in Perforce is regularly exported to a cvsup
server for access via the cvsup network tool.  You can pull down either a
snapshot of the source code as it currently stands, or you can pull down a
snapshot of the TrustedBSD revision history in the form of a CVS
repository, making it easier to maintain local patches against the
TrustedBSD code.  Ilmar has had cvsup up and running for a few days
pulling down the MAC code, so I figured I'd publish the instructions more
generally for those that are interested.  You'll need to install cvsup,
which is available as a binary package for supported FreeBSD platforms, as
well as for many other platforms (it is widely used for CVS repository
replication and rapid file transfer).  cvsup relies on a configuration
file to tell it where to find a server, and what files and revisions to
transfer.  Start with one of the standard sample cvsup configuration files
in FreeBSD's /usr/share/examples/cvsup, and then tweak as follows:

Set the host to 'cvsup10.FreeBSD.org'.  This is the only cvsup server
carrying these modules, so you can't use 'cvsup.FreeBSD.org'.

Set release=cvs, and then either 'tag=.' to check out the head, or no tag
entry to check out the repository version history.

Then select a module name from one of the following:

	p4-cvs-trustedbsd

This module pulls down all TrustedBSD branches currently exported,
including "base", the version of 5.0-CURRENT that other TrustedBSD work is
sync'd to, then MAC and the CAP trees.  Those trees may be pulled down
individually as:

	p4-cvs-trustedbsd-base
	p4-cvs-trustedbsd-mac
	p4-cvs-trustedbsd-cap

Currently, work is going on actively in both the mac and the cap trees,
modulo some slow-down over the holiday season here.  Shortly, we'll
introduce trustedbsd-audit and trustedbsd-doc trees also.  For reference,
here's a brief status statement for each tree:

trustedbsd-mac	Currently, I'm maintaining this branch, and in the process
		of merging past MAC code I've written with Ilmar's work on
		network MAC support.  As of some commits this morning,
		network booting is now supported again.  Chris Costello is
		also providing new documentation support for this branch,
		and I anticipate more NAI Labs developers working on it
		shortly.

trustedbsd-cap	This branch is fairly mature, and Brian Feldman of NAI
		Labs is currently responsible for improving its maturity
		further for integration into the base FreeBSD tree.  He's
		working to improve integration into userland, work out
		semantics issues, etc.  Chris Costello will also be
		providing documentation support for this branch.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
robert at fledge.watson.org      NAI Labs, Safeport Network Services

To Unsubscribe: send mail to majordomo at trustedbsd.org
with "unsubscribe trustedbsd-discuss" in the body of the message


To Unsubscribe: send mail to majordomo at trustedbsd.org
with "unsubscribe trustedbsd-discuss" in the body of the message