From owner-freebsd-current Wed Oct 4 15:29:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D88DD37B503; Wed, 4 Oct 2000 15:29:05 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA20603; Thu, 5 Oct 2000 09:28:41 +1100 Date: Thu, 5 Oct 2000 09:28:36 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jordan Hubbard Cc: current@freebsd.org, bde@freebsd.org Subject: Re: ext2fs support for writing - what's the verdict? In-Reply-To: <91787.970681331@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Oct 2000, Jordan Hubbard wrote: > As most people probably know, you can't write on ext2fs filesystems > with any of the "newer" Linux distributions, like Red Hat 6.2 on > up. The filesystem mount refuses r/w permission with the message > "WARNING: R/W mount of #
denied due to unsupported optional features" > > Do we plan to do anything about that? Heck, I'm not even sure who > maintains ext2fs these days - bde maybe? [hopeful facial expression] :-) I have 64K off uncommitted diffs (-c2) for ext2fs, but none for sparse superblocks. This problem is easy to work around by not using unsupported optional features. Run tune2fs and e2fsck under Linux to turn off the features (see tune2fs(8)). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message