Date: Wed, 6 Jun 2007 19:31:54 +0400 From: Ruslan Ermilov <ru@freebsd.org> To: Yuri Pankov <yuri.pankov@gmail.com> Cc: freebsd-current@freebsd.org, Pav Lucistnik <pav@freebsd.org> Subject: Re: /boot/mbr miscompiled? Message-ID: <20070606153154.GB14456@rambler-co.ru> In-Reply-To: <20070606150536.GB875@darklight.abyss> References: <20070606135815.GA913@darklight.abyss> <20070606145904.GA14456@rambler-co.ru> <20070606150536.GB875@darklight.abyss>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 06, 2007 at 07:05:36PM +0400, Yuri Pankov wrote: > On Wed, Jun 06, 2007 at 06:59:04PM +0400, Ruslan Ermilov wrote: > > On Wed, Jun 06, 2007 at 05:58:15PM +0400, Yuri Pankov wrote: > > > Hi, > > > > > > I've noticed lately that I can't install /boot/mbr using boot0cfg. > > > > > > [root@darklight:~]# boot0cfg -B -b /boot/mbr ad4 > > > boot0cfg: /boot/mbr: unknown or incompatible boot code > > > > > > -r--r--r-- 1 root wheel - 512 Jun 6 17:45 /boot/mbr > > > /boot/mbr: x86 boot sector > > > > > I think you'll have to use "fdisk -B" to do that. > > (boot0cfg(8) only installs boot0 and boot0sio.) > > > > Thank you Ruslan. > > Shouldn't boot0cfg(8) manpage be updated accordingly (EXAMPLES section, > at least)? > Hmm. The documentation bug was introduced recently in rev. 1.30 of boot0cfg.8 (and merged into RELENG_6). I've just checked on 4.x, 6.x, and 7.0 systems here, and /boot/mbr could never be accepted by boot0cfg(8) because the second signature (the "Drive" string) isn't there. I've Cc:ed the committer of this change. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070606153154.GB14456>