Date: Tue, 25 Oct 2011 08:34:02 +0400 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: freebsd-current@freebsd.org Subject: Re: aliasing (or renaming) kern.geom.debugflags Message-ID: <4EA63C3A.90304@yandex.ru> In-Reply-To: <alpine.GSO.1.10.1110242118020.882@multics.mit.edu> 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> <alpine.GSO.1.10.1110242118020.882@multics.mit.edu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 25.10.2011 5:18, Benjamin Kaduk wrote: >>> 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. Yes. boot0cfg uses GEOM_PART' control interface and it may write bootcode to the "open" disk. Actually i found bug here and now it is fixed in r226714. -- WBR, Andrey V. Elsukov [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJOpjw6AAoJEAHF6gQQyKF6JpcIAKr7sg8vBAEC9243BEpQVwm8 ycvr9GOTC9eMTiFq4HiaRFlZj3+9n/HzhBp/3pKxXM1tu5kjsnfMDzcdvDlPO3UL +UdYMMozgEcz+lu3/Bg4O2x0MalU9vPmrZt2JJ24laUVYgl6MKpdCXAEgCBat2jN gIEcCSU4RZZp3yxGz0K47RLFnzR4O+PJ6Wd1grXJ3ffbhu2A6VHI9L0OdRKnDBlp KHzwCuAfm8hxT5ZlDUGimPDYitgedkagsNbgg0Z31lfLmkTwXfu1E6w6FhLDn0pt kRZy0GfkPAddh1B1P2JMO1ZVH5Q3XYvZ/+dSSDBBvmeF5sx3a3bqZWULFuOV59Y= =pF4w -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EA63C3A.90304>