On Thu, May 26, 2005 at 09:49:02PM +0200, Vincent wrote:
> > Unfortunately the logic of disklabel is overly complex because it 
> contains
> >code to update the bootcode on about 2 architectures.  Until this is all
> >ripped out it is rather difficult to fix properly - ie separate the 'read
> >disk label' and 'write disk label' paths completely.
> 
> 
> Thank you for this explanation.
> Yet, it raises another question: why did it work on sd1? :)

It depends on the initial state of the disk...

Before I added the (short) banner message to the mbr code it looked
as though the system had locked up.  The banner output does give a
good clue as to what is actually hapenning.

	David

-- 
David Laight: david@l8s.co.uk