All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Al Viro <viro@ftp.linux.org.uk>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compatible fstat()
Date: Tue, 08 Nov 2005 17:57:07 -0500	[thread overview]
Message-ID: <43712D43.5080404@tmr.com> (raw)
In-Reply-To: <FC49A7EB-A267-4C94-8739-2321C4DC1A1B@comcast.net>

Parag Warudkar wrote:
> 
> On Nov 8, 2005, at 2:39 PM, Bob Copeland wrote:
> 
>> Isn't this just because the device size is > 2**32?  What if you  use 
>> fseeko(3)
>> and #define _FILE_OFFSET_BITS 64?
>>
> 
> Yep. I got it to return the correct hard disk size (17Gb) using  lseek64 
> and
> #define _LARGEFILE64_SOURCE
> #define _FILE_OFFSET_BITS 64
> 
> Here is what I did
> -------------------------------------------------
> #define _LARGEFILE64_SOURCE
> #define _FILE_OFFSET_BITS 64
> #include <stdio.h>
> #include <unistd.h>
> #include <fcntl.h>
> 
> int main()
> {
>         int f;
>         off64_t off=0;
Why is this initialized?
>         f = open("/dev/hda", O_RDONLY );
>         if(f <= 0){
>                 perror("open");
>                 exit(0);
>         }
>         off = lseek64(f, 0, SEEK_SET);
Why do this? it always returns zero.
>         off = lseek64(f, 0, SEEK_END);
>         perror("llseek");
>         printf ("Size %lld\n", off);
>         close(f);
>         return 0;
> }
> 
RETURN VALUE
   Upon successful completion, lseek returns the resulting offset
   location as measured in bytes from the beginning of the  file.
   Otherwise,  a  value  of  (off_t)-1 is returned and errno is
   set to indicate the error.


-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-11-08 22:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 15:48 Compatible fstat() linux-os (Dick Johnson)
2005-11-08 17:10 ` Parag Warudkar
2005-11-08 17:22   ` Al Viro
2005-11-08 17:56     ` linux-os (Dick Johnson)
2005-11-08 17:58     ` Parag Warudkar
2005-11-08 18:10       ` linux-os (Dick Johnson)
2005-11-08 18:15         ` Parag Warudkar
2005-11-08 18:20           ` linux-os (Dick Johnson)
2005-11-08 19:39             ` Bob Copeland
2005-11-08 20:03               ` linux-os (Dick Johnson)
2005-11-08 21:06               ` Parag Warudkar
2005-11-08 22:57                 ` Bill Davidsen [this message]
2005-11-09  0:14                   ` Parag Warudkar
2005-11-12 13:41                     ` Bill Davidsen
2005-11-08 18:49     ` Theodore Ts'o
2005-11-08 19:12       ` Parag Warudkar
2005-11-09  3:23         ` Theodore Ts'o
2005-11-08 17:53   ` linux-os (Dick Johnson)
2005-11-08 18:04     ` Parag Warudkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43712D43.5080404@tmr.com \
    --to=davidsen@tmr.com \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.