From owner-freebsd-current Wed Aug 13 21:59:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA23105 for current-outgoing; Wed, 13 Aug 1997 21:59:42 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA23100 for ; Wed, 13 Aug 1997 21:59:40 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA23455; Wed, 13 Aug 1997 21:59:44 -0700 (PDT) Message-Id: <199708140459.VAA23455@implode.root.com> To: Terry Lambert cc: kato@migmatite.eps.nagoya-u.ac.jp (KATO Takenori), current@FreeBSD.ORG Subject: Re: Read-only mount of union filesystem In-reply-to: Your message of "Wed, 13 Aug 1997 11:19:46 PDT." <199708131819.LAA12802@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 13 Aug 1997 21:59:44 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I'm not 100% sure of the change in union_lookup(). >> >> >> 2. Following patch supports rdonly mount in vfs layer: >[ ... ] > >> I will commit one of them after discussion. Please comment. > >I support the second patch. > >Note that read-only devices need to propagate this falg as an >override from the device attributes. I changed the behavior in FreeBSD to what it is now (which is also the same as it is in Lite-2). For information on why it is this way, see PR#782. In my opinion, the current structure is correct. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project