From: Andreas Dilger <adilger@clusterfs.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: olarge -- force O_LARGEFILE on app binaries.
Date: Mon, 14 Apr 2003 10:19:59 -0600 [thread overview]
Message-ID: <20030414101959.E26054@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.44.0304141554560.3687-100000@einstein31.homenet>; from tigran@veritas.com on Mon, Apr 14, 2003 at 04:03:32PM +0100
On Apr 14, 2003 16:03 +0100, Tigran Aivazian wrote:
> Some time ago I was annoyed to see that ghostscript didn't support large
> files (>2G) and, although the fix to gs(1) was trivial it was very
> undesirable to have to recompile it (for lots of reasons like mismatch
> between the source set and fonts, libraries etc). So the only (efficient)
> solution in my case would have been to "modify" the behaviour of the gs
> binary without rebuilding it. One way is to use LD_PRELOAD feature but I
> found it easier to just knock up a simple kernel module olarge.o to do the
> job.
I don't see how this helps you very much. So now, instead of the kernel
complaining with EFBIG and/or SIGXFSZ, your 32-bit size offset wraps in
the application.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-04-14 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 15:03 olarge -- force O_LARGEFILE on app binaries Tigran Aivazian
2003-04-14 16:19 ` Andreas Dilger [this message]
2003-04-14 16:29 ` Tigran Aivazian
2003-04-14 17:28 ` Andreas Dilger
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=20030414101959.E26054@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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.