system5 thanks! I am aware of the bugginess with bleeding edge..However, since I am running 130 on another machine in a vm with none of the above problems, I thought that I would try it on my notebook.
Main difference though is that on other box, it was not an upgrade. I installed dev 130 in vm from scratch and so far working great for me.... I will try the suggestions you referred to when I can access my notebook.. I have two questions though 1, If I reboot my machine and then just select snv111 from the menu, won't that still run without the beadm command? 2, If I decide to bag it and just wait until 131 or 132 etc. would I choose to doan image update from my original 111 build or the buggy 130 build? And if it is from the buggy 130 build won't alot of those problems just carry over, or will the install/upgrade process filter out those and correct them? For example if I cannot fix the thunderbird issue, won't that just be applied to the next update? Sorry for all the (for you) newbie type questions. For me critical for understanding the process. Thanks again...... -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
