Date: Fri, 14 Jan 2000 11:00:07 -0800 (PST) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: wonko@entropy.tmok.com Cc: Michael Lucas <mwlucas@blackhelicopters.org>, sheldonh@uunet.co.za, khera@kciLink.com, ady@warpnet.ro, trond@ramstind.gtf.ol.no, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Making sure /var/tmp/vi.recover exists during reboot Message-ID: <200001141900.LAA29741@troutmask.apl.washington.edu> In-Reply-To: <200001141817.NAA04478@entropy.tmok.com> from Brian Hechinger at "Jan 14, 2000 01:17:52 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001141900.LAA29741>