Hi Sarah!
> Hi Alexander,
> 
> I wanted to follow up with you on this bug. I spoke
> with Ethan 
> yesterday, and I think for now we have to put your
> fixes for this bug on 
> hold.
> 
> The overall concerns I have are:
> 
> 1. Changing the behavior of install to actually write
> to the disk before 
> the install has actually started. I know in the case
> of AI the user has 
> really started the install by booting the client, but
> it seems as if 
> what you are proposing is to label the disk part way
> in to reading the 
> manifest, and then proceed with the rest of the
> manifest processing to 
> start the installation.

Yes, I've already change this, now in do_ti.

> 2. Adding this flag to the schema doesn't seem like
> the right thing to 
> do in general. My philosophy about adding things to
> our schema is that 
> we only do this if it is something that we must have
> user input on. I am 
> not sure that this bug indicates that this is the
> answer.

Here I rely on you )

> 3) I agree that we need the disk geometry information
> but, I think there 
> are several issues we need to look at with regard to
> this bug:
> A) First, liborchestrator shouldn't fail if we don't
> t have
> all the attributes for a disk. liborchestrator will
> l be going
> away eventually so making the change in this code is
> s likely not
>       the right thing to do.
>       
> B) We need to figure out if we can get geometry
> y information in
> libdiskmgt even if there isn't a label, for sparc.
> . Right now we
> call GGEOM to get information about a disk on sparc,
> , but if
> there is no label, it doesn't succeed. I am
> m investigating this.

That's right, "Bad Geometry" as answer is not the best solution )       

> C)If it isn't possible to get geometry information
> n about a disk
> on sparc without the disk being labeled, we need to
> o understand
> what the user experience should be to make a disk
> k usable by the
>       installers.
> 
> Thank you for working on this! It is very much
> appreciated. However, at 
> this time let's keep this work on hold until we
> understand the best way 
> to proceed.
> 
> Regards,
> sarah
> ****
Thank you very much, Sarah, 
let's keep each other informed.


Cheers,
Alex
-- 
This message posted from opensolaris.org
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to