From owner-freebsd-questions@FreeBSD.ORG  Fri Apr  1 19:12:07 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4E0E216A4CE
	for <freebsd-questions@freebsd.org>;
	Fri,  1 Apr 2005 19:12:07 +0000 (GMT)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E88F443D5C
	for <freebsd-questions@freebsd.org>;
	Fri,  1 Apr 2005 19:12:06 +0000 (GMT)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.12.6/8.12.6) with ESMTP id j31JC69S047762
	for <freebsd-questions@freebsd.org>;
	Fri, 1 Apr 2005 13:12:06 -0600 (CST)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200504011912.j31JC69S047762@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
Date: Fri, 01 Apr 2005 13:12:06 -0600
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: Best Practice for Allowing non-root Users Access to Serial
	Port? 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2005 19:12:07 -0000

	My thanks to all who have responded with this and similar
recommendations:

Roland Smith writes:
>Making kermit users members of a group, and have that group own
>/dev/cuaa* with read/write privileges seems like a good idea.
>
>For instance, create a group "kermit" with 'pw groupadd kermit'. Then
>you can use devfs(8) to change the ownership and permissions of the
>relevant device: "devfs rule add path 'cuaa*' mode 0660 group
>kermit". This setting will not survive a reboot, so you'll have to add the
>following to /etc/devfs.rules: "add path 'cuaa*' mode 0660 group kermit".
>
>Now add the relevant users to the group kermit:
>'pw groupmod kermit -m foo,bar,baz'
>
>Roland