This is the mail archive of the
mailing list for the Cygwin project.
Re: 64-bit file operations (lseek64() etc) misbehaving
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 1 Apr 2004 10:36:29 +0200
- Subject: Re: 64-bit file operations (lseek64() etc) misbehaving
- References: <20040331183428.GA1710@esd-mbrown.us.dg.com> <Pine.GSO.email@example.com> <20040331201910.GC1710@esd-mbrown.us.dg.com> <Pine.GSO.firstname.lastname@example.org> <20040331215849.GD1710@esd-mbrown.us.dg.com> <Pine.GSO.email@example.com>
- Reply-to: cygwin at cygwin dot com
On Mar 31 17:36, Igor Pechtchanski wrote:
> Please make sure your mailer respects the Reply-To: header. Thanks.
> Frankly, I don't see any reason why open() *wouldn't* succeed on
> \\.\PhysicalDrive0... All it'll do is recognize a Win32 pathname (because
> of the '\'), and pass it along to Windows. OTOH, Cygwin will not see this
> name as special -- from Cygwin's point of view it's just another file. So
> any operations invoked on it (including "open") will be regular Windows
> file calls, not special ones (e.g., NtOpenFile with the right attributes,
> as done in fhandler_dev_raw::open). This might be the reason for your
> initial problem.
Perfect explanation, Igor!
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:firstname.lastname@example.org
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html