From owner-freebsd-fs Mon Apr 29 15:45:26 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mail.allcaps.org (mail.allcaps.org [208.252.245.17]) by hub.freebsd.org (Postfix) with ESMTP id 00A7137B404 for ; Mon, 29 Apr 2002 15:45:24 -0700 (PDT) Received: from mail.allcaps.org (localhost [127.0.0.1]) by mail.allcaps.org (Postfix) with ESMTP id 83C7632601 for ; Mon, 29 Apr 2002 15:45:23 -0700 (PDT) Received: from localhost (bsder@localhost) by mail.allcaps.org (8.12.3/8.12.3/Submit) with ESMTP id g3TMjNJ9016549 for ; Mon, 29 Apr 2002 15:45:23 -0700 (PDT) X-Authentication-Warning: mail.allcaps.org: bsder owned process doing -bs Date: Mon, 29 Apr 2002 15:45:23 -0700 (PDT) From: "Andrew P. Lentvorski" To: Subject: Non-standard root filesystems Message-ID: <20020429153020.Q16532-100000@mail.allcaps.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Could someone fill me in on the current status of either A) remounting a root filesystem or B) mounting a non-standard fs as a root fs? I've bumped into this three times now. Twice as part of the vinum stuff and a third as part of a solid-state media problem. In the case of vinum, I actually had a client choose a Linux system because its rootfs is software RAIDable. Other people are also starting to bump into the issue as brought up in the NFS attribute thread. (AFS can't be used because the root filesystem can't be remounted completely) What is the current status? Or, alternatively, what are the issues with implementation? Is it a political problem (no perceived need/low priority/coming in FreeBSD 5.X) or is it a massive amount of work problem? Thanks, -a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message