Re: [osol-discuss] SNV_124: Worth the Wait!!!

[Calum Benson]

On 25 Sep 2009, at 01:52, Ignacio Marambio Catán wrote:

will we follow the trend and migrate from pidgin to what gnome uses  
these days?


Empathy? Yes, eventually, but not in the 2010.02 timeframe AFAIK.  
(Some of the underlying Telepathy libraries have already integrated,  
though.)


Cheeri,
Calum.

--
CALUM BENSON, Usability Engineer   Sun Microsystems Ireland
mailto:calum.ben...@sun.comOpenSolaris Desktop Team
http://blogs.sun.com/calum +353 1 819 9771

Any opinions are personal and not necessarily those of Sun Microsystems

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

Re: [osol-discuss] SNV_124: Worth the Wait!!!

[Ignacio Marambio Catán]

will we follow the trend and migrate from pidgin to what gnome uses these days?

On Thu, Sep 24, 2009 at 9:29 PM, Calum Benson  wrote:
>
> On 24 Sep 2009, at 19:12, Cyril Plisko wrote:
>
>> 2009/9/24 Ignacio Marambio Catán :
>>>
>>> why is that?
>>>
>>
>> WAG: Gnome 2.28
>
> Hmm.  That would hardly be a 'surprise' (given that new GNOME releases are
> always integrated as soon as possible), and there isn't much in 2.28 that
> wasn't in 2.26.  (Ironically, you're more likely to notice things that have
> gone in 2.28, rather than anything new...)
>
> Cheeri,
> Calum.
>
> --
> CALUM BENSON, Usability Engineer       Sun Microsystems Ireland
> mailto:calum.ben...@sun.com            OpenSolaris Desktop Team
> http://blogs.sun.com/calum             +353 1 819 9771
>
> Any opinions are personal and not necessarily those of Sun Microsystems
>
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SNV_124: Worth the Wait!!!

[Calum Benson]

On 24 Sep 2009, at 19:12, Cyril Plisko wrote:


2009/9/24 Ignacio Marambio Catán :

why is that?



WAG: Gnome 2.28


Hmm.  That would hardly be a 'surprise' (given that new GNOME releases  
are always integrated as soon as possible), and there isn't much in  
2.28 that wasn't in 2.26.  (Ironically, you're more likely to notice  
things that have gone in 2.28, rather than anything new...)


Cheeri,
Calum.

--
CALUM BENSON, Usability Engineer   Sun Microsystems Ireland
mailto:calum.ben...@sun.comOpenSolaris Desktop Team
http://blogs.sun.com/calum +353 1 819 9771

Any opinions are personal and not necessarily those of Sun Microsystems

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

Re: [osol-discuss] opensolaris wallpaper

[Calum Benson]

On 24 Sep 2009, at 17:02, Thorsten Manda wrote:

But i can't find it. Could someone please upload this Wallpaper for  
me or give me a link?


I know you've found it now, but for future reference, most of the  
OpenSolaris wallpapers past and present can be found in the  
opensolaris-backgrounds tarballs here:




Cheeri,
Calum.

--
CALUM BENSON, Usability Engineer   Sun Microsystems Ireland
mailto:calum.ben...@sun.comOpenSolaris Desktop Team
http://blogs.sun.com/calum +353 1 819 9771

Any opinions are personal and not necessarily those of Sun Microsystems

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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Alex Smith (K4RNT)]

Deny listings with tcpwrappers takes precedence over allow entries.

Your hosts.deny was disallowing the connections.

On Thu, Sep 24, 2009 at 17:37, Christopher Smith  wrote:
> Hi,
>
> In my searching before coming to the mailing list, I read somewhere (I can't
> find the reference now) that remote gdm login wasn't allowed without tcp
> wrappers being enabled.  Also, if I check the list if services being
> controlled by inetadm I don't see anything I recognize as being for gdm
> login, which seems odd.  Anyways, I commented the "ALL: ALL" line in
> hosts.deny and retried the connection, it worked.
>
> It does seem like something is awry in inetd/tcp wrappers.  From my reading
> of the man pages, having ALL: 192.168. in hosts.allow should take effect
> before the ALL: ALL in hosts.deny.  If I try, ALL: ALL EXCEPT 192.168. in
> hosts.deny, the connection fails. Its as if inetd/tcp wrappers isn't
> recognising the IP address (I tried ALL: ALL EXCEPT
> 192.168.0.0/255.255.255.0 too). For now, I've set ALL EXCEPT gdm: ALL and
> things keep working.
>
> Thanks for your help.

-- 
" ' With the first link, the chain is forged. The first speech
censured, the first thought forbidden, the first freedom denied,
chains us all irrevocably.' Those words were uttered by Judge Aaron
Satie as wisdom and warning... The first time any man's freedom is
trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron
Satie, Star Trek: TNG episode "The Drumhead"
- Alex Smith (K4RNT)
- Murfreesboro/Nashville, Tennessee USA
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Program of OSDevCon 2009 published

[Che Kristo]

I am particularly interested in hearing Vineeth Pillai's talk on the ARM
port but am on the other side of the world, will anybody be toting a video
camera?

On Fri, Sep 25, 2009 at 07:57, Dirk Wetter  wrote:

>
> Hi,
>
> Am 09/19/2009 10:44 PM, Dirk Wetter schrieb:
>
> > just for information: We released the program [1] of this years
> > OpenSolaris Developer Conference which takes place in
> > historical Dresden / Germany between October 27-30, 2009.
>
> [..]
>
> >   Registration will be opened within the next few days.
>
> In the meantime the registration [2] is open.
>
> The special thing this year is that you can hop between
> Linux-Kongress [3] and OSDevCon. Also feel free to pick
> tutorials from both conferences.
>
> [1] http://www.osdevcon.org/2009/program.html
> [2] http://www.osdevcon.org/2009/fees_reg.html#reg ,
>
> https://registration.guug.de/macomaweb-lk2009/registration/registration.jsp
> [3] http://www.linux-kongress.org/2009/
>
>
>
>
> Best / Schöne Grüße,
>
>Dirk
>
> --
> Dr. Dirk Wetter
> Member of board / Mitglied des Vorstands
>
> German Unix User Group (GUUG) e.V.http://www.guug.de
> Postfach 250123, D-44739 Bochum, Germany
>
> OpenPGP key fingerprint: 2AD6 BE0F 9863 C82D 21B3 64E5 C967 34D8 11B7 C62F
>
>
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Still confused about SCXE versus OpenSolaris 2010.02 Developer Builds

[Glynn Foster]

On 25/09/2009, at 10:45 AM, Errol Neal wrote:




I admit, it does not take very much to confuse me, but I think I'm  
at my limits here.


I realize SCXE is going away. I know there are some features that  
are not available in Opensolaris (Indiana). What I don't know is if:


1. The Dev Build of OpenSolaris contain all the features of SCXE.


Yes, more or less. There may be some software in SXCE that isn't yet  
available in OpenSolaris. This is due to the fact that OpenSolaris is  
re-distributable by design. Some of that software is available in the  
extra repository (https://pkg.sun.com), some isn't yet. Some you  
probably wouldn't even miss.



2. If a method exists to "upgrade" from SCXE to Opensolaris


A method exists, but isn't yet supported.

http://blogs.sun.com/edp/entry/moving_from_nevada_and_live

(and other google searches)

will help.



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

[osol-discuss] Still confused about SCXE versus OpenSolaris 2010.02 Developer Builds

[Errol Neal]

I admit, it does not take very much to confuse me, but I think I'm at my limits 
here. 

I realize SCXE is going away. I know there are some features that are not 
available in Opensolaris (Indiana). What I don't know is if:

1. The Dev Build of OpenSolaris contain all the features of SCXE.
2. If a method exists to "upgrade" from SCXE to Opensolaris

If my first question is not true, then what are SCXE users supposed to do? 

Thanks,


_
This email was transferred using an evaluation version
of AXIGEN Mail Server.

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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Christopher Smith]

Hi,

In my searching before coming to the mailing list, I read somewhere (I  
can't find the reference now) that remote gdm login wasn't allowed  
without tcp wrappers being enabled.  Also, if I check the list if  
services being controlled by inetadm I don't see anything I recognize  
as being for gdm login, which seems odd.  Anyways, I commented the  
"ALL: ALL" line in hosts.deny and retried the connection, it worked.


It does seem like something is awry in inetd/tcp wrappers.  From my  
reading of the man pages, having ALL: 192.168. in hosts.allow should  
take effect before the ALL: ALL in hosts.deny.  If I try, ALL: ALL  
EXCEPT 192.168. in hosts.deny, the connection fails. Its as if inetd/ 
tcp wrappers isn't recognising the IP address (I tried ALL: ALL EXCEPT  
192.168.0.0/255.255.255.0 too). For now, I've set ALL EXCEPT gdm: ALL  
and things keep working.


Thanks for your help.

Chris


On 24 Sep 2009, at 21:38, Brian Cameron wrote:



Christopher:

Looking at the GDM code, it only prints out the "XDMCP: Sending
UNWILLING to %s" message if the function gdm_xdmcp_host_allow()
function in daemon/gdm-xdmcp-manager.c returns FALSE.

This only happens if the following call returns FALSE:

  ret = hosts_ctl("gdm", client, host, "");

In this case client would be "192.168.0.105" and host is a
value returned from the gdm_address_get_info () call, which
would be the "host" value returned from a call to getnameinfo().

Since hosts_ctl is a a libwrap() function (see "man libwrap"),
I think that the problem is likely with either your tcp wrappers
configuration, or perhaps a problem with your system configuration
not returning a good "host" value when getnameinfo() is called?

You say you see the same error regardless of how tcp wrappers is
configured, which seems odd.  I'd think that you should be
able to configure tcp wrappers to always make hosts_ctl return
TRUE.  If so, I'd think you'ld see a different error message
in this case.  As I say above the "Sending UNWILLING" message
should not appear if hosts_ctl returns TRUE, and you should
see some other error message if it is still failing.

Just speculating, but from looking at the code, this hopefully
narrows down what you should be looking at.

Brian



On 24 Sep 2009, at 20:32, Brian Cameron wrote:


Christopher:


Hello Brian, thanks for replying.
options/tcp_listen is set to true.  That is what I meant by  
enabled tcp-listen for x11.  After changing that particular  
setting, port 6000 opened, but the connection would still  
breakdown with "Manager unwilling, Host unwilling" error.


You could try setting Enable=true in the [debug] section of the
GDM configuration file (/usr/share/gdm/defaults.conf), and restart
GDM.  Then try to connect and check your syslog (/var/adm/messages)
and see if there is any useful information about what might be
happening.
I did that and with tcpwrappers off, the five log messages were  
esssentially the same, see below.

supernova is the machine name of the opensolaris box.
192.168.0.105 is the IP address of the computer attempting to make  
the connection.
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911  
daemon.warning] DEBUG: decode_packet: GIOCondition 1
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911  
daemon.warning] DEBUG: XDMCP: Received opcode QUERY from  
client :::192.168.0.105 : 49642
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911  
daemon.warning] DEBUG: gdm_xdmcp_host_allow: client->hostname is  
192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911  
daemon.warning] DEBUG: XDMCP: Sending UNWILLING to ::: 
192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911  
daemon.warning] DEBUG: Denied XDMCP query from host ::: 
192.168.0.105




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

Re: [osol-discuss] Program of OSDevCon 2009 published

[Dirk Wetter]

Hi,

Am 09/19/2009 10:44 PM, Dirk Wetter schrieb:

> just for information: We released the program [1] of this years
> OpenSolaris Developer Conference which takes place in
> historical Dresden / Germany between October 27-30, 2009.

[..]

>   Registration will be opened within the next few days.

In the meantime the registration [2] is open.

The special thing this year is that you can hop between
Linux-Kongress [3] and OSDevCon. Also feel free to pick
tutorials from both conferences.

[1] http://www.osdevcon.org/2009/program.html
[2] http://www.osdevcon.org/2009/fees_reg.html#reg ,
https://registration.guug.de/macomaweb-lk2009/registration/registration.jsp
[3] http://www.linux-kongress.org/2009/




Best / Schöne Grüße,

Dirk

-- 
Dr. Dirk Wetter
Member of board / Mitglied des Vorstands

German Unix User Group (GUUG) e.V.http://www.guug.de
Postfach 250123, D-44739 Bochum, Germany

OpenPGP key fingerprint: 2AD6 BE0F 9863 C82D 21B3 64E5 C967 34D8 11B7 C62F


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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Christopher Smith]

See below.

On 24 Sep 2009, at 20:32, Brian Cameron wrote:



Christopher:


Hello Brian, thanks for replying.
options/tcp_listen is set to true.  That is what I meant by enabled  
tcp-listen for x11.  After changing that particular setting, port  
6000 opened, but the connection would still breakdown with "Manager  
unwilling, Host unwilling" error.


You could try setting Enable=true in the [debug] section of the
GDM configuration file (/usr/share/gdm/defaults.conf), and restart
GDM.  Then try to connect and check your syslog (/var/adm/messages)
and see if there is any useful information about what might be
happening.


I did that and with tcpwrappers off, the five log messages were  
esssentially the same, see below.


supernova is the machine name of the opensolaris box.
192.168.0.105 is the IP address of the computer attempting to make the  
connection.


Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning]  
DEBUG: decode_packet: GIOCondition 1
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning]  
DEBUG: XDMCP: Received opcode QUERY from client :::192.168.0.105 :  
49642
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning]  
DEBUG: gdm_xdmcp_host_allow: client->hostname is 192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning]  
DEBUG: XDMCP: Sending UNWILLING to :::192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning]  
DEBUG: Denied XDMCP query from host :::192.168.0.105



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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Christopher Smith]

Hello Brian, thanks for replying.

options/tcp_listen is set to true.  That is what I meant by enabled  
tcp-listen for x11.  After changing that particular setting, port 6000  
opened, but the connection would still breakdown with "Manager  
unwilling, Host unwilling" error.


- Chris

On 24 Sep 2009, at 19:28, Brian Cameron wrote:



Chris:

Refer to "man Xserver".  Note that you may need to set the SMF
property "options/tcp_listen" to true so that the Xserver accepts
incoming TCP/IP connections.  You can use the svccfg(1M) command
to set this property as the Xserver manpage explains.

Brian


I have a box running OpenSolaris 09.06 which I would like to run  
headless and access the desktop from a Mac (currently running OSX  
10.5.8) on the same LAN.
This used to work under OS 08.05.  09.06 seems more secure and I'm  
struggling to locate all the appropriate settings to enable remote  
login. Specifically, I can't seem to get OpenSolaris to listen on  
port 177 for the xdmcp connection.

After searching around, I've made the following changes:
- /etc/X11/gdm/custom.conf
 add to [security] DisallowTCP=false
 add to [xdmcp] Enable=true
- enabled tcp wrappers
- enabled tcp-listen for x11
- set hosts.allow to ALL: 192.168. and hosts.deny to ALL: ALL
gdmsetup shows all the correct xdmcp settings.  but still port 177  
refuses to open.

enabling tcp-listen for x11, did open port 6000.
Any help would be appreciated.




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

Re: [osol-discuss] GRUB hang

[Sean Liu]

I'll try this a bit later and report back.

Thanks,

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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Brian Cameron]

Christopher:

Looking at the GDM code, it only prints out the "XDMCP: Sending
UNWILLING to %s" message if the function gdm_xdmcp_host_allow()
function in daemon/gdm-xdmcp-manager.c returns FALSE.

This only happens if the following call returns FALSE:

   ret = hosts_ctl("gdm", client, host, "");

In this case client would be "192.168.0.105" and host is a
value returned from the gdm_address_get_info () call, which
would be the "host" value returned from a call to getnameinfo().

Since hosts_ctl is a a libwrap() function (see "man libwrap"),
I think that the problem is likely with either your tcp wrappers
configuration, or perhaps a problem with your system configuration
not returning a good "host" value when getnameinfo() is called?

You say you see the same error regardless of how tcp wrappers is
configured, which seems odd.  I'd think that you should be
able to configure tcp wrappers to always make hosts_ctl return
TRUE.  If so, I'd think you'ld see a different error message
in this case.  As I say above the "Sending UNWILLING" message
should not appear if hosts_ctl returns TRUE, and you should
see some other error message if it is still failing.

Just speculating, but from looking at the code, this hopefully
narrows down what you should be looking at.

Brian



On 24 Sep 2009, at 20:32, Brian Cameron wrote:



Christopher:


Hello Brian, thanks for replying.
options/tcp_listen is set to true.  That is what I meant by enabled 
tcp-listen for x11.  After changing that particular setting, port 
6000 opened, but the connection would still breakdown with "Manager 
unwilling, Host unwilling" error.


You could try setting Enable=true in the [debug] section of the
GDM configuration file (/usr/share/gdm/defaults.conf), and restart
GDM.  Then try to connect and check your syslog (/var/adm/messages)
and see if there is any useful information about what might be
happening.


I did that and with tcpwrappers off, the five log messages were 
esssentially the same, see below.


supernova is the machine name of the opensolaris box.
192.168.0.105 is the IP address of the computer attempting to make the 
connection.


Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning] 
DEBUG: decode_packet: GIOCondition 1
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning] 
DEBUG: XDMCP: Received opcode QUERY from client :::192.168.0.105 : 
49642
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning] 
DEBUG: gdm_xdmcp_host_allow: client->hostname is 192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning] 
DEBUG: XDMCP: Sending UNWILLING to :::192.168.0.105
Sep 24 21:01:48 supernova gdm-binary[750]: [ID 702911 daemon.warning] 
DEBUG: Denied XDMCP query from host :::192.168.0.105





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

Re: [osol-discuss] GRUB hang

[Vikram Hegde]

Hi,

Do the following

at grub> prompt do

find  /boot/grub/menu.lst

you will get sonmething like

(hdX, Y, Z)

Then boot Solaris (manually) as you did before.

Once booted do

installgrub  stage1  stage2  /dev/rdsk/cMdNtOsP

(note, using -m option is discouraged, as install software may not use 
-m option in which case your -m option will override install software 
even if the latter does an installgrub later.)


where M,N, O need to be determined. If you have only 1 disk - this is 
straightforward.

P is the slice and can be directly determined from Z above.

If Z == a,   P == 0
and so on.

Also do zpool status to make sure the /dev/dsk/* above contains a ZFS 
root pool.


Vikram

Sean Liu wrote:

Vikram,

Thanks for your reply.
After adding $ sign, the system booted up - which proves that rpool was fine.
However when I boot directly from disk, I still get the dreaded "GRUB" prompt 
and then goes nowhere.
I tried again "installgrub -m stage1 stage2 /dev/rdsk/c1t0d0s0", no help.

What else can I try?

Thanks,

Sean
  



--
==
FOR SALE:  Intelligent purebred donkeys available. Call 1-800-DARWIN-0
==

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

Re: [osol-discuss] GRUB hang

[Sean Liu]

Vikram,

Thanks for your reply.
After adding $ sign, the system booted up - which proves that rpool was fine.
However when I boot directly from disk, I still get the dreaded "GRUB" prompt 
and then goes nowhere.
I tried again "installgrub -m stage1 stage2 /dev/rdsk/c1t0d0s0", no help.

What else can I try?

Thanks,

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

Re: [osol-discuss] nVidia 9800m GTX Driver

[John Martin]

David wrote:

I have installed OpenSolaris 2009.06 (which is supposed to support the geForce 
9800m GTX out-of-the-box) and am having display driver problems.  I had to do a 
remote install and that is the only way I can login to the system.  On boot it 
hangs at the splash screen.  Research has shown that there was a bug 
fixed(http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6883157) but I 
do not know where to get the fix or how to apply it.
  

The nv driver described in 6883157 shouldn't matter as the nvidia
driver in 2009.06 should be attached to the hardware instead.
If you can login remotely, can you send me the output of:

 $ /usr/bin/nvidia-SunOS-bug-report.sh


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

[osol-discuss] nVidia 9800m GTX Driver

[David]

I have installed OpenSolaris 2009.06 (which is supposed to support the geForce 
9800m GTX out-of-the-box) and am having display driver problems.  I had to do a 
remote install and that is the only way I can login to the system.  On boot it 
hangs at the splash screen.  Research has shown that there was a bug 
fixed(http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6883157) but I 
do not know where to get the fix or how to apply it.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Brian Cameron]

Christopher:


Hello Brian, thanks for replying.

options/tcp_listen is set to true.  That is what I meant by enabled 
tcp-listen for x11.  After changing that particular setting, port 6000 
opened, but the connection would still breakdown with "Manager 
unwilling, Host unwilling" error.


You could try setting Enable=true in the [debug] section of the
GDM configuration file (/usr/share/gdm/defaults.conf), and restart
GDM.  Then try to connect and check your syslog (/var/adm/messages)
and see if there is any useful information about what might be
happening.

You might also try turning off tcpwrappers and see if you can get
it working without using that.  That might help to determine if it
is a problem with GDM XDMCP in general, or with the tcpwrapper
code.


- Chris

On 24 Sep 2009, at 19:28, Brian Cameron wrote:



Chris:

Refer to "man Xserver".  Note that you may need to set the SMF
property "options/tcp_listen" to true so that the Xserver accepts
incoming TCP/IP connections.  You can use the svccfg(1M) command
to set this property as the Xserver manpage explains.

Brian


I have a box running OpenSolaris 09.06 which I would like to run 
headless and access the desktop from a Mac (currently running OSX 
10.5.8) on the same LAN.
This used to work under OS 08.05.  09.06 seems more secure and I'm 
struggling to locate all the appropriate settings to enable remote 
login. Specifically, I can't seem to get OpenSolaris to listen on 
port 177 for the xdmcp connection.

After searching around, I've made the following changes:
- /etc/X11/gdm/custom.conf
 add to [security] DisallowTCP=false
 add to [xdmcp] Enable=true
- enabled tcp wrappers
- enabled tcp-listen for x11
- set hosts.allow to ALL: 192.168. and hosts.deny to ALL: ALL
gdmsetup shows all the correct xdmcp settings.  but still port 177 
refuses to open.

enabling tcp-listen for x11, did open port 6000.
Any help would be appreciated.






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

Re: [osol-discuss] Enabling Remote GUI Login via XDMCP

[Brian Cameron]

Chris:

Refer to "man Xserver".  Note that you may need to set the SMF
property "options/tcp_listen" to true so that the Xserver accepts
incoming TCP/IP connections.  You can use the svccfg(1M) command
to set this property as the Xserver manpage explains.

Brian



I have a box running OpenSolaris 09.06 which I would like to run headless and 
access the desktop from a Mac (currently running OSX 10.5.8) on the same LAN.

This used to work under OS 08.05.  09.06 seems more secure and I'm struggling 
to locate all the appropriate settings to enable remote login. Specifically, I 
can't seem to get OpenSolaris to listen on port 177 for the xdmcp connection.

After searching around, I've made the following changes:
- /etc/X11/gdm/custom.conf
  add to [security] DisallowTCP=false
  add to [xdmcp] Enable=true
- enabled tcp wrappers
- enabled tcp-listen for x11
- set hosts.allow to ALL: 192.168. and hosts.deny to ALL: ALL

gdmsetup shows all the correct xdmcp settings.  but still port 177 refuses to 
open.

enabling tcp-listen for x11, did open port 6000.

Any help would be appreciated.


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

Re: [osol-discuss] SNV_124: Worth the Wait!!!

[Cyril Plisko]

2009/9/24 Ignacio Marambio Catán :
> why is that?
>

WAG: Gnome 2.28


> On Wed, Sep 23, 2009 at 11:20 PM, ken mays  wrote:
>> Hello,
>>
>> For our OpenSolaris distributors, this release may be worth the wait. I 
>> think we are in for a big suprise...
>>


-- 
Regards,
Cyril
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] GRUB hang

[Vikram Hegde]

Hi,

You missed the the $ sign after module and kernel

Try

findroot  (...)
bootfs ...
kernel$  /platform/i86pc/kernel/$ISADIR/unix  -B $ZFS-BOOTFS
module$  /platform/i86pc/$ISADIR/boot_archive
boot

Sean Liu wrote:

Hi there,

I've got a Sun x4150 running (or, was running) opensolaris b122.
Recently I attached a new SATA disk to the machine, then used zpool replace 
technique to transfer rpool from the old disk to the new disk.
I believe the new disk actually booted up once then it's not bootable anymore.
When the system boots, only "GRUB" prompt is on the screen and it goes no 
further.

I booted up my B122 usb stick, I can import the rpool no problem, so the 
filesystem/pool was fine.

I tried a few other things, including getting rid of the zpool.cache, updating 
boot archives etc., but no help.

Then I tried booting the USB stick again, this time I went into GRUB command 
line. findroot found rpool no problem, manually entered the grub info, but boot 
hangs. Attahced is a screenshot.

Anyone can point me to the right direction?

TIA,

Sean
  



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



--
==
FOR SALE:  Intelligent purebred donkeys available. Call 1-800-DARWIN-0
==

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

Re: [osol-discuss] opensolaris wallpaper

[Thorsten Manda]

For those who want the wallpaper:

http://img5.imagebanana.com/view/y021qrax/BlueDarkFlare.jpg
http://img5.imagebanana.com/img/7155b3s4/opensolarisdefault.jpg
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] How to go about finding where apache logs errors?

[Brandon Hume]

> But of course this `log' is nearly useless.  And is
> beyond useless for
> anything to do with connection errors like misfiring
> cgi or whatever.

That's because that's not Apache's log, that's SMF's log as relates to its 
duties starting/stopping Apache.

> Why are the usefull logs not listed there?

Because there's no way for SMF to know how or what or where a given application 
is logging.  It'd be like looking for CGI errors in init.log or kernel.log.

>  And what is a surefire way
> to find useful logs on opensolaris?

svcs -l will list the logs managed by SMF.  Anything that uses the system log 
will be listed in /etc/syslog.conf.  If you want something specific to an 
application - like Apache - you need to look at the application's own 
configuration files.  In Apache's case, you'll find those in /etc/apache on 
OpenSolaris, or /etc/apache2 on Solaris.

Really, Linux works in exactly the same way.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] opensolaris wallpaper

[Thorsten Manda]

Hey guys,

I'm searching for this wallpaper:

http://upload.wikimedia.org/wikipedia/commons/8/88/OpenSolaris0811.png

But i can't find it. Could someone please upload this Wallpaper for me or give 
me a link?

Thx,
bye
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] unable to install netbeans in os2008.11

[solarg]

hello all,
i've an os2008.11 server, and in a zone, i'm trying to install 
netbeans.The install script is netbeans-6.7.1-ml-solaris-x86.sh

and here, it is said that os2008.11 is supported:
http://www.netbeans.org/community/releases/67/relnotes.html#system_requirements

but the script failed with errors:
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
/test1/netbeans-6.7.1-ml-solaris-x86.sh[458]: [: argument expected
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
/test1/netbeans-6.7.1-ml-solaris-x86.sh[438]: [: argument expected
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
/test1/netbeans-6.7.1-ml-solaris-x86.sh[1064]: [: argument expected
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
/test1/netbeans-6.7.1-ml-solaris-x86.sh[1077]: [: argument expected
Can't exec "a2p": No such file or directory at /usr/bin/awk line 97.
Couldn't run a2p (wait status == -1) at /usr/bin/awk line 100.
/test1/netbeans-6.7.1-ml-solaris-x86.sh[1087]: [: argument expected
Configuring the installer...
Illegal character in prototype for main::removeFile : $fileName at 
/usr/bin/rm line 109.
main::getOptions() called too early to check prototype at /usr/bin/rm 
line 42.
main::processFile() called too early to check prototype at /usr/bin/rm 
line 48.

Can`t get disk block size


I verified that a2p is present on the system, and i don't understand the 
problem.


If anybody can help?

thanks in advance,

gerard


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

Re: [osol-discuss] AHCI errors after updating to dev b123

[Travis Tabbal]

snv_111b, 2009.06 release version. I also reverted to this version. This is the 
first time I've tried the dev releases, so I'm not sure if other versions have 
this issue or not.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] AHCI errors after updating to dev b123

[Dan Reiland]

What build were you running before the move to b123? I have a feeling this may 
be a regression introduced by: 
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6451665
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Where is SXCE b123?

[Alan Steinberg]

It should be updated in the next few days. -- Alan

Keith wrote:
I am still running sxce.How do I get to the iso? Usually, I access the 
link posting in the announcement forum.



Che Kristo wrote:
It is right now...do you mean iso or in the repository? I have 
accessed both for quite as while now.


On Thu, Sep 24, 2009 at 09:09, keithk > wrote:


Hi:
It's been 3 weeks since the release of b122. Is there any news when
b123 will be available for download?

Thanks,
Keith
--
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] Where is SXCE b123?

[Keith]

I am still running sxce.How do I get to the iso? Usually, I access the 
link posting in the announcement forum.



Che Kristo wrote:
It is right now...do you mean iso or in the repository? I have accessed 
both for quite as while now.


On Thu, Sep 24, 2009 at 09:09, keithk > wrote:


Hi:
It's been 3 weeks since the release of b122. Is there any news when
b123 will be available for download?

Thanks,
Keith
--
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] AHCI errors after updating to dev b123

[Travis Tabbal]

I am using the xVM kernel, so perhaps that's why I see it as well. I didn't try 
the regular one as I updated specifically for the xVM updates. Hopefully the 
next release fixes the issue. I rolled back to 2009.06 + whatever updates are 
available in that repo and everything is working fine again. I am also running 
the xVM kernel in this release. The hypervisor and dom0 are OpenSolaris, the 
only other OS installed is Ubuntu 9.04 in a domU, not currently running.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] SSH with public keys not working (not recognizing the key file)?

[Jonathan C. Bailey]

I found a "solution" of sorts. No idea why it works...

If I generate a new RSA key (ssh-keygen -t rsa) on either the Linux box or the 
OpenSolaris box, everything works fine.

No idea why, but I think I'll just cut my losses and re-generate keys..

-Jon

- Original Message -
From: "Jonathan C. Bailey" 
To: opensolaris-discuss@opensolaris.org
Sent: Wednesday, September 23, 2009 10:42:14 PM GMT -06:00 US/Canada Central
Subject: Re: [osol-discuss] SSH with public keys not working (not recognizing 
the key file)?

Hmmm... Figured that...

BTW, I tried the same keys (without the "command" stuff - just plain keys) on 
an unprivileged user and got the same thing. I built a key with ssh-keygen -t 
rsa on my Solaris box, copied it to the Linux client machine, and logged in as 
my unprivileged test user and as rsyncbackup without problem. I checked the 
problem keys with ssh-vulnkey since they came from Ubuntu systems, but they are 
marked as not blacklisted, so I'm lost again. Guess it's off to the security 
list...

-Jon

- Original Message -
From: "Mike Gerdts" 
To: "Jonathan C. Bailey" 
Cc: opensolaris-discuss@opensolaris.org
Sent: Wednesday, September 23, 2009 8:39:07 PM GMT -05:00 Colombia
Subject: Re: [osol-discuss] SSH with public keys not working (not recognizing  
the key file)?

On Wed, Sep 23, 2009 at 8:31 PM, Jonathan C. Bailey
 wrote:
> / and /home have correct permissions. rsyncbackup is another UID 0 user 
> (don't ask - it's worked fine on other platforms). All the SSH related 
> permissions seem fine too. I've also tried authorized_keys and 
> authorized_keys2. I've copied the same keys to root and it still works.

Solaris ssh is a hybrid of OpenSSH and Solarisisms.  Your
configuration may be tripping over a Solarisism.  Perhaps leading with
this at security-discuss will get the attention of someone more
familiar with the details of the differences.

They response will probably include something like:

Why not use a non-UID 0 account with RBAC and have the following in
authorized_keys?

command="/usr/bin/pfexec /backup/validate-rsync ntso" ssh-rsa KEY_TEXT
rsyncbac...@ntso


>
> BTW, I *did* turn root into a real user and added the 'PermitRootLogin yes' 
> line to sshd_config.
>
> -Jon
>
> - Original Message -
> From: "Mike Gerdts" 
> To: "Jonathan C. Bailey" 
> Sent: Wednesday, September 23, 2009 8:25:20 PM GMT -05:00 Colombia
> Subject: Re: [osol-discuss] SSH with public keys not working (not recognizing 
>  the key file)?
>
> On Wed, Sep 23, 2009 at 7:13 PM, Jonathan C. Bailey
>  wrote:
>> /home/rsyncbackup is 700
>> /home/rsyncbackup/.ssh is 700
>> /home/rsyncbackup/.ssh/authorized_keys2 is 600
>
> I assume that the user rsyncbackup is also the owner of all of those.
>
> (grasping at straws a bit...)
>
> And how about / and /home?  They should be writable by only root.
>
> sshd is also picky about permissions on the path to the sshd_confg
> file.  Check the permissions on /etc, /etc/ssh, and
> /etc/ssh/sshd_config.
>
>>
>> Also removed the "command" option from the key (so it started with ssh-rsa), 
>> and no difference.. Same problem... Here's the server side of that exchange:
>> debug1: userauth-request for user rsyncbackup service ssh-connection method 
>> publickey
>> debug1: attempt 1 initial attempt 0 failures 1 initial failures 0
>> debug2: input_userauth_request: try method publickey
>> debug1: test whether pkalg/pkblob are acceptable
>> debug1: temporarily_use_uid: 0/0 (e=0/0)
>> debug1: trying public key file /home/rsyncbackup/.ssh/authorized_keys
>> debug1: restore_uid: 0/0
>> debug1: temporarily_use_uid: 0/0 (e=0/0)
>> debug1: trying public key file /home/rsyncbackup/.ssh/authorized_keys2
>
> I see here that it is looking at authorized_keys and authorized_keys2.
>  Which file did you add it to?  What happens if you try the other?
>
>> debug3: secure_filename: checking '/home/rsyncbackup/.ssh'
>> debug3: secure_filename: checking '/home/rsyncbackup'
>> debug3: secure_filename: terminating check at '/home/rsyncbackup'
>> debug1: restore_uid: 0/0
>> debug2: key not found
>> debug2: userauth_pubkey: authenticated 0 pkalg ssh-rsa
>> Failed publickey for rsyncbackup from 10.243.193.3 port 52043 ssh2
>
> I seriously doubt this is your problem, but usernames > 8 characters
> long are not supported.
>
>>
>>
>> -Jon
>>
>> - Original Message -
>> From: "Mike Gerdts" 
>> To: "Jonathan C. Bailey" 
>> Cc: "opensolaris-discuss" 
>> Sent: Wednesday, September 23, 2009 6:57:16 PM GMT -05:00 Colombia
>> Subject: Re: [osol-discuss] SSH with public keys not working (not 
>> recognizing  the key file)?
>>
>> On Wed, Sep 23, 2009 at 6:31 PM, Jonathan C. Bailey
>>  wrote:
>>> Everything is on one line.. Actually, the authorized_keys file was copied 
>>> (working) from an Ubuntu 8.04 system.. Here's an example below. I've 
>>> removed the actual key text in this case to shorten up the line (but 
>>> everything *is* on one line)...
>>>
>>> command="/backup/validate-rsync nts

[osol-discuss] backup a zpool

[glidic anthony]

Hi all i search a method to backup my zpool with a linux,windows or third party 
software.
What are the solutions?
Thanks for answer.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] Issues installing httpd-2.2.12(Apache)

[camps support]

Has anyone had this problem before  I have attached all of the output:

Making all in srclib
Making all in apr
Making all in apr-util
Making all in pcre
Making all in os
Making all in unix
Making all in server
Making all in mpm
Making all in prefork

*** Error code 1
The following command caused the error:
if test -f exports.c; then \
if test -f export_files; then \
files=`cat export_files`; \
headers="`find $files -newer exports.c`"; \
if test -n "$headers"; then \
   echo Found newer headers. Will rebuild exports.c.; \
   echo rm -f exports.c export_files; \
   rm -f exports.c export_files; \
fi; \
else \
rm -f exports.c; \
fi; \
fi
make: Fatal error: Command failed for target `delete-exports'
Current working directory /export/home/httpd-2.2.12/server
*** Error code 1
The following command caused the error:
otarget=`echo all-recursive|sed s/-recursive//`; \
list='  mpm'; \
for i in $list; do \
if test -d "$i"; then \
target="$otarget"; \
echo "Making $target in $i"; \
if test "$i" = "."; then \
made_local=yes; \
target="local-$target"; \
fi; \
(cd $i && make $target) || exit 1; \
fi; \
done; \
if test "$otarget" = "all" && test -z 'delete-exports libmain.la  export_vars.h 
httpd.exp'; then \
made_local=yes; \
fi; \
if test "$made_local" != "yes"; then \
make "local-$otarget" || exit 1; \
fi
make: Fatal error: Command failed for target `all-recursive'
Current working directory /export/home/httpd-2.2.12/server
*** Error code 1
The following command caused the error:
otarget=`echo all-recursive|sed s/-recursive//`; \
list='  srclib os server modules support'; \
for i in $list; do \
if test -d "$i"; then \
target="$otarget"; \
echo "Making $target in $i"; \
if test "$i" = "."; then \
made_local=yes; \
target="local-$target"; \
fi; \
(cd $i && make $target) || exit 1; \
fi; \
done; \
if test "$otarget" = "all" && test -z 'httpd  '; then \
made_local=yes; \
fi; \
if test "$made_local" != "yes"; then \
make "local-$otarget" || exit 1; \
fi
make: Fatal error: Command failed for target `all-recursive'


[b]I also tried doing a gmake instead of a make and this is the result:[/b]

DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE
-I/export/home/httpd-2.2.12/srclib/pcre -I. -I/export/home/httpd-2.2.12/os/unix 
-I/export/home/httpd-2.2.12/server/mpm/prefork 
-I/export/home/httpd-2.2.12/modules/http 
-I/export/home/httpd-2.2.12/modules/filters 
-I/export/home/httpd-2.2.12/modules/proxy -I/export/home/httpd-2.2.12/include 
-I/export/home/httpd-2.2.12/modules/generators 
-I/export/home/httpd-2.2.12/modules/mappers 
-I/export/home/httpd-2.2.12/modules/database 
-I/export/home/httpd-2.2.12/srclib/apr/include 
-I/export/home/httpd-2.2.12/srclib/apr-util/include 
-I/export/home/httpd-2.2.12/modules/proxy/../generators 
-I/export/home/httpd-2.2.12/modules/ssl 
-I/export/home/httpd-2.2.12/modules/dav/main  -prefer-non-pic -static -c 
gen_test_char.c && touch gen_test_char.lo
/export/home/httpd-2.2.12/srclib/apr/libtool --silent --mode=link gcc -g -O2
-o gen_test_char  gen_test_char.lo util_debug.lo -lm
./gen_test_char > test_char.h
/export/home/httpd-2.2.12/srclib/apr/libtool --silent --mode=compile gcc -g -O2 
   -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE  
  -I/export/home/httpd-2.2.12/srclib/pcre -I. 
-I/export/home/httpd-2.2.12/os/unix 
-I/export/home/httpd-2.2.12/server/mpm/prefork 
-I/export/home/httpd-2.2.12/modules/http 
-I/export/home/httpd-2.2.12/modules/filters 
-I/export/home/httpd-2.2.12/modules/proxy -I/export/home/httpd-2.2.12/include 
-I/export/home/httpd-2.2.12/modules/generators 
-I/export/home/httpd-2.2.12/modules/mappers 
-I/export/home/httpd-2.2.12/modules/database 
-I/export/home/httpd-2.2.12/srclib/apr/include 
-I/export/home/httpd-2.2.12/srclib/apr-util/include 
-I/export/home/httpd-2.2.12/modules/proxy/../generators 
-I/export/home/httpd-2.2.12/modules/ssl 
-I/export/home/httpd-2.2.12/modules/dav/main  -prefer-non-pic -static -c 
config.c && touch config.lo
/export/home/httpd-2.2.12/srclib/apr/libtool --silent --mode=compile gcc -g -O2 
   -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE  
  -I/export/home/httpd-2.2.12/srclib/pcre -I. 
-I/export/home/httpd-2.2.12/os/unix 
-I/export/home/httpd-2.2.12/server/mpm/prefork 
-I/export/home/httpd-2.2.12/modules/http 
-I/export/home/httpd-2.2.12/modules/filters 
-I/export/home/httpd-2.2.12/modules/proxy -I/export/home/httpd-2.2.12/include 
-I/export/home/httpd-2.2.12/modules/generators 
-I/export/home/httpd-2.2.12/modules/mappers 
-I/export/home/httpd-2.2.12/modules/database 
-I/export/home/httpd-2.2.12/srclib/apr/include 
-I/export/home/httpd-2.2.12/srclib/apr-util/include 
-I/export/home/httpd-2.2.12/modules/proxy/

[osol-discuss] Enabling Remote GUI Login via XDMCP

[Chris]

I have a box running OpenSolaris 09.06 which I would like to run headless and 
access the desktop from a Mac (currently running OSX 10.5.8) on the same LAN.

This used to work under OS 08.05.  09.06 seems more secure and I'm struggling 
to locate all the appropriate settings to enable remote login. Specifically, I 
can't seem to get OpenSolaris to listen on port 177 for the xdmcp connection.

After searching around, I've made the following changes:
- /etc/X11/gdm/custom.conf
  add to [security] DisallowTCP=false
  add to [xdmcp] Enable=true
- enabled tcp wrappers
- enabled tcp-listen for x11
- set hosts.allow to ALL: 192.168. and hosts.deny to ALL: ALL

gdmsetup shows all the correct xdmcp settings.  but still port 177 refuses to 
open.

enabling tcp-listen for x11, did open port 6000.

Any help would be appreciated.
-- 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Where is SXCE b123?

[Che Kristo]

SXCE is EOL so I doubt we will see any further updates...
http://204.152.191.100/wiki/index.php/SXCE_EOL maybe one more if you're
lucky

On Thu, Sep 24, 2009 at 22:00, Keith  wrote:

> I am still running sxce.How do I get to the iso? Usually, I access the link
> posting in the announcement forum.
>
>
> Che Kristo wrote:
>
>> It is right now...do you mean iso or in the repository? I have accessed
>> both for quite as while now.
>>
>> On Thu, Sep 24, 2009 at 09:09, keithk > keithc...@gmail.com>> wrote:
>>
>>Hi:
>>It's been 3 weeks since the release of b122. Is there any news when
>>b123 will be available for download?
>>
>>Thanks,
>>Keith
>>--
>>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] Where is SXCE b123?

[Che Kristo]

It is right now...do you mean iso or in the repository? I have accessed both
for quite as while now.

On Thu, Sep 24, 2009 at 09:09, keithk  wrote:

> Hi:
> It's been 3 weeks since the release of b122. Is there any news when b123
> will be available for download?
>
> Thanks,
> Keith
> --
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] clarksfield opensolaris laptop

[Che Kristo]

Any chance that the next release of the OpenSolaris/Toshiba laptops could
include a model with the new quad core nehalem based chipsets?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org