From owner-freebsd-current Thu Feb 5 08:20:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11206 for current-outgoing; Thu, 5 Feb 1998 08:20:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11195 for ; Thu, 5 Feb 1998 08:20:16 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA09900; Thu, 5 Feb 1998 08:20:08 -0800 (PST) (envelope-from jdp) Message-Id: <199802051620.IAA09900@austin.polstra.com> To: abial@nask.pl Subject: Re: Custom init(8) (and some ideas) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 05 Feb 1998 08:20:08 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In article , Andrzej Bialecki wrote: > Also, IMHO it would be a good option to the kernel and/or ld.so to tell > them not to load .text at all (it could apply to .text section of binaries > as well as shared libs), just to mmap it, if the backing filesystem is of > MFS type. Both the kernel and ld.so do that (use mmap), no matter what type of filesystem the executable or shared library is on. Actually, they mmap not only text, but also data and bss. Copy-on-write prevents that from causing problems. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth