From owner-freebsd-current@FreeBSD.ORG Mon Sep 27 09:31:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B5A916A4CE for ; Mon, 27 Sep 2004 09:31:22 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE95343D3F for ; Mon, 27 Sep 2004 09:31:21 +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 i8R9VKFM043594 for ; Mon, 27 Sep 2004 11:31:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) From: "Poul-Henning Kamp" Date: Mon, 27 Sep 2004 11:31:20 +0200 Message-ID: <43593.1096277480@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: [TEST] ucom detach patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2004 09:31:22 -0000 http://phk.freebsd.dk/patch/ucom.patch This patch should make it safe to remove a ucom serial device no matter what is going on at the time of removal. The patch also changes the naming of the devices to give the full complement of serial facilities, so you will see the following devices in /dev: /dev/ttyU0 /dev/ttyU0.init /dev/ttyU0.lock /dev/cuaU0 /dev/cuaU0.init /dev/cuaU0.lock Please test and report. -- 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.