From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: Largefile support in 2.4
Date: Wed, 24 Jan 2001 14:38:00 -0500 [thread overview]
Message-ID: <06dc01c0863d$29383390$e1de11cc@csihq.com> (raw)
How do normal users get to create/maintain large files (i.e. >2G) in Linux
2.4 on i386?
The root user can make filesize unlimited but a non-root user cannot. They
come up with the same limits in both tcsh and bash (i.e. filesize
1048576 kbytes or 0x40000000)
I can't seem to find where this number comes from anywhere -- either in
glibc-2.2.1 or the kernel. getrlimit64 returns it.
I can't make all my users root users!!! Can anybody help?
________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-24 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 19:38 Mike Black [this message]
2001-01-25 17:03 ` Largefile support in 2.4 Stephen C. Tweedie
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='06dc01c0863d$29383390$e1de11cc@csihq.com' \
--to=mblack@csihq.com \
--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