> > "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote: > [...] > > > I don't think real sessions will ever actually overlap; I believe > > > they > > > just refer to data outside their own session using absolute disc > > > addresses. > > Sure, but a bad partition table may specify that too partitions > > span > > overlapping areas. That's what I mean. The partition module > > rejecting > > the session, as done now, is a very simple solution, but, if one > > doesn't do that, one has to decide, what to present to the user. > > Both > > partitions=3F One=3F None=3F > > That's a good question. I would just iterate them in standard order > and > throw away anything that overlaps. That should be almost clean. Mmh, that would work, I believe, but I am too lazy to implement it now. ;-) I think, I put it on a TODO list for the time being. > In fact, I had this once, since the f&#=3Fing fdisk tool from Windows > 98 > created a partition in the middle of the hard disk that spanned over > two other partitions - fortunately, I didn't lost anything due to > that, > and I could remove the partition without any problems later again. I think, that was the right punishment for you for getting involved with The Evil. ;-) CU, Ingo