From: "Alex Adriaanse" <alex_a@caltech.edu>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: LFS stopped working
Date: Thu, 15 Nov 2001 03:57:35 -0800 [thread overview]
Message-ID: <JIEIIHMANOCFHDAAHBHOOEOOCMAA.alex_a@caltech.edu> (raw)
In-Reply-To: <howv0s48nx.fsf@gee.suse.de>
Well, I'm running Debian 2.2 (with a few recompiled newer packages, as well
as a recompiled glibc 2.1.3 obviously), which comes with bash 2.03.
Compiling & installing bash 2.05, and commenting out that line in
/etc/pam.d/ssh that was mentioned in the web page you provided unfortunately
didn't change anything - the ulimit for file size was still unlimited, and I
still couldn't write >2GB files.
Alex
-----Original Message-----
From: aj@suse.de [mailto:aj@suse.de]
Sent: Thursday, November 15, 2001 2:43 AM
To: Alex Adriaanse
Cc: linux-kernel@vger.kernel.org
Subject: Re: LFS stopped working
"Alex Adriaanse" <alex_a@caltech.edu> writes:
> But ulimit shows that the file size is unlimited... would this be a bug?
If
> that's the case, then how/why would it work before?
If you use an older distro, bash will not handle the changed getrlimit
syscall in 2.4, for details check the Red Hat entry under:
http://www.suse.de/~aj/linux_lfs.html
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-11-15 11:57 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
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 [this message]
[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=JIEIIHMANOCFHDAAHBHOOEOOCMAA.alex_a@caltech.edu \
--to=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