Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Need name and functionality suggestions for a new utility X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 24 Oct 2001 15:54:54 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Need name and functionality suggestions for a new utility Thread-Index: AcFcTpYAEtE+84eFR0GLW/4GZBk0NQAAalVw From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id f9O5l0I07798 > -----Original Message----- > > Well, mmap()ed (as in the system call mmap()) objects certainly are > created using win32 paths. Found it - get_namehash which uses namehash which is set via namehash = hash_path_name (0, get_win32_name ()); so you're correct, I'm jumping at ghosts. For the record, my ftok() will be ok because it uses the inode number - which is the namehash. Rob