On Tue, 22 Jun 2004 21:38:20 +0100, Kepa Lyman <kepa(a)oceanvoyages.com> wrote:
So after successfully convincing my boss to allow me to install linux at work
on a dual boot machine, I did so this week. Guess what? The infamous (that
I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm
in trouble for screwing up a windows computer that other people need, and the
case for linux at work has just recieved a nail in the coffin... So I get to
try to fix this on my own time, thank you fedora, and just hope that in the
far off future I can try again with fedora core 10 or something...
Prevention and Revovery:
http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html
fwiw, this isn't necessarily widely reproducible as can be assumed,
its certaintly not clear that one can point to a specific
bios/motherboard and know without fail that this issue is going to
happen.
fwiw, the lastest suse and mandrake releases appear to have the same problem and
its very much related to a decision made by the mainline kernel developers
to change how disk geometry is handled. I would imagine that any 2.6
kernel based distribution that boots into a 2.6 kernel environment to
do installation will have similar issues.
reference:
http://qa.mandrakesoft.com/show_bug.cgi?id=7959#c27
http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html#troubleshoot
http://www.eweek.com/article2/0,1759,1585840,00.asp
-jef"the real question is, why was there a communication breakdown
upstream between mainline kernel development and partitioning tool
projects like parted about the importance of dual boot situations
invovling CHS"spaleta