Michal,

beadmin.py:

447 - I would highly recommend against constructing this path.
Use bee.get("root_ds") instead (we will likely implement a better api
to get these elements in the future so that apps don't need to know these
key names.  We won't change the key names of course...)

463 - Does this app get back-published to 86?  If so it was -f to suppress
the prompt back then.  In build 91 and later, its -F to suppress, and -f is
changed to force the unmount of the BE if its currently mounted.
Sorry :-\   If this really breaks you, use be.beDestroy(bename, 1, 1)
which works all the way back to 86.


thanks,
-ethan


Michal Pryc wrote:
> Hello,
> I have made some changes to support BE Management:
> http://defect.opensolaris.org/bz/show_bug.cgi?id=3201
>
> The webrev is at:
> http://cr.opensolaris.org/~migi/10_09_be_management_3201_v1/
>
> I have made some tests and it looks like everying works fine :)
>
> Some screenshots from the BE Management:
> http://cr.opensolaris.org/~migi/be_admin_screenshots_v0/
>
> be_admin0.png: Menu entry
>
> be_admin1.png: BE management just after start. The OK and Cancel buttons 
> are active all the time. Reset is active only when the user made some 
> changes.
>
> be_admin2.png: Only the "Active on Reboot" BE was changed and OK was 
> pressed by the user - the confirmation dialog.
>
> be_admin3.png: Only one BE was selected to be removed and user clicked 
> OK button - the confirmation dialog.
>
> be_admin4.png: 3 BE were selected to be deleted and the "Active on 
> Reboot" BE was changed. User pressed OK - the confirmation dialog.
>
> be_admin5.png: User selected some BE to be deleted or activated, pressed 
> OK and then in the confirmation dialog pressed OK again.
>
> be_admin7.png: Some error occured (for example user didn't have 
> permissions to remove BE, or other error...). The error dialog popups. 
> When the user clicks Close button, the default BE management is still 
> there, but the list is updated reflecting about the current status. So 
> for example the Active on Reboot BE was changed but somehow we couldn't 
> delete 2 of 4 selected BE's then the list will show changed Active on 
> Reboot BE and also will not contain the 2 BE's which were removed.
>
> be_admin8.png: If user selects some BE to be removed, those BE can not 
> be selected to be Activated. If some BE are selected to be Active on 
> Reboot then this BE can not be deleted. The Active BE from the initial 
> state (opensolaris-3) can not be deleted at all.
>
>   
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to