Hi Reginald There have been quite some drastic changes in terms of required step for updates.
In Short. Just do "pkg update -v" it will do everything you want for you. The Publisher URL is correct. pkg update will: 1. Refresh the Package Catalog from the Location specified. 2. Create a Boot Environment 3. Update all packages in the new Boot Environment to the latest available version 4. Mark Boot Environment as active on next boot Then just reboot and you are done. pkg refresh only refreshes the list of available packages from openindiana.org If you cannot find a package with pkg search try pkg search *firefox* or pkg list -a | grep firefox Hope this Helps Greetings Till On 14.05.19 18:33, Reginald Beardsley via openindiana-discuss wrote: > > I'd like to do an update from what appears to be 2017.10. In my retirement > I have gotten rather lazy. Solaris 10 u8 will never get an update, so no > changes there. That's where I do real work and it is on a private network. > > OI is a moving target and I've been forced to use Win 7 and Debian 9.3 after > having previously occasionally used CentOS 6.x and no Win 7 at all. But i > have installed most Linux and BSD flavors in the past. So my mind is clouded > by all the different ways that distros use to do system updates. > > Here's how the system is currently setup as best I can tell. > > root@Hipster:~# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > openindiana.org origin online F > http://pkg.openindiana.org/hipster/ > root@Hipster:~# uname -a > SunOS Hipster 5.11 illumos-2727bb055f i86pc i386 i86pc > root@Hipster:~# cat /etc/motd > The Illumos Project SunOS 5.11 illumos-2727bb055f October 2017 > root@Hipster:~# > > I do not know if this is definitive. It seems to me looking at the pkg lists > that "uname -a" should return "5.11-2017.10" instead of just "5.11". > > The wiki mentions various repositories without making clear which I should be > using. The current setting was the result of trying to install Firefox 60 > ESR for which "pkg search firefox" produced no results. > > It is not at all clear to me what the update model should be. My instincts > based on experience starting with SunOS 4.0.X are to do the following: > > 1) refresh 2017.10 from the appropriate repository, which may or may not be > what is currently set > > 2) create a new boot environment and update that to the most recent Hipster > ISO version > > Part of the problem is I used to do all this manually before beadm(1m) and > friends appeared and have only used beadm(1m) a few times and not since I did > the update to u8. > > A search of the wiki using the wiki search facility didn't turn up anything > definitive. > > So I have a few questions: > > 1) Will "pkg refresh --full" update just the installed 2017.10 packages that > have been changed? > > 2) Is there a documented procedure such as found here: > > https://wiki.openindiana.org/oi/Hipster > > for updating from one ISO release to another? I lost a disk and did a bare > install of 2017.10. This system is my production desktop for access to the > internet. I do not want to follow hipster changes except bug fixes to ISO > snapshots. So it is unclear to me what my publisher list should look like > other than I need to add the SFE repository. > > The procedure cited above appears to be somewhat specific to updating from > pre-Hipster systems images. > > Thanks, > Reg > > _______________________________________________ > openindiana-discuss mailing list > [email protected] > https://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
