[osol-discuss] Fwd: Added tag onnv_80 for changeset 7066e93e6b89

[Cyril Plisko]

There is no dedicated ON list, so sending it to opensolaris-discuss.

Am I the only one who feels uncomfortable when ONNV notification
comes from <[EMAIL PROTECTED]> ? Nothing personal against
the owner of that mail address. Just think that at this point there is
no way for someone outside of Sun to generate the SCM notification
mail on ON repository...

Probably a bug in the script somewhere...


-- Forwarded message --
From:  <[EMAIL PROTECTED]>
Date: Dec 11, 2007 9:13 AM
Subject: Added tag onnv_80 for changeset 7066e93e6b89
To: [EMAIL PROTECTED]


Author: [EMAIL PROTECTED]
Repository: /hg/onnv/onnv-gate
Latest revision: f4e076788720b0955398a3a7021ce6d3e434aee2
Total changesets: 1
Log message:
Added tag onnv_80 for changeset 7066e93e6b89

Files:
update: .hgtags
___
onnv-notify mailing list
[EMAIL PROTECTED]
http://mail.opensolaris.org/mailman/listinfo/onnv-notify



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

Re: [osol-discuss] Cisco VPN Client for Solaris x86, anyone?

[Dan McDonald]

Try not to quote back the whole post next time...

> So would this solution be compatible with the
> existing Cisco solutions that many companies have?

Nope, and I thought the protocol explanation would've made that point obvious.

BTW, that complete incompatibility with anything else out there was another 
reason to not open-source it immediately.  People would be like, "Why?"

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

Re: [osol-discuss] Cisco VPN Client for Solaris x86, anyone?

[Ché Kristo]

> Hello!
> 
> I don't read this alias normally, but I was pointed
> to it by folks.  I'm also using JIVE to read this one
> instead of my normal e-mail.
> 
> Punchin started its life as a test-tool for Solaris
> IPsec and IKE during the S9 bringup of IKE(v1).
> Punchin is different than other remote-access
> solutions because it doesn't augment IKE to perform
> user authentication and internal-address deployment.
> If one were to put the all-seeing packet sniffer
> (with a small amount of client and server
> observability, too) between a punchin client and
>  server, you'd see something like this:
> 
> * IKE Phase I (self-signed certificates)
> * IKE QM for diagnostic ping
> * ESP-protected ping
> * IKE QM for UDP port 2112 for setup (maybe TCP
> coming soon)
> * ESP-protected UDP port 2112 exchange
>  - Request
> - Challenge (e.g. "Password" or Token-card
>  challenge)
> - Response
>  - Failure or Success(with internal IP address)
> (client then rewhacks routing tables and plumbs an
> ip.tun0, server plumbs an ip.tunN)
> * IKE QM for Tunnel Mode,
> internal-local==previously-asssigned,
>  internal-remote==default
>* ESP-protected internal traffic.
> nce we got NAT-Traversal working and we discovered
> cisco wasn't going to do an Sol x86 client, punchin
> took on a life of its own within Sun.  We've also
> found bugs in other IPsec implementations while
> attempting to port punchin to those platforms.
> 
> Punchin's nice because it's just a set of scripts and
> one binary application (two if you're using MacOS X)
> that control the OS's built-in IPsec functionality.
> Most "VPN clients" require kernel modules that have
> varying levels of stability or rely on undocumented
> or unstable interfaces.  You'll never get a kernel
> panic with punchin unless your OS is broken (which
> is why punchin is such a nice test tool for
>  Solaris/OpenSolaris).
> 
> We haven't open-sourced it mostly because it's not
> Team IPsec's day jobs.  One idea we've been kicking
> around is putting the source in /usr/demo ala. the
> DTrace or MDB examples.  Nothing we do in punchin is
> encumbered (even though our IKEv1 is encumbered
> w.r.t. source only), so it's just a matter of time
> and resources, something we're short on with Labelled
> IPsec and IKEv2 + RFC 430x coming up.
> 
> BTW, our IKEv2 will be open-source, and if you hang
> out on networking- or security- discuss we'll have
> something to say there soon.  Also, IKEv2 has the
> IKEv1 hacks baked-into the spec, so punchin's
> functionality could (and probably should) be subsumed
> by a decent IKEv2 implementation.
> 
> Does that answer everyone's questions?
> 
> Dan McD.

So would this solution be compatible with the existing Cisco solutions that 
many companies have?
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] PulseAudio

[Ignacio Marambio Catán]

He mentioned that the feature set would be significantly reduced since
> OSS (when integrated) won't nearly provide as much capability as Alsa does on
> Linux, but confirmed it does work fine on Solaris already.

what capabilities from alsa are missing in oss?

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

Re: [osol-discuss] PulseAudio

[Glynn Foster]

Victor wrote:
> I have a question... Is there any plan to integrate PulseAudio as the sound
> server in Solaris?
> 
> I have been searching around forums and mailing lists and still didn't find
> anything about this... but it's becoming kind of the standard in the big
> linux distros (and GNOME) and it might be useful for solaris as well..

I talked to Lennart during the week, and he's keen to see PulseAudio in Solaris
as well. He mentioned that the feature set would be significantly reduced since
OSS (when integrated) won't nearly provide as much capability as Alsa does on
Linux, but confirmed it does work fine on Solaris already.


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

Re: [osol-discuss] OpenSolaris with iSCSI Luns and IPMP 3 x "1 Gbe" eth SAN . Is it sensib

[John Brewer]

You could take a look at Sun Trunking 1.3, but Sun Trunking 1.3, like any 
server trunking software, load balances the outgoing traffic, not the incoming 
packets. Trunking 1.3 software relies on the link partner (switch or server) to 
load balance the incoming packets.

1. Download the binary. http://www.sun.com/download/products.xml?id=42e56519
2. Search the Installation Guide 
http://docs.sun.com/app/docs/doc/817-3374-10?l=en&q=sun+trunking+1.3
3. Follow the installation steps stated in page 46 
4. Install the appropriate patches are referenced in the product for only 
Production version of Solaris i.e 10u4 or only use the latest OpenSolaris.
5. Set local-mac-address as root on the command-line for sparc eeprom 
local-mac-address?=true
6. Reboot

So one workaround I have only been able to use for services entries. i.e oracle 
tnsnames, or nfs, for the inbound using standard IPMP with active - active and 
two virtual interfaces hostnames and IP's defined one for each ipmp-group so 
then define each Virtual Interfaces for your 10 and 20 IP address in the hosts 
and dns with repect to each physical IP and hostname, then for your 10 and 20 
virtual interface hostnames share the entries i.e hostnames VirtInt10 and 
VirtInt20 your dfstab and set the automounter to make use of both virtual 
interface hostnames and set the time out to allow fail over to work in a timely 
manner i.e automounter, I am not sure of a ISCSI client can make use of a 
second known virtual and has a time out value for hostname or not in using a 
inbound traffic? maybe a RFE could be added, if technically is sound!
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Build 78 ,79

[Ben Middleton]

Also awaiting 78 for a Wireless Network fix...

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

Re: [osol-discuss] Cisco VPN Client for Solaris x86, anyone?

[Dan McDonald]

Hello!

I don't read this alias normally, but I was pointed to it by folks.  I'm also 
using JIVE to read this one instead of my normal e-mail.

Punchin started its life as a test-tool for Solaris IPsec and IKE during the S9 
bringup of IKE(v1).  Punchin is different than other remote-access solutions 
because it doesn't augment IKE to perform user authentication and 
internal-address deployment.  If one were to put the all-seeing packet sniffer 
(with a small amount of client and server observability, too) between a punchin 
client and server, you'd see something like this:

* IKE Phase I (self-signed certificates)
* IKE QM for diagnostic ping
* ESP-protected ping
* IKE QM for UDP port 2112 for setup (maybe TCP coming soon)
* ESP-protected UDP port 2112 exchange
 - Request
 - Challenge (e.g. "Password" or Token-card challenge)
 - Response
 - Failure or Success(with internal IP address)
(client then rewhacks routing tables and plumbs an ip.tun0, server plumbs 
an ip.tunN)
* IKE QM for Tunnel Mode, internal-local==previously-asssigned, 
internal-remote==default
* ESP-protected internal traffic.

Once we got NAT-Traversal working and we discovered cisco wasn't going to do an 
Sol x86 client, punchin took on a life of its own within Sun.  We've also found 
bugs in other IPsec implementations while attempting to port punchin to those 
platforms.

Punchin's nice because it's just a set of scripts and one binary application 
(two if you're using MacOS X) that control the OS's built-in IPsec 
functionality.  Most "VPN clients" require kernel modules that have varying 
levels of stability or rely on undocumented or unstable interfaces.  You'll 
never get a kernel panic with punchin unless your OS is broken (which is why 
punchin is such a nice test tool for Solaris/OpenSolaris).

We haven't open-sourced it mostly because it's not Team IPsec's day jobs.  One 
idea we've been kicking around is putting the source in /usr/demo ala. the 
DTrace or MDB examples.  Nothing we do in punchin is encumbered (even though 
our IKEv1 is encumbered w.r.t. source only), so it's just a matter of time and 
resources, something we're short on with Labelled IPsec and IKEv2 + RFC 430x 
coming up.

BTW, our IKEv2 will be open-source, and if you hang out on networking- or 
security- discuss we'll have something to say there soon.  Also, IKEv2 has the 
IKEv1 hacks baked-into the spec, so punchin's functionality could (and probably 
should) be subsumed by a decent IKEv2 implementation.

Does that answer everyone's questions?

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

Re: [osol-discuss] OpenSolaris with iSCSI Luns and IPMP 3 x "1 Gbe" eth SAN . Is it sensib

[chandan maddanna]

First of all Thanks to all, i am getting so much valuable Information here.

secondly, as of now, I am thinking That on the transmittion end, where i am
concerned with outbound load spreading, i will use IPMP group.

Now as james said, i am thinking if there are three interfaces in the ipmp
group, i will use address on one and other two i will mark, 0.0.0.0 and make
them "up". So it does efficient outbound load spreading, in Round Robin
Type.

And for clients, at the receiving end, what i am planning to use aggregated
links, Something like this :

# dladm create-aggr -d e1000g0 -d e1000g1 -d e1000g2 1
# ifconfig aggr1 plumb 192.168.10.210  up

So now i expect   "aggr1"   to give me an *INBOUND* bandwidth of atleast 2.5to
2.6 GBPS as all three ( VIZ e1000g0 e1000g1 and e1000g2 are GBE cards  and
very well supported with Solaris )

( Please *NOTE* : that i don't need outbound and inbound load spreading on
the same machine )


And now you all may be thinking why i am concerned about this performance
part so much, The reason is, i want to implement a iSCSI SAN , which almost
matches or at least stands something like 85 % Performance of usual Fabric
SAN implementations.

So you see,  I want outbound Load Spreading and performance for "iSCSI
Targets" and inbound Load spreading and performance for "iSCSI Initiators"


i am drawing a detailed architecture of how i want to proceed, and once that
is done , I will DEFINITELY share with you guys, so that i may get valuable
inputs and guidance for you "guru's" here.

BUt still there is one problem with iSCSI SAN Replacement, our iSCSI SAN
implementation with opensolaris does not support PGR, ( persistent SCSI
Reservations ) , though this should not be a problem in normal cases, But it
is definitely a problem, if some applications makes explicit usage of this
feature ( ex : Sun Cluster )

nice discussing with you people, I will keep you all updated.

-- Chandan Maddanna


On Dec 10, 2007 7:20 PM, James Carlson <[EMAIL PROTECTED]> wrote:

> Ceri Davies writes:
> > On Sat, Dec 08, 2007 at 11:53:27PM -0800, Chandan Maddanna wrote:
> > > Guys to be more clear, look at the diagram below, and tell me how to
> get a single load spread 2 Gbps link  with IP Multi Pathing on Solaris 10 ?
> > >
> > > Note : Please see Image Below .
> > >
> > >
> > > http://img514.imageshack.us/img514/8928/ipmpmultipathinghz4.gif";> 
> > >
> > > Now i don't want two public ip , what i need is just one IP which
> utilizes the bandwidth provided by both the nic's. Can anyone help me out
> guys .
> > >
> > > meaning i want active-active configuration and i should use one ip at
> client side and it should make use of the bandwidth of both the NIC's .. can
> this be done and how, just outbound load spreading is enough for me, as
> there is no much in bound load generated, except few scsi commands through
> ip and stuff..
> >
> > You can't; there is no inbound load-spreaing with IPMP.
>
> That's not quite true.
>
> IPMP's inbound load spreading makes use of multiple data addresses in
> a group.  When we make outbound connections to multiple peers and
> there are multiple data addresses, we'll intentionally round-robin
> select among those addresses to use as source addresses, each with a
> separate MAC address.  That allows the return traffic to be spread
> among the available links.
>
> The other part of the picture is DNS.  For spreading of inbound
> connections, you should insert all of the data addresses as IN A
> records for a single name, and configure your server so that it does
> round-robin responses.  (If the peers are Solaris, disabling or
> configuring nscd may be necessary.)
>
> As for outbound load spreading alone, as long as interfaces are marked
> "up" in the group, they'll be used.  They don't all have to have
> addresses, and interfaces that are "up" but with 0.0.0.0 address will
> be used for outbound load spreading using source (data) addresses from
> other interfaces.
>
> --
> James Carlson, Solaris Networking  <[EMAIL PROTECTED]>
> Sun Microsystems / 35 Network Drive71.232W   Vox +1 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Cisco VPN Client for Solaris x86, anyone?

[Joerg Schilling]

John Tracy <[EMAIL PROTECTED]> wrote:

> If something else can get the job done well, I'm not averse to using it. But 
> it appears at moment I have no way to access or otherwise using punchin. 
> Furthermore, does it work with the existing Cisco based VPN server 
> deployments that are already in use in many of Sun's customers' shops?

Just to give some additional information:

For Solaris 9 there is Cisco VPN-5000

This does not work anymore for Solaris 10 or newer.

I would expect that you need a special Punchin server
at the "dial in" side.

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED](uni)  
   [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] November 2007 OpenSolaris Community Newsletter

[Linda Bernal]

Here's the November issue of the OpenSolaris Community Newsletter:
http://www.opensolaris.org/os/community/advocacy/newsletter/nov/

Thanks to all for your contributions.  If you have any content you would 
like to submit for December's newsletter, please send them to 
[EMAIL PROTECTED]


-Linda
begin:vcard
fn:Linda  Bernal
n:Bernal;Linda 
org:OPG;Kernel Networking
adr;dom:;;17 Network Circle;Menlo Park;CA;94025
email;internet:[EMAIL PROTECTED]
title:Program Manager 
tel;work:650-786-6165
tel;fax:650-745-3307
version:2.1
end:vcard

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

Re: [osol-discuss] Cisco VPN Client for Solaris x86, anyone?

[John Tracy]

If something else can get the job done well, I'm not averse to using it. But it 
appears at moment I have no way to access or otherwise using punchin. 
Furthermore, does it work with the existing Cisco based VPN server deployments 
that are already in use in many of Sun's customers' shops?

--I'm most happy to try it out if it would be beneficial/appreciated--

Thanks!
John
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sound problems in SXCE77?

[Patrick Ale]

On 12/10/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
>
>
>
> On 12/10/07, Brian Cameron <[EMAIL PROTECTED]> wrote:
> >
> > Patrick:
> >
> > > This is a regression then, in my opinion. Prior to SXCE77 I never had
> > to
> > > rebuild anything.
>
>
> [snip]
>
> Hi Brian :)
>
>

And again, hi :P

So, checking out the repository again as we speak, and I can confirm
something did go wrong yesterday. Right now I see spec files in the 'top'
directory of my svn checkout, something I didn't see yesterday. Yesterday I
only saw spec files inside directories residing in the 'top' directory.

I'll let you know how things go when I am done building.

Cheers,

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

Re: [osol-discuss] Sound problems in SXCE77?

[Patrick Ale]

On 12/10/07, Brian Cameron <[EMAIL PROTECTED]> wrote:
>
> Patrick:
>
> > This is a regression then, in my opinion. Prior to SXCE77 I never had to
> > rebuild anything.


[snip]

Hi Brian :)

As far as I can tell I am using the same OSS modules 4.00, but I am not sure
about the minor release version so I'll assume this version is different
then.
Regarding building JDS, what you describe looks exactly like what I tried
yesterday evening, with the addition that I did a pkgtool uninstall-pkgs
*.spec in the base-spec directory after checking out the svn repository.

I dunno, maybe something went horribly wrong during the checkout which
rendered me with a local repository I shouldn't have, I am gonna retry it as
we speak :)

Thanks for your explanations and time,

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

Re: [osol-discuss] Sound problems in SXCE77?

[Brian Cameron]

Patrick:

> This is a regression then, in my opinion. Prior to SXCE77 I never had to 
> rebuild anything.

It should work fine without needing to rebuild anything.  However, if
you don't rebuild SUNWgnome-audio and SUNWgnome-media then you are using
the SADA shim.  This shim allows programs that use the old Sun Audio
interfaces to redirect properly to use OSS.

I am aware that some users have complained that bugs in the SADA shim
cause audio problems on some systems.  If you are using the same
version of the OSS binaries that worked before, then you are probably
not running into these problems.

However, trying to rebuild SUNWgnome-audio and SUNWgnome-media to get
full OSS support is something you can try as a possible workaround.

> Not to mention that jds doesn't build from source due to all kind of 
> errors in the spec files (invalid boolean errors from the top of my 
> head) and the documentation not being confirming the 'real world'. 
> (During svn checkout you get spec files in directories like 
> exta,base-specs,closed where the documentation tells you to do pkgtool 
> build -v *.spec).

I don't have any problems uninstalling and rebuilding these two spec
files on my Nevada build 72 system with vermillion 80 running on it.

What you need to do is:

1) Run ". /opt/jdsbld/bin/env.sh".

If this command doesn't work, then you probably need to install the
CBE.  Note the steps in the URL I provided before.

2) Run "pkgtool uninstall-pkgs SUWNgnome-audio.spec
SUNWgnome-media.spec" in the top level spec-files directory.

3) Run "pkgtool --download build SUNWgnome-audio.spec
SUNWgnome-media.spec" in the same directory.  This takes about an
hour on my machine.  Mostly because rebuilding the gtk-docs is a bit
slow.  Perhaps your computer is faster since my machine is a bit old.

That should be it.  If the build fails after doing this, then you might
not have the right Sun Studio compiler installed on your system?  That
works for me anyway.


Brian

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

Re: [osol-discuss] Sound problems in SXCE77?

[Patrick Ale]

On Dec 10, 2007 7:17 PM, Brian Cameron <[EMAIL PROTECTED]> wrote:

> Patrick:
>
> Note that for GNOME/GStreamer to work best with OSS, you need to rebuild
> the SUNWgnome-audio* and SUNWgnome-media* packages after installing the
> OSS packages.  To do this you should use the CBE, which you can get
> from the OpenSolaris website:
>

This is a regression then, in my opinion. Prior to SXCE77 I never had to
rebuild anything.
Not to mention that jds doesn't build from source due to all kind of errors
in the spec files (invalid boolean errors from the top of my head) and the
documentation not being confirming the 'real world'. (During svn checkout
you get spec files in directories like exta,base-specs,closed where the
documentation tells you to do pkgtool build -v *.spec).


Cheers,

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

Re: [osol-discuss] Sound problems in SXCE77?

[Brian Cameron]

Patrick:

Note that for GNOME/GStreamer to work best with OSS, you need to rebuild
the SUNWgnome-audio* and SUNWgnome-media* packages after installing the
OSS packages.  To do this you should use the CBE, which you can get
from the OpenSolaris website:

http://www.opensolaris.org/os/project/jds/contributing/building/

For example, rebuilding these packages, ensures that the GStreamer
OSS plugins are built.

Once OSS actually integrates with Solaris, then we will build these
plugins as a part of Solaris, but until then you will need to rebuild
these packages by hand to get full OSS support in
Nevada/OpenSolaris/etc.

Brian


> Just wondering, is anyone experiencing sound problems under SXCE77 where 
> they didn't before?
> I have an Intel HDAUDIO chipset in my laptop. I installed the oss 
> drivers from opensound.com  (as I always do), 
> osstest spews out sound but things like Rhythmbox or the volume control 
> tell me the correct gstreamer plugins or sounddevice arent installed.
> 
> Does anyone here recognize this behaviour?
> 
> Cheers,
> 
> Patrick
> 
> 
> 
> 
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org

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

Re: [osol-discuss] How to enable XDM?

[Brian Cameron]

Patrick Blaas wrote:
> What i would like to do is keep using the cde-login and get access with XDMCP 
> to the dtlogin. That doesn't seem to work in b76 x86. Changing to gdm is not 
> a fix, it's a workarround imho.
> 
> This worked out-of-the-box on previous solaris versions.
> Anyone know what changed here?

Does it make a difference if you configure the Xserver to allow TCP?
You can enable this by running the following command:

svccfg -s application/x11/x11-server setprop options/tcp_listen=true

I understand that the default setting of this properly changed from
true to false in a recent build, so this change might be causing your
problem.

Note that this effects both CDE login and GDM equally.  You can not
use XDMCP with either login program without first setting the tcp_listen
property to true.

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

[osol-discuss] Build 78 ,79

[Mike DeMarco]

Anxiously awaiting build 79 to resolve my Gnome problems

Any word on the delay of 78 and if it will delay 79?

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

Re: [osol-discuss] PulseAudio

[Shawn Walker]

On Dec 10, 2007 10:26 AM, Dick Davies <[EMAIL PROTECTED]> wrote:
> On Dec 10, 2007 3:55 PM, UNIX admin <[EMAIL PROTECTED]> wrote:
> > > I have a question... Is there any plan to integrate
> > > PulseAudio as the sound server in Solaris?
>
> > I suggest to contact the developers of PulseAudio to ask them if they
> > have any plans on porting this software to Solaris.
>
> That's not the same as integrating it.

Until it has adoption and stability I'm not sure it's worth spending
the work integrating. Part of the reason so many GNU/Linux
distributions use Audio Servers is because most of their sound drivers
lack support for multiple applications to output audio at the same
time. Once we get OSS integrated, not only will we have better sound
support than most GNU/Linux, but one of the reasons they use sound
servers won't apply to us.

Unlike the GNU/Linux world, integration tends to imply a certain level
of support and commitment in our world. In relation to that, I am
unable to find any documentation regarding their commitment to
interface stability, etc. PulseAudio also seems redundant in the face
of OSS which provides many of the same pieces of functionality. About
the only advantage I can see to having it available is its possible
adoption by future project and its network audio support.

Finally, I have serious concerns about its affects on audio
performance after reading the FAQ where it talks about audio buffer
fragmentation, changing the server to real-time priority scheduling to
alleviate audio issues, etc. I would rather see OSS enhanced for the
per-application functionality that it adds and use that without adding
another layer of indirection on top of the ridiculous amount we
already have today for some applications for audio.

For the record, Solaris is listed as a supported platform:
http://www.pulseaudio.org/wiki/AboutPulseAudio

-- 
Shawn Walker, Software and Systems Analyst
http://binarycrusader.blogspot.com/

"To err is human -- and to blame it on a computer is even more so." -
Robert Orben
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] PulseAudio

[Dick Davies]

On Dec 10, 2007 3:55 PM, UNIX admin <[EMAIL PROTECTED]> wrote:
> > I have a question... Is there any plan to integrate
> > PulseAudio as the sound server in Solaris?

> I suggest to contact the developers of PulseAudio to ask them if they
> have any plans on porting this software to Solaris.

That's not the same as integrating it.

-- 
Rasputnik :: Jack of All Trades - Master of Nuns
http://number9.hellooperator.net/
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] PulseAudio

[Cyril Plisko]

On Dec 10, 2007 5:55 PM, UNIX admin <[EMAIL PROTECTED]> wrote:
> Likewise, perhaps you are asking at a wrong place.  I suggest to contact the 
> developers of PulseAudio to ask them if they have any plans on porting this 
> software to Solaris.
>
> Perhaps you might be able to convince them that Solaris is gratis and runs 
> really well and fast on their PCs, and that there is no reason for them to 
> really say "we don't have Solaris to test on".

>From PulseAudio home page ( http://pulseaudio.org )

"PulseAudio has been tested on Linux, Solaris, FreeBSD, Windows 2000
and Windows XP."

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

Re: [osol-discuss] PulseAudio

[UNIX admin]

> I have a question... Is there any plan to integrate
> PulseAudio as the sound server in Solaris?
> 
> I have been searching around forums and mailing lists
> and still didn't find anything about this... but it's
> becoming kind of the standard in the big linux
> distros (and GNOME) and it might be useful for
> solaris as well..

"Why isn't the serum working?"

"Perhaps we are asking the wrong questions."

Likewise, perhaps you are asking at a wrong place.  I suggest to contact the 
developers of PulseAudio to ask them if they have any plans on porting this 
software to Solaris.

Perhaps you might be able to convince them that Solaris is gratis and runs 
really well and fast on their PCs, and that there is no reason for them to 
really say "we don't have Solaris to test on".
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working

[Casper . Dik]

>"ifconfig -a plumb" is an intentional, though undocumented, special
>case.  Ordinarily, the "-a" option means "read SIOCGIFCONF to
>determine what interfaces IP knows about, and operate on them."
>

The code to find all interfaces is as simple as:


#include 
#include 

static int
devfs_entry(di_node_t node, di_minor_t minor, void *arg)
{
if (di_minor_type(minor) != DDM_ALIAS)
return (DI_WALK_CONTINUE);
printf("%s%d\n", di_minor_name(minor), di_instance(node));
return (DI_WALK_CONTINUE);
}

int
main(void)
{
di_node_t root = di_init("/", DINFOCACHE);

di_walk_minor(root, DDI_NT_NET, DI_CHECK_ALIAS, NULL, devfs_entry);
di_fini(root);

return (0);
}


(When compiled as, e.g., "findifs", it will list all interfaces on recent 
Solaris versions; plumbed or not plumbed)

Casper

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

Re: [osol-discuss] How to enable XDM?

[Casper . Dik]

>
>>What i would like to do is keep using the cde-login and get access with XDMCP 
>>to the dtlogin. Tha
t
> doesn't seem to work in b76 x86. Changing to gdm is not a fix, it's a 
> workarround imho.
>>
>>This worked out-of-the-box on previous solaris versions.
>>Anyone know what changed here?
>
>
>Security, probaby.
>
>Check for the "-udpPort 0" argument to dtlogin.
>
>
>svccfg -s cde-login
>setprop dtlogin/args = ""
>
>svcadm refresh cde-login
>svcadm restart cde-login


Note that the latter command will actually cause all current sessions to 
terminate.

Casper


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

Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working

[Robin Bowes]

UNIX admin wrote:

> This is piece of cake stuff. Normally all of this is set up during
> the install, if you chose not to do so, then it's all in all 45
> seconds to enter the interace names in /etc/hosts and create the
> corresponding /etc/hosname.e1000g[0-n] files. You might be
> experiencing a hardware or an IRQ problem, BIOS settings might be
> incorrect, and so on, and so forth.

I know it's "piece of cake stuff", which was why I didn't understand why
it didn't work.

It turned out to be a bizarre hardware issue - I have one or more bad
disks or bad ports on my PCI-X SATA card and that was killing the NICs.

Once I'd removed the offending disks from offending ports (still not
sure which was the problem) the NICs were discovered and configured
normally.

R.

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

Re: [osol-discuss] OpenSolaris with iSCSI Luns and IPMP 3 x "1 Gbe" eth SAN . Is it sensib

[James Carlson]

chandan maddanna writes:
> Now as james said, i am thinking if there are three interfaces in the ipmp
> group, i will use address on one and other two i will mark, 0.0.0.0 and make
> them "up". So it does efficient outbound load spreading, in Round Robin
> Type.

Note that the load spreading is _currently_ done on a per-peer basis,
so if you have multiple connections to the same remote node, you
generally won't get load spreading among those connections.

Even if we change this implementation detail at some point in the
future (which is quite possible), you won't get load spreading within
a single flow (e.g., a single TCP/IP stream) due to reordering
concerns.  (That's also true for aggregations.)

> And for clients, at the receiving end, what i am planning to use aggregated
> links, Something like this :
> 
> # dladm create-aggr -d e1000g0 -d e1000g1 -d e1000g2 1
> # ifconfig aggr1 plumb 192.168.10.210  up

I'm a bit confused by that.

This may well work, but if aggregation is possible, I would have
expected that it would be possible at both ends.

-- 
James Carlson, Solaris Networking  <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working

[James Carlson]

UNIX admin writes:
> > Yes, I tried "ifconfig -a plumb". It didn't change
> > anything; I still
> > just see the two lo0 devices (IPv4 & IPv6)
> 
> While Juergen migh be correct with `ifconfig -a`, this syntax is new and 
> unknown to me. As far as I know, "plumb" argument always needs a NIC instance.

"ifconfig -a plumb" is an intentional, though undocumented, special
case.  Ordinarily, the "-a" option means "read SIOCGIFCONF to
determine what interfaces IP knows about, and operate on them."

With the "plumb" keyword, however, it means "read libdevinfo to find
all of the network devices in the system, and plumb each one into IP."

It's a handy feature if you know that your system has network
interface(s), but you're not sure what they're called, and can't
figure out the output of prtconf, prtpicl, and similar utilities.

If "ifconfig -a plumb" doesn't find the interface, then this means
that either the hardware isn't recognized by Solaris as being
associated with any usable driver, or the driver installed isn't a
network driver.

-- 
James Carlson, Solaris Networking  <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] How to enable XDM?

[Casper . Dik]

>What i would like to do is keep using the cde-login and get access with XDMCP 
>to the dtlogin. That
 doesn't seem to work in b76 x86. Changing to gdm is not a fix, it's a 
workarround imho.
>
>This worked out-of-the-box on previous solaris versions.
>Anyone know what changed here?


Security, probaby.

Check for the "-udpPort 0" argument to dtlogin.


svccfg -s cde-login
setprop dtlogin/args = ""

svcadm refresh cde-login
svcadm restart cde-login

Casper

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

Re: [osol-discuss] How to enable XDM?

[Patrick Blaas]

What i would like to do is keep using the cde-login and get access with XDMCP 
to the dtlogin. That doesn't seem to work in b76 x86. Changing to gdm is not a 
fix, it's a workarround imho.

This worked out-of-the-box on previous solaris versions.
Anyone know what changed here?
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] OpenSolaris with iSCSI Luns and IPMP 3 x "1 Gbe" eth SAN . Is it sensib

[James Carlson]

Ceri Davies writes:
> On Sat, Dec 08, 2007 at 11:53:27PM -0800, Chandan Maddanna wrote:
> > Guys to be more clear, look at the diagram below, and tell me how to get a 
> > single load spread 2 Gbps link  with IP Multi Pathing on Solaris 10 ?
> > 
> > Note : Please see Image Below .
> > 
> > 
> > http://img514.imageshack.us/img514/8928/ipmpmultipathinghz4.gif";> 
> > 
> > 
> > Now i don't want two public ip , what i need is just one IP which utilizes 
> > the bandwidth provided by both the nic's. Can anyone help me out guys . 
> > 
> > meaning i want active-active configuration and i should use one ip at 
> > client side and it should make use of the bandwidth of both the NIC's .. 
> > can this be done and how, just outbound load spreading is enough for me, as 
> > there is no much in bound load generated, except few scsi commands through 
> > ip and stuff.. 
> 
> You can't; there is no inbound load-spreaing with IPMP.

That's not quite true.

IPMP's inbound load spreading makes use of multiple data addresses in
a group.  When we make outbound connections to multiple peers and
there are multiple data addresses, we'll intentionally round-robin
select among those addresses to use as source addresses, each with a
separate MAC address.  That allows the return traffic to be spread
among the available links.

The other part of the picture is DNS.  For spreading of inbound
connections, you should insert all of the data addresses as IN A
records for a single name, and configure your server so that it does
round-robin responses.  (If the peers are Solaris, disabling or
configuring nscd may be necessary.)

As for outbound load spreading alone, as long as interfaces are marked
"up" in the group, they'll be used.  They don't all have to have
addresses, and interfaces that are "up" but with 0.0.0.0 address will
be used for outbound load spreading using source (data) addresses from
other interfaces.

-- 
James Carlson, Solaris Networking  <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] Unsubscribe

[Sabri Ali]

 
 
SABRI ALI

MEDIAPOST SERVICES

DSI - Ressources 

Administrateur système

9 boulevard du Général de GAULLE

92126 Montrouge CEDEX

E.mail: [EMAIL PROTECTED]  

Tel : 0146124526 Fax : 0146124550

P Pensons ENVIRONNEMENT: n'imprimer que si nécessaire ... 

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

Re: [osol-discuss] PulseAudio

[Richard L. Hamilton]

> I have a question... Is there any plan to integrate
> PulseAudio as the sound server in Solaris?
> 
> I have been searching around forums and mailing lists
> and still didn't find anything about this... but it's
> becoming kind of the standard in the big linux
> distros (and GNOME) and it might be useful for
> solaris as well..
> 
> from the webpage ( http://www.pulseaudio.org/ ) :
> 
> "PulseAudio is a sound server for POSIX and Win32
> systems. A sound server is basically a proxy for your
> sound applications. It allows you to do advanced
> operations on your sound data as it passes between
> your application and your hardware. Things like
> transferring the audio to a different machine,
> changing the sample format or channel count and
> mixing several sounds into one are easily achieved
> using a sound server."
> 
> and here are some of the announcements or projects of
> pulseaudio in the distros: 
> Fedora:
> http://fedoraproject.org/wiki/Releases/FeaturePulseaud
> io
> Ubuntu: https://launchpad.net/pulseaudio
> openSUSE:
> http://dev.compiz-fusion.org/~cyberorg/2007/11/22/puls
> eaudio-compiz-for-sound-on-opensuse/
> Mandriva:
> http://www.happyassassin.net/2007/12/05/pulseaudio-for
> -20081/



The problem with network based audio servers is that there are so many to choose
from, and a number of them don't seem to have survived the test of time:

* MAS   http://www.mediaapplicationserver.net/indexframes.html
  apparently inactive; at one time, claimed to be part of the
  path to eventual audio integration into X-Windows itself

* NAS http://www.radscan.com/nas.html
  active

* ESD ???
  active (sort of)

* Phonon http://phonon.kde.org/
  active


* aRts  http://www.arts-project.org/
  inactive

* JACK http://jackaudio.org/
  plus NetJack http://netjack.sourceforge.net/
  active

and somewhat different,

* X11 Audio Extension  http://www.chaoticmind.net/~hcb/murx/xaudio/
  (relatively new?)


(I probably left out some, too...)

To make it available on a very uncommitted (downright experimental) basis,
in case there are app that work best (or only) with it, might _maybe_ not
be a bad idea.  But I think things are probably a long way from consensus,
and I _know_ I'm not qualified to make an architectual evaluation of the
various alternatives.  All I know is that I want as many audio (including MIDI),
multimedia, and related apps to work on Solaris as possible, without waiting
for consensus to be reached as to the One True Audio Solution; while at the
same time hoping that consensus, effort, and application support will eventually
coalesce around the alternative with the greatest potential.  But on that last 
point,
I'm not very optimistic, remembering VHS vs Beta, or looking at the current 
Blu-Ray vs HD DVD.
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] PulseAudio

[Victor]

I have a question... Is there any plan to integrate PulseAudio as the sound 
server in Solaris?

I have been searching around forums and mailing lists and still didn't find 
anything about this... but it's becoming kind of the standard in the big linux 
distros (and GNOME) and it might be useful for solaris as well..

from the webpage ( http://www.pulseaudio.org/ ) :

"PulseAudio is a sound server for POSIX and Win32 systems. A sound server is 
basically a proxy for your sound applications. It allows you to do advanced 
operations on your sound data as it passes between your application and your 
hardware. Things like transferring the audio to a different machine, changing 
the sample format or channel count and mixing several sounds into one are 
easily achieved using a sound server."

and here are some of the announcements or projects of pulseaudio in the 
distros: 
Fedora: http://fedoraproject.org/wiki/Releases/FeaturePulseaudio
Ubuntu: https://launchpad.net/pulseaudio
openSUSE: 
http://dev.compiz-fusion.org/~cyberorg/2007/11/22/pulseaudio-compiz-for-sound-on-opensuse/
Mandriva: http://www.happyassassin.net/2007/12/05/pulseaudio-for-20081/
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working

[UNIX admin]

> Yes, I tried "ifconfig -a plumb". It didn't change
> anything; I still
> just see the two lo0 devices (IPv4 & IPv6)

While Juergen migh be correct with `ifconfig -a`, this syntax is new and 
unknown to me. As far as I know, "plumb" argument always needs a NIC instance.

So please try:

ifconfig e1000g0 plumb

and then:

ifconfig e1000g0  broadcast + up

like so:

ifconfig e1000g0 1.2.3.4/16 broadcast + up

This will work only if the entry for "pci8086,109a" exists in 
/etc/driver_aliases and is bound to "e1000g". If it is bound to another driver, 
then you need to replace "e1000g" with the name of the correct driver.

>  Why is nothing ever easy!!!

This is piece of cake stuff. Normally all of this is set up during the install, 
if you chose not to do so, then it's all in all 45 seconds to enter the 
interace names in /etc/hosts and create the corresponding 
/etc/hosname.e1000g[0-n] files. You might be experiencing a hardware or an IRQ 
problem, BIOS settings might be incorrect, and so on, and so forth.
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] OpenSolaris with iSCSI Luns and IPMP 3 x "1 Gbe" eth SAN . Is it sensible ?

[UNIX admin]

> 1.) I am trying IPMP group for performance,
> "Outbound" load spreading i am not worried of , as i
> have myself seen it in action and is quite efficient,
> But does Inbound Load Spreading work with IPMP and
> will it have same effect.

Unfortunately, no; IPMP can only do outbound load balancing; inbound requests 
still come to the MAC that answered first.

For what you need, you might want to consider trunking. You'll need to 
configure it in Solaris, but also on the switch as well.  This implies managed 
switches.
 
 
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org