Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe:	<mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Mon, 2 Aug 1999 15:54:30 -0400
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	Egor Duda <deo AT logos-m DOT ru>
Cc:	Corinna Vinschen <corinna AT vinschen DOT de>,
	cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	Re: chown and chmod for /dev/*
Message-ID:	<19990802155430.A2383@cygnus.com>
References:	<10934 DOT 990802 AT logos-m DOT ru>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.6i
In-Reply-To:	<10934.990802@logos-m.ru>; from Egor Duda on Mon, Aug 02, 1999 at 10:26:03PM +0400

On Mon, Aug 02, 1999 at 10:26:03PM +0400, Egor Duda wrote:
>  If one thy to call "chown" of "chmod" functions for cygwin-emulated
>files like /dev/tty0 they'll return (-1) and error "path not found".
>It doesn't seem to be a major issue -- the only place i've seen, which
>is affected by this is sshd, which prints a warning message. But it
>certanly could break other programs.
>Quick solution is to check win32_path.is_device() in this functions.
>Or files like <win32p_path_for_"/">\dev\tty0 should be created to hold
>security info -- as more unix-like way?

This is a good point.  For now, I've changed chmod and chown to always
succeed with devices.  In the future we'll probably want to do something
more sophisticated.

cgf

- Raw text -