Date: Fri, 20 Mar 2009 23:34:18 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ivoras@FreeBSD.org Cc: reg@FreeBSD.org, svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, marcel@FreeBSD.org Subject: Re: svn commit: r190182 - head Message-ID: <20090320.233418.1605903587.imp@bsdimp.com> In-Reply-To: <9bbcef730903201554x773f46bdy890c8ab48760dce2@mail.gmail.com> References: <200903202151.n2KLpRMB014702@svn.freebsd.org> <20090320221211.GA5205@flint.openpave.org> <9bbcef730903201554x773f46bdy890c8ab48760dce2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <9bbcef730903201554x773f46bdy890c8ab48760dce2@mail.gmail.co=
m>
Ivan Voras <ivoras@FreeBSD.org> writes:
: 2009/3/20 Jeremy Lea <reg@freebsd.org>:
: > Hi,
: >
: > On Fri, Mar 20, 2009 at 09:51:27PM +0000, Ivan Voras wrote:
: >> +20090320:
: >> + =A0 =A0 GEOM_PART has become the default partition slicer for st=
orage devices,
: >> + =A0 =A0 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT sli=
cers. It
: >> + =A0 =A0 introduces some changes: the devices created from MSDOS =
extended
: >> + =A0 =A0 partition entries (EBR) can be named differently than wi=
th GEOM_MBR
: >> + =A0 =A0 and are now symlinks to devices with offset-based names,=
and kernel
: >> + =A0 =A0 dumps are now not allowed to be written to devices whose=
partition
: >> + =A0 =A0 types indicate they are meant to be used for file system=
s.
: >> +
: >
: > This should probably also note the issue with stale disklabels from=
old
: > DD mode disks, which causes the machine to be unbootable. =A0It sho=
uld
: > also mention the "geometry does not match label (255h,63s !=3D 16h,=
63s)"
: > message (which appears to be harmless), and it should also probably=
: > mention that the c partition now covers the entire disk, not just t=
he
: > "DOS partition"... =A0And it should be noted that these changes too=
k place
: > in Decemeber, so that people have a better chance of knowing if the=
y are
: > going to be bitten.
: =
: Ok. Should I re-sort the note into December (probably not since it
: mentions development from a large period) or just mention it in text?=
: =
: @Marcel: is the warning important (I didn't encounter it yet; I guess=
: it probably a quirk of UFS?) and is the "c" change intended? (isn't i=
t
: time to abandon the special case of "c"?)
Historically, UPDATING has done the 'revisionist history' thing where
if we discover a commit on May 5th caused the problem, we use May 5th
as the date, even though the issue was discovered/documented July
31st.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090320.233418.1605903587.imp>