Re: [osol-discuss] OpenSolaris SPARC AI Installation in DHCP-enabled corporate network

[roman]

Hi all.
I've pefrormed all actions from how-to guide 
(http://dlc.sun.com/osol/docs/content/2009.06/AIinstall)), but faced such 
problem:

ok boot net:172.16.1.xxx:46503
Boot device: /p...@1f,70/netw...@2:172.16.1.xxx:46503  File and args: 
100 Mbps FDX Link up
Timeout waiting for ARP/RARP packet

where 172.16.1.xxx:46503 is static IP of my x86 machine with osol0906. (My x86 
machine is host in dhcp network, but i set a static IP for it). Do anyone have 
ideas?
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] dealing with Xutf8LookupString absence

[Dennis Clarke]

follow up ...

Always *after* I hit send.  :-P

It is possible to use :

 len = XmbLookupString(winPtr->inputContext, &eventPtr->xkey,
 Tcl_DStringValue(&buf), len, NULL, &status);


but one would think UTF8 is possible.

Dennis



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

[osol-discuss] dealing with Xutf8LookupString absence

[Dennis Clarke]

Has anyone hit an issue where Xutf8LookupString simply is not available in
the implementaion of X on Solaris/OpenSolaris ?

I refer to this function :
http://www.xfree86.org/current/Xutf8LookupString.3.html

I have looked around and found a statement by Mr. Coopersmith that says :

  Actually there are two implementation of the XLookupString in the Xlib
  namely a 'core protocol' one and an XKB replacement for this subroutine.
  And the XKB's XLookupString does this 'HACKing' from its birth.

Although there is nothing under /usr/X11/man that has anything to do with
a lookup of any kind.

Consider the following code :

if ((winPtr->dispPtr->flags & TK_DISPLAY_USE_IM)
&& (winPtr->inputContext != NULL)
&& (eventPtr->type == KeyPress))
{
int len;
Status status;

Tcl_DStringSetLength(dsPtr, TCL_DSTRING_STATIC_SIZE-1);
len = Xutf8LookupString(winPtr->inputContext, &eventPtr->xkey,
Tcl_DStringValue(dsPtr), Tcl_DStringLength(dsPtr),
NULL, &status);

/*   will not work on Solaris/OpenSolaris because
 *   Xutf8LookupString is absent.
 */

if (status == XBufferOverflow) { /* Expand buffer and try again */
Tcl_DStringSetLength(dsPtr, len);
/* same issue on Solaris/OpenSolaris */
len = Xutf8LookupString(winPtr->inputContext, &eventPtr->xkey,
Tcl_DStringValue(dsPtr), Tcl_DStringLength(dsPtr),
NULL, &status);
}
if ((status != XLookupChars) && (status != XLookupBoth)) {
Tcl_DStringSetLength(dsPtr, 0);
len = 0;
.
.
.

A search in src.opensolaris.org says there is no XmbLookupString nor
Xutf8LookupString.

Any suggestions ? [1]

-- 
Dennis


[1] besides do a whole hog port of XFree86 or similar.

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

Re: [osol-discuss] SXCE end-of-life plans

[Ken Mays]

This is nothing new. SXCE was planned for EOL for quite some time (i.e. three
years since I heard about Indiana at least) but I guess we are hearing the 
"nail in the
coffin" announcement. Tools like the Distribution Constructor and IPS will 
become more important as distro providers get to learn about what they can pull 
from IPS repositories for "value add" to their own distros.

What is interesting is that a lot of work gets shifted over to the IPS 
repository
as people build packages..the core OS is wrapped and packaged in a nice 
official product release with value added software with yearly support.

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

Re: [osol-discuss] SXCE end-of-life plans

[Che Kristo]

Cool, just getting started now at
http://wiki.genunix.org/wiki/index.php/SXCE_EOL will just copy and paste for
now and will clean up language etc later...

On Tue, Aug 11, 2009 at 12:24 PM, Glynn Foster  wrote:

>
> On 11/08/2009, at 2:15 PM, Che Kristo wrote:
>
>  Looking at the response so far perhaps it is a good idea to get a FAQ set
>> up on the genunix wiki...does anyone else support this idea?
>>
>
> Sounds like a good idea to me and can probably help writing it based on the
> responses here.
>
>
> Glynn
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] [osol-announce] SXCE end-of-life plans

[Glynn Foster]

On 11/08/2009, at 9:23 AM, Uros Nedic wrote:



I hope before you stop releasing SXCE you'll provide all
tools to build OpenSolaris from source code on OpenSolaris platform.

As far as I know today is very hard to build OpenSolaris distribution
on OpenSolaris even if we have closed binaries included. We still need
SXCE to do it.


Part of what is being planned is ensuring that consolidations can  
natively create IPS packages, so a lot of the heavy lifting that has  
been on in the past (using the solaris.py script from the IPS gate)  
won't be necessary. However, folks have been building ON on  
OpenSolaris for a while now -


http://www.opensolaris.org/os/project/indiana/building_on/

Hopefully Liane can fill in some of the details here.

Obviously frustrations or suggestions for how to improve things are  
welcome.



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

Re: [osol-discuss] SXCE end-of-life plans

[Glynn Foster]

On 11/08/2009, at 2:15 PM, Che Kristo wrote:

Looking at the response so far perhaps it is a good idea to get a  
FAQ set up on the genunix wiki...does anyone else support this idea?


Sounds like a good idea to me and can probably help writing it based  
on the responses here.



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

Re: [osol-discuss] SXCE end-of-life plans

[Glynn Foster]

On 11/08/2009, at 2:06 PM, Octave Orgeron wrote:



It does bring up the big question.. how will customers migrate from  
S10 to OpenSolaris? Or is it a "tough luck" situation and customers  
have to do a painfully manual upgrade? I mean if SVR4 pkgs go away,  
that kinda leaves Solaris on a isolated island. There are plenty of  
things that still need to be sorted out in the Indiana tree before  
the ties can be cut.


It definitely won't be 'tough luck', though the supported migration  
path will not be from S10 to OpenSolaris per se but rather to a long  
term supported enterprise product. SVR4 support will still be  
available - the ability to install stand alone SVR4 packages will be  
supported, and very much desired. However, we appreciate that actual  
tools to do that migration now are not yet available.


Does anyone know if S10 will be the last Solaris release? If so,  
there has to be more thought around how to migrate customers and  
users to OpenSolaris.


There will be another long term supported release as indicated in the  
OpenSolaris 2009.06 release (http://www.sun.com/aboutsun/pr/2009-06/sunflash.20090601.1.xml 
), but further details for this are not yet available.


"This preview of the next generation of Solaris "


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

Re: [osol-discuss] SXCE end-of-life plans

[Glynn Foster]

On 11/08/2009, at 10:51 AM, Boyd Adamson wrote:

No doubt there will be a number of queries from those of us still  
currently using SXCE. For me the two big missing features in  
OpenSolaris are:


- Sparse root zones (more for the immutability of OS-critical  
filesystems than for space reasons)

- A non-AI based SPARC installer

Any plans on either of those features?


Both are being worked on. I don't know yet about the timelines for  
sparse root zones (though it's been discussed that ZFS dedup might be  
the logical answer here), but I'm hoping a text based interactive  
installer will be available for 2010.02 which will be for both SPARC  
and x86.


You can read about the plans for the text based installer here -

http://www.opensolaris.org/os/project/caiman/TextInstallerProject/


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

Re: [osol-discuss] SXCE end-of-life plans

[Che Kristo]

Looking at the response so far perhaps it is a good idea to get a FAQ set up
on the genunix wiki...does anyone else support this idea?

On Tue, Aug 11, 2009 at 6:49 AM, Glynn Foster  wrote:

>
> Sun is announcing the intent to discontinue production of the Solaris
> Express
> Community Edition (SXCE) by the end of October time-frame. As we intend to
> continue on a bi-weekly build schedule, consolidations will move towards
> producing native Image Packaging System (IPS) packages alongside SVR4
> packages and then phase out the latter completely. Technologies such as
> IPS, Automated Install, Snap Upgrade and the Distribution Constructor will
> be
> integrating into a consolidation after following through the established
> processes including architectural (ARC) review.
>
> We recognize that this transition will require some effort for all members
> of
> the OpenSolaris development community, and are committed to working with
> all of you in making that transition a success.  You can expect updated
> information from us and the communities which manage the consolidations
> as we further plan the transition schedules.
>
> Questions can be directed to David Comay, Glynn Foster, William Franklin,
> Stephen Hahn, Dave Miner, Vincent Murphy, or Dan Roberts.
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SXCE end-of-life plans

[Boyd Adamson]

No doubt there will be a number of queries from those of us still  
currently using SXCE. For me the two big missing features in  
OpenSolaris are:


- Sparse root zones (more for the immutability of OS-critical  
filesystems than for space reasons)

- A non-AI based SPARC installer

Any plans on either of those features?

Boyd

On 11/08/2009, at 6:49 AM, Glynn Foster wrote:



Sun is announcing the intent to discontinue production of the  
Solaris Express
Community Edition (SXCE) by the end of October time-frame. As we  
intend to
continue on a bi-weekly build schedule, consolidations will move  
towards

producing native Image Packaging System (IPS) packages alongside SVR4
packages and then phase out the latter completely. Technologies such  
as
IPS, Automated Install, Snap Upgrade and the Distribution  
Constructor will be
integrating into a consolidation after following through the  
established

processes including architectural (ARC) review.

We recognize that this transition will require some effort for all  
members of
the OpenSolaris development community, and are committed to working  
with
all of you in making that transition a success.  You can expect  
updated
information from us and the communities which manage the  
consolidations

as we further plan the transition schedules.

Questions can be directed to David Comay, Glynn Foster, William  
Franklin,

Stephen Hahn, Dave Miner, Vincent Murphy, or Dan Roberts.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org



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

Re: [osol-discuss] [osol-announce] SXCE end-of-life plans

[Uros Nedic]

I hope before you stop releasing SXCE you'll provide all
tools to build OpenSolaris from source code on OpenSolaris platform.

As far as I know today is very hard to build OpenSolaris distribution
on OpenSolaris even if we have closed binaries included. We still need
SXCE to do it.

Uros


> Date: Tue, 11 Aug 2009 08:49:07 +1200
> From: glynn.fos...@sun.com
> To: opensolaris-annou...@opensolaris.org; opensolaris-discuss@opensolaris.org
> Subject: [osol-announce] SXCE end-of-life plans
>
>
> Sun is announcing the intent to discontinue production of the Solaris
> Express
> Community Edition (SXCE) by the end of October time-frame. As we
> intend to
> continue on a bi-weekly build schedule, consolidations will move towards
> producing native Image Packaging System (IPS) packages alongside SVR4
> packages and then phase out the latter completely. Technologies such as
> IPS, Automated Install, Snap Upgrade and the Distribution Constructor
> will be
> integrating into a consolidation after following through the established
> processes including architectural (ARC) review.
>
> We recognize that this transition will require some effort for all
> members of
> the OpenSolaris development community, and are committed to working with
> all of you in making that transition a success. You can expect updated
> information from us and the communities which manage the consolidations
> as we further plan the transition schedules.
>
> Questions can be directed to David Comay, Glynn Foster, William
> Franklin,
> Stephen Hahn, Dave Miner, Vincent Murphy, or Dan Roberts.
> ___
> opensolaris-announce mailing list
> opensolaris-annou...@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/opensolaris-announce

_
Show them the way! Add maps and directions to your party invites. 
http://www.microsoft.com/windows/windowslive/products/events.aspx
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SXCE end-of-life plans

[Octave Orgeron]

It does bring up the big question.. how will customers migrate from S10 to 
OpenSolaris? Or is it a "tough luck" situation and customers have to do a 
painfully manual upgrade? I mean if SVR4 pkgs go away, that kinda leaves 
Solaris on a isolated island. There are plenty of things that still need to be 
sorted out in the Indiana tree before the ties can be cut. 

Does anyone know if S10 will be the last Solaris release? If so, there has to 
be more thought around how to migrate customers and users to OpenSolaris.

 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web: http://unixconsole.blogspot.com
E-Mail: unixcons...@yahoo.com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*



- Original Message 
From: Gary Gendel 
To: opensolaris-discuss@opensolaris.org
Sent: Monday, August 10, 2009 8:57:03 PM
Subject: Re: [osol-discuss] SXCE end-of-life plans

Glynn,

Thanks for the heads up, I don't think any of are completely surprised.

I hope careful thought will be given to step-by-step instructions on how to get 
from where we are to where we should be without a long downtime.  I'd hate to 
think we will need half a day per machine because we have to start from scratch.

For example, I have a SOHO server that has a UFS root partition and a zfs 
mirrored pool on each drive.  Liveupgrade allowed minimal downtime in this 
configuration which has been running since snv_49.  It seems that the way to do 
right now would be to split the mirror, load 2009.2 on one disk, mount the old 
root and zfs pool and copy what is needed to the new drive, unmount and then 
mirror and resilver the old drive.  This sound like a very scary proposition.  
The other way would be to install from scratch and then bring stuff in from a 
backup, which is just as scary.  I was reserving this nonsense for a disaster 
recovery, not an upgrade.

Gary
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org



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

Re: [osol-discuss] SXCE end-of-life plans

[Gary Gendel]

Glynn,

Thanks for the heads up, I don't think any of are completely surprised.

I hope careful thought will be given to step-by-step instructions on how to get 
from where we are to where we should be without a long downtime.  I'd hate to 
think we will need half a day per machine because we have to start from scratch.

For example, I have a SOHO server that has a UFS root partition and a zfs 
mirrored pool on each drive.  Liveupgrade allowed minimal downtime in this 
configuration which has been running since snv_49.  It seems that the way to do 
right now would be to split the mirror, load 2009.2 on one disk, mount the old 
root and zfs pool and copy what is needed to the new drive, unmount and then 
mirror and resilver the old drive.  This sound like a very scary proposition.  
The other way would be to install from scratch and then bring stuff in from a 
backup, which is just as scary.  I was reserving this nonsense for a disaster 
recovery, not an upgrade.

Gary
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SXCE end-of-life plans

[Ignacio Marambio Catán]

is there a summary of the changes in indiana that have to go through arc?

On Mon, Aug 10, 2009 at 9:12 PM, Che Kristo wrote:
> I assume by the security issue you are reffering to
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1945 &
> http://defect.opensolaris.org/bz/show_bug.cgi?id=4885
>
> My understanding is that a fix for 4885 is targeted for indiana.next to get
> rid of the XP style "admin by default"
>
> On Tue, Aug 11, 2009 at 9:03 AM, Joerg Schilling
>  wrote:
>>
>> Glynn Foster  wrote:
>>
>> >
>> > Sun is announcing the intent to discontinue production of the Solaris
>> > Express
>> > Community Edition (SXCE) by the end of October time-frame. As we
>> > intend to
>> > continue on a bi-weekly build schedule, consolidations will move towards
>> > producing native Image Packaging System (IPS) packages alongside SVR4
>> > packages and then phase out the latter completely. Technologies such as
>> > IPS, Automated Install, Snap Upgrade and the Distribution Constructor
>> > will be
>> > integrating into a consolidation after following through the established
>> > processes including architectural (ARC) review.
>>
>> I propose not to do this before there was a correct ARC review for all
>> deviations in Indiana and not before there was a fix for all security
>> problems that have been introduced with Indiana.
>>
>> 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
>
>
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Returning with a Question

[Che Kristo]

I like that argument :) the amount of double dipping from patent holders is
ridiculous though i'd love to see it tested in court and have precedent set.

On Tue, Aug 11, 2009 at 2:59 AM, David Babb  wrote:

> Well, I hold several licensed copies of Windows 2k, XP, Vistax32, Vistax64,
> none of which are in use at this point.
>
> As these OS's ship with the default codecs I need (except flac), legally,
> I'm squeaky clean.
>
> Just because they aren't installed at this point does not negate their
> license.
>
> I so appreciate the information and the appropriate warnings, I'm going to
> go the "home" route.
>
> THANK YOU!
>
>
>
> Dave Babb
> --
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SXCE end-of-life plans

[Che Kristo]

I assume by the security issue you are reffering to
http://defect.opensolaris.org/bz/show_bug.cgi?id=1945 &
http://defect.opensolaris.org/bz/show_bug.cgi?id=4885

My understanding is that a fix for 4885 is targeted for indiana.next to get
rid of the XP style "admin by default"

On Tue, Aug 11, 2009 at 9:03 AM, Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> wrote:

> Glynn Foster  wrote:
>
> >
> > Sun is announcing the intent to discontinue production of the Solaris
> > Express
> > Community Edition (SXCE) by the end of October time-frame. As we
> > intend to
> > continue on a bi-weekly build schedule, consolidations will move towards
> > producing native Image Packaging System (IPS) packages alongside SVR4
> > packages and then phase out the latter completely. Technologies such as
> > IPS, Automated Install, Snap Upgrade and the Distribution Constructor
> > will be
> > integrating into a consolidation after following through the established
> > processes including architectural (ARC) review.
>
> I propose not to do this before there was a correct ARC review for all
> deviations in Indiana and not before there was a fix for all security
> problems that have been introduced with Indiana.
>
> 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
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] request: Prepare your os.org content for migration to XWiki

[Michelle Olson]

Hi all,

In six short weeks (Sept. 14th) all content on opensolaris.org will be 
migrated to XWiki. To prepare your web pages for this migration, please 
check the first test migration here:


http://hub.opensolaris.org/bin/view/Main/

If you find any problems, please refer to the tips and tricks for 
preparing your source here:


http://www.opensolaris.org/os/community/web/restructuring/content_preparations/

Note: ALL content preparation work must take place on opensolaris.org.

We'll do several test migrations between now and Sept. 14th and I'll 
send out a reminder mail each week after hub has been updated from the 
snapshot on stage.opensolaris.org.


Send questions to website-disc...@opensolaris.org. We'll also host a 
public meeting this Thursday at 9am PT, using the following conference 
call numbers:

http://www.opensolaris.org/os/community/web/files/con-call-numbers.pdf

Thanks in advance for your help to make this migration a success!

Regards,
Michelle Olson
OpenSolaris.org Content PM


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

Re: [osol-discuss] SXCE end-of-life plans

[Joerg Schilling]

Glynn Foster  wrote:

>
> Sun is announcing the intent to discontinue production of the Solaris  
> Express
> Community Edition (SXCE) by the end of October time-frame. As we  
> intend to
> continue on a bi-weekly build schedule, consolidations will move towards
> producing native Image Packaging System (IPS) packages alongside SVR4
> packages and then phase out the latter completely. Technologies such as
> IPS, Automated Install, Snap Upgrade and the Distribution Constructor  
> will be
> integrating into a consolidation after following through the established
> processes including architectural (ARC) review.

I propose not to do this before there was a correct ARC review for all
deviations in Indiana and not before there was a fix for all security 
problems that have been introduced with Indiana.

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

[osol-discuss] Odd smf issue with console-login service

[Mark]

All --

I'm currently building a home-rolled 64 bit distro with opensolaris (to be 
booted from a flash device), and have it mostly booting clean.  my last big 
issue is the console-login:default service.  It currently fails and gets 
transitioned to maintenance with the following error:

Aug 10 17:03:16 svc.startd[7]: svc:/system/console-login:default: Could not get 
supplemental groups property.
Aug 10 17:03:16 svc.startd[7]: system/console-login:default failed: 
transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

After it outputs this, I am able to enter in a user/pass for system maintenance 
(over the serial link), and get a shell.

Checking out the service log file, all it says is "Rereading configuration"

I have been unable to find much out there regarding this error, and was 
wondering what might be wrong?

For full disclosure, I have modified the 
/var/svc/manifest/system/console-login.xml file to change some of the propval 
settings for the serial console:
  label (to 57600), prompt and terminal_type (vt100) were all changed 

Otherwise, the file is the stock version from opensolaris snv_111b

Any help or insight would be greatly appreciated.

--
Mark
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Where can I download 101b (not RC)?

[Shawn Walker]

Roman Naumenko wrote:

Hi,

I'm looking for an old version of opensolaris: 101b
But what I can find on ftp sites from this page 
http://www.opensolaris.com/get/index.jsp
is only release candidates RC2 of 101.
ftp://ftp.saix.net/pub/OpenSolaris/2008/11/osol-0811.iso - this shows RC2 
during boot, it's weird.

Where can I download a right one?


The final release files are identical to the rc2 files released on Nov 
21st, which is why you see that.


Cheers,
--
Shawn Walker
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] Where can I download 101b (not RC)?

[Roman Naumenko]

Hi,

I'm looking for an old version of opensolaris: 101b
But what I can find on ftp sites from this page 
http://www.opensolaris.com/get/index.jsp
is only release candidates RC2 of 101.
ftp://ftp.saix.net/pub/OpenSolaris/2008/11/osol-0811.iso - this shows RC2 
during boot, it's weird.

Where can I download a right one?

--
Roman

Message was edited by: rokka
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SXCE end-of-life plans

[Glynn Foster]

On 11/08/2009, at 8:49 AM, Glynn Foster wrote:



Sun is announcing the intent to discontinue production of the  
Solaris Express
Community Edition (SXCE) by the end of October time-frame. As we  
intend to
continue on a bi-weekly build schedule, consolidations will move  
towards

producing native Image Packaging System (IPS) packages alongside SVR4
packages and then phase out the latter completely. Technologies such  
as
IPS, Automated Install, Snap Upgrade and the Distribution  
Constructor will be
integrating into a consolidation after following through the  
established

processes including architectural (ARC) review.

We recognize that this transition will require some effort for all  
members of
the OpenSolaris development community, and are committed to working  
with
all of you in making that transition a success.  You can expect  
updated
information from us and the communities which manage the  
consolidations

as we further plan the transition schedules.

Questions can be directed to David Comay, Glynn Foster, William  
Franklin,

Stephen Hahn, Dave Miner, Vincent Murphy, or Dan Roberts.


It should be noted that there was no connection with the recent  
quality issues around SXCE (and builds being synced up to  
pkg.opensolaris.org). Those have been addressed by John Beck in a  
previous mail and have been predominantly issues within the ON  
consolidation. You can read about the action taken at the following  
link - http://www.opensolaris.org/os/community/on/flag-days/pages/2009080502/



Glynn

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

[osol-discuss] SXCE end-of-life plans

[Glynn Foster]

Sun is announcing the intent to discontinue production of the Solaris  
Express
Community Edition (SXCE) by the end of October time-frame. As we  
intend to

continue on a bi-weekly build schedule, consolidations will move towards
producing native Image Packaging System (IPS) packages alongside SVR4
packages and then phase out the latter completely. Technologies such as
IPS, Automated Install, Snap Upgrade and the Distribution Constructor  
will be

integrating into a consolidation after following through the established
processes including architectural (ARC) review.

We recognize that this transition will require some effort for all  
members of

the OpenSolaris development community, and are committed to working with
all of you in making that transition a success.  You can expect updated
information from us and the communities which manage the consolidations
as we further plan the transition schedules.

Questions can be directed to David Comay, Glynn Foster, William  
Franklin,

Stephen Hahn, Dave Miner, Vincent Murphy, or Dan Roberts.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Returning with a Question

[Thommy M . Malmström]

>The non-licensed way:  href="http://solaris.homeunix.com/";>http://solaris.hom
> eunix.com/ appropriate for home-use situations
> and for countries where the licensing conditions for
> the codecs are not relevant

Great stuff. Thanks.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] Toshiba OpenSolaris Laptops

[andrew]

Can anyone tell me how long I should expect to wait for my Toshiba OpenSolaris 
laptop? I ordered it 2 weeks ago and apart from the confirmation email when I 
placed the order I have not heard anything about how my order is progressing. I 
phoned the number on the confirmation email the other day and they basically 
told me to wait a bit longer, but I'm slightly concerned as I've had absolutely 
no indication that my order is actually progressing, which is a bit worrying. 
Also, to have waited 2 weeks and the laptop has apparently not even been 
despatched is an awful long time to wait!

Cheers

Andrew.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Conflicts after build 111

[Kristinn Richter]

I've gotten response from my RFE (6862065) on the matter.  Garrett have sent 
new driver binaries, which completely solve the problem for me.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] solaris iscsi mpxio

[Omer Faruk Sen]

Hi ,

I am trying to enable iscsi multipath on Solaris 10 Update 3 using
mpxio which is shown as supported on netapp support matrix.
We have made following on the system to enable iscsi+mpxio
pkgadd -d NTAPSANTool.pkg
 cd /opt/NTAP/SANToolkit/
 ./mpxio_set -e
 reboot -- -r

Our netapp IP address is 192.168.199.31 and 192.168.199.32. I have
used following commands on Solaris

iscsiadm add discovery-address 192.168.199.31:3260 (adding first head of netapp)
iscsiadm add discovery-address 192.168.199.32:3260 (adding second head
of netapp)
iscsiadm modify discovery --sendtargets enable

/opt/NTAP/SANToolkit/bin/sanlun lun show all shows

   filer:  lun-pathname device
filename   adapter  protocol  lun size
lun state
btelnetapp2:  /vol/iscsisolaris/data/iscsilun1
/dev/rdsk/c2t60A98000572D43354E4A524249686F6Cd0s2  iscsi0   iSCSI
 40.0g (42953867264)GOOD

iscsiadm  list target command gives following output:

Target: iqn.1992-08.com.netapp:sn.151701231
Alias: -
TPGT: 1002
ISID: 402a
Connections: 0
Target: iqn.1992-08.com.netapp:sn.151701231
Alias: -
TPGT: 1001
ISID: 402a
Connections: 1
Target: iqn.1992-08.com.netapp:sn.151701367
Alias: -
TPGT: 1002
ISID: 402a
Connections: 0
Target: iqn.1992-08.com.netapp:sn.151701367
Alias: -
TPGT: 1001
ISID: 402a


bash-3.00#  iscsiadm list initiator-node
Initiator node name: iqn.1986-03.com.sun:01:00144faadea8.4a801672
Initiator node alias: -
Login Parameters (Default/Configured):
Header Digest: NONE/-
Data Digest: NONE/-
Authentication Type: NONE
RADIUS Server: NONE
RADIUS access: unknown
Configured Sessions: 1
bash-3.00#
bash-3.00# iscsiadm list target-param -v iqn.1992-08.com.netapp:sn.151701231
Target: iqn.1992-08.com.netapp:sn.151701231
Alias: -
Bi-directional Authentication: disabled
Authentication Type: NONE
Login Parameters (Default/Configured):
Data Sequence In Order: yes/-
Data PDU In Order: yes/-
Default Time To Retain: 20/-
Default Time To Wait: 2/4
Error Recovery Level: 0/-
First Burst Length: 65536/-
Immediate Data: yes/-
Initial Ready To Transfer (R2T): yes/-
Max Burst Length: 262144/-
Max Outstanding R2T: 1/-
Max Receive Data Segment Length: 8192/-
Max Connections: 1/-
Header Digest: NONE/-
Data Digest: NONE/-
Configured Sessions: 1

bash-3.00# iscsiadm list target-param -v iqn.1992-08.com.netapp:sn.151701367
Target: iqn.1992-08.com.netapp:sn.151701367
Alias: -
Bi-directional Authentication: disabled
Authentication Type: NONE
Login Parameters (Default/Configured):
Data Sequence In Order: yes/-
Data PDU In Order: yes/-
Default Time To Retain: 20/-
Default Time To Wait: 2/4
Error Recovery Level: 0/-
First Burst Length: 65536/-
Immediate Data: yes/-
Initial Ready To Transfer (R2T): yes/-
Max Burst Length: 262144/-
Max Outstanding R2T: 1/-
Max Receive Data Segment Length: 8192/-
Max Connections: 1/-
Header Digest: NONE/-
Data Digest: NONE/-
Configured Sessions: 1
Connections: 1

After that we use commands listed
http://docs.sun.com/app/docs/doc/817-5093/gcawf?a=view
iscsiadm modify initiator-node -c 2
iscsiadm modify target-param -c 2  iqn.1992-08.com.netapp:sn.151701367
iscsiadm modify target-param -c  192.168.199.32,192.168.199.31
iqn.1992-08.com.netapp:sn.151701367



While issuing those commands we get  following errors:

Aug 10 16:33:05 bn-dse1 iscsi: NOTICE: iscsi connection(14) unable to
connect to target iqn.1992-08.com.netapp:sn.151701367 (errno:145)
Aug 10 16:33:06 bn-dse1 iscsi: NOTICE: iscsi session(11)
iqn.1992-08.com.netapp:sn.151701367 online
Aug 10 16:33:13 bn-dse1 NE_Create: Child Process(pid=775) Created
Aug 10 16:33:21 bn-dse1 svc.startd[7]: system/filesystem/volfs:default
failed: transitioned to maintenance (see 'svcs -xv' for details)
Aug 10 16:33:31 bn-dse1 iscsi: NOTICE: iscsi connection(14) unable to
connect to target iqn.1992-08.com.netapp:sn.151701367 (errno:145)
bn-dse1 console login: Aug 10 16:37:59 bn-dse1 last message repeated 6 times
Aug 10 16:39:47 bn-dse1 iscsi: NOTICE: iscsi connection(14) unable to
connect to target iqn.1992-08.com.netapp:sn.151701367 (errno:145)
Aug 10 16:41:46 bn-dse1 iscsi: NOTICE: iscsi connection(37) unable to
connect to target iqn.1992-08.com.netapp:sn.151701231 (err

Re: [osol-discuss] Returning with a Question

[David Babb]

Well, I hold several licensed copies of Windows 2k, XP, Vistax32, Vistax64, 
none of which are in use at this point.

As these OS's ship with the default codecs I need (except flac), legally, I'm 
squeaky clean.

Just because they aren't installed at this point does not negate their license.

I so appreciate the information and the appropriate warnings, I'm going to go 
the "home" route.

THANK YOU!



Dave Babb
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Returning with a Question

[Brian Cameron]

Dave/Che:


The licensed and supported way:
http://www.fluendo.com/shop/product/complete-set-of-playback-plugins/
use this if you are in a country in which the relevant codecs must be
appropriately licensed (most countries), essential if you are
implementing within a corporate environment unless you want to risk
having you company end up in court


A further advantage of using the Fluendo plugins is that they are
supported and should work without problems when you do things like
upgrade your system.  If you want a solution you install once and then
"just works", then Fluendo is a good choice.  You get what you pay for
and all that.


The non-licensed way: http://solaris.homeunix.com/ appropriate for
home-use situations and for countries where the licensing conditions for
the codecs are not relevant


You probably need to check with a lawyer to find out when going the
"non-licensed" way is appropriate.  Businesses are probably more exposed
to the legal risks than home users, but it is probably inaccurate to
suggest home users do not need to worry about such risks.

Brian



Hope this helps and have fun!

I've used both and they are great!

Ché
myunix.org 

On Mon, Aug 10, 2009 at 1:34 PM, David Babb mailto:dcb...@gmail.com>> wrote:

Good evening all,

2008.11 just caused too many issues with my hardware, so I took a
sabbatical.

Now after the 2009 Release, I'm giving O.S. another look.

Before on 2008.11, I got the multimedia apps I needed from
lifewithsolaris.jp , now, there is no
multimedia there.

If I port, I need to have the ability to listen to my sound library,
some of which I have converted from vinyl. Think Woodstock,
(although I was somewhere else((Vietnam Era Vet)).

Some of it is in flac, wmv, mpeg4, the whole gauntlet of formats.


Question:
What is the new mechanism of enabling a movie player and a sound
player, and installing the proper codecs for each in Open Solaris?

This is my only question/issue to overcome, and I'll move the shops
machine over first.



Thank you sincerely,


Dave babb
--
This message posted from opensolaris.org 
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org






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


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

Re: [osol-discuss] Fault tolerance in OpenSolaris xVM

[Tirthankar]

Check out HA-xVM  and OHAC
http://opensolaris.org/os/project/ha-xvm/

You can use OpenHACluster 2009.06 and use the HA-xVM agent

Since you do not want to use any shared storage, you can keep all the shared 
data on  a mirrored zpool. This zpool is created from the iscsi targets that 
are exported from the local disk of each cluster node.

Refer to 
http://blogs.sun.com/SC/entry/announcing_open_ha_cluster_2009


Thanks,
Tirthankar
http://blogs.sun.com/tirthankar
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] snv_120 on a laptop - no keyboard?

[john kroll]

will snv_120 be released to the general public [regular Sun download] or is it 
reserved as laptop only or something ??
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] snv_120 on a laptop - no keyboard? (more info)

[roland]

>The call to drive_present never returns.

that sounds like edd - i know sysstems where you need to pass "edd=off" to 
correctly boot linux. 
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e479c8306f898fcdb9b36179071eae6338a17364)

dobiosdev=0 sounds like the solaris equivalent for that.

is that correct ?

i`m wondering that solaris can get past this bios call, while linux hangs 
endlessly in those routines and needs "edd=off" to work around that. 

does someone know details about the difference?
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Fault tolerance in OpenSolaris xVM

[roland]

>I am looking for a way to run a fault tolerant virtual machine using
>OpenSolaris xVM. 

you mean "fault tolerance" lilke "VMWare Fault Tolerance" ?

>If it is possible, I would like to do it, without a
>separate, shared storage.
i think xVM cannot do that and especially without shared storage you should 
forget about that idea entirely
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] OpenCL on Solaris

[Che Kristo]

Haven't heard anything yet, best chance would be NVidia although their
current implementation is only for Linux and Windows. Send them an email and
let them know you want it supported on Solaris too...

On Mon, Aug 10, 2009 at 4:51 AM, Brandon Barker wrote:

> Does anyone know of planned support for OpenCL for various CPUS and GPUS in
> solaris?  See:
> http://www.businesswire.com/portal/site/google/?ndmViewId=news_view&newsId=20090804006502&newsLang=en
> --
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org