From owner-freebsd-stable Wed Dec 13 3:53: 1 2000 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 13 03:53:00 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from newport.piter.net (unknown [195.131.87.24]) by hub.freebsd.org (Postfix) with ESMTP id C2B0537B400 for ; Wed, 13 Dec 2000 03:52:58 -0800 (PST) Received: (from cyril@localhost) by newport.piter.net (8.9.3/8.9.3) id OAA95968; Wed, 13 Dec 2000 14:55:37 +0300 (MSK) (envelope-from cyril) Date: Wed, 13 Dec 2000 14:55:37 +0300 (MSK) From: "Cyril A. Vechera" Message-Id: <200012131155.OAA95968@newport.piter.net> To: cyril@newport.piter.net, doconnor@gsoft.com.au Subject: Re: softupdates and "/" Cc: danh@gelatinous.com, stable@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 12-Dec-00 Cyril A. Vechera wrote: > > * danh@gelatinous.com [001211 11:50] wrote: > > > Hi, is there anything wrong with enabling softupdates > > > on my / partition? > > > > The total pure way is to mount / read-only with softupdating other > > file systems. > > One of the easiest ways is to edit /etc/rc and add the appropriate tunefs commands > before the file systems are mounted.. > > Works well :) Sorry, broken language. I meant that on server only safe way is mounting / read-only to keep out of unrecoverable file system errors and do not allow usual writes at all (mount -u -w / when it needed). Hold static compiled sshd somewhere in /sbin so we can login in after any crash (we assume, that read-only / is not affected) and do repairs. Cyril. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message