Date: Thu, 15 Dec 2011 05:47:15 -0600 From: CyberLeo Kitsana <cyberleo@cyberleo.net> To: perryh@pluto.rain.com Cc: lists@midsummerdream.org, freebsd-questions@freebsd.org Subject: Re: AHCI driver and static device names Message-ID: <4EE9DE43.4050402@cyberleo.net> In-Reply-To: <4eea1a01.qEj3VB/DCaWfmK%2B8%perryh@pluto.rain.com> References: <4ED98E9F.9010401@midsummerdream.org> <CAN3mi_2u%2BHwFf3m%2BxvsNncfNpj_rFp94xjAv%2Bf0eFT7c4a%2B8Tg@mail.gmail.com> <4EDA489B.9060503@midsummerdream.org> <4EDA56A3.6090108@cyberleo.net> <4EE912BC.502@midsummerdream.org> <4EE955E7.4010708@cyberleo.net> <4eea1a01.qEj3VB/DCaWfmK%2B8%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/15/2011 10:02 AM, perryh@pluto.rain.com wrote: > I suppose if someone wanted to track down the "official" way of > solving this problem, they could look into how Windows handles it. To my knowledge, Windows (XP, at least; probably others) labels the boot filesystem on install, and just probes all disks every boot for a filesystem with the given label. This is why you can move a Windows disk around with relative impunity (as long as the controller drivers are installed); but simply copying all those files to another filesystem (a-la dump/restore on BSD) never results in a bootable OS, even if you put them back in the same place. This is also why booting with two attached clones of the same Windows system disk is so fun. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net <CyberLeo@CyberLeo.Net> Furry Peace! - http://wwww.fur.com/peace/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE9DE43.4050402>