From owner-freebsd-rc@FreeBSD.ORG Wed May 12 11:53:51 2004 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5003B16A4CE for ; Wed, 12 May 2004 11:53:51 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC5443D41 for ; Wed, 12 May 2004 11:53:50 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i4CIros0020210; Wed, 12 May 2004 11:53:50 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i4CIrolA020209; Wed, 12 May 2004 11:53:50 -0700 Date: Wed, 12 May 2004 11:53:50 -0700 From: Brooks Davis To: freebsd-rc@freebsd.org Message-ID: <20040512185350.GA17713@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline User-Agent: Mutt/1.5.4i cc: lukem@netbsd.org Subject: rcorder keep list X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to /etc/rc.d design and implementation. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 18:53:51 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable While working on some diskless cluster support I realized that it would be useful to be able to run initdiskless (and its requirement preseedrandom) before the main rcorder run. This would allow inserting new scripts using /conf to reduce the number of modifications required to the source tree. The obvious thing to do seemed to be to tag scripts that need to run before the main rcorder run in some way. I tried taging them with an early keyword, but ran into a problem with rcorder because I then need to check for both FreeBSD and early keywords. I was suprised to discover that keep lists are evaluated as an OR operation so you only need to have one of they keyword. The only way I can see to evaluate them with AND is something like: files=3D`rcorder -k keyword1 /etc/rc.d/*` files=3D`rcorder -k keyword2 ${files}` This seems to be a somewhat expensive solution. Also, the documentation is a bit vague. I'd tend to read it as an AND not an OR list, but I'm not 100% sure and I've got an obvious bias: -k Add the specified keyword to the ``keep list''. If any -k opt= ion is given, only those files containing the matching keyword are listed. Is the current implemenation correct? If so, should we add the ability to make the list evaluate as AND instead of OR or even change the behavior? -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAonKaXY6L6fI4GtQRAnpzAKCh0Tdp4ZPBGF9A9dEn0sm73jRsnACg0vYU 9Aj8FttOlV2c0BAQ1uDmYJw= =02U3 -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--