From owner-freebsd-hackers Wed Aug 14 10:19:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA15236 for hackers-outgoing; Wed, 14 Aug 1996 10:19:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA15230 for ; Wed, 14 Aug 1996 10:19:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA29273; Wed, 14 Aug 1996 10:10:48 -0700 From: Terry Lambert Message-Id: <199608141710.KAA29273@phaeton.artisoft.com> Subject: Re: Nightmare. To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 14 Aug 1996 10:10:48 -0700 (MST) Cc: ulf@lamb.net, jkh@time.cdrom.com, hackers@freebsd.org In-Reply-To: <199608141645.LAA12047@brasil.moneng.mei.com> from "Joe Greco" at Aug 14, 96 11:45:36 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I would go more into the direction of checking if the dump device is a > > mounted file system. Easy check. > > I tend to agree, but wonder if it would not make more sense to tackle this > from a different angle. > > Consider all the programs that could clobber a mounted file system. Would > it make more sense if we somehow protected a mounted disk device from > being clobbered? Yes. Disable the raw device for mounted disks. The stacking architecture disallows (since it internall references the vnodes) a device level soloution that does anything to the non-raw device. If we can get past the point where devfs is a mandatory item, then we can fix all of this without breaking FS stacking. There is no soloution otherwise that could not be broken by a clever idiot. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.