OpenHoosiers, Something else which can complicate updating from 151a7 is hipster. If you have "gone hipster" on a 151a7 installation, then your work is more complicated. I have successfully upgraded a hipster 151a7 installation through a8 dev to a9 dev. I would not be able to retrace my steps precisely, but generally, I did the following: * Mount a Boot Environment so to work with it offline: # beadm mount theBEname /mnt/mountDir * Update this offline Boot Environment using the -R switch in pkg. * Identify offensive packages: # pkg -R /mnt/mountDir update -n * In pkg, --reject offensive packages. At this point, I was able to continue updating by ... # pkg -R /mnt/mountDir update -- reject gdm@0.5.11-0.151.1.9 *@*-0.151.1.9 * Update of gdm will fail if user gdm is gone from /etc/passwrd, /etc/shadow, or /etc/group So from within that BE: # user add -c "GDM Reserved UID" -g 50 -u 50 -d /var/lib/gdm gdm then ... # groupadd -g 50 gdm /etc/shadow should look like ... gdm:*LK*::::::: * If possible, occasionally run pkg fix --accept * Look in svcs to see that gdm is enabled to run. If not, then ... # svcadm enable gdm
And as Udo said, ensure that gvfs is installed. Be patient! The iterative process took me a couple of weeks with much study and reading of man pages. Godspeed ------------oooo--O--oooo---------- Stephen Stanford Jones The Citadel, Department of Chemistry stationary: sjones3ATcitadelDOTedu mobile: ss_jonesATmacDOTcom -----Original Message----- From: Hans J. Albertsson [mailto:hans.j.alberts...@branneriet.se] Sent: Wed 2014-02-19 09:44 To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ? This is basically my7 experience, too. And no one seems to have any idea about why these Gnome problems ACTUALLY occur. On 2014-02-19 15:09, Dmitry Kozhinov wrote: > Not to blame anyone, but IMO every next OI release becomes less stable > than previous... > > The latest release which works stable for me is 151a7. 151a8 also > worked, though I could not configure network interface using GUI tool > in it (after disabling "nwam" and enabling "default"). > > Then 151a9 was released. After upgrading my 32-bit production server, > it simply did not boot. It gone into infinite boot loop at the very > early stage of the boot process. OK, who needs a decade-old 32-bit > hardware (which though worked like a clockwork with 151a7, and had 3GB > of RAM, not the very minimum)... I have upgraded my hardware. Now it > is 64-bit. > > I have started from 151a7, not 8 (to avoid hassle with setting static > IP address manually in various config files - I could miss something > and spend much more time to do this simple setting). OK, 151a7 is > working fine. Upgrading to 151a9... GNOME degraded. No upper toolbar, > no lower status bar, no Nimbus theme, just background image and mouse > pointer. Right-click menu is working though. > > There was an advice to reinstall gvfs. Tried in a test virtualbox > setup. This worked in reverse! In /virtualbox/, 151a7 /successfully/ > upgraded to 151a9. Though in vbox the upgrade went successfully, I > have tried if reinstalling gvfs is safe (before trying it at > production server). Booted into single user mode, log in as root, and did > # pkg uninstall gvfs > # pkg install gvfs > And rebooted. What do you think? GNOME degraded. In the same way as in > the production server. Reinstalling gvfs caused exactly the same > symptoms which it intended to cure. > > If someone knows how to upgrade 151a7 to 151a9, please post step-by > step instructions. > > Regards, > Dmitry.
_______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss