Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <0d6101c144f2$411f4fb0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Corinna Vinschen" References: <20010924111806 DOT O17037 AT cygbert DOT vinschen DOT de> <0cfd01c144dc$57e9ab70$0200a8c0 AT lifelesswks> <20010924140127 DOT P17037 AT cygbert DOT vinschen DOT de> Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff) Date: Mon, 24 Sep 2001 22:12:59 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 24 Sep 2001 12:20:55.0285 (UTC) FILETIME=[5BE96A50:01C144F3] ----- Original Message ----- From: "Corinna Vinschen" To: "cygwin" Sent: Monday, September 24, 2001 10:01 PM Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff) > On Mon, Sep 24, 2001 at 07:36:07PM +1000, Robert Collins wrote: > > From: "Corinna Vinschen" > > > So /dev is kinda `bastard' containing virtual device entries > > > but also real symlinks. > > > > Ahh, well, there are two approaches there. 1 is what I described. A > > second one is to mount each device separately at it's appropiate point, > > and have a real /dev directory. > > > > IMO if you want full fs at /dev, then you should create it. AFAIK the > > linux devfs is readonly, with the exception of adding nodes when devices > > are detected at runtime. > > We could simulate /dev through the fhandler, though. Assuming > we already have a fhandler_devfs, its opendir()/readdir() could > begin with listing the real /dev directory if and as it exists. > When finished, it could go ahead with listing the internal > Cygwin devices. The `stat' call itself isn't concerned at all > by this approach. It would work as before. A good idea would > just be to create a /dev by setup to have the real directory > node to be able to list . and .. w/o handstands. And we don't > have to worry about the order since that's done by ls. Sure. All I meant to say is that we shouldn't design this behaviour in. Allow it - yes; require it - no. Quite obviously any fhandler can do what it wants - merge network, win32, and virtual data. As long as they don't _have to_ I'm happy :]. > > > > Ok, well that makes sense. Any objection to it being done :}? > > Yes and no. > > - Another yes due to our long term devlopment target to substitute > the fhandler classes by device and file system classes. But that > will take much time so we can neglect that for now. Ah, didn't know about that. Still, IMO this is actually helpful for that, as it starts the process of making all fs calls into the fhandler class and out of syscalls.cc. Rob -- 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/