FreeBSD-src - Raptor Engineering's fork of pfsense FreeBSD src with pfSense changes

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove the absolute count g_access_abs() function since experience has	phk	2004-02-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	shown that it is not useful. Rename the relative count g_access_rel() function to g_access(), only the name has changed. Change all g_access_rel() calls in our CVS tree to call g_access() instead. Add an #ifndef BURN_BRIDGES #define of g_access_rel() for source code compatibility.
*	Use __FBSDID().	obrien	2003-06-11	1	-2/+3
\| \| \| \|	Approved by: phk
*	Remove the G_CLASS_INITIALIZER, we do not need it anymore.	phk	2003-05-31	1	-1/+0
\|
*	Use g_slice_spoiled() instead of g_std_spoiled().	phk	2003-05-02	1	-1/+1
\|
*	Back out all the stuff that didn't belong in the last commit.	phk	2003-05-02	1	-6/+2
\|
*	Use g_slice_spoiled() rather than g_std_spoiled().	phk	2003-05-02	1	-2/+6
\| \| \| \|	Remember to free the buffer we got from g_read_data().
*	Time has run from the "run GEOM in userland" harness, and the new regression	phk	2003-04-13	1	-9/+0
\| \| \| \| \| \| \|	test is built to test GEOM as running in the kernel. This commit is basically "unifdef -D_KERNEL" to remove the mainly #include related code to support the userland-harness.
*	Premptively change initializations of struct g_class to use C99	phk	2003-03-24	1	-3/+2
\| \| \| \| \|	sparse struct initializations before we extend the struct with new OAM related member functions.
*	Add some comments about the deficiencies of this module. I had hoped to get	gordon	2003-02-07	1	-0/+7
\| \| \| \| \|	around to addressing them some more, but Real Life (tm) has gotten in the way.
*	Correct a comment. GEOM modules do not create /dev entries. They create	gordon	2003-02-03	1	-2/+2
\| \| \| \| \| \|	providers. Pointed out by: phk
*	Add the GEOM module that makes volume labels useful. A kernel compiled with	gordon	2003-02-03	1	-0/+146
	this will cause volume labels to be exposed in /dev/vol/<volname>. Currently, there is no conflict resolution if more than one FS has the same volume name. Reviewed by: phk