From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 10:23:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDC5816A41C for ; Fri, 10 Jun 2005 10:23:58 +0000 (GMT) (envelope-from andrew@scoop.co.nz) Received: from a2.scoop.co.nz (aurora.scoop.co.nz [202.50.109.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6A843D1F for ; Fri, 10 Jun 2005 10:23:57 +0000 (GMT) (envelope-from andrew@scoop.co.nz) Received: from a2.scoop.co.nz (localhost [127.0.0.1]) by a2.scoop.co.nz (8.13.3/8.12.11) with ESMTP id j5AANuKd097821; Fri, 10 Jun 2005 22:23:56 +1200 (NZST) (envelope-from andrew@scoop.co.nz) Received: from localhost (andrew@localhost) by a2.scoop.co.nz (8.13.3/8.12.11/Submit) with ESMTP id j5AANtCI097818; Fri, 10 Jun 2005 22:23:55 +1200 (NZST) (envelope-from andrew@scoop.co.nz) X-Authentication-Warning: a2.scoop.co.nz: andrew owned process doing -bs Date: Fri, 10 Jun 2005 22:23:55 +1200 (NZST) From: Andrew McNaughton To: "Andrey V. Elsukov" In-Reply-To: <42A950C0.4060809@yandex.ru> Message-ID: <20050610221931.R20085@a2.scoop.co.nz> References: <42A93B71.5080202@yandex.ru> <20050610070645.GB9196@xor.obsecurity.org> <42A94207.9070507@yandex.ru> <20050610195040.M20085@a2.scoop.co.nz> <42A950C0.4060809@yandex.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.83/921/Wed Jun 8 20:51:44 2005 on a2.scoop.co.nz X-Virus-Status: Clean Cc: FreeBSD Mailing List Subject: Re: How to configure FreeBSD for rebooting when kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 10:23:59 -0000 On Fri, 10 Jun 2005, Andrey V. Elsukov wrote: > Andrew McNaughton wrote: >> You can't unmount your root file system. > >> Because of this it's possibly a good idea to have as minimal a root >> partition system as possible, off the raid system, and very rarely changed, >> so it's unlikely to get screwed up. > > Yes, i know. Root FS, and othser system FS's is on the other disk. RAID > stripe have only public data. You want a system where if the mounts (other than the root fs) fail, the system will still be adminsterable. To maintain remote access, you'd need to make sure that all your basic login tools are on the root disk. eg sshd, root's default shell, etc. Should be doable, but would be nice if it didn't involve as much custom tinkering as I expect it would. Andrew -- Life is a process of becoming, a combination of states we have to go through. Where people fail is that they wish to elect a state and remain in it. This is a kind of death. -- Anais Nin ------------------------------------------------------------------- Andrew McNaughton http://www.scoop.co.nz/ andrew@scoop.co.nz Mobile: +61 422 753 792 -- pgp encrypted mail welcome keyid: 70F6C32D keyserver: pgp.mit.edu 5688 2396 AA81 036A EBAC 2DD4 1BEA 7975 A84F 6686