Date: Thu, 27 Aug 2015 19:49:39 -0400 From: Quartz <quartz@sneakertech.com> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Stop using a SATA drive Message-ID: <55DFA213.4030304@sneakertech.com> In-Reply-To: <20150828000118.31f33a35.freebsd@edvax.de> References: <CAPi0psvT5aaHR7kU%2B28qwVDdutyMn7LjhFUGZRWctz4gGfgvgw@mail.gmail.com> <20150824214252.53aa04c6.freebsd@edvax.de> <55DEF869.1010202@sneakertech.com> <20150828000118.31f33a35.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> That would surely be possible if the device in question > would implement a proper reaction to the "eject" command. > If it does, and how it does it, is up to the manufacturer. > Let's say you send the "eject" command to the drive - the > firmware then says goodbye to the host - the device file > disappears. ---- > Yes - mostly the software inside the device, which we > commonly call firmware. On USB, and to a certain extent, > on SATA, the device identifies to the system and enters > a communication with it: stating what device class, who > built it, which model, what capabilities are available > and so on. If the firmware is able to delete that > connection (which is, after all, a _data_ exchange, > not primarily an electric connection), the OS would > act accordingly by removing the device file entry. This line of reasoning doesn't make any sense, or at least it's not related to what I was talking about. Let me try phrasing it a different way: 'diskutil eject foo' will kick the disk off an OSX system and remove its entry from /dev, and this functionality works across all devices and adapters regardless of make or model. Whatever the 'eject' command is doing, it's clearly entirely software side within the OS*. Being software, FreeBSD should be capable of the same, especially considering both OSs have such a close common heritage. *(unless you're claiming all devices everywhere have implemented mac-specific commands in their firmware, but that wouldn't really make sense either since if it's everywhere any other OS could use it too)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55DFA213.4030304>