This is a discussion on Solaris9 vs. Solaris9 9/04 within the comp.unix.solaris forums, part of the Solaris Operating System category; --> I have an installation of a Solaris9 release that is earlier than Solaris9 9/04. It is not even Solaris9 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have an installation of a Solaris9 release that is earlier than Solaris9 9/04. It is not even Solaris9 9/02, based on /etc/release. My question is, isn't any release of Solaris9 really just Solaris9 plus all the cluster patches ? For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte support for Solaris Volume Manager" as a new feature. Do I get this feature by simply installing the latest cluster patches ? |
| |||
| noone wrote: > > I have an installation of a Solaris9 release that is earlier than Solaris9 > 9/04. It is not even Solaris9 9/02, based on /etc/release. > > My question is, isn't any release of Solaris9 really just Solaris9 plus > all the cluster patches ? > > For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte > support for Solaris Volume Manager" as a new feature. Do I get this > feature by simply installing the latest cluster patches ? Cluster patches are only maintainance. Equivilant of an IRIX Maintainance release. Relating to Solaris 9, why not install Solaris 10? its a free download! Matt |
| |||
| noone <noone@noone.org> writes: >I have an installation of a Solaris9 release that is earlier than Solaris9 >9/04. It is not even Solaris9 9/02, based on /etc/release. >My question is, isn't any release of Solaris9 really just Solaris9 plus >all the cluster patches ? No; the updates include new packages which aren't installed by patches. >For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte >support for Solaris Volume Manager" as a new feature. Do I get this >feature by simply installing the latest cluster patches ? Possibly. Casper |
| |||
| Casper H.S. Dik wrote: > noone <noone@noone.org> writes: > >>For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte >>support for Solaris Volume Manager" as a new feature. Do I get this >>feature by simply installing the latest cluster patches ? > > > Possibly. > > Casper > Answering my own question. The main patch to achieve multiterabyte support is patch 114131-02. The README then mentions other patches to achieve full multi-TB support. |
| |||
| noone wrote: > Casper H.S. Dik wrote: > >> noone <noone@noone.org> writes: >> >>> For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte >>> support for Solaris Volume Manager" as a new feature. Do I get this >>> feature by simply installing the latest cluster patches ? >> >> >> >> Possibly. >> >> Casper >> > > Answering my own question. > > The main patch to achieve multiterabyte support is patch 114131-02. The > README then mentions other patches to achieve full multi-TB support. > > Funnily enough, Sun support said that I MUST install 9 4/03 to get multiterabyte support, despite what the patch README says |
| |||
| On Sun, 20 Feb 2005, noone wrote: > For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte > support for Solaris Volume Manager" as a new feature. Do I get this > feature by simply installing the latest cluster patches ? Not likely. As a rule, new features aren't added via patches, although there are some exceptions. -- Rich Teer, SCNA, SCSA, author of "Solaris Systems Programming" President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-group.com/rich |
| |||
| Rich Teer wrote: > On Sun, 20 Feb 2005, noone wrote: > > >>For example, docs.sun.com says that Solaris9 4/03 has "Multiterabyte >>support for Solaris Volume Manager" as a new feature. Do I get this >>feature by simply installing the latest cluster patches ? > > > Not likely. As a rule, new features aren't added via patches, although > there are some exceptions. > In this case, the Multiterabyt feature is actually available via a group of patches. Possibly starting with patch 114131-02 and then the other patches indicated in the README file |