From: Marius Gedminas <mgedmin@centras.lt>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: DD-ing from device to device.
Date: Mon, 19 Nov 2001 21:51:12 +0200 [thread overview]
Message-ID: <20011119215112.B25118@gintaras> (raw)
In-Reply-To: <20011119101340.I1308@lynx.no> <200111191728.SAA05962@cave.bitwizard.nl>
In-Reply-To: <200111191728.SAA05962@cave.bitwizard.nl>
On Mon, Nov 19, 2001 at 06:28:55PM +0100, Rogier Wolff wrote:
> Now, can someone tell me why "unlimited" is interpreted somehow as 2G
> or something thereabouts? :
>
> /home/wolff> limit
> cputime unlimited
> filesize unlimited
I seem to recall seeing something about this on lkml: the kernel
considers 0xffffffff to be unlimited internally, but the setrlimit
syscall converts user-supplied 0xffffffff into 0x7fffffff.
Here's the relevant thread:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0111.1/0086.html
Marius Gedminas
--
"If it ain't broke, don't fix it."
- Bert Lantz
next prev parent reply other threads:[~2001-11-19 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 13:26 DD-ing from device to device Rogier Wolff
2001-11-19 17:13 ` Andreas Dilger
2001-11-19 17:28 ` Rogier Wolff
2001-11-19 19:51 ` Marius Gedminas [this message]
2001-11-19 20:02 ` Andreas Dilger
2001-11-19 20:13 ` Rogier Wolff
2001-11-19 20:50 ` 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=20011119215112.B25118@gintaras \
--to=mgedmin@centras.lt \
--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