From owner-freebsd-bugs Tue May 9 0:40: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 6B61A37BAAA for ; Tue, 9 May 2000 00:40:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA83785; Tue, 9 May 2000 00:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 9 May 2000 00:40:02 -0700 (PDT) Message-Id: <200005090740.AAA83785@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Gregory Bond Subject: Re: conf/18461: vi.recover misplaced in /var/tmp Reply-To: Gregory Bond Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/18461; it has been noted by GNATS. From: Gregory Bond To: clefevre@citeweb.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: conf/18461: vi.recover misplaced in /var/tmp Date: Tue, 09 May 2000 17:36:14 +1000 > vi.recover should not be in /var/tmp. imagine the case > where /var/tmp is a memory filesystem. upon reboot, > everything is lost. On the contrary, /var/tmp is exactly the right spot for vi.recover, because /var/tmp is -explicitly documented- to remain over reboots. See "man hier". Anyone who uses mfs for /var/tmp is just plain wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message