From owner-freebsd-stable@FreeBSD.ORG Tue Nov 29 06:03:26 2005 Return-Path: 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 85F1416A41F for ; Tue, 29 Nov 2005 06:03:26 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3610043D55 for ; Tue, 29 Nov 2005 06:03:25 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 6300119F2C; Mon, 28 Nov 2005 22:03:24 -0800 (PST) From: "Darren Pilgrim" To: "'Kevin Oberman'" Date: Mon, 28 Nov 2005 22:04:05 -0800 Message-ID: <000801c5f4aa$b7d340a0$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <20051129054922.48ACA5D0A@ptavv.es.net> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: stable@freebsd.org Subject: RE: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 06:03:26 -0000 From: Kevin Oberman > > 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. The normal tools (chmod, chown, etc.) don't work on devfs. You need to create devfs rules to change permissions, ownership, etc. on device nodes. See devfs.rules(5) and devfs.conf(5).