From owner-freebsd-stable@FreeBSD.ORG  Tue Nov 29 05:49:26 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@freebsd.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DB7E816A41F
	for <stable@freebsd.org>; Tue, 29 Nov 2005 05:49:26 +0000 (GMT)
	(envelope-from oberman@es.net)
Received: from postal1.es.net (postal1.es.net [198.128.3.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9D88843D46
	for <stable@freebsd.org>; Tue, 29 Nov 2005 05:49:26 +0000 (GMT)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
	by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465
	for <stable@freebsd.org>; Mon, 28 Nov 2005 21:49:22 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP id 48ACA5D0A
	for <stable@freebsd.org>; Mon, 28 Nov 2005 21:49:22 -0800 (PST)
To: stable@freebsd.org
Date: Mon, 28 Nov 2005 21:49:22 -0800
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20051129054922.48ACA5D0A@ptavv.es.net>
Cc: 
Subject: Unable to set device characteristics with devd
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2005 05:49:27 -0000

I've been trying to use devd for a number of things, but have not gotten
far.

One issue is when I attach an ATAPI disk:
attach 100 {
        device-name "acd0";
        action "/bin/chmod 666 /dev/$device-name";
}

I have similar statements for my second hard drive (ad2s2).

By using the -D option I see the device attach, but the chmod returns
an error indicating that /dev/acd0 does not exist. I get similar results
for other devices.

Is there a delay between the attach event and the creation of the /dev
entry? Am I missing something here? Maybe I should use devfs for this.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634