NetBSD

History

elad 53ca19a3b3 First part of secmodel cleanup and other misc. changes: - Separate the suser part of the bsd44 secmodel into its own secmodel and directory, pending even more cleanups. For revision history purposes, the original location of the files was src/sys/secmodel/bsd44/secmodel_bsd44_suser.c src/sys/secmodel/bsd44/suser.h - Add a man-page for secmodel_suser(9) and update the one for secmodel_bsd44(9). - Add a "secmodel" module class and use it. Userland program and documentation updated. - Manage secmodel count (nsecmodels) through the module framework. This eliminates the need for secmodel_{,de}register() calls in secmodel code. - Prepare for secmodel modularization by adding relevant module bits. The secmodels don't allow auto unload. The bsd44 secmodel depends on the suser and securelevel secmodels. The overlay secmodel depends on the bsd44 secmodel. As the module class is only cosmetic, and to prevent ambiguity, the bsd44 and overlay secmodels are prefixed with "secmodel_". - Adapt the overlay secmodel to recent changes (mainly vnode scope). - Stop using link-sets for the sysctl node(s) creation. - Keep sysctl variables under nodes of their relevant secmodels. In other words, don't create duplicates for the suser/securelevel secmodels under the bsd44 secmodel, as the latter is merely used for "grouping". - For the suser and securelevel secmodels, "advertise presence" in relevant sysctl nodes (sysctl.security.models.{suser,securelevel}). - Get rid of the LKM preprocessor stuff. - As secmodels are now modules, there's no need for an explicit call to secmodel_start(); it's handled by the module framework. That said, the module framework was adjusted to properly load secmodels early during system startup. - Adapt rump to changes: Instead of using empty stubs for securelevel, simply use the suser secmodel. Also replace secmodel_start() with a call to secmodel_suser_start(). - 5.99.20. Testing was done on i386 ("release" build). Spearated module_init() changes were tested on sparc and sparc64 as well by martin@ (thanks!). Mailing list reference: http://mail-index.netbsd.org/tech-kern/2009/09/25/msg006135.html		2009-10-02 18:50:12 +00:00
..
lists	First part of secmodel cleanup and other misc. changes:	2009-10-02 18:50:12 +00:00
attrs
checkflist	Simplify the way EXCLUDE_REGEXP is built.	2009-04-23 09:30:56 +00:00
comments	Remove LKMs and switch to the module framework, pass 1.	2008-11-12 12:35:50 +00:00
culldeps
deps	Remove LKMs and switch to the module framework, pass 1.	2008-11-12 12:35:50 +00:00
descrs	Remove LKMs and switch to the module framework, pass 1.	2008-11-12 12:35:50 +00:00
getdirs.awk
join.awk
listpkgs
Makefile	Only generate SHA512 and MD5 checksums for releases.	2009-09-19 07:09:53 +00:00
makeflist
makeobsolete
makeplist
makesrctars	Only generate SHA512 and MD5 checksums for releases.	2009-09-19 07:09:53 +00:00
makesums	Only generate SHA512 and MD5 checksums for releases.	2009-09-19 07:09:53 +00:00
maketars	If there are errors in creating a ${set}.tgz tar file, then don't	2009-09-12 11:01:55 +00:00
README	mention ./etc/mtree/set.<set name>	2009-09-12 09:24:32 +00:00
regpkg	Consistently use gzip with the -n flag so dates are not embedded.	2009-04-03 22:36:34 +00:00
regpkgset
sets.subr	Multicast DNS ("Bonjour") support, based on Apple's mDNSResponder.	2009-09-29 23:56:26 +00:00
syspkgdeps
TODO
versions

README

# $NetBSD: README,v 1.11 2009/09/12 09:24:32 jnemeth Exp $

the scripts should be run from the directory where they reside.

makeflist:	output the list of files that should be in a
		distribution, according to the contents of the
		'lists' directory.

checkflist:	check the file list (as internally generated
		by makeflist) against the tree living in $DESTDIR.
		(that tree should be made with 'make distribution'.)

maketars:	make tarballs of the various sets in the distribution,
		based on the contents of the lists, the tree in
		$DESTDIR, and put the tarballs in $RELEASEDIR.
		Note that this script _doesn't_ create the 'secr'
		distribution, because (for now) it requires
		manual intervention to get the binaries right...
		(i'll add another script to create that dist, later.)

what's in 'lists':

lists describing file sets.  There are two sets of lists per file
set: machine dependent and machine-independent files. (there's
also another file in the 'man' dir, which is used by the 'man'
and 'misc' sets, but that's explained later.)

There is one machine-independent file, named "mi".  There are
N machine-dependent files (one per architecture), named "md.${ARCH}".

the sets are as follows:

	base:	the base binary set.  excludes everything described
		below.

	comp:	compiler tools.  All of the tools relating to C, C++,
		and FORTRAN (yes, there are two!) that are in the
		tree.  This includes includes, the linker, tool chain,
		and the .a versions of the libraries.  (obviously,
		base includes ldd, ld.so, and the shared versions.
		base also includes 'cpp', because that's used by X11.)
		includes the man pages for all the binaries contained
		within.  Also, includes all library and system call
		manual pages.

	etc:	/etc, and associated files (/var/cron/tabs, /root,
		etc.).  things that shouldn't be blindly reinstalled
		on an upgrade.

	games:	the games and their man pages.

	man:	all of the man pages for the system, except those
		listed elsewhere (e.g. in comp, games, misc, text).
		Includes machine-dependent man pages for this CPU.

	misc:	share/dict, share/doc, and the machine-dependent
		man pages for other CPUs which happen to always
		be installed.

	modules:	stand/${MACHINE}/${OSRELEASE}/modules kernel modules

	tests:	unit, regression, integration and stress tests for the
		whole system.

	text:	text processing tools.  groff and all of its friends.
		includes man pages for all bins contained within.


as noted, in addition to the "standard" files in each dir, there's
a file called 'md_share' in lists/man.  it's the list of man pages
that are installed from /usr/src/share, which are machine-dependent.
(note that ones that are installed from elsewhere, and thus are
installed on only one architecture, are listed in the md.${ARCH}
file.)  basically, it's grepped through, to see which of the
machine-dependent man pages that are always installed should go
in the 'man' set, and which should go into the 'misc' set.

Each set must contain "./etc/mtree/set.<set name>" within the mi
list.  Failure to add this will break unprivileged builds.