From owner-freebsd-rc@FreeBSD.ORG  Wed Dec 27 11:33:37 2006
Return-Path: <owner-freebsd-rc@FreeBSD.ORG>
X-Original-To: freebsd-rc@freebsd.org
Delivered-To: freebsd-rc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C413B16A416
	for <freebsd-rc@freebsd.org>; Wed, 27 Dec 2006 11:33:37 +0000 (UTC)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97])
	by mx1.freebsd.org (Postfix) with ESMTP id EDF1113C46D
	for <freebsd-rc@freebsd.org>; Wed, 27 Dec 2006 11:33:36 +0000 (UTC)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (localhost [127.0.0.1])
	by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id kBRAuVuA032475
	for <freebsd-rc@freebsd.org>; Wed, 27 Dec 2006 13:56:31 +0300 (MSK)
	(envelope-from yar@comp.chem.msu.su)
Received: (from yar@localhost)
	by comp.chem.msu.su (8.13.4/8.13.3/Submit) id kBRAuVsl032474
	for freebsd-rc@freebsd.org; Wed, 27 Dec 2006 13:56:31 +0300 (MSK)
	(envelope-from yar)
Date: Wed, 27 Dec 2006 13:56:31 +0300
From: Yar Tikhiy <yar@comp.chem.msu.su>
To: freebsd-rc@freebsd.org
Message-ID: <20061227105630.GB21493@comp.chem.msu.su>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Subject: rc.d namespace
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."
	<freebsd-rc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-rc>
List-Post: <mailto:freebsd-rc@freebsd.org>
List-Help: <mailto:freebsd-rc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2006 11:33:37 -0000

Hi folks,

My attention has been drawn by the fact that rc.subr and rc.d/*
don't seem to follow uniform namespace rules.  Namely both rc.subr
and rc.d use global identifiers starting with an underscore.
Fortunately, rc.subr doesn't seem to use global identifiers not
starting with an underscore besides the names exported to scripts
on purpose.

What do you think about adopting the following rule: "_foo" names
are for the rc.subr internals while just "foo" names are for rc.d
scripts?  Another possible way is: __foo or even __rc_foo for
rc.subr, _foo for scripts, foo for the documented rc.subr interface.

Comments?

-- 
Yar