From owner-freebsd-hackers Thu Mar 2 17:20:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id D9B2D37B587 for ; Thu, 2 Mar 2000 17:20:18 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id RAA24014; Thu, 2 Mar 2000 17:16:52 -0800 (PST) Date: Thu, 2 Mar 2000 17:16:52 -0800 From: Brooks Davis To: James Howard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Keeping using locally modified source Message-ID: <20000302171652.A22288@orion.ac.hmc.edu> References: <200003030059.TAA29567@rac4.wam.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200003030059.TAA29567@rac4.wam.umd.edu>; from howardjp@wam.umd.edu on Thu, Mar 02, 2000 at 07:59:39PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 02, 2000 at 07:59:39PM -0500, James Howard wrote: > At a site I am working at, we need to be able to limit which users can > bind a socket to an address under IPv4. Basically, bind() needs to check > the caller's groups and if you are one of several allowable groups, let it > pass, otherwise, error out. > > Now, I glanced over the bind() code and it does not look that > difficult. The problem is how do we keep up with -STABLE > afterwards? Using CVSup, out changes will get clobbered every time. Is > there a facility where you can keep up with the source but let local > modifications through? Yup, just use cvsup to maintain an up to date copy of the repository localy and then cvs checkout your source tree from there. This allows you to keep in sync and keep local modifications in your tree. Updates take longer and I recommend updating ports via direct cvsup instead of via cvs checkout (it's much faster if you aren't modifying ports), but it works quite well. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message