From owner-freebsd-hackers Tue Aug 24 6:58:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [132.206.78.3]) by hub.freebsd.org (Postfix) with ESMTP id E669F14D18 for ; Tue, 24 Aug 1999 06:58:06 -0700 (PDT) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id JAA00845; Tue, 24 Aug 1999 09:56:12 -0400 (EDT) Date: Tue, 24 Aug 1999 09:56:12 -0400 (EDT) From: der Mouse Message-Id: <199908241356.JAA00845@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech-kern@netbsd.org Subject: Re: Need some advice regarding portable user IDs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Solving this is not trivial, I don't think changing the panic() to >> return(appropriate_error_code) is the rigth thing to do, in some >> case you want to panic if a filesystem gets corrupted. > [...consider / or /usr...] I think an error return is preferable to a panic, during the mount operation. During normal operation, it seems to me that the right thing is to panic if the mount was done by root and to do the forcible-unmount thing if non-root. (This arguably should be a mount option which is forced on for non-root mounts, so that root mounts can get the force-unmount semantics if desired.) der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message