Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Oct 2009 16:32:18 +0100 (BST)
From:      Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
To:        Daniel Nebdal <dnebdal@gmail.com>
Cc:        Antony Mawer <lists@mawer.org>, =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= <des@des.no>, David Ehrmann <ehrmann@gmail.com>, freebsd-current@freebsd.org, John Baldwin <john@baldwin.cx>
Subject:   Re: 8.0rc1 not recognizing partitions on EPIA SN
Message-ID:  <20091018162750.E82400@ury.york.ac.uk>
In-Reply-To: <f8b073790910171705p1c5c996atee2c6aa109ec9d15@mail.gmail.com>
References:  <4ACE6D84.3000209@gmail.com> <4ACE833A.3030506@uffner.com> <4ACE9DFD.3010207@gmail.com> <200910131644.04358.john@baldwin.cx> <ea2d4a5b0910170126r78b2afcfib1547722bb3758b8@mail.gmail.com> <86ljja3ud5.fsf@ds4.des.no> <f8b073790910171705p1c5c996atee2c6aa109ec9d15@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-329387635-1255879938=:82400
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Sun, 18 Oct 2009, Daniel Nebdal wrote:
> 2009/10/17 Dag-Erling Sm=F8rgrav <des@des.no>:
>> Antony Mawer <lists@mawer.org> writes:
>>> Am I correct in reading this as saying that -any- system which was
>>> setup as dangerously dedicated will be unbootable under 8.0, and the
>>> only way to fix is to basically repartition and reinstall...? If so
>>> ... !!!
>>
>> You brought it upon yourself by setting it up that way in the first
>> place. =A0It's called *dangerously* dedicated for a reason.
>>
>
> Indeed, though I was under the impression that the reason was "nothing
> else will understand this", not "we might not support this in the
> future".

As I understand things, the problems are partially due to a bug in older=20
versions of sysinstall that created incorrect disklables in DD mode, and=20
partially due to the new GEOM partitioning modules, which now parse these=
=20
ambiguous disk labels differently.

You can get around this by compiling a custom kernel and using the old=20
partitioning modules (use GEOM_MBR and GEOM_BSD rather than GEOM_PART),=20
but you may well just be postponing the problem as I believe the old=20
modules were planned to be removed at some point.

Gavin
--0-329387635-1255879938=:82400--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091018162750.E82400>