summaryrefslogtreecommitdiffstats
path: root/usr.bin/comm
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1997-09-13 11:41:50 +0000
committerpeter <peter@FreeBSD.org>1997-09-13 11:41:50 +0000
commit763b84b2965e460b085c5f5e2edd1fda366f7841 (patch)
tree0fe42166fe0a90bad4815970c0a830885b25ff9a /usr.bin/comm
parentfeaeba35cd6a2eb29f6751f4ea6527b8966d49c8 (diff)
downloadFreeBSD-src-763b84b2965e460b085c5f5e2edd1fda366f7841.zip
FreeBSD-src-763b84b2965e460b085c5f5e2edd1fda366f7841.tar.gz
Some tweaks to get this to cope with ELF where the address space starts
higher up in memory (0x0800000 upwards) rather than near zero (0x1000 for our qmagic a.out format). The method that mount_mfs uses to allocate the memory within data size rlimits for the ram disk is entirely too much of a kludge for my liking. I mean, if it's run as root, surely it makes sense to just raise the resource limits to infinity or something, and if it's a non-root user mount (do these work? with mfs?) it could just fail if it's outside limits.
Diffstat (limited to 'usr.bin/comm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud