[osol-discuss] PLEASE READ - Annual Elections/Meeting

2010-02-26 Thread Valerie Bubb Fenwick
Greetings! The OpenSolaris Elections are nearly here. The OGB has been working hard to get ready for them and we hope you'll be able to participate. Please read this entire email carefully. If you have questions send them to ogb-disc...@opensolaris.org or ask during the Members Meeting. This

Re: [osol-discuss] image-update hanging on ioctl call

2010-02-26 Thread Shawn Walker
[moving to pkg-discuss] On 02/25/10 12:09 PM, Kristin Amundsen-Cubanski wrote: Hello, I have searched all over and I cannot find any reference to an error like this. We're trying to update our opensolaris server and it is getting stuck on either indexing packages or optimizing the index in an

[osol-discuss] using digest with stdin command line input.

2010-02-26 Thread Morten Gulbrandsen
Please how can I with bash read a string for hashing with digest, from stdin? bash-3.00$ digest -v -a md5 This is an input string. digest: can not open input file This is an input string. I did observe that the redirect operators are not displayed in the preview, so I attach my example

[osol-discuss] Gnome-terminal broken after update from build 111b to build 133

2010-02-26 Thread Christian PĂ©lissier
On a DELL LATITUDE D630 and after upgrading from 111b to 133 gnome terminal is broken. When booting build 133 GDM is OK. After login it's impossible to work with gnome-terminal. No echo, No line feed stty sane CTRL-J give echo again Message readline: warning: turning off output flushing is

Re: [osol-discuss] using digest with stdin command line input.

2010-02-26 Thread Brian Ruthven - Sun UK
You were so close :-( $ echo This is an input string | digest -v -a md5 md5 35e1332bf506d35c7c9f1c2b0cb39d4e Brian Morten Gulbrandsen wrote: Please how can I with bash read a string for hashing with digest, from stdin? bash-3.00$ digest -v -a md5 This is an input string. digest: can

Re: [osol-discuss] Gnome-terminal broken after update from build 111b to build 133

2010-02-26 Thread Alan Burlison
On 26/02/2010 13:15, Christian PĂ©lissier wrote: On a DELL LATITUDE D630 and after upgrading from 111b to 133 gnome terminal is broken. When booting build 133 GDM is OK. After login it's impossible to work with gnome-terminal. Hit that myself, it's in the release notes: 2380 image-update

[osol-discuss] OS 2009.06: QEMU/Crossbow combination.

2010-02-26 Thread Karel Gardas
Hello, I wonder if anybody here attempted to get Qemu working with Crossbow provided virtual NIC instead of using Qemu's TUN/TAP device. Yes, I can use VBox instead of Qemu, but VBox does not allow me to set more virtual CPUs than 2x real CPUs of the target machine and I would like to use Qemu

Re: [osol-discuss] image-update hanging on ioctl call

2010-02-26 Thread Bruno Damour
On 02/25/10 11:18 PM, Shawn Walker wrote: [moving to pkg-discuss] On 02/25/10 12:09 PM, Kristin Amundsen-Cubanski wrote: Hello, I have searched all over and I cannot find any reference to an error like this. We're trying to update our opensolaris server and it is getting stuck on either

[osol-discuss] Gnome Performance Monitor in XVNC session issue snv_133

2010-02-26 Thread Tonmaus
When I am logged on as user in local session and in xvnc session I can not open Gnome Performance Monitor. The workaround is to log off on the local session. Can anybody reproduce? Regards, Tonmaus -- This message posted from opensolaris.org ___

Re: [osol-discuss] COMSTAR iSCSI / CIFS performance not stable

2010-02-26 Thread Vik
Some would say it is probably a bad idea, but this helped me. in /etc/system set this line: set zfs:zfs_nocacheflush = 1 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

[osol-discuss] Bordeaux 2.0.2 for Solaris and OpenSolaris Released

2010-02-26 Thread Tom Wickline
The Bordeaux Technology Group released Bordeaux 2.0.2 for Solaris today. Bordeaux 2.0.2 is a maintenance release that fixes a critical bug with sound support. Customers who need sound support are advised to upgrade to this newer release. This release has been tested on OpenSolaris 2009.06 as

Re: [osol-discuss] opensolaris on slashdot

2010-02-26 Thread W. Wayne Liauh
snip My take is this, I read all the 300+ messages posted at Slashdot, and found it amazing that one could surmise what Oracle may or may not do wrt one of its most important assets without seriously entering Chairman Larry into the equation. (As we all know, Chairman Larry owns about one

Re: [osol-discuss] Software is free. Service is not. Mike Rocha and Tim Chou.

2010-02-26 Thread Marion Hakanson
Apologies for reviving a 2-week-old thread, but developments continue. For example, our non-contract Solaris-10 systems using updatemanager just got a couple new security patches this week kgund...@teamcool.net said: This will be the undoing of Solaris. One reason Sun got into such bad

[osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Bill Shannon
Why am I seeing different information from Package Manager than what I see when browsing pkg.opensolaris.org/dev? (Yes, Package Manager is pointing at the dev repository.) For instance, if I look at SUNWgmake in Package Manager, I see version 3.81 (Build 5.11-0.133). Browsing the repo I see:

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Shawn Walker
On 02/26/10 06:20 PM, Bill Shannon wrote: Why am I seeing different information from Package Manager than what I see when browsing pkg.opensolaris.org/dev? (Yes, Package Manager is pointing at the dev repository.) For instance, if I look at SUNWgmake in Package Manager, I see version 3.81

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Bill Shannon
Shawn Walker wrote on 02/26/10 04:28 PM: On 02/26/10 06:20 PM, Bill Shannon wrote: Why am I seeing different information from Package Manager than what I see when browsing pkg.opensolaris.org/dev? (Yes, Package Manager is pointing at the dev repository.) For instance, if I look at SUNWgmake in

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Shawn Walker
On 02/26/10 06:49 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 04:28 PM: On 02/26/10 06:20 PM, Bill Shannon wrote: Why am I seeing different information from Package Manager than what I see when browsing pkg.opensolaris.org/dev? (Yes, Package Manager is pointing at the dev

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Shawn Walker
On 02/26/10 07:30 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 05:05 PM: On 02/26/10 06:49 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 04:28 PM: On 02/26/10 06:20 PM, Bill Shannon wrote: Why am I seeing different information from Package Manager than what I see when

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Bill Shannon
Shawn Walker wrote on 02/26/2010 05:44 PM: On 02/26/10 07:30 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 05:05 PM: On 02/26/10 06:49 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 04:28 PM: On 02/26/10 06:20 PM, Bill Shannon wrote: Why am I seeing different information

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Shawn Walker
On 02/26/10 08:15 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/2010 05:44 PM: On 02/26/10 07:30 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 05:05 PM: On 02/26/10 06:49 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 04:28 PM: On 02/26/10 06:20 PM, Bill Shannon

Re: [osol-discuss] Package Manager vs. package repo browser

2010-02-26 Thread Bill Shannon
Shawn Walker wrote on 02/26/2010 06:25 PM: On 02/26/10 08:15 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/2010 05:44 PM: On 02/26/10 07:30 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 05:05 PM: On 02/26/10 06:49 PM, Bill Shannon wrote: Shawn Walker wrote on 02/26/10 04:28

[osol-discuss] very long wait in the end of pkg install

2010-02-26 Thread Bruno Damour
Hello, I ran pkg install with truss, in the hope of discovering why it takes so long to complete, especially AFTER it has reported that every thing is installed. I ran into this (for me) mysterious result : # truss -o pkg.log -D pkg install diagnostic/wireshark