Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Bruno Sousa]

Hi Hernan,

Thanks for the tip!

P.S Any "noticeable" changes in snv_142 ?

On 21-6-2010 8:44, Hernan Saltiel wrote:
> Hi, Bruno!
> Yes, I booted again into snv_134, and then back into onnv_142.
> Take special care to the instructions about "image-update"!!!
> If you want to see this command list in Spanish, go to AOSUG web site
> - HowTos section: http://www.aosug.com.ar/?q=node/40 .
> Thanks to all!!!
> Best regards,
>
> HeCSa.
>
> On Mon, Jun 21, 2010 at 3:40 AM, Bruno Sousa  > wrote:
>
> Hi,
>
> Thanks to all that made this really nice howto.
> BTW, after this procedure is it still possible to boot into
> snv_134 environment, i.e will the grub.conf be updated to have
> have snv_134 and snv_142 boot entries?
>
> Thanks,
> Bruno
>
>
>
> On 21-6-2010 8:15, Hernan Saltiel wrote:
>> Thanks to Rich Lowe, I know what I did in the wrong way.
>> Here is what needs to be done in order to have a working onnv_142
>> OpenSolaris:
>>
>> a) Install OpenSolaris snv_134 (this is my case only).
>>
>> b) Create a directory where to put the untar'ed, unbzip2'ed binaries:
>>1) mkdir -p /export/repo
>>
>> c) Untar and unbzip2 the binaries:
>>1) cd /export/repo
>>2) tar jxvf /path/to/file/on-nightly-142.i386.tar.bz2
>>
>> d) Start the local repository in one terminal window (it cannot
>> be closed):
>>1) /usr/lib/pkg.depotd -d /export/repo/on-nightly-142.i386 -p
>> 13000
>>
>> e) Execute onu.sh, downloaded from
>> 
>> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>>1) cd /opt (where I want onu.sh downloaded)
>>2) wget
>> 
>> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>>3) chmod +x onu.sh
>>4) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>>
>> f) After the upgrade, poweroff the machine.
>>1) poweroff
>>
>> g) Boot again, and be happy! I have, now, an onnv_142 OpenSolaris!!!
>>
>> Thanks again for the help, and best regards,
>>
>> HeCSa.
>>
>>
>>
>>
>>
>>
>> On Sun, Jun 20, 2010 at 5:42 PM, Hernan Saltiel
>> mailto:hsalt...@gmail.com>> wrote:
>>
>> Hi, Ken!
>> I didn't BFU'ed since first OpenSolaris 2008.05 appeared.
>> Taking a look to the README you posted, it seems that if I
>> want to upgrade from snv_134 to 142 I need to:
>>
>> a) Create a new Boot Environment and boot into it:
>>1) beadm create new134
>>2) beadm activate new134
>>3) poweroff and boot again.
>>
>> b) Create a local repository:
>>1) zfs create rpool/export/repo
>>2) zfs set mountpoint=/export/repo rpool/export/repo
>>3) pkgsend -s file:///export/repo create-repository
>> --set-property publisher.prefix=hecsa.servehttp.com
>>  (this is the URL I have from
>> no-ip.org )
>>4) svccfg -s application/pkg/server setprop pkg/port=13000
>>5) svccfg -s application/pkg/server setprop
>> pkg/inst_root=/export/repo
>>6) svcadm refresh application/pkg/server
>>7) svcadm restart application/pkg/server
>>
>> c) Download "onu.sh" from
>> 
>> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>> (I did this into /opt).
>>
>> d) Execute:
>>1) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>>
>> ...but after executing this last command, I only have this
>> output:
>> r...@snv134:/opt# ./onu.sh -Ot on-nightly-142.i38 -u
>> http://localhost:13000
>> PHASEACTIONS
>> Removal Phase  54/54
>> No updates available for this image.  
>>
>> There is something I'm doing wrong, but don't know what...any
>> help?
>> Thanks a lot, and best regards,
>>
>> HeCSa.
>>
>>
>>
>>
>> On Sun, Jun 20, 2010 at 11:43 AM, Ken Mays
>> mailto:maybird1...@yahoo.com>> wrote:
>>
>> Basically, you can recreate the test DVD based on
>> OSOL-DEV-134 and initial work based on enhancements from:
>>
>> 1. Nexenta Core v3.0rc1 CD (initial work on that platform):
>> http://www.nexenta.org/projects/site/wiki/DownloadUnstable
>> 
>> http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip
>>
>> 2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
>> http://www.genunix.org/dist/richlowe/README.txt
>> http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2
>>
>> Optional packaging:
>> 
>>
>> 3. Blastwave's 64-bit optimized AMP Web Stack (based on

Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Hernan Saltiel]

Hi, Bruno!
Yes, I booted again into snv_134, and then back into onnv_142.
Take special care to the instructions about "image-update"!!!
If you want to see this command list in Spanish, go to AOSUG web site -
HowTos section: http://www.aosug.com.ar/?q=node/40 .
Thanks to all!!!
Best regards,

HeCSa.

On Mon, Jun 21, 2010 at 3:40 AM, Bruno Sousa  wrote:

>  Hi,
>
> Thanks to all that made this really nice howto.
> BTW, after this procedure is it still possible to boot into snv_134
> environment, i.e will the grub.conf be updated to have have snv_134 and
> snv_142 boot entries?
>
> Thanks,
> Bruno
>
>
>
> On 21-6-2010 8:15, Hernan Saltiel wrote:
>
> Thanks to Rich Lowe, I know what I did in the wrong way.
> Here is what needs to be done in order to have a working onnv_142
> OpenSolaris:
>
> a) Install OpenSolaris snv_134 (this is my case only).
>
> b) Create a directory where to put the untar'ed, unbzip2'ed binaries:
>1) mkdir -p /export/repo
>
> c) Untar and unbzip2 the binaries:
>1) cd /export/repo
>2) tar jxvf /path/to/file/on-nightly-142.i386.tar.bz2
>
> d) Start the local repository in one terminal window (it cannot be closed):
>1) /usr/lib/pkg.depotd -d /export/repo/on-nightly-142.i386 -p 13000
>
> e) Execute onu.sh, downloaded from
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>1) cd /opt (where I want onu.sh downloaded)
>2) wget
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>3) chmod +x onu.sh
>4) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>
> f) After the upgrade, poweroff the machine.
>1) poweroff
>
> g) Boot again, and be happy! I have, now, an onnv_142 OpenSolaris!!!
>
> Thanks again for the help, and best regards,
>
> HeCSa.
>
>
>
>
>
>
> On Sun, Jun 20, 2010 at 5:42 PM, Hernan Saltiel wrote:
>
>> Hi, Ken!
>> I didn't BFU'ed since first OpenSolaris 2008.05 appeared.
>> Taking a look to the README you posted, it seems that if I want to upgrade
>> from snv_134 to 142 I need to:
>>
>> a) Create a new Boot Environment and boot into it:
>>1) beadm create new134
>>2) beadm activate new134
>>3) poweroff and boot again.
>>
>> b) Create a local repository:
>>1) zfs create rpool/export/repo
>>2) zfs set mountpoint=/export/repo rpool/export/repo
>>3) pkgsend -s file:///export/repo create-repository --set-property
>> publisher.prefix=hecsa.servehttp.com (this is the URL I have from
>> no-ip.org)
>>4) svccfg -s application/pkg/server setprop pkg/port=13000
>>5) svccfg -s application/pkg/server setprop pkg/inst_root=/export/repo
>>6) svcadm refresh application/pkg/server
>>7) svcadm restart application/pkg/server
>>
>> c) Download "onu.sh" from
>> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh(I
>>  did this into /opt).
>>
>> d) Execute:
>>1) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>>
>> ...but after executing this last command, I only have this output:
>> r...@snv134:/opt# ./onu.sh -Ot on-nightly-142.i38 -u
>> http://localhost:13000
>> PHASEACTIONS
>> Removal Phase  54/54
>> No updates available for this image.
>>
>> There is something I'm doing wrong, but don't know what...any help?
>> Thanks a lot, and best regards,
>>
>> HeCSa.
>>
>>
>>
>>
>> On Sun, Jun 20, 2010 at 11:43 AM, Ken Mays  wrote:
>>
>>> Basically, you can recreate the test DVD based on OSOL-DEV-134 and
>>> initial work based on enhancements from:
>>>
>>> 1. Nexenta Core v3.0rc1 CD (initial work on that platform):
>>> http://www.nexenta.org/projects/site/wiki/DownloadUnstable
>>>
>>> http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip
>>>
>>> 2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
>>> http://www.genunix.org/dist/richlowe/README.txt
>>> http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2
>>>
>>> Optional packaging:
>>> 
>>>
>>> 3. Blastwave's 64-bit optimized AMP Web Stack (based on work from
>>> InitWorks
>>> and Falconpl.org):
>>> http://www.blastwave.org
>>>
>>> 4. KDE4Solaris KDE 4.4.4 project:
>>> http://solaris.bionicmutton.org/index.html
>>> http://solaris.bionicmutton.org/SRC/
>>>
>>> 5. Oracle Open Office 3.2.1:
>>> http://www.genunix.org/dist/openoffice/
>>>
>>> 6. Package repository based on IPS b134:
>>> http://pkg.opensolaris.org/dev
>>>
>>> 7. GRUB2 (v1.98) migration
>>>
>>> I did this so more resources could easily jump in and continue to remain
>>> compatible with previous OSOL-DEV release(s) for now. There are some
>>> 'gotchas' I'm dealing with - so packages are being provided through
>>> Blastwave
>>> and other resources but hope to make everything available soon.
>>>
>>> Ken Mays
>>> Blastwave.org
>>>  --
>>> This message posted from opensolaris.org
>>> ___
>>> opensolaris-discuss mailing list
>>> opensolaris-dis

Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Bruno Sousa]

Hi,

Thanks to all that made this really nice howto.
BTW, after this procedure is it still possible to boot into snv_134
environment, i.e will the grub.conf be updated to have have snv_134 and
snv_142 boot entries?

Thanks,
Bruno


On 21-6-2010 8:15, Hernan Saltiel wrote:
> Thanks to Rich Lowe, I know what I did in the wrong way.
> Here is what needs to be done in order to have a working onnv_142
> OpenSolaris:
>
> a) Install OpenSolaris snv_134 (this is my case only).
>
> b) Create a directory where to put the untar'ed, unbzip2'ed binaries:
>1) mkdir -p /export/repo
>
> c) Untar and unbzip2 the binaries:
>1) cd /export/repo
>2) tar jxvf /path/to/file/on-nightly-142.i386.tar.bz2
>
> d) Start the local repository in one terminal window (it cannot be
> closed):
>1) /usr/lib/pkg.depotd -d /export/repo/on-nightly-142.i386 -p 13000
>
> e) Execute onu.sh, downloaded from
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>1) cd /opt (where I want onu.sh downloaded)
>2) wget
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
>3) chmod +x onu.sh
>4) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>
> f) After the upgrade, poweroff the machine.
>1) poweroff
>
> g) Boot again, and be happy! I have, now, an onnv_142 OpenSolaris!!!
>
> Thanks again for the help, and best regards,
>
> HeCSa.
>
>
>
>
>
>
> On Sun, Jun 20, 2010 at 5:42 PM, Hernan Saltiel  > wrote:
>
> Hi, Ken!
> I didn't BFU'ed since first OpenSolaris 2008.05 appeared.
> Taking a look to the README you posted, it seems that if I want to
> upgrade from snv_134 to 142 I need to:
>
> a) Create a new Boot Environment and boot into it:
>1) beadm create new134
>2) beadm activate new134
>3) poweroff and boot again.
>
> b) Create a local repository:
>1) zfs create rpool/export/repo
>2) zfs set mountpoint=/export/repo rpool/export/repo
>3) pkgsend -s file:///export/repo create-repository
> --set-property publisher.prefix=hecsa.servehttp.com
>  (this is the URL I have from
> no-ip.org )
>4) svccfg -s application/pkg/server setprop pkg/port=13000
>5) svccfg -s application/pkg/server setprop
> pkg/inst_root=/export/repo
>6) svcadm refresh application/pkg/server
>7) svcadm restart application/pkg/server
>
> c) Download "onu.sh" from
> 
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
> (I did this into /opt).
>
> d) Execute:
>1) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>
> ...but after executing this last command, I only have this output:
> r...@snv134:/opt# ./onu.sh -Ot on-nightly-142.i38 -u
> http://localhost:13000
> PHASEACTIONS
> Removal Phase  54/54
> No updates available for this image.  
>
> There is something I'm doing wrong, but don't know what...any help?
> Thanks a lot, and best regards,
>
> HeCSa.
>
>
>
>
> On Sun, Jun 20, 2010 at 11:43 AM, Ken Mays  > wrote:
>
> Basically, you can recreate the test DVD based on OSOL-DEV-134
> and initial work based on enhancements from:
>
> 1. Nexenta Core v3.0rc1 CD (initial work on that platform):
> http://www.nexenta.org/projects/site/wiki/DownloadUnstable
> 
> http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip
>
> 2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
> http://www.genunix.org/dist/richlowe/README.txt
> http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2
>
> Optional packaging:
> 
>
> 3. Blastwave's 64-bit optimized AMP Web Stack (based on work
> from InitWorks
> and Falconpl.org):
> http://www.blastwave.org
>
> 4. KDE4Solaris KDE 4.4.4 project:
> http://solaris.bionicmutton.org/index.html
> http://solaris.bionicmutton.org/SRC/
>
> 5. Oracle Open Office 3.2.1:
> http://www.genunix.org/dist/openoffice/
>
> 6. Package repository based on IPS b134:
> http://pkg.opensolaris.org/dev
>
> 7. GRUB2 (v1.98) migration
>
> I did this so more resources could easily jump in and continue
> to remain compatible with previous OSOL-DEV release(s) for
> now. There are some
> 'gotchas' I'm dealing with - so packages are being provided
> through Blastwave
> and other resources but hope to make everything available soon.
>
> Ken Mays
> Blastwave.org
> --
> This message posted from opensolaris.org 
> ___
> o

Re: [osol-discuss] New to OSOL: Move from Linux/Xen: BrandZ, xVM, virtualBox?

[Euan Thoms]

Zones + ZFS ~= Virtualisation Perfection!

Zones is the way to go, there so easy to set up, rock solid and the way they 
partition resources is unparalleled by any other virtualisation framework. 
After ZFS, I'd say zones are second best feature of Solaris. IMHO it's worth 
finding the right web, mail and jabber/xmpp server for Solaris and use zones, 
rather than find the right server for your web/mail/IM servers.

If you want a well supported, high quality, highly scalable solution, look at 
"Sun Java Webserver 7" and "Sun Communications Suite 7", they're what I use and 
it's great stuff. Otherwise apache, postfix and jabberd should run well on 
Solaris.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Hernan Saltiel]

Thanks to Rich Lowe, I know what I did in the wrong way.
Here is what needs to be done in order to have a working onnv_142
OpenSolaris:

a) Install OpenSolaris snv_134 (this is my case only).

b) Create a directory where to put the untar'ed, unbzip2'ed binaries:
   1) mkdir -p /export/repo

c) Untar and unbzip2 the binaries:
   1) cd /export/repo
   2) tar jxvf /path/to/file/on-nightly-142.i386.tar.bz2

d) Start the local repository in one terminal window (it cannot be closed):
   1) /usr/lib/pkg.depotd -d /export/repo/on-nightly-142.i386 -p 13000

e) Execute onu.sh, downloaded from
http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
   1) cd /opt (where I want onu.sh downloaded)
   2) wget
http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh
   3) chmod +x onu.sh
   4) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000

f) After the upgrade, poweroff the machine.
   1) poweroff

g) Boot again, and be happy! I have, now, an onnv_142 OpenSolaris!!!

Thanks again for the help, and best regards,

HeCSa.






On Sun, Jun 20, 2010 at 5:42 PM, Hernan Saltiel  wrote:

> Hi, Ken!
> I didn't BFU'ed since first OpenSolaris 2008.05 appeared.
> Taking a look to the README you posted, it seems that if I want to upgrade
> from snv_134 to 142 I need to:
>
> a) Create a new Boot Environment and boot into it:
>1) beadm create new134
>2) beadm activate new134
>3) poweroff and boot again.
>
> b) Create a local repository:
>1) zfs create rpool/export/repo
>2) zfs set mountpoint=/export/repo rpool/export/repo
>3) pkgsend -s file:///export/repo create-repository --set-property
> publisher.prefix=hecsa.servehttp.com (this is the URL I have from
> no-ip.org)
>4) svccfg -s application/pkg/server setprop pkg/port=13000
>5) svccfg -s application/pkg/server setprop pkg/inst_root=/export/repo
>6) svcadm refresh application/pkg/server
>7) svcadm restart application/pkg/server
>
> c) Download "onu.sh" from
> http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh(I
>  did this into /opt).
>
> d) Execute:
>1) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000
>
> ...but after executing this last command, I only have this output:
> r...@snv134:/opt# ./onu.sh -Ot on-nightly-142.i38 -u
> http://localhost:13000
> PHASEACTIONS
> Removal Phase  54/54
> No updates available for this image.
>
> There is something I'm doing wrong, but don't know what...any help?
> Thanks a lot, and best regards,
>
> HeCSa.
>
>
>
>
> On Sun, Jun 20, 2010 at 11:43 AM, Ken Mays  wrote:
>
>> Basically, you can recreate the test DVD based on OSOL-DEV-134 and initial
>> work based on enhancements from:
>>
>> 1. Nexenta Core v3.0rc1 CD (initial work on that platform):
>> http://www.nexenta.org/projects/site/wiki/DownloadUnstable
>>
>> http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip
>>
>> 2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
>> http://www.genunix.org/dist/richlowe/README.txt
>> http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2
>>
>> Optional packaging:
>> 
>>
>> 3. Blastwave's 64-bit optimized AMP Web Stack (based on work from
>> InitWorks
>> and Falconpl.org):
>> http://www.blastwave.org
>>
>> 4. KDE4Solaris KDE 4.4.4 project:
>> http://solaris.bionicmutton.org/index.html
>> http://solaris.bionicmutton.org/SRC/
>>
>> 5. Oracle Open Office 3.2.1:
>> http://www.genunix.org/dist/openoffice/
>>
>> 6. Package repository based on IPS b134:
>> http://pkg.opensolaris.org/dev
>>
>> 7. GRUB2 (v1.98) migration
>>
>> I did this so more resources could easily jump in and continue to remain
>> compatible with previous OSOL-DEV release(s) for now. There are some
>> 'gotchas' I'm dealing with - so packages are being provided through
>> Blastwave
>> and other resources but hope to make everything available soon.
>>
>> Ken Mays
>> Blastwave.org
>> --
>> This message posted from opensolaris.org
>> ___
>> opensolaris-discuss mailing list
>> opensolaris-discuss@opensolaris.org
>>
>
>
>
> --
> HeCSa
>



-- 
HeCSa
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Alexander]

> > I also recommend Debian for servers, CentOS when
> rpm based distros are 
> > preferred; and Linux Mint for the desktop.
> 
> I recommend Solaris or OpenSolaris for servers, but
> what do I know?
We use SXCE for two our servers, and they serve our needs. But these servers 
are hidden in intranet. In other cases, when server should be public I have to 
update it. And I can't do it free with Solaris/OpenSolaris. So, without 
contract it is not an option for externally-visible server. And I don't see a 
lot of "magic bullets" of (Open)Solaris for which I would recommend to pay (at 
least any features that may be useful in our computer center). So, we have 
migrated almost all servers to FreeBSD and x64 servers long ago (it seems about 
5-7 years ago, before my coming to this job). It was partly caused by bad 
service for SPARCs in our city. (It was hardly possible to find cheap change 
for faulted hardware).  And I don't see any reasons to go back to Solaris. One 
of our team speaks about migrating part of infrastructure to Linux. But it will 
not happen at least for several years.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] JDK in the installer...

[John Plocher]

> Realistically, it's just for the installer. Exactly what it's doing you'd
> have to ask the Solaris folks, but its not used during network/jumpstart
> installs, only for the interactive ones, IIRC.
>
>
>
One word: I18N

  -John
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Edward Ned Harvey]

> From: opensolaris-discuss-boun...@opensolaris.org [mailto:opensolaris-
> discuss-boun...@opensolaris.org] On Behalf Of Dmitry G. Kozhinov
> 
> Would you recommend Fedora?

> From: opensolaris-discuss-boun...@opensolaris.org [mailto:opensolaris-
> discuss-boun...@opensolaris.org] On Behalf Of Mark Kaiman
>
> Time to jump ship to Ubuntu?


Knock it off you guys.

If you want to have legitimate discussion of the merits of different
platforms, by all means.  But this is stupid.  Please do jump ship, so you
won't care about this mailing list anymore.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Oracle torpedos HP's Solaris OEM contract

[Edward Ned Harvey]

> From: opensolaris-discuss-boun...@opensolaris.org [mailto:opensolaris-
> discuss-boun...@opensolaris.org] On Behalf Of Edward Martinez
> 
> quote:
> 
> As you may have heard, Oracle has exercised its right to terminate HP's
> Solaris technical support agreement. If you have purchased Solaris 10
> 
> http://www.theregister.co.uk/2010/06/18/oracle_spikes_hp_solaris/

Wow.
They said that on the register?
And it's nowhere else on the internet?
Time to sell out now, and abandon solaris.  Quick.  Hurry up, and quit this
mailing list.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] JDK in the installer...

[Erik Trimble]

On 6/20/2010 12:36 PM, W. Wayne Liauh wrote:



   

--
Erik Trimble
Java System Support
Mailstop:  usca22-123
Phone:  x17195
Santa Clara, CA
 

Hi Erik,

Thanks a whole lot for taking time to post your thoughts.  Different people 
will react differently.  I am sure you are aware that the stronger a person is 
devoted to Solaris, the stronger the voice you are going to hear.  IMNSHO, this 
is what we need to keep this project alive.

So much for my 8th-kissing, now my real motive/question.  Since you appear to 
be working in Sun's Java System, Perhaps you might have some answer to a 
question that I asked almost five years ago but never received any reply?

During the installation of Solaris Express, shortly after the kernel is loaded, a Java 
virtual machine will appear which will take over the installation process.  I was 
wondering whether this is a special version of JVM, and if so, how "useful" 
(capability-wise) it is? where can I find any info?  More to the point, do you think it 
may be possible to build a Open Solaris distro based on this kernel+JVM combo?

Thanks again and apologize for forking the subject.
   


Last I checked, this is a vanilla version of the JDK - I think they're 
using 1.4.2 during the old Nevada/Solaris 10 install process.  It's a 
fully-featured JDK.


Realistically, it's just for the installer. Exactly what it's doing 
you'd have to ask the Solaris folks, but its not used during 
network/jumpstart installs, only for the interactive ones, IIRC.




--
Erik Trimble
Java System Support
Mailstop:  usca22-123
Phone:  x17195
Santa Clara, CA

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Oracle torpedos HP's Solaris OEM contract

[Erik Trimble]

On 6/20/2010 3:23 PM, Dave Koelmeyer wrote:

Do us _all_ a favor and please shut up. You're doing
OpenSolaris no favors with all the crap you've been
vomiting out. Really, more harm than good since its
all based on what you think, or what you ate that
day, or if traffic was bad that morning, or any one
of a million factors that obviously have nothing to
do with reality.
 

I'm really not seeing that in Erik's post, nor any of the other one's he's 
made. On the contrary they are interesting and useful thoughts.
   


That's OK. It was resolved off-list. No harm, no foul.

(speaking of foul [play], oh boy, did you see the acting job that got 
Kaka ejected during Brasil/Ivory Coast?)


--
Erik Trimble
Java System Support
Mailstop:  usca22-123
Phone:  x17195
Santa Clara, CA

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Oracle torpedos HP's Solaris OEM contract

[Dave Koelmeyer]

> Do us _all_ a favor and please shut up. You're doing
> OpenSolaris no favors with all the crap you've been
> vomiting out. Really, more harm than good since its
> all based on what you think, or what you ate that
> day, or if traffic was bad that morning, or any one
> of a million factors that obviously have nothing to
> do with reality.

I'm really not seeing that in Erik's post, nor any of the other one's he's 
made. On the contrary they are interesting and useful thoughts.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Mark Kaiman]

I hope you're right and all of that is true. I dont want to see OpenSolaris 
become another orphan OS or another "might have been."

BTW, I use it as a desktop OS, not as a server. There are some things I have to 
use Windows 7 for, but most of my day to day computing tasks can be 
accomplished with OpenSolaris. I dont want to see it go away.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] zfs periodic writes on idle system [Re: Getting desktop to auto sleep]

[Jürgen Keil]

Why does zfs produce a batch of writes every 30 seconds on opensolaris b134
(5 seconds on a post b142 kernel), when the system is idle?

On an idle OpenSolaris 2009.06 (b111) system,  /usr/demo/dtrace/iosnoop.d
shows no i/o activity for at least 15 minutes.

The same dtrace test on an idle b134 system shows a batch of writes every 30 
seconds.

And on current opensolaris bits, on an idle system, I see writes every 5 
seconds.


The periodic writes prevents that the disk can enter power save mode.
And this breaks the /etc/power.conf autoS3 feature.  Why does zfs have
to write something to disk when the system is idle?



> > Putting the flag does not seem to do anything to the
> > system. Here is my power.conf file: 
> ...
> > autopm  enable
> > autoS3  enable
> > S3-support  enable
> 
> Problem seems to be that all power managed devices
> must be at their lowest power level, otherwise autoS3
> won't suspend the system.  And somehow one or more
> device does not reach the lowest power level.
...
> The laptop still does not power down, because every
> 30 seconds there is a batch of writes to the hdd drive,
> apparently from zfs, and that keeps the hdd powered
> up.
> 
> The periodic writes can be monitored with:
> 
> dtrace -s /usr/demo/dtrace/iosnoop.d
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Ian Collins]

On 06/21/10 06:02 AM, HeCSa wrote:



On 06/20/10 12:38 PM, Alexander wrote:

RHEL, SLES, or possibly Debian

Would you recommend Fedora?
IMHO, it is positioned as desktop or "feature-preview" of RHEL-next. 
After living with Ubuntu on laptop for several years, I'm not 
satisfied with its stability in last two releases. So, maybe Debian  
would be more adequate even for desktop, and indeed it is preferable 
for server. However, for server there are a lot of other suitable OS.


Hi!
Used Ubuntu since first versions. Latest are a bit strange, specially 
10.04.
I also recommend Debian for servers, CentOS when rpm based distros are 
preferred; and Linux Mint for the desktop.


I recommend Solaris or OpenSolaris for servers, but what do I know?

--
Ian.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Hernan Saltiel]

Hi, Ken!
I didn't BFU'ed since first OpenSolaris 2008.05 appeared.
Taking a look to the README you posted, it seems that if I want to upgrade
from snv_134 to 142 I need to:

a) Create a new Boot Environment and boot into it:
   1) beadm create new134
   2) beadm activate new134
   3) poweroff and boot again.

b) Create a local repository:
   1) zfs create rpool/export/repo
   2) zfs set mountpoint=/export/repo rpool/export/repo
   3) pkgsend -s file:///export/repo create-repository --set-property
publisher.prefix=hecsa.servehttp.com (this is the URL I have from no-ip.org)
   4) svccfg -s application/pkg/server setprop pkg/port=13000
   5) svccfg -s application/pkg/server setprop pkg/inst_root=/export/repo
   6) svcadm refresh application/pkg/server
   7) svcadm restart application/pkg/server

c) Download "onu.sh" from
http://www.opensolaris.org/sc/src/onnv/onnv-gate/usr/src/tools/scripts/onu.sh(I
did this into /opt).

d) Execute:
   1) ./onu.sh -Ot on-nightly-142.i386 -u http://localhost:13000

...but after executing this last command, I only have this output:
r...@snv134:/opt# ./onu.sh -Ot on-nightly-142.i38 -u http://localhost:13000
PHASEACTIONS
Removal Phase  54/54
No updates available for this image.

There is something I'm doing wrong, but don't know what...any help?
Thanks a lot, and best regards,

HeCSa.



On Sun, Jun 20, 2010 at 11:43 AM, Ken Mays  wrote:

> Basically, you can recreate the test DVD based on OSOL-DEV-134 and initial
> work based on enhancements from:
>
> 1. Nexenta Core v3.0rc1 CD (initial work on that platform):
> http://www.nexenta.org/projects/site/wiki/DownloadUnstable
>
> http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip
>
> 2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
> http://www.genunix.org/dist/richlowe/README.txt
> http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2
>
> Optional packaging:
> 
>
> 3. Blastwave's 64-bit optimized AMP Web Stack (based on work from InitWorks
> and Falconpl.org):
> http://www.blastwave.org
>
> 4. KDE4Solaris KDE 4.4.4 project:
> http://solaris.bionicmutton.org/index.html
> http://solaris.bionicmutton.org/SRC/
>
> 5. Oracle Open Office 3.2.1:
> http://www.genunix.org/dist/openoffice/
>
> 6. Package repository based on IPS b134:
> http://pkg.opensolaris.org/dev
>
> 7. GRUB2 (v1.98) migration
>
> I did this so more resources could easily jump in and continue to remain
> compatible with previous OSOL-DEV release(s) for now. There are some
> 'gotchas' I'm dealing with - so packages are being provided through
> Blastwave
> and other resources but hope to make everything available soon.
>
> Ken Mays
> Blastwave.org
> --
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>



-- 
HeCSa
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] thanks to all who helped choochoo with OSOL & message to Oracle/ Sun

[W. Wayne Liauh]

> 
> -- 
> Erik Trimble
> Java System Support
> Mailstop:  usca22-123
> Phone:  x17195
> Santa Clara, CA

Hi Erik,

Thanks a whole lot for taking time to post your thoughts.  Different people 
will react differently.  I am sure you are aware that the stronger a person is 
devoted to Solaris, the stronger the voice you are going to hear.  IMNSHO, this 
is what we need to keep this project alive.

So much for my 8th-kissing, now my real motive/question.  Since you appear to 
be working in Sun's Java System, Perhaps you might have some answer to a 
question that I asked almost five years ago but never received any reply?

During the installation of Solaris Express, shortly after the kernel is loaded, 
a Java virtual machine will appear which will take over the installation 
process.  I was wondering whether this is a special version of JVM, and if so, 
how "useful" (capability-wise) it is? where can I find any info?  More to the 
point, do you think it may be possible to build a Open Solaris distro based on 
this kernel+JVM combo?

Thanks again and apologize for forking the subject.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[HeCSa]

On 06/20/10 12:38 PM, Alexander wrote:

RHEL, SLES, or possibly Debian
   

Would you recommend Fedora?
 

IMHO, it is positioned as desktop or "feature-preview" of RHEL-next. After 
living with Ubuntu on laptop for several years, I'm not satisfied with its stability in 
last two releases. So, maybe Debian  would be more adequate even for desktop, and indeed 
it is preferable for server. However, for server there are a lot of other suitable OS.
   


Hi!
Used Ubuntu since first versions. Latest are a bit strange, specially 10.04.
I also recommend Debian for servers, CentOS when rpm based distros are 
preferred; and Linux Mint for the desktop.

Best regards,

HeCSa.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Getting desktop to auto sleep

[Jürgen Keil]

> Putting the flag does not seem to do anything to the
> system. Here is my power.conf file: 
...
> autopmenable
> autoS3enable
> S3-supportenable

Problem seems to be that all power managed devices
must be at their lowest power level, otherwise autoS3
won't suspend the system.  And somehow one or more
device does not reach the lowest power level.

The number of devices that are currently not at
their lowest power level can be monitored on the
kernel variable "pm_comps_notlowest", e.g. like this:

# echo pm_comps_notlowest::print | mdb -k
0x3

When the returned number ever reaches 0, the
system should start the auto suspend.


On my Tecra A10 laptop running b134 the s-ata hdd
and s-ata optical device are power managed, and both
cpu cores are power managed.

I experimented with these additional /etc/power.conf entries
to get the hdd and dvd drive powered down:

device-thresholds   /p...@0,0/pci1179,1...@1f,2/d...@0,0 (20s 20s 20s)
device-thresholds   /p...@0,0/pci1179,1...@1f,2/cd...@1,0 60s

These physical device paths are from:

# iostat -En
c5t0d0   Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: ATA  Product: Hitachi HTS72323 Revision: C30F Serial No:  
Size: 320,07GB <320072933376 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 10 Predictive Failure Analysis: 0 
c5t1d0   Soft Errors: 0 Hard Errors: 10 Transport Errors: 0 
Vendor: MATSHITA Product: DVD-RAM UJ880AS  Revision: 1.21 Serial No:  
Size: 0,00GB <0 bytes>
Media Error: 0 Device Not Ready: 10 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 

# ls -l /dev/rdsk/c5t0d0s2 
lrwxrwxrwx   1 root root  51 Feb 20 20:26 /dev/rdsk/c5t0d0s2 -> 
../../devices/p...@0,0/pci1179,1...@1f,2/d...@0,0:c,raw

# ls -l /dev/rdsk/c5t1d0s2
lrwxrwxrwx   1 root root  52 Feb 20 20:26 /dev/rdsk/c5t1d0s2 -> 
../../devices/p...@0,0/pci1179,1...@1f,2/cd...@1,0:c,raw




I also experimented with disabling event mode for cpupm,
by changing cpupm to poll mode in power.conf,

cpupm   enable  poll-mode



The laptop still does not power down, because every
30 seconds there is a batch of writes to the hdd drive,
apparently from zfs, and that keeps the hdd powered up.

The periodic writes can be monitored with:

dtrace -s /usr/demo/dtrace/iosnoop.d 


After I lowered the hdd timeouts to 7 seconds,
the hdd would transition from active->idle->standby->off
before the next batch of zfs writes (in 3*7 = 21 seconds),
and the system did automatically enter S3.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Alexander]

> >RHEL, SLES, or possibly Debian
> 
> Would you recommend Fedora?

IMHO, it is positioned as desktop or "feature-preview" of RHEL-next. After 
living with Ubuntu on laptop for several years, I'm not satisfied with its 
stability in last two releases. So, maybe Debian  would be more adequate even 
for desktop, and indeed it is preferable for server. However, for server there 
are a lot of other suitable OS.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Aurélien Larcher]

Le 19/06/10 18:08, Mark Kaiman a écrit :

I dont think its at all clear that OpenSolaris (or Solaris for that matter!) 
has a future under Oracle. They're as bad as Apple. Secretive. Uncommunicative. 
Leaving customers in the dark.

Time to jump ship to Ubuntu?
   

Time to provide something else than useless mumbling ?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SNV_142 Test DVD & Blastwave's AMP stack

[Ken Mays]

Basically, you can recreate the test DVD based on OSOL-DEV-134 and initial work 
based on enhancements from:

1. Nexenta Core v3.0rc1 CD (initial work on that platform):
http://www.nexenta.org/projects/site/wiki/DownloadUnstable
http://www.genunix.org/dist/nexenta/nexenta-core-platform_3.0-b134-rc1_x86.iso.zip

2.  Richard Lowe's contributed ON 142 work (inc. Caiman/Pkg):
http://www.genunix.org/dist/richlowe/README.txt
http://www.genunix.org/dist/richlowe/on-nightly-142.i386.tar.bz2

Optional packaging:


3. Blastwave's 64-bit optimized AMP Web Stack (based on work from InitWorks
and Falconpl.org):
http://www.blastwave.org

4. KDE4Solaris KDE 4.4.4 project:
http://solaris.bionicmutton.org/index.html
http://solaris.bionicmutton.org/SRC/

5. Oracle Open Office 3.2.1:
http://www.genunix.org/dist/openoffice/

6. Package repository based on IPS b134:
http://pkg.opensolaris.org/dev

7. GRUB2 (v1.98) migration

I did this so more resources could easily jump in and continue to remain 
compatible with previous OSOL-DEV release(s) for now. There are some
'gotchas' I'm dealing with - so packages are being provided through Blastwave
and other resources but hope to make everything available soon.

Ken Mays
Blastwave.org
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Getting desktop to auto sleep

[Jürgen Keil]

> keithk  wrote:
> 
> > Hi eam1,
> > I did. After which, I reboot the system. Still nothing happens.
> 
> This is a well known bug that was introduced with SXCE build 130.

Is there a bug filed to track this problem?
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Getting desktop to auto sleep

[Joerg Schilling]

keithk  wrote:

> Hi eam1,
> I did. After which, I reboot the system. Still nothing happens.

This is a well known bug that was introduced with SXCE build 130.

Build 129 correctly auto-suspends but there are other problems
(like e.g. massive performance problems in the 3d support that slows
down normal applications and cause hangs) that make it unusable on laptops with
intel graphic. With build 130 3d support finally _enhances_ performance the 
first time with intel chips, but auto-syspend is no longer functional.
I am forced to call "uadmin 3 20" since I installed SXCE 130.

The basic development coordination problem started aprox. 2 years ago. Since 
then, problems have been fixed slowly and new problems have been introduced
at the same time, making it impossible to find a Solaris build without problems.
The usual method to deal with such problems is to stop integrating new code and
to concentrate on fixing bugs. If this development problem was not planned, then
it was caused by massive lay-offs and the missing coordination at high level
or by the missing will of other departments to stop their code integrations.

The sum all problems is of course not caused by Sun, many of the problems have
been introduced by Linux developers that create completely inapropriate sofware
structures (things like power management control just do not belong _into_ the 
GUI). 

If we asume that some people at Orcale now identified the problem, it may be 
that the delay of the next Indiana release is a result of fixing all bugs from
the past 2 years at at time.

Jörg

-- 
 EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
   j...@cs.tu-berlin.de(uni)  
   joerg.schill...@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Software Product Map- opensolaris not included

[Dmitry G. Kozhinov]

>RHEL, SLES, or possibly Debian

Would you recommend Fedora?
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org