From owner-freebsd-questions@freebsd.org Mon Aug 31 13:32:16 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FC629C61E1 for ; Mon, 31 Aug 2015 13:32:16 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25F701F71 for ; Mon, 31 Aug 2015 13:32:15 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id CA3A73F710 for ; Mon, 31 Aug 2015 09:32:07 -0400 (EDT) Message-ID: <55E45757.9000901@sneakertech.com> Date: Mon, 31 Aug 2015 09:32:07 -0400 From: Quartz MIME-Version: 1.0 To: freebsd-questions Subject: Re: Stop using a SATA drive References: <20150824214252.53aa04c6.freebsd@edvax.de> <55DEF869.1010202@sneakertech.com> <55DEFB5A.3080408@FreeBSD.org> <55DEFC74.3040609@sneakertech.com> <20150828000602.b9a288a8.freebsd@edvax.de> <20150829220809.438bbf30.freebsd@edvax.de> In-Reply-To: <20150829220809.438bbf30.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2015 13:32:16 -0000 > The remaining question is: Is it technically valid to > remove a device special file from the devfs file system > corresponding to a device that currently is not in use > (anymore), but is _present_ (attached to the system in > some way)? I keep using OSX as a point of reference, but the way they do it is that once the drive has been "ejected", it's effectively not present anymore. Their mental model is that a drive can be physically attached without being 'connected' software-wise, just that the process of establishing that connection when a device is plugged in has been automated. Personally I've never had a problem with this mental model. Many different things can be physically plugged into a computer without actually functioning (ie; network cable) so I don't see why drives should have special rules. Any anyway, when I eject a drive it's because I'm about to physically remove it.