From owner-freebsd-questions@FreeBSD.ORG Wed Feb 8 22:15:58 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A9D71065670 for ; Wed, 8 Feb 2012 22:15:58 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB8D8FC18 for ; Wed, 8 Feb 2012 22:15:58 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 9E5F55081B for ; Wed, 8 Feb 2012 13:58:10 -0800 (PST) To: freebsd-questions@freebsd.org Date: Wed, 08 Feb 2012 13:58:10 -0800 Message-ID: <2068.1328738290@tristatelogic.com> From: "Ronald F. Guilmette" Subject: /dev/ulpt0 -- How is it created? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 22:15:58 -0000 It would appear that the device node /dev/ulpt0 gets (re-)created every time I plug my USB printer back in. Could somebody please kindly tell me what the exact mechanism is that causes this device node to be (re-)created upon such events? I am rather hoping that whatever that mechanism is, that I can diddle it somehow so that every time /dev/ulpt0 gets created, it will be created with perms set to 0666. (Sorry, yes, I'm almost totally ignorant about how these kinds of transient device nodes get automagically created these days.)