Date: Tue, 27 Sep 2016 12:16:39 +0930 From: "O'Connor, Daniel" <darius@dons.net.au> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@freebsd.org, Ngie Cooper <yaneurabeya@gmail.com>, Ernie Luzar <luzar722@gmail.com>, "Hartmann, O." <ohartman@mail.zedat.fu-berlin.de> Subject: Re: Destroy GPT partition scheme absolutely, how? Message-ID: <C03C20AC-FE67-4D7C-8239-ED48F844EE38@dons.net.au> In-Reply-To: <1785064.lgVzRW13Wf@ralph.baldwin.cx> References: <20160926150109.0d0d793e@hermann> <57E92726.2020605@gmail.com> <5484D815-4B17-456B-BA60-CC6F4E97AFE3@gmail.com> <1785064.lgVzRW13Wf@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 Sep 2016, at 06:21, John Baldwin <jhb@FreeBSD.org> wrote: > That doesn't always work. In particular, if a disk was partitioned = with GPT > and then you use normal MBR on it afterwards, the 'gpart destroy -F' = of the > MBR will leave most of the GPT intact and the disk will come up with = the old > GPT partitions, not as a raw disk. I wonder how feasible it would be to have a command which runs destroy = for every known partition scheme on a particular device.. Sure there would be some duplicate zeroing but it's not likely to be = significantly slower and considerably more robust. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C03C20AC-FE67-4D7C-8239-ED48F844EE38>