Messages in this thread | | | Date | Sat, 20 Feb 1999 21:18:53 -0500 (EST) | From | Alexander Viro <> | Subject | Re: either kernel or fdisk does not understand Win95 extended partitions. |
| |
On Sun, 21 Feb 1999, Guest section DW wrote:
> > Add to your collection the following example: guy installed RH on > > /dev/hda and got the type of /dev/hdb1 changed from 0xa5 to 0xb5. > > Hmm. Usually this is user error. > Certain bootloaders such as System Commander XOR the partition type > with 0x10 in order to hide the partition. (OS/2 BM also uses this > technique, and changes 1,4,6,7 into 11,14,16,17 (hex).)
I know. But AFAIK setup was: hdb - old hda (wd0 ;-) with FreeBSD *only* and BootEasy as loader. hda - new disk with fresh RH install (LILO as loader with B-E as chained one). I will look through LILO and B-E source, but IIRC none of them pulls such tricks.
It *may* be user error (and normally I would assume exactly that), but I *really* doubt that it was error in use of either LILO or B-E.
> So, I tend to believe that people reporting a change from > 0xa5 to 0xb5 use e.g., System Commander, and that there is > not necessarily a connection with the installation of RedHat. > > (Or maybe RedHat changed the active partition without undoing > the XOR.) If it touched partition table on *slave* - it's broken. Active or not, it's on the second disk and there is no reason to do anything with it - LILO is in full control anyway.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |