Date: Mon, 20 Apr 1998 06:54:18 +0200 (CEST) From: Martin Welk <mw@freibergnet.de> To: The Hermit Hacker <scrappy@hub.org> Cc: stable@FreeBSD.ORG, lrios <lrios@ziplink.net>, Wes Peters - Softweyr LLC <softweyr@xmission.com> Subject: Re: Linux And FreeBSD Message-ID: <XFMail.980420065418.mw@freibergnet.de> In-Reply-To: <Pine.NEB.3.95.980416150841.10565Q-100000@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16-Apr-98 The Hermit Hacker wrote: () Not completely accurate...I've had a bugger of a time with my () -stable box and crashes, yet my ASYNC mounted drives have *yet* to cause () me any grief. I don't do it on anything i consider to be critical, so () just use it for news, but my history file is mounted async, and I () imagine () I would notice corruption very quickly in that... I do the same, mounting /var/tmp and /var/news on a separate disk async. Until the system is running normally and shut down regularly, I have experienced no problems. I don't experience difficulties either mounting /usr async doing compiles in /usr/src. But on power failure, I have one time lost my file /var/tmp when there was heavy disk activity. For /var/tmp, that's no problem, newfs is your friend. For /var/news, it's not totally the same, but as I run a single-user leaf site, I have no problem to deal with that risk. At work, on "production machines", I don't use async mounts. Regards, Martin -- Liebscher & Partner Werbeagentur GbR // Martin Welk Advertising, Art Design & DTP // network administration Xlink Point Of Presence Freiberg // phone: (+49|0) 3731 781-387 Am St. Niclas Schacht 13 // fax: (+49|0) 3731 781-377 D-09599 Freiberg, Germany // http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980420065418.mw>