Date: Fri, 14 Jan 2000 13:17:52 -0500 (EST) From: Brian Hechinger <wonko@users.tmok.com> To: mwlucas@blackhelicopters.org (Michael Lucas) Cc: 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: <200001141817.NAA04478@entropy.tmok.com> In-Reply-To: <200001141602.LAA51996@blackhelicopters.org> from Michael Lucas at "Jan 14, 2000 11: 2:58 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Lucas drunkenly mumbled... > A *lot* of us have local administration procedures that are > inappropriate elsewhere, but are proper in a local context (or are > wrong, but they want or need to do anyway). i'm sorry for not letting this die, however.... while it is true that a lot of people have a lot of administration procedures that exist solely for our local setup there are sometimes better solutions than the ones we are using. for example, we'll go with this current thread. /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) now cc is faster and vi.recovery isn't broken. maybe we should spend less time discussing the technical merits of an action and rather spend our time look for better solutions. -brian -- Brian Hechinger UNIX System Administrator Half.com brian@half.com 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?200001141817.NAA04478>