From owner-freebsd-stable Fri Jan 14 11: 6:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E243B156F8; Fri, 14 Jan 2000 11:01:32 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA29741; Fri, 14 Jan 2000 11:00:08 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001141900.LAA29741@troutmask.apl.washington.edu> Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: <200001141817.NAA04478@entropy.tmok.com> from Brian Hechinger at "Jan 14, 2000 01:17:52 pm" To: wonko@entropy.tmok.com Date: Fri, 14 Jan 2000 11:00:07 -0800 (PST) Cc: Michael Lucas , sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Hechinger wrote: > > /var/tmp on MFS makes cc go faster, but breaks vi.recovery > so if we look at the problem we should not be trying to change the vi recovery > system, but rather cc. if making a change for ANY reason breaks something > else you shouldn't fix the thing you broke, but the thing you are changing. > > make /var/mfs_tmp and have cc use it for it's temporary storage. if cc doesn't > support that then fix cc since being able to specify where your compiler > stores it's temp files is a Good Idea(TM) > *sigh* man gcc Either use -pipe or set the environmental variable TMPDIR. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message