From: k.lichtenwalder@computer.org
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 raw devices don't do 64bit offset?
Date: Mon, 16 Apr 2001 14:53:12 +0200 [thread overview]
Message-ID: <3ADAEB38.44CBD71A@computer.org> (raw)
In-Reply-To: <E14p7Fo-0008VK-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
Alan Cox wrote:
>
> > sorry if this was already discussed, but I couldn't find it in the
> > archives. I'm trying to use xine (the linux dvd player) on
> > linux-2.4.3-ac3 and can't watch the whole dvd. The reason is that as
> > soon as the llseek sets a value in the offset_high field for sys_llseek,
> > I get a EINVAL back from the seek. Is this intentional? Or simply still
> > (only) a missing feature?
>
> Did you open the file with open64() ?
Sorry for being a bit clueless, but it's just the application I was
using. I didn't check that further, because if I don't use the raw
device, it's working fine... So let me check...
No it's using open(), but sets -D_FILE_OFFSET_BITS=64. Looks like this
is not enough for the raw devices?
Klaus
--
-------------------------------------------------------------------------
Klaus Lichtenwalder, Dipl. Inform., http://www.webforum.de/Klaus/
Fax +49-(0)89-91072699 Lichtenwalder@ACM.org
NIC: KL2100, KL76-RIPE K.Lichtenwalder@Computer.org
PGP Key fingerprint = 2658 EA97 E1A1 2680 5ECA 0036 80F5 F250 3CF8
C2C7
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2036 bytes --]
next prev parent reply other threads:[~2001-04-16 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 8:52 2.4 raw devices don't do 64bit offset? k.lichtenwalder
2001-04-16 11:33 ` Alan Cox
2001-04-16 12:53 ` k.lichtenwalder [this message]
2001-04-16 15:39 ` k.lichtenwalder
2001-04-17 13:29 ` k.lichtenwalder
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=3ADAEB38.44CBD71A@computer.org \
--to=k.lichtenwalder@computer.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox