On 1 Aug 02 at 23:16, Marcin Dalecki wrote:
> Lets not forgett that the code removed would allow to read behind the
> partion in question and was broken therefore. However the real world
> example from Petr worries me and makes me thinking that the partition
> scanning time solution could turn out to be most adequate -> we have the
> FAT partition ID there at hand and could adjust the partition
> parameters in question properly with ease. Both of them: offset *and* size.
>
> Petr would you mind dumping the dd=/dev/hdx count=10 of the
> disk in question at me? Or do you preferr to go after this blotch
> yourself?
First sector contains valid partition table, but all partitions are
set to type 0x55, EZDrive. AFAIK EZDrive synchronizes this inivisble
partition with one from sector 2 on each reboot. Second sector contains
'real' partition table, with types set to Linux, Linux swap, VFAT and
so on. I do not have extended partition on the drive, so I do not know
whether this record will have 0x55 or correct type in the sector 1.
Problem only occurs when you'll run LILO (if you have installed it
in /dev/hdx instead of in /dev/hdx#), or install-mbr - it will overwrite
ezdrive, and you have to find diskette and reinstall EZDrive to make
disk bootable in this obsolete system (btw, it is PentiumII).
So only problem is that we do not have special /dev/hdx-mbr device
for accessing MBR, all code expects that it is in first sector of the
/dev/hdx, while with 0_to_1 remap it is in second one.
Petr Vandrovec
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:17 EST