From owner-freebsd-rc@FreeBSD.ORG Mon Jun 5 11:03:13 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 17E5416A484 for ; Mon, 5 Jun 2006 11:03:13 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2A3443D48 for ; Mon, 5 Jun 2006 11:03:12 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k55B3CaK010379 for ; Mon, 5 Jun 2006 11:03:12 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k55B3BAl010375 for freebsd-rc@freebsd.org; Mon, 5 Jun 2006 11:03:11 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 5 Jun 2006 11:03:11 GMT Message-Id: <200606051103.k55B3BAl010375@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-rc@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 05 Jun 2006 11:03:13 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- p [2006/03/12] conf/94377 rc [patch] /etc/rc.d/sshd improperly tests r 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/11/12] conf/45226 rc Fix for rc.network, ppp-user annoyance o [2003/08/24] conf/55916 rc [PATCH] ppp-user options p [2004/11/13] conf/73909 rc [patch] rc.d/sshd does not work with port o [2005/02/18] conf/77663 rc Suggestion: add /etc/rc.d/addnetswap afte o [2005/03/16] conf/78906 rc [patch] Allow mixer_enable="NO" in rc.con o [2005/05/14] kern/81006 rc ipnat not working with tunnel interfaces p [2005/06/28] conf/82738 rc [patch] add amd_program line to defaults/ o [2005/08/27] conf/85363 rc syntax error in /etc/rc.d/devfs o [2005/11/13] conf/88913 rc [patch] wrapper support for rc.subr o [2005/12/03] conf/89870 rc [patch] feature request to make netif ver o [2006/01/30] conf/92523 rc [patch] allow rc scripts to kill process o [2006/02/25] conf/93815 rc [patch] Adds in the ability to save ipfw o [2006/05/04] conf/96766 rc run_rc_command doesn't work for Python sc 13 problems total. From owner-freebsd-rc@FreeBSD.ORG Tue Jun 6 10:01:42 2006 Return-Path: X-Original-To: freebsd-rc@hub.freebsd.org Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B118C16AA4D; Tue, 6 Jun 2006 10:00:04 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4948443D45; Tue, 6 Jun 2006 10:00:04 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (flz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k56A04UD010327; Tue, 6 Jun 2006 10:00:04 GMT (envelope-from flz@freefall.freebsd.org) Received: (from flz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k56A03uH010323; Tue, 6 Jun 2006 10:00:03 GMT (envelope-from flz) Date: Tue, 6 Jun 2006 10:00:03 GMT From: Florent Thoumie Message-Id: <200606061000.k56A03uH010323@freefall.freebsd.org> To: fmysh@iijmio-mail.jp, flz@FreeBSD.org, freebsd-rc@FreeBSD.org Cc: Subject: Re: conf/82738: [patch] add amd_program line to defaults/rc.conf X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Jun 2006 10:01:47 -0000 Synopsis: [patch] add amd_program line to defaults/rc.conf State-Changed-From-To: patched->closed State-Changed-By: flz State-Changed-When: Tue Jun 6 10:00:02 UTC 2006 State-Changed-Why: MFC to RELENG_6 done. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=82738 From owner-freebsd-rc@FreeBSD.ORG Tue Jun 6 21:04:02 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 58E3416AE25 for ; Tue, 6 Jun 2006 20:53:26 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0814643D46 for ; Tue, 6 Jun 2006 20:53:25 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k56KrPiY019100 for ; Tue, 6 Jun 2006 13:53:25 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k56KrPKl019099 for freebsd-rc@freebsd.org; Tue, 6 Jun 2006 13:53:25 -0700 Date: Tue, 6 Jun 2006 13:53:25 -0700 From: Brooks Davis To: freebsd-rc@freebsd.org Message-ID: <20060606205325.GA13570@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Subject: The future of set_rcvar X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Jun 2006 21:04:08 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable We need to decide what we're doing with set_rcvar. Doug has been advocating against it in a number of forums, but no move has been made to actually deprecate it that I've seen. I believe we need to speak with one voice on this issue and have one style that is both documented for ports and used in the base. I can see three main options: - Use set_rcvar unless there is a good reason not to (generally the very few historical scripts). This is the default in the base and was the status quo in ports for a while. - Always manually set $rcvar, deprecating set_rcvar with a loud warning and removing in in 7 or 8. - The same as above, but default $rcvar to ${name}_enable requiring that scripts that don't use have an rcvar value explicitly unset it. I slightly prefer the first or third option because I don't like the idea of the default style encouraging inconsistent naming which I believe forcing rcvar to be set manually by default does. My only strong opinion on the subject is that we must make up out minds and act consistently instead of continuing the current split between ports documentation and the base. -- 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 --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEhetEXY6L6fI4GtQRAjF/AJ9v/XHXH6TZcHHuVWVnVCT/bGLX9QCbBTLE /5v9Y0/qbFy+b+ujGuR0Jss= =SkJh -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- From owner-freebsd-rc@FreeBSD.ORG Tue Jun 6 21:58:45 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 CA2E916B95C for ; Tue, 6 Jun 2006 21:47:49 +0000 (UTC) (envelope-from alex@foxybanana.com) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.192.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F36743D55 for ; Tue, 6 Jun 2006 21:47:49 +0000 (GMT) (envelope-from alex@foxybanana.com) Received: from laptop.mine.box (unknown[68.36.46.193]) by comcast.net (rwcrmhc13) with ESMTP id <20060606214747m1300jhq8ge>; Tue, 6 Jun 2006 21:47:48 +0000 Received: from Laptop.mine.box (localhost [127.0.0.1]) by Laptop.mine.box (8.13.6/8.13.6) with ESMTP id k56LlXvn059773; Tue, 6 Jun 2006 17:47:33 -0400 (EDT) (envelope-from alex@Laptop.mine.box) Received: (from alex@localhost) by Laptop.mine.box (8.13.6/8.13.6/Submit) id k56LlW3i059772; Tue, 6 Jun 2006 17:47:32 -0400 (EDT) (envelope-from alex) From: Alexander Botero-Lowry Message-Id: <200606062147.k56LlW3i059772@Laptop.mine.box> Date: Tue, 06 Jun 2006 17:47:31 -0400 To: freebsd-rc@freebsd.org, brooks@one-eyed-alien.net References: <20060606205325.GA13570@odin.ac.hmc.edu> In-Reply-To: <20060606205325.GA13570@odin.ac.hmc.edu> User-Agent: nail 11.25 7/29/05 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: The future of set_rcvar X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Jun 2006 21:58:47 -0000 One question I've always had is why FreeBSD picked to have ${name}_enable instead of just ${name} like on NetBSD? Was there a lot of debate about this, was it to make the variables less ambigious, or osmething else? I would advocate for the third option if there is really a good reason to not just do what NetBSD does. It makes it hard for packagers to use consistent rc scripts between NetBSD and FreeBSD when the $rcvar is different between the two platforms (and with a lot of stuff in ports and pkgsrc the same rc scripts could be used and even packaged with the application if upstream likes that idea). Alex Brooks Davis wrote: > We need to decide what we're doing with set_rcvar. Doug has been > advocating against it in a number of forums, but no move has been made > to actually deprecate it that I've seen. I believe we need to speak > with one voice on this issue and have one style that is both documented > for ports and used in the base. I can see three main options: > > - Use set_rcvar unless there is a good reason not to (generally the very > few historical scripts). This is the default in the base and was the > status quo in ports for a while. > - Always manually set $rcvar, deprecating set_rcvar with a loud warning > and removing in in 7 or 8. > - The same as above, but default $rcvar to ${name}_enable requiring that > scripts that don't use have an rcvar value explicitly unset it. > > I slightly prefer the first or third option because I don't like the > idea of the default style encouraging inconsistent naming which I > believe forcing rcvar to be set manually by default does. My only > strong opinion on the subject is that we must make up out minds and act > consistently instead of continuing the current split between ports > documentation and the base. > > -- Brooks > > -- > 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 From owner-freebsd-rc@FreeBSD.ORG Tue Jun 6 22:40:04 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 154D416B1C5 for ; Tue, 6 Jun 2006 22:17:20 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 474D143D9E for ; Tue, 6 Jun 2006 22:17:18 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k56MHFcv024933; Tue, 6 Jun 2006 15:17:15 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k56MHFTt024932; Tue, 6 Jun 2006 15:17:15 -0700 Date: Tue, 6 Jun 2006 15:17:15 -0700 From: Brooks Davis To: Alexander Botero-Lowry Message-ID: <20060606221715.GB13570@odin.ac.hmc.edu> References: <20060606205325.GA13570@odin.ac.hmc.edu> <200606062147.k56LlW3i059772@Laptop.mine.box> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline In-Reply-To: <200606062147.k56LlW3i059772@Laptop.mine.box> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-rc@freebsd.org Subject: Re: The future of set_rcvar X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Jun 2006 22:40:05 -0000 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 06, 2006 at 05:47:31PM -0400, Alexander Botero-Lowry wrote: > One question I've always had is why FreeBSD picked to have > ${name}_enable instead of just ${name} like on NetBSD? Was there a lot > of debate about this, was it to make the variables less ambigious, or > osmething else? My understanding is that we did it for historical reasons in the base system and in ports because they should be consistent with the base system. Changing now would be difficult and have little or no value. -- 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 --neYutvxvOLaeuPCA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEhf7qXY6L6fI4GtQRAj67AJ46rgRhVFl+oZVf2i/7Xz31CpyEiQCgiJu2 T0S4o0w8qTyYA/hDpOyr2wc= =bQ7g -----END PGP SIGNATURE----- --neYutvxvOLaeuPCA-- From owner-freebsd-rc@FreeBSD.ORG Tue Jun 6 23:12:02 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 5056016D77F for ; Tue, 6 Jun 2006 22:43:07 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79B6B43D55 for ; Tue, 6 Jun 2006 22:43:03 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 96960 invoked by uid 0); 6 Jun 2006 22:42:58 -0000 Received: from fnord.cryptophone.de (HELO ?10.1.1.71?) (erdgeist@erdgeist.org@62.220.7.20) by elektropost.org with AES256-SHA encrypted SMTP; 6 Jun 2006 22:42:58 -0000 Message-ID: <448604F0.9070406@erdgeist.org> Date: Wed, 07 Jun 2006 00:42:56 +0200 From: Dirk Engling User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: freebsd-rc X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: New feature exec_afterstart X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Jun 2006 23:12:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, while incorporating some of the jail options grouping stuff into /etc/rc.d/jail I noticed the introduction of a new feature called "exec_afterstart". This has not been discussed here on list but yet was introduced in 1.34 and is going to be MFCed somewhere around soon. When googling around I found this: http://www.freebsd.org/cgi/query-pr.cgi?pr=97697 I do not see, what this approach yields that cannot simply be accomplished by a second jail on the same jailroot/IP-combination, correct me, if I am wrong. Further I can not see, what /bin/sh introduces in terms of system (in)security that will not happen to you if you have syscalls. The patch introduces the same ugly enumeration style that already sucks in the ifconfig rc script and should be deprecated. Correct me, if I am wrong. So I'd strongly vote to not to MFC but rather remove this feature. Btw.: Where do these kinds of discussions normally take place? I mean before things are committed. Regards erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) iD8DBQFEhgTwImmQdUyYEgkRArG7AJ9jDlwuq9jsfq+97oMirf3NBDqQDACbB051 HZm2ibjGGHMbriiwrGIjDt8= =fd4p -----END PGP SIGNATURE----- From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 00:24:58 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 08B0416BF8A; Wed, 7 Jun 2006 00:06:26 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 579C443D46; Wed, 7 Jun 2006 00:06:26 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id CBD0A1172F; Wed, 7 Jun 2006 02:06:24 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64602-01; Wed, 7 Jun 2006 02:06:01 +0200 (CEST) Received: from cream.stl.xbsd.org (unknown [193.120.13.130]) by smtp.xbsd.org (Postfix) with ESMTP id ACF2A1148C; Wed, 7 Jun 2006 02:05:59 +0200 (CEST) From: Florent Thoumie To: Dirk Engling In-Reply-To: <448604F0.9070406@erdgeist.org> References: <448604F0.9070406@erdgeist.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Gk/hHI4x9/UgF3+9Cp8A" Date: Wed, 07 Jun 2006 01:05:54 +0100 Message-Id: <1149638754.7125.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at xbsd.org Cc: matteo@FreeBSD.org, freebsd-rc , deyan.dyankov@gmail.com Subject: Re: New feature exec_afterstart X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 00:25:00 -0000 --=-Gk/hHI4x9/UgF3+9Cp8A Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2006-06-07 at 00:42 +0200, Dirk Engling wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hello, >=20 > while incorporating some of the jail options grouping stuff into > /etc/rc.d/jail I noticed the introduction of a new feature called > "exec_afterstart". >=20 > This has not been discussed here on list but yet was introduced in 1.34 > and is going to be MFCed somewhere around soon. >=20 > When googling around I found this: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D97697 >=20 > I do not see, what this approach yields that cannot simply be > accomplished by a second jail on the same jailroot/IP-combination, > correct me, if I am wrong. Further I can not see, what /bin/sh > introduces in terms of system (in)security that will not happen to you > if you have syscalls. The /bin/sh thing seemed discutable to me but I didn't investigate enough to ask for backout. > The patch introduces the same ugly enumeration style that already sucks > in the ifconfig rc script and should be deprecated. Correct me, if I am > wrong. >=20 > So I'd strongly vote to not to MFC but rather remove this feature. It still can be discussed now. > Btw.: Where do these kinds of discussions normally take place? I mean > before things are committed. Here and in gnats. See conf and rc PRs. PS: Matteo and submitter CC'ed. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --=-Gk/hHI4x9/UgF3+9Cp8A Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEhhhiMxEkbVFH3PQRAmByAKCQLEG8xG3cNbub8thqAg9MoAKuVQCbBT2f TnvEnZX0z9SWf+TMukAiwu4= =Ioq3 -----END PGP SIGNATURE----- --=-Gk/hHI4x9/UgF3+9Cp8A-- From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 01:32:48 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 8AFD116AD08 for ; Wed, 7 Jun 2006 01:14:25 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5DE43D46 for ; Wed, 7 Jun 2006 01:14:24 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 64997 invoked by uid 0); 7 Jun 2006 01:14:17 -0000 Received: from fnord.cryptophone.de (HELO ?10.1.1.71?) (erdgeist@erdgeist.org@62.220.7.20) by elektropost.org with AES256-SHA encrypted SMTP; 7 Jun 2006 01:14:17 -0000 Message-ID: <44862864.7050800@erdgeist.org> Date: Wed, 07 Jun 2006 03:14:12 +0200 From: Dirk Engling User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: freebsd-rc X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: jail configs separation X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 01:32:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The patch available at http://erdgeist.org/arts/software/jail/jail.1.34.diff does the following things: * Allow jail names of the kind foo.com, those are converted into foo_com * Scan /etc/jails for jail configs, sort them by rcorder and add them to jail_list, when script is invoked without parameters * Test for /etc/jails/ for each jail and try to source config file This helps in the automation of jail creation, deletion and configuration. You can put configs for all your jails into a central directory and have the list automatically generated by the directories content. Editing /etc/rc.conf and providing lots of repetitive lines becomes unnecessary. The rcorder statements inside jail configs enable the user to exactly specify startup order of jails. The clean up of jail configs enables configuration utilities to easily access config for certain jails without expansive parsing of /etc/rc.conf. For an outline of how this might look like, see the ezjail project page. Further the patch removes the "ifconfig -alias " when stopping jails, since this is outright dangerous as already described in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=14661+0+archive/2006/freebsd-rc/20060514.freebsd-rc Having the IP configured on your interface, even if you don't need it, should not be a problem. Comments? Suggestions? erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) iD8DBQFEhihjImmQdUyYEgkRAlCeAKCA6in7kRhE1uq2KF1UIIXEr1xKhgCbBOXc Nk5J6hodYWjt4LRE0+DVI1U= =VHjH -----END PGP SIGNATURE----- From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 07:12:29 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 A606F16AF88 for ; Wed, 7 Jun 2006 07:04:43 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id E3F5F43D48 for ; Wed, 7 Jun 2006 07:04:42 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 1058 invoked by uid 399); 7 Jun 2006 07:04:41 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 Jun 2006 07:04:41 -0000 Message-ID: <44867A88.5060307@FreeBSD.org> Date: Wed, 07 Jun 2006 00:04:40 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (X11/20060604) MIME-Version: 1.0 To: Alexander Botero-Lowry References: <20060606205325.GA13570@odin.ac.hmc.edu> <200606062147.k56LlW3i059772@Laptop.mine.box> In-Reply-To: <200606062147.k56LlW3i059772@Laptop.mine.box> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-rc@freebsd.org Subject: Re: The future of set_rcvar X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 07:12:33 -0000 [FYI, the convention on the FreeBSD lists is not to top-post] > Brooks Davis wrote: > >> We need to decide what we're doing with set_rcvar. Doug has been >> advocating against it in a number of forums, but no move has been made >> to actually deprecate it that I've seen. I believe we need to speak >> with one voice on this issue and have one style that is both documented >> for ports and used in the base. I can see three main options: Well I certainly didn't mean to stir up trouble. :) I'm also not opposed to its usage in the manner you seem to imply (although no harm/no foul either way). The reason I started "spelling it out" was to help someone understand better what was happening "behind the scenes" in rc.subr. There is a lot of power/capability in our rc.d system, but IMO there is also a lot of pointless indirection, and complication of things that could be simpler. I'm not opposed to coming up with a consistent viewpoint on this, and I will not oppose any sensible direction we choose to take. I also don't think it is necessarily that big a deal, but I'm willing to be persuaded either way. >> - Use set_rcvar unless there is a good reason not to (generally the >> very few historical scripts). This is the default in the base and was >> the status quo in ports for a while. >> - Always manually set $rcvar, >> deprecating set_rcvar with a loud warning and removing in in 7 or 8. >> - The same as above, but default $rcvar to ${name}_enable requiring that >> scripts that don't use have an rcvar value explicitly unset it. I would like to suggest a fourth option (unless I misunderstand your third option above), which is for rc.subr to do this: : ${rcvar=${name}_enable} IOW, the default will be ${name}_enable unless the port sets a different value, or sets the value to null. I would hesitate to literally use/encourage unset, especially in ports where the interaction between scripts and rc.subr is harder to follow closely and things are more likely to break in weird ways. >> I slightly prefer the first or third option because I don't like the >> idea of the default style encouraging inconsistent naming which I >> believe forcing rcvar to be set manually by default does. My only >> strong opinion on the subject is that we must make up out minds and act >> consistently instead of continuing the current split between ports >> documentation and the base. I'd be interested to hear why you think this is a matter of some importance. As a data point, out of 133 /etc/rc.d/ scripts on my 6-stable box, 32 do not use set_rcvar. 2 of the 32 (including named :)) set name_enable explicitly, 3 unset rcvar, and the rest set it to something-not-name_enable. Alexander Botero-Lowry wrote: > One question I've always had is why FreeBSD picked to have ${name}_enable > instead of just ${name} like on NetBSD? Was there a lot of debate about > this, was it to make the variables less ambiguous, or osmething else? Hysterical raisins. The rc.conf variables on FreeBSD have always been foo_enable, since long before rc.d was imported. It was decided to keep things consistent to minimize the impact on users during the rc.d import. > I would advocate for the third option if there is really a good reason to > not just do what NetBSD does. It makes it hard for packagers to use > consistent rc scripts between NetBSD and FreeBSD when the $rcvar is > different between the two platforms (and with a lot of stuff in ports and > pkgsrc the same rc scripts could be used and even packaged with the > application if upstream likes that idea). The original goal of the rc.d import was to share code between the two systems, but it quickly became obvious that this was not a practical goal, as there are enough fundamental differences between how the systems are started that the cost::benefit ratio went too high too fast. That goal has basically been abandoned for some time now. The one port I know of that tried to have a script that was generic enough to work on both systems was so broken on FreeBSD that it needed to be replaced, so I'm not sure that this is a useful goal either. However, if there is a groundswell of support for it, we could certainly work something out. If we followed my suggestion above, we would actually not have to change set_rcvar in any way, we'd just add a note in the code (and man pages, docs, etc.) that its use is deprecated, and make sure that nothing in the base uses it (so as to avoid having confusing examples). Then again, some might see that as the same kind of ambiguity that we have now, so we'd have to have this conversation all over again. :) In any case, I hope that this clarifies my thinking a bit more, and once again, not really trying to stir up any trouble here. Doug -- This .signature sanitized for your protection From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 11:49:11 2006 Return-Path: X-Original-To: freebsd-rc@hub.freebsd.org Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 066B216DA45; Wed, 7 Jun 2006 10:45:58 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4F8743D48; Wed, 7 Jun 2006 10:45:57 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (flz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k57Ajvhh012805; Wed, 7 Jun 2006 10:45:57 GMT (envelope-from flz@freefall.freebsd.org) Received: (from flz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k57AjvoP012801; Wed, 7 Jun 2006 10:45:57 GMT (envelope-from flz) Date: Wed, 7 Jun 2006 10:45:57 GMT From: Florent Thoumie Message-Id: <200606071045.k57AjvoP012801@freefall.freebsd.org> To: dwhite@FreeBSD.org, flz@FreeBSD.org, freebsd-rc@FreeBSD.org Cc: Subject: Re: conf/94377: [patch] /etc/rc.d/sshd improperly tests random dev state X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 11:49:19 -0000 Synopsis: [patch] /etc/rc.d/sshd improperly tests random dev state State-Changed-From-To: patched->closed State-Changed-By: flz State-Changed-When: Wed Jun 7 10:45:28 UTC 2006 State-Changed-Why: MFC'ed to RELENG_6. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=94377 From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 11:49:55 2006 Return-Path: X-Original-To: freebsd-rc@hub.freebsd.org Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E82916DA6A; Wed, 7 Jun 2006 10:46:47 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FCDF43D79; Wed, 7 Jun 2006 10:46:46 +0000 (GMT) (envelope-from flz@FreeBSD.org) Received: from freefall.freebsd.org (flz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k57AkkGQ012880; Wed, 7 Jun 2006 10:46:46 GMT (envelope-from flz@freefall.freebsd.org) Received: (from flz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k57AkkeE012876; Wed, 7 Jun 2006 10:46:46 GMT (envelope-from flz) Date: Wed, 7 Jun 2006 10:46:46 GMT From: Florent Thoumie Message-Id: <200606071046.k57AkkeE012876@freefall.freebsd.org> To: oliver@freebsd.org, flz@FreeBSD.org, freebsd-rc@FreeBSD.org Cc: Subject: Re: conf/73909: [patch] rc.d/sshd does not work with ports-ssh X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 11:50:03 -0000 Synopsis: [patch] rc.d/sshd does not work with ports-ssh State-Changed-From-To: patched->closed State-Changed-By: flz State-Changed-When: Wed Jun 7 10:46:16 UTC 2006 State-Changed-Why: MFC'ed to RELENG_6. http://www.freebsd.org/cgi/query-pr.cgi?pr=73909 From owner-freebsd-rc@FreeBSD.ORG Wed Jun 7 18:01:01 2006 Return-Path: X-Original-To: freebsd-rc@FreeBSD.org 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 E0FA916F712; Wed, 7 Jun 2006 15:49:15 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F87243D46; Wed, 7 Jun 2006 15:49:15 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k57FnEEo020933; Wed, 7 Jun 2006 08:49:14 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k57FnEXV020932; Wed, 7 Jun 2006 08:49:14 -0700 Date: Wed, 7 Jun 2006 08:49:14 -0700 From: Brooks Davis To: Doug Barton Message-ID: <20060607154914.GA18940@odin.ac.hmc.edu> References: <20060606205325.GA13570@odin.ac.hmc.edu> <200606062147.k56LlW3i059772@Laptop.mine.box> <44867A88.5060307@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <44867A88.5060307@FreeBSD.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-rc@FreeBSD.org Subject: Re: The future of set_rcvar X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jun 2006 18:01:03 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 07, 2006 at 12:04:40AM -0700, Doug Barton wrote: > [FYI, the convention on the FreeBSD lists is not to top-post] >=20 > > Brooks Davis wrote: > >=20 > >> We need to decide what we're doing with set_rcvar. Doug has been=20 > >> advocating against it in a number of forums, but no move has been made= =20 > >> to actually deprecate it that I've seen. I believe we need to speak= =20 > >> with one voice on this issue and have one style that is both documented > >> for ports and used in the base. I can see three main options: >=20 > Well I certainly didn't mean to stir up trouble. :) I'm also not opposed= to > its usage in the manner you seem to imply (although no harm/no foul either > way). The reason I started "spelling it out" was to help someone understa= nd > better what was happening "behind the scenes" in rc.subr. There is a lot = of > power/capability in our rc.d system, but IMO there is also a lot of > pointless indirection, and complication of things that could be simpler. >=20 > I'm not opposed to coming up with a consistent viewpoint on this, and I w= ill > not oppose any sensible direction we choose to take. I also don't think it > is necessarily that big a deal, but I'm willing to be persuaded either wa= y. I think the spelling out of the setting of rcvar has some value, but I also think less code is good, hence option three which makes then _enable case entirely implicit. > >> - Use set_rcvar unless there is a good reason not to (generally the > >> very few historical scripts). This is the default in the base and was > >> the status quo in ports for a while.=20 > >> - Always manually set $rcvar, > >> deprecating set_rcvar with a loud warning and removing in in 7 or 8.= =20 > >> - The same as above, but default $rcvar to ${name}_enable requiring th= at > >> scripts that don't use have an rcvar value explicitly unset it. >=20 > I would like to suggest a fourth option (unless I misunderstand your third > option above), which is for rc.subr to do this: >=20 > : ${rcvar=3D${name}_enable} >=20 > IOW, the default will be ${name}_enable unless the port sets a different > value, or sets the value to null. I would hesitate to literally > use/encourage unset, especially in ports where the interaction between > scripts and rc.subr is harder to follow closely and things are more likely > to break in weird ways. This is option three, described less ambiguously. I meant rcvar=3D"" rather than unset above. > >> I slightly prefer the first or third option because I don't like the= =20 > >> idea of the default style encouraging inconsistent naming which I=20 > >> believe forcing rcvar to be set manually by default does. My only=20 > >> strong opinion on the subject is that we must make up out minds and act > >> consistently instead of continuing the current split between ports=20 > >> documentation and the base. >=20 > I'd be interested to hear why you think this is a matter of some importan= ce. >=20 > As a data point, out of 133 /etc/rc.d/ scripts on my 6-stable box, 32 do = not > use set_rcvar. 2 of the 32 (including named :)) set name_enable explicitl= y, > 3 unset rcvar, and the rest set it to something-not-name_enable. I think it's important because people will cut and paste from the first random script they find that looks vaguely like what they want. If they aren't consistent we get rapidly increasing inconsistency. I'm also somewhat personally annoyed that we had a style and then you started telling people to use a different one. It's not that big a deal, but if we're going to review submissions for style, we should actually have one. I'm a firm believer that any style, even one with historical warts, is better than none. -- 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 --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEhvV5XY6L6fI4GtQRAkgSAKChHdPZ+b99ZuTGwOrFswrVgtB/EQCePN9L jOGAB4+QR5jSxTVmnsZug1c= =owBt -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-rc@FreeBSD.ORG Thu Jun 8 13:35:07 2006 Return-Path: X-Original-To: freebsd-rc@hub.freebsd.org Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFE1B170119 for ; Thu, 8 Jun 2006 11:20:27 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FAFA43D67 for ; Thu, 8 Jun 2006 11:20:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k58BKQXC026621 for ; Thu, 8 Jun 2006 11:20:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k58BKQFj026620; Thu, 8 Jun 2006 11:20:26 GMT (envelope-from gnats) Date: Thu, 8 Jun 2006 11:20:26 GMT Message-Id: <200606081120.k58BKQFj026620@freefall.freebsd.org> To: freebsd-rc@FreeBSD.org From: Rostislav Krasny Cc: Subject: Re: conf/94377 : [patch] /etc/rc.d/sshd improperly tests random dev state X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Rostislav Krasny 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: Thu, 08 Jun 2006 13:35:07 -0000 The following reply was made to PR conf/94377; it has been noted by GNATS. From: Rostislav Krasny To: Florent Thoumie , Doug White Cc: bug-followup@FreeBSD.org Subject: Re: conf/94377 : [patch] /etc/rc.d/sshd improperly tests random dev state Date: Thu, 8 Jun 2006 11:55:46 +0300 I've seen that patch just today, when it is already MFCed. I think it could be simpler. Instead of [ "x${seeded}" != "x" ] && [ ${seeded} -eq 0 ] you can write just [ "${seeded}" = "0" ] and it will be still correct against sysctl failing and returning an empty string. From owner-freebsd-rc@FreeBSD.ORG Thu Jun 8 18:43:32 2006 Return-Path: X-Original-To: freebsd-rc@freebsd.org 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 AA52A16D8D9 for ; Thu, 8 Jun 2006 16:40:46 +0000 (UTC) (envelope-from reed@pilchuck.reedmedia.net) Received: from pilchuck.reedmedia.net (pilchuck.reedmedia.net [209.166.74.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7884743D6E for ; Thu, 8 Jun 2006 16:40:42 +0000 (GMT) (envelope-from reed@pilchuck.reedmedia.net) Received: from reed by pilchuck.reedmedia.net with local (Exim 4.44) id 1FoNYY-0002BI-EC; Thu, 08 Jun 2006 09:40:26 -0700 Date: Thu, 8 Jun 2006 09:40:26 -0700 (PDT) From: "Jeremy C. Reed" To: Alan Robertson In-Reply-To: <447D955F.4070907@unix.sh> Message-ID: References: <20060513015129.C95601@arbitor.digitalfreaks.org> <446D3B73.3040202@unix.sh> <447D87DC.7040104@coolfactor.org> <447D955F.4070907@unix.sh> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: "Jeremy C. Reed" Cc: freebsd-rc@freebsd.org, ocf@lists.community.tummy.com, tech-userlevel@netbsd.org, General Linux-HA mailing list , Gavan Fantom Subject: Re: [Linux-HA] Integrating OCF framework w/ (Net|Free)BSD rc.d X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 08 Jun 2006 18:43:36 -0000 > > > OK. You don't have to write OCF scripts if you don't want to. BUT, for > > > R2, you really do want something equivalent to "status" operations. Is > > > that available in *BSD rc.d scripts? > > > > /etc/rc.d/