/dev/dump

I've just pushed changeset: 13278:dabee83e3bb7 tag: tip user: Garrett D'Amore date: Mon Jan 31 17:40:15 2011 -0800 description: 519 RFE audiocmihd Reviewed by: gwr@nexenta.com Reviewed by: dev@opensound.com Reviewed by: trisk@nexenta.com Reviewed by: ams@nexenta.com Approved by: trisk@nexenta.com This represents the first significant contribution to illumos by a third party other than Nexenta, and is also the first hardware driver illumos has support for which Solaris does not. This is for ASUS Xonar cards. You can tell you have a card that could benefit from this if prtconf -vp | grep pci13f6,8788 shows a result. I expect this will be introduced soon into a forthcoming OpenIndiana build. Enjoy, and a big thanks again to 4Front Technologies for making this contribution!

I'd like to take a minute to publicly welcome the following engineers, who are well known in the OpenSolaris community, to my team within Nexenta . Dan McDonald - Dan just started today, and joins us from Oracle (and previously Sun), where he was one of the lead engineers on IPsec and networking security in general. He's also famous as the creator of the internal "punchin" tool used by Sun engineers for many years. At Nexenta he'll be doing some different things, but also will be our go-to man for issues involving the TCP/IP stack within NexentaStor and we expect to see contributions coming from him back into illumos . Andrew Stormont - Andy started on Jan 1, and is our first software engineer in the UK. He's known for creating the StormOS desktop distribution based on XFCE on top of Nexenta Core Platform . We're looking forward to capitalizing on the synergy of StormOS and Nexenta Core Platform forward. Roland Mainz - Roland is known throughou

First off, let me state that the following changes are aimed at both easing the challenging of contributing changes to illumos, while increasing our level of "confidence" in what changes are being integrated into our source code tree. Up until now, illumos has used a contribution model that is primarily derived from the model used within Sun and Oracle for Solaris development. This development model is based on the notion that all contributors have (or had at least) the direct ability to "push" code to the repository, after a certain number of review steps had been followed. This model works well with a small team, or where all contributors are reasonably well trusted. This is also not typical at all of the way most FOSS projects work. (Indeed, with OpenSolaris, this model was not used for external contribution.) Going forward, we want to enable a much wider group of developers, some of whom may not hang around long enough in our community to get a high level of

I have an illumos partner that is interested in finding a strong system administrator/system integrator candidate for work on an illumos-based product in New York. Candidates need to be strong with Solaris, security, scripting (perl, python and/or ruby, etc.) and should have cross platform experience. If this sounds interesting to you, please contact me directly.

I'm looking to hire a few really smart folks who can work in southwest Riverside County, CA (near Temecula, CA). I want people who are sharp C programmers, want to work on open source kernel software, and are eager to stretch themselves. This is a great learning opportunity. If you know anyone like that, let me know!

I'll be giving an update on illumos , as part of my talk in LA this evening . If you're around, please join us!