Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 24 Sep 2001 11:18:06 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff) Message-ID: <20010924111806.O17037@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from robert.collins@itdomain.com.au on Mon, Sep 24, 2001 at 01:13:15PM +1000 On Mon, Sep 24, 2001 at 01:13:15PM +1000, Robert Collins wrote: > * create the cygdrive fhandler class. > * create the devfs fhandler class. > * Alter setup.exe to add the new default mount point registry entries > (for /cygdrive and /dev). I think it's a bit more tricky. /dev is a wonderful example. By default it contains only device entries: /dev/tty /dev/st0 ... which you could nicely support by a dev fhandler. The problem is that I wouldn't like to disallow to create symlinks inside of /dev: ln -s /dev/st0 /dev/tape So /dev is kinda `bastard' containing virtual device entries but also real symlinks. In that case it would make sense to support reading the real /dev in the Cygwin tree on disk plus listing all virtual device entries. Sure, you could manage that in the dev fhandler... I think that you'll have some work to implement that due to a design constraint inside of Cygwin. In theory the functionality of stat/readdir etc. has to be moved inside of the fhandlers first. While that already works for stat on disk files it's currently not implemented for readdir at all. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.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/