From owner-freebsd-questions@FreeBSD.ORG  Wed Apr  7 06:13:31 2004
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 31E2016A4CE
	for <freebsd-questions@freebsd.org>;
	Wed,  7 Apr 2004 06:13:31 -0700 (PDT)
Received: from asarian-host.net (mail.asarian-host.net [194.109.160.70])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6284643D53
	for <freebsd-questions@freebsd.org>;
	Wed,  7 Apr 2004 06:13:30 -0700 (PDT)
	SRS0=KPBrk5KO=HD=asarian-host.net=admin@asarian-host.net)
Comments: To protect the identity of the sender, certain header
	fields are either not shown, or masked. Anonymous email
	accounts can be requested by filling in the appropriate
	form at: https://asarian-host.net/cgi-bin/signup.cgi
Received: (from root@localhost)
	by mail.asarian-host.net (8.12.11/8.12.11) id i37DBkpO029587
	for freebsd-questions@freebsd.org;
	Wed, 7 Apr 2004 15:11:46 +0200 (CEST)
	(envelope-from admin@asarian-host.net)
From: Mark <admin@asarian-host.net>
Received-SPF: pass (asarian-host.net: domain of admin@asarian-host.net
	designates sender IP as SASL permitted sender)
Message-Id: <200404071311.I37DBKRS029575@asarian-host.net>
Date: Wed, 07 Apr 2004 13:11:46 GMT
X-Authenticated-Sender: admin@asarian-host.net
X-Trace: 2vJIVr52dDaE+nU1aJYcSzZpNT8+nH07cEuoUZgIPbMvsdHy/zoB/O3BJ20m99YK3O+Yph0FtYYRTUdFjppTdg==
X-Complaints-To: abuse@asarian-host.net
X-Abuse-Info: Please be sure to forward a copy of ALL headers,
	otherwise we are unable to process your complaint
Organization: Asarian-host
To: <freebsd-questions@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Auth: Asarian-host PGP signature
	iQEVAwUAQHP+EjFqW1BleBN9AQGfJAf/RHp2kzJ08nH8dFiKHj3wRvtjx29ZLpZ4
	o3aXhI894NQqvUrmgDeV1lmy/Tj94OLn6BVFmJAwQ+7VlpanI8aNNu596d/cLNgW
	umoSkB6KynoJCvYKQbDuu570s76rAzxr6OLX4xRp7NSFQauYGLTon3txpcv+UC/N
	LHQvui9q5VAaHLo1zq7AsJCKtL/20ZuXowqSU4KkndVium/JABw1mwSldCxnjL5C
	T155Cmp6f+AA087fVbCXdheFtwy7WGnqmZ3pqltRdXE7wLOmIbMqkD80hgBvpsvv
	K8zZGftnIA+LZ16f8v6QMLcdZiUJ7XpKSLOecmS/wPYzYbe4srTr6g==
	=JrDb
Subject: Seting schg flags on /dev/?
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: Wed, 07 Apr 2004 13:13:31 -0000

Hello,

Is it useful/desireable to set schg flags on /dev/? Obviously, setting schg
on /dev/null, for instance, prevents writing to it, which kind of defeats
its purpose. There are probably other such devices that need to be written
to. So, are then any devices in /dev/ that actually can be set schg?

Thanks,

- Mark