From owner-freebsd-arch@FreeBSD.ORG Sat Dec 18 17:51:59 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E353616A4CE for ; Sat, 18 Dec 2004 17:51:59 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D33143D49 for ; Sat, 18 Dec 2004 17:51:59 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBIHpvic067698 for ; Sat, 18 Dec 2004 18:51:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org From: Poul-Henning Kamp Date: Sat, 18 Dec 2004 18:51:57 +0100 Message-ID: <67697.1103392317@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: Forcefully unmounting devfs... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2004 17:52:00 -0000 Brainteaser for the x-mas days: What is the correct handling of busy device vnodes belonging to a devfs mountpoint which is being forcefully unmounted ? If you think this has a simple answer, please don't bother replying. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.