From owner-cvs-all  Tue Dec 14 10:48:54 1999
Delivered-To: cvs-all@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id E19BC15044; Tue, 14 Dec 1999 10:48:49 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id KAA22993;
	Tue, 14 Dec 1999 10:48:43 -0800 (PST)
	(envelope-from dillon)
Date: Tue, 14 Dec 1999 10:48:43 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199912141848.KAA22993@apollo.backplane.com>
To: "Louis A. Mamakos" <louie@TransSys.COM>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, obrien@NUXI.com,
	cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/chown Makefile 
References: <199912140617.WAA18057@gndrsh.dnsmgr.net>  <199912141402.JAA35445@whizzo.transsys.com>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

:
:So, do we need to wait until the perfect solution until any progress
:can be made at all?  The place that I suspect most folks trip across
:the chown problem is when making new device nodes for disk devices.
:You don't need awk for that particular problem, and given all the flux
:in the disk arena these days, it would be nice if unsuspecting users
:can unscrew themselves by making (e.g., ad0s1a) device nodes when they
:stumble across that change.
:
:louie

    I would solve this problem by adding options to 'mknod' to allow the
    user & group to be specified, and leaving chown where it was before.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message