From owner-freebsd-arch Wed Oct 25 10: 9:34 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 557FF37B4D7 for ; Wed, 25 Oct 2000 10:09:31 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id TAA29531; Wed, 25 Oct 2000 19:09:30 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id TAA54796; Wed, 25 Oct 2000 19:09:30 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 25 Oct 2000 19:09:30 +0200 (CEST) From: Marius Bendiksen To: Dag-Erling Smorgrav Cc: arch@FreeBSD.ORG Subject: Re: Ideas concerning fsck In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We can get around the need for fstab by using the bootfs idea that AIX and > > others use (Poul-Henning has suggested this also in connection with DEVFS) > > to get less magic in the boot sequence. > I'm not familiar with the concept of bootfs - can somebody enlighten > me? Certainly. A bootfs is basically a filesystem that the system can boot from, which will be in a safe state, because changes are not written back to disk. One example would be when you make an MFS image and boot from it, the other would be doing SCO-style stripped down fs'es which are mounted read-only. The advantage is that you can then hardwire rootvp to that filesystem, and have files stuck on it to intelligently discover how to bring up the system correctly, without doing lots of magic to discover what devices are available for use, and which one you want to boot from, etc. Also, as the state is always consistant, you have no problem with stuff like depending on the validity of the contents of a file, and you don't need to fsck / seperately from the rest of the volumes. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message