From owner-freebsd-chat Wed Apr 14 21:35: 0 1999 Delivered-To: freebsd-chat@freebsd.org Received: from mail.webmaster.com (mail.webmaster.com [209.133.28.138]) by hub.freebsd.org (Postfix) with ESMTP id 8BE7614C03 for ; Wed, 14 Apr 1999 21:34:58 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by mail.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 14 Apr 1999 21:23:50 -0700 From: "David Schwartz" To: Cc: Subject: RE: swap-related problems Date: Wed, 14 Apr 1999 21:32:36 -0700 Message-ID: <000001be86f8$fcd4d2d0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-reply-to: <14101.21892.460225.807747@avalon.east> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can't affect ANSI compliance since it is outside the C world. > Nor should it be a practical problem, since one just supplies > distinct backing files. Inelegant perhaps, is the worst I could > say of it. I'm not sure I'm following you. How are you suggesting a person write a portable application so that copy-on-write of its code or libraries doesn't cause it to blow up in an overcommit situation? DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message