Date: Mon, 24 Oct 2011 21:18:57 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: freebsd-current@freebsd.org Subject: Re: aliasing (or renaming) kern.geom.debugflags Message-ID: <alpine.GSO.1.10.1110242118020.882@multics.mit.edu> In-Reply-To: <4EA4E6B8.7040108@yandex.ru> References: <81477.1318015137@critter.freebsd.dk> <4E8F55CC.3060302@FreeBSD.org> <4E8F5D47.9070904@yandex.ru> <CACqU3MXr-JoAd=q%2BobUiSOkQG03Kq4jEs6g%2BvkJ5V99i23713g@mail.gmail.com> <4EA4E6B8.7040108@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Oct 2011, Andrey V. Elsukov wrote: > On 24.10.2011 1:54, Arnaud Lacombe wrote: >> NOTE >> Protection mechanisms in the geom(4) subsystem might prevent boot0cfg >> from being able to update the MBR on a mounted disk. Instructions for >> temporarily disabling these protection mechanisms can be found in the >> geom(4) manpage. Specifically, do a >> >> sysctl kern.geom.debugflags=0x10 >> >> to allow writing to the MBR, and restore it to 0 afterwards. > > This is stale message. boot0cfg might work without this. On a *mounted* disk? Surely that qualifies as an "open" for the purposes of the check. -Ben Kaduk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1110242118020.882>