Date: Fri, 28 May 2010 10:13:12 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Garrett Cooper <yanefbsd@gmail.com> Cc: geom@freebsd.org Subject: Re: gpart - how to point to the other disk? Message-ID: <4BFF6D08.3080907@icyb.net.ua> In-Reply-To: <AANLkTing_n-oXqztKyODYX2DE8HKs_N10_jGsKSuY8W4@mail.gmail.com> References: <AANLkTikSBEPKD1Hxd7EbF7B282OeA2GXtMCnKrwTjIv7@mail.gmail.com> <AANLkTing_n-oXqztKyODYX2DE8HKs_N10_jGsKSuY8W4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/05/2010 00:16 Garrett Cooper said the following: > On Thu, May 27, 2010 at 2:04 PM, Garrett Cooper <yanefbsd@gmail.com> wrote: >> Hi FS folks, >> I'm currently looking at switching over bits of our existing >> infrastructure from boot0cfg / fdisk to gpart, and one of the things >> that not 100% clear is -- how do I get one disk to point to the other >> one? I can do this today with boot0cfg [...] -s 5, but AFAICT gpart >> bootcode should supersede this usage (or am I incorrect?). Partially. the usage of boot0cfg that you mention changes some bits within installed boot0 to reconfigure it. boot0cfg can either read existing boot block from disk, modify it and write back; or it can take a new boot block image and do the same. gpart bootcode can install boot0 and can do equivalent of boot0cfg -B -b ... gpart doesn't do any boot block configuration. As I understand boot0cfg should still work well. It reads boot block directly from disk device using RO access and it write boot block using "bootcode" geom verb, which exactly the same as what gpart does. But perhaps I misunderstood something. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFF6D08.3080907>