delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/09/24/16:42:06

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 24 Sep 2001 22:41:35 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff)
Message-ID: <20010924224135.C16412@cygbert.vinschen.de>
Mail-Followup-To: cygwin <cygwin AT cygwin DOT com>
References: <20010924150136 DOT V17037 AT cygbert DOT vinschen DOT de> <NFBBLOMHALONCDMPGBLFKEELCCAA DOT info AT rlsystems DOT net>
Mime-Version: 1.0
User-Agent: Mutt/1.2.5i
In-Reply-To: <NFBBLOMHALONCDMPGBLFKEELCCAA.info@rlsystems.net>; from info@rlsystems.net on Mon, Sep 24, 2001 at 09:24:23PM +0200

On Mon, Sep 24, 2001 at 09:24:23PM +0200, Ronald Landheer wrote:
> directories exist before listing the magic ones. The only problem I 
> forsee is that they might start conflicting with eachother - i.e. if I 
> make a *file* called /dev/tty and I write stuff to it, it might end up 
> in the file in stead of the device.

Nope.  Even if the file exists, opening and writing will ever
end up in the device.  That's not a problem even right now.

> I wouldn't mind having the fhandler just not allow actual file vs. 
> device conflicts - let the "magic" one override the actual one, and 
> remove the actual one if it's offensive. /dev is no place for files 
> anyway - it's like storing data in a void, storing icecream in a 
> volcano: it doesn't last, it's not a good idea, and noone in his/her 
> right mind would do it.. Symlinks are another matter, but the same 
> precedence would apply: symlinks are meant to make life a bit easier, 
> but don't contain any actual data, so if an magic dir would conflict 
> with a symlink, the symlink would have to go..

IMO it doesn't matter.  Files are listed as files, symlinks as
symlinks.  If somebody creates a file called like a device
(which is only possible outside of Cygwin processes) it will
exist but has no further influence except, perhaps, that the
corresponding device will be listed twice.

> In the case of both /cygdrive and /registry, I simply wouldn't allow the 
> existance of real files - though Win32 will mess that up, ofcourse.

Yep, that's it.  You can't prevent it.  The question is just if
the fhandler has to list it or not.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019