Linked by Thom Holwerda on Fri 20th Aug 2010 14:55 UTC, submitted by anilg
Sun Solaris, OpenSolaris The Nexenta Core Platform marches on with the release of version 3.0 of the OpenSolaris based distribution, based on b134. It has also officially unveiled plans of moving from OpenSolaris to Illumos, the fully open branch of OpenSolaris. It will also now plan on moving to a new userland release. Grab the iso here.
Thread beginning with comment 437698
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I have to admit
by Dubhthach on Sat 21st Aug 2010 18:59 UTC in reply to "I have to admit"
Dubhthach
Member since:
2006-01-12

OpenSolaris/Illumos uses the FreeBSD wireless network stack. This is shared with both NetBSD (where it had originated) and OpenBSD (since 3.6). Several wireless drivers have been ported to OpenSolaris from both FreeBSD and OpenBSD (rum for example)

This wireless stack (net80211) has also been ported to Haiku as can be seen in the article here:
http://www.osnews.com/story/21822/Haiku_WiFi_Stack_Prototype_Connec...

There is also a project to port it to Mac OSX. Having a common Unix architecture for generic ieee80211 layer is a good idea in my opinion.

net80211 originated in NetBSD from what I recall before been adapted by FreeBSD and subsequently improved. There was an attempt to bring it into Linux but it was seen by some kernel developers as been "tainted" due to it's *BSD origin.

Generally I find the best support on laptops comes from those that are labeled as "Centrino"

Reply Parent Score: 3

RE[2]: I have to admit
by kaiwai on Sun 22nd Aug 2010 02:11 in reply to "RE: I have to admit"
kaiwai Member since:
2005-07-06

OpenSolaris/Illumos uses the FreeBSD wireless network stack. This is shared with both NetBSD (where it had originated) and OpenBSD (since 3.6). Several wireless drivers have been ported to OpenSolaris from both FreeBSD and OpenBSD (rum for example)

This wireless stack (net80211) has also been ported to Haiku as can be seen in the article here:
http://www.osnews.com/story/21822/Haiku_WiFi_Stack_Prototype_Connec...

There is also a project to port it to Mac OSX. Having a common Unix architecture for generic ieee80211 layer is a good idea in my opinion.

net80211 originated in NetBSD from what I recall before been adapted by FreeBSD and subsequently improved. There was an attempt to bring it into Linux but it was seen by some kernel developers as been "tainted" due to it's *BSD origin.

Generally I find the best support on laptops comes from those that are labeled as "Centrino"


Cool, the problem is that many laptops these days are being bundled with Broadcom wireless especially those of the NZ$1000 range; there is the bwn driver from OpenBSD and the Linux STA driver from broadcom, neither one has been ported to Solaris even though the hardware is hugely popular out there. Yes I understand I can use NDIS but it isn't a particularly good solution given how iffy it is in terms of stability and the idea of running Windows code on Solaris does send a shudder up the spine. Hence my wondering whether I'm better off putting up a one off contractof $1000 to pay for Linux STA driver or the bwn driver to be ported to Solaris.

I know this is unrelated to your post but I'll tack it onto the reply - As for power management, the last reply on the mailing list for the tesla-dev was in June, has nothing happened in terms of development since then? kind of depressing that Solaris is sucking down the power and nothing is being done about it. I remember that there was a move to make the kernel tickless with the deprecation of lbolt64/lbolt in favour of ddi_get_lbolt()/ddi_get_lbolt64() and yet new drivers are still being merged that use the old deprecated calls - its a mickey mouse setup if you ask me! As for the tickless project, it is in a state of riga mortus since March with no new mail on their mailing list since then. To be pretty damn honest it is depressing to say the least.

But then again I can hardly complain if I fail to put my money where my mouth is and actually do something about by either paying someone to do it or address it myself. I guess in terms of such development there are higher priorities such as finishing off i18n in libc and other components that need open source replacements.

Edited 2010-08-22 02:17 UTC

Reply Parent Score: 2

RE[3]: I have to admit
by Dubhthach on Sun 22nd Aug 2010 11:36 in reply to "RE[2]: I have to admit"
Dubhthach Member since:
2006-01-12

Well I think the illumos guys at the moment are working on just having a booting system. It just shows though that Sun could have easily replaced the closed bits of libc by tasking 1-2 engineers to it. Garrett basically replaced it in a couple weeks of work all by himself. Perhaps Sun preferred that certain elements were kept closed source as it force the maintenance of an umbilical cord where 3rd party distro's were dependent on Sun to continue releasing the closed binary bits with each update.

Regarding Broadcom, I would think part of the issue here is no one has raised a bugfix/change request to incorporate bwn. If it was raised and relevant links pointed to OpenBSD/FreeBSD you might get a quicker turn around. (Emphasis on *Might*) Illumos do have a feature request list, I see for example they've added extra support for different Marvell Nic's to yge.

I myself refuse to buy laptops with Broadcom chips in them since I had a similar issue with Linux back in 2004. My solution was to buy an Intel mini-pcie wireless card (2915abg) card and install it. Result I had a Athlon64 laptop with intel wireless :-) which worked out of box with whatever *nix I put on it.

Reply Parent Score: 1