From owner-freebsd-current@FreeBSD.ORG  Mon Jan  5 21:00:06 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EF11716A4D1
	for <current@freebsd.org>; Mon,  5 Jan 2004 21:00:06 -0800 (PST)
Received: from mail.XtremeDev.com (xtremedev.com [216.241.38.65])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3B15343D3F
	for <current@freebsd.org>; Mon,  5 Jan 2004 21:00:04 -0800 (PST)
	(envelope-from bsdc@xtremedev.com)
Received: from localhost (localhost [127.0.0.1])
	by mail.XtremeDev.com (Postfix) with ESMTP id 6448611A08
	for <current@freebsd.org>; Mon,  5 Jan 2004 22:00:03 -0700 (MST)
Received: from mail.XtremeDev.com ([127.0.0.1])
 by localhost (Amber.XtremeDev.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 75474-02 for <current@freebsd.org>;
 Mon,  5 Jan 2004 22:00:02 -0700 (MST)
Received: by mail.XtremeDev.com (Postfix, from userid 1001)
	id 57EA811701; Mon,  5 Jan 2004 22:00:02 -0700 (MST)
Date: Mon, 5 Jan 2004 22:00:02 -0700
From: BSDC <bsdc@xtremedev.com>
To: current@freebsd.org
Message-ID: <20040106050002.GA5271@Amber.XtremeDev.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1i
X-Virus-Scanned: by amavisd-new at xtremedev.com
Subject: devfs_set_ruleset doesn't seem to like jail_cvs_devfs_ruleset="4"
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2004 05:00:07 -0000

Trying to setup a jail'd cvs, I came across the jail_cvs_devfs_ruleset
variable for /etc/rc.conf. Running /etc/rc.d/jail start, I get:

/etc/rc.d/jail: DEBUG: found ruleset: devfsrules_jail=4
/etc/rc.d/jail: DEBUG: adding rule (add include $devfsrules_hide_all)
/etc/rc.d/jail: DEBUG: adding rule (add include $devfsrules_unhide_basic)
/etc/rc.d/jail: DEBUG: adding rule (add include $devfsrules_unhide_login)
/etc/rc.d/jail: DEBUG: devfs_init_rulesets: devfs rulesets initialized
/etc/rc.d/jail: DEBUG: devfs_domount(): mount-point is (/var/jail/172.16.1.1/dev), ruleset is (4)
/etc/rc.d/jail: DEBUG: devfs_init_rulesets: devfs rulesets already initialized
/etc/rc.d/jail: WARNING: devfs_set_ruleset: you must specify a ruleset number

I don't know much about shell scripting, but it seems that line 1169
of /etc/rc.subr seems to be resetting the rs variable from 4 to an empty
string:

  [ -n "$1" ] && eval rs=\$$1 || rs=

Since I don't know what eval rs=\$$1 is suppose to be doing, I removed
it. Now, with:

  [ -n "$1" ] || rs=

I get:

/etc/rc.d/jail: DEBUG: found ruleset: devfsrules_jail=4
/etc/rc.d/jail: DEBUG: adding rule (add include $devfsrules_hide_all)
/etc/rc.d/jail: DEBUG: adding rule (add include
$devfsrules_unhide_basic)
/etc/rc.d/jail: DEBUG: adding rule (add include
$devfsrules_unhide_login)
/etc/rc.d/jail: DEBUG: devfs_init_rulesets: devfs rulesets initialized
/etc/rc.d/jail: DEBUG: devfs_domount(): mount-point is
(/var/jail/172.16.1.1/dev), ruleset is (4)
/etc/rc.d/jail: DEBUG: devfs_init_rulesets: devfs rulesets already
initialized
/etc/rc.d/jail: DEBUG: devfs_set_ruleset: setting ruleset (4) on
mount-point (/var/jail/172.16.1.1/dev)


Yet when I do a listing of /var/jail/172.16.1.1/dev, it still lists all
the devices, none are hidden. Any suggestions as to what's going on, and
why rule #4 (copied /etc/defaults/devfs.conf to /etc/devfs.conf) doesn't
seem to be applied?