Mailinglist Archive: opensuse-bugs (4760 mails)

< Previous Next >
[Bug 597723] boot partition may exceed certain BIOS limits
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 22 Apr 2010 09:27:55 +0000
  • Message-id: <20100422092755.37FEDCC69A@xxxxxxxxxxxxxxxxxxxxxx>

Thomas Fehr <fehr@xxxxxxxxxx> changed:

What |Removed |Added
CC| |kukuk@xxxxxxxxxx,
| |mge@xxxxxxxxxx
InfoProvider|fehr@xxxxxxxxxx |coolo@xxxxxxxxxx

--- Comment #39 from Thomas Fehr <fehr@xxxxxxxxxx> 2010-04-22 09:27:53 UTC ---
According to Torstens interesting claim in comment #37 BIOS can only reliable
boot from the first 503 Megabytes of a disk. Founded on that claim he demands
in comment 38 that we change yast2 partitioning code so that we enforce a
separate boot partition or a root partition smaller than 503MB for all
installation scenarios.

Fulfilling this demand would have following slight disadvantages:
- coexistence of Windows and Linux would be impossible since most Windows
installations are at the start of the disk, larger than 503 MB and Windows
shrinking makes space available only at the end of the disk
- having multiple installations on the same disk would be much harder.
So far there was one root fs for every installation. Now there is a separate
partition needed for /boot and one for root for each installation with the
additional restriction that every boot partition need to be in starting 503MB
of a disk.
- Since these restrictions are new, almost all older installations do not
them and update would be impossible from a lot of older secnarios
- We are currently at Milestone 5 and it is quite late in development process
to rewrite yast2 partitioning code
- Lots of old autoyast.xml files would not work any more (the problem was first
observed on Uwe's test machine with his standard autoyast test XML file).

Because of the above disadvantages, I am a little bit reluctant to change yast2
partitioning code solely on Torsten's demand (and in addition this would not
fix the problem of non-booting autoyast installations at all). I am adding SLES
people to CC: since the partitioning code is common between SLES and
openSuSE and I would prefer to avoid to rewrite the code again for next SLES.

So how should we proceed with this bug?

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >