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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use err(3). Add usage() and #includes.	charnier	1997-10-13	5	-52/+58
\|
*	Typo fix: ${.DESTDIR} -> ${DESTDIR}.	asami	1997-05-23	1	-2/+2
\| \| \| \|	Reviewed by: bde
*	Fixed type mismatch caused by bogus prototypes. rpcgen for some reason	bde	1997-04-15	1	-2/+2
\| \| \| \|	doesn't generate any prototypes for the functions to be registered.
*	Typo police.	mpp	1997-03-16	1	-2/+2
\| \| \| \|	Partially obtained from: NetBSD PR# 3333
*	Revert $FreeBSD$ to $Id$	peter	1997-02-22	1	-1/+1
\|
*	Sort cross references.	wosch	1997-01-20	1	-2/+2
\|
*	Make the long-awaited change from $Id$ to $FreeBSD$	jkh	1997-01-14	1	-1/+1
\| \| \| \| \| \| \| \|	This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
*	rpc.rstatd -> rpc.lockd typo	peter	1996-08-16	1	-1/+1
\| \| \| \|	Noticed by: tholo@sigmasoft.com (Thorsten Lockert)
*	Correct the rpc.lockd and rpc.statd man pages to not reference	mpp	1996-04-07	1	-3/+3
\| \| \| \| \| \|	their path names in the synopsis line (especially since they referenced the wrong path!). Corrected some other minor problems with the rpc.lockd man page.
*	Tweaks for the stub lockd.	peter	1996-04-01	6	-242/+46
\| \| \| \| \| \| \|	- Use rpcgen to generate the unmodified boilerplate code rather than having it in the repository. - Eliminate the conflicting function names by changing them to their "natural" rpcgen generated names
*	Import Jan 15 version of Andrew Gordon <andrew.gordon@net-tel.co.uk>'s	peter	1996-02-17	7	-0/+1481
	stub lockd. This implements just the protocol, but does not interact with the kernel. It says "Yes!" to all requests. This is useful if you have people using tools that do locking for no reason (eg: some PC NFS systems running some Microsoft products) and will happily report they couldn't lock the file and merrily proceed anyway. Running this will not change the reliability of sharing files, it'll just keep it out of everybody's face.