Date: Mon, 31 Aug 2015 09:32:07 -0400 From: Quartz <quartz@sneakertech.com> To: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Stop using a SATA drive Message-ID: <55E45757.9000901@sneakertech.com> In-Reply-To: <20150829220809.438bbf30.freebsd@edvax.de> References: <CAPi0psvT5aaHR7kU%2B28qwVDdutyMn7LjhFUGZRWctz4gGfgvgw@mail.gmail.com> <20150824214252.53aa04c6.freebsd@edvax.de> <55DEF869.1010202@sneakertech.com> <55DEFB5A.3080408@FreeBSD.org> <55DEFC74.3040609@sneakertech.com> <20150828000602.b9a288a8.freebsd@edvax.de> <CAPi0psvMcrHKCQK9kBSacMmNie_042q9RQtKit6k4dvwA0GJQg@mail.gmail.com> <20150829220809.438bbf30.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55E45757.9000901>