From owner-freebsd-current Fri Nov 22 7:56:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 889B037B401; Fri, 22 Nov 2002 07:56:58 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D116143E3B; Fri, 22 Nov 2002 07:56:57 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAMFusBF062132; Fri, 22 Nov 2002 10:56:55 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 22 Nov 2002 10:56:54 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: dd@FreeBSD.org Cc: current@FreeBSD.org Subject: Keeping mdmfs in sync with newfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dima, I recently switched two of my diskless crash boxes over to rc.d from the old rc scripts, and discovered that the new rc.diskless code uses mdmfs. Unfortunately, it doesn't appear to support UFS2, since the newfs "-O" flag isn't supported -- and it isn't quite so simple to add, since mdmfs has renamed the newfs "-o" flags to "-O", causing a namespace collision. Basically, we need to be able to generate the -O1 or -O2 argument in the newfs call from mdmfs. I can hack it locally in the mean time, but there is a long term maintenance question about passing newfs options through mdmfs due to command line argument collisions. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message