From: Ben Collins <bcollins@debian.org>
To: Alex Adriaanse <alex_a@caltech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LFS stopped working
Date: Wed, 14 Nov 2001 21:58:15 -0500 [thread overview]
Message-ID: <20011114215815.S329@visi.net> (raw)
In-Reply-To: <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu>
In-Reply-To: <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu>
On Wed, Nov 14, 2001 at 02:05:21PM -0800, Alex Adriaanse wrote:
> Hey,
>
> I've been running 2.4.14 for a few days now. I needed LFS support, so I
> recompiled glibc 2.1.3 with the new 2.4 headers, and after that I could
> create large files (e.g. using dd if=/dev/zero of=test bs=1M count=0
> seek=3000) just fine.
>
> However, as of yesterday, I couldn't create files bigger than 2GB anymore.
> I did not change kernels, nor did I mess with libc or anything else (I did
> some Debian package upgrades/installations/recompiles, but I don't think
> they should affect this) - I'm not quite sure what happened. Now commands
> such as the dd command I mentioned above will die with the message "File
> size limit exceeded", leaving a 2GB file behind. Rebooting didn't solve
> anything. My ulimits seem to be fine (file size = unlimited).
Actually it does affect it. Recompiling glibc isn't the end all to LFS
support. In fact, 2.1.3 has less than adequate support for LFS, IIRC, so
use 2.2.x. For Debian, that just means upgrading to woody(testing).
Your problem extends from programs also needing to be recompiled with
LFS support. This involves some special LFS CFLAGS, and most common
programs detect whether to do this using autoconf (fileutils, gzip and
tar are perfect examples of programs that use this feature).
Ben
--
.----------=======-=-======-=========-----------=====------------=-=-----.
/ Ben Collins -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
next prev parent reply other threads:[~2001-11-15 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 22:05 LFS stopped working Alex Adriaanse
2001-11-15 2:58 ` Ben Collins [this message]
2001-11-15 6:29 ` Alex Adriaanse
2001-11-15 9:38 ` Andreas Jaeger
2001-11-15 10:03 ` Alex Adriaanse
2001-11-15 10:42 ` Andreas Jaeger
2001-11-15 11:57 ` Alex Adriaanse
[not found] <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu.suse.lists.linux.kernel>
2001-11-15 6:08 ` Andi Kleen
2001-11-21 19:07 ` Andreas Dilger
2001-11-21 20:06 ` Alex Adriaanse
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=20011114215815.S329@visi.net \
--to=bcollins@debian.org \
--cc=alex_a@caltech.edu \
--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