Slashdot Mirror


FreeBSD 6.0 to Target Wireless Devices

BSDForums writes "FreeBSD is hoping to move beyond the server and desktop market by providing expanded wireless support. FreeBSD developer Scott Long said that 'one of the primary reasons for improving wireless support is to give companies the tools to put FreeBSD into their wireless devices. The guy at FreeBSD who is adding wireless support is under contract from wireless companies to do the work.'"

10 of 215 comments (clear)

  1. The reluctant adoption of Linux by HishamMuhammad · · Score: 5, Insightful

    This is an interesting development. Companies have been using Linux in their wireless boxes due to the lack of any viable alternative. Due to the GPL, these companies were forced to publish their changes to the kernel, which has allowed the number of cool hacks we've been seing. Clearly, those companies would rather keep their changes proprietary, so BSD based systems are much more attractive to them. While it's nice to see improved hardware support to another free operating system, this might bring adverse consequences in the long run. We'll see...

    1. Re:The reluctant adoption of Linux by HishamMuhammad · · Score: 3, Insightful

      Well, all those Linksys hacks are based on the tarballs originally released by Linksys in their process of complying to the GPL.

      While it's not impossible to do it without vendor support (XBox Linux, etc), the cool hacks are greatly helped by packages released by vendors.

      Hopefully, as companies see the benefits that ensue from this relation, they develop a different attitude towards Linux (Sony wrt Linux on the PlayStations is a good example -- here's hoping their announcements for Linux on the PS3 will materialize (but I'm not holding my breath)).

  2. this is really big by Anonymous Coward · · Score: 5, Insightful

    as someone who works for a company that uses many variants of linux in their products, i can tell you that most companies dont have a clue about the GPL and the parts about giving away _their_ code comes as a shock to them.

    i see more and more companies turn to BSD licensed stuff, such as the *BSD OSes

    (no linux vs BSD flame, please)

    1. Re:this is really big by twiddlingbits · · Score: 3, Insightful

      Some one should be firing the S/W Manager and their corporate attorneys for getting into that mess without looking. ANY License for something you plan to redistribute bears close scrutiny from expert technical and legal resources. Even if it was a small company, for a few 100's of dollars they could have had a lawyer tell them what they were obligated to under the GPL.

  3. Re:sorry freebsd, you are too late by LittleLebowskiUrbanA · · Score: 3, Insightful

    The beautiful part is that OpenBSD is NOT in a competition with anybody despite what your post asserts. The OpenBSD developers have goals that are in line with their ideals and they haven't strayed from them and the developers certainly aren't out to "corner wireless development."
        You make it sound like 2 companies competing against each other when it's just FreeBSD's developers losing sight of their ideals and doing thing the easy, non-OpenSource way.

  4. Can we stop this? by iamdrscience · · Score: 4, Insightful

    Like many articles about BSD, this one will surely have a ton of comments along the lines of "Oh no, companies don't want to give away their code, so they're all going to use BSD licensed software and the world is going to end!". This arguement is, in almost all cases, bullshit. Why? Because usually it's not the operating system that matters so much as the software on top of it, and Company X has just as much control of their own program with Linux as with BSD (or Windows, etc.). Most products do not require significant changes to the OS, if any at all, and even in those products that do, far more of the products value comes from the company's own software.

    So stop it people, the sky isn't falling.

    1. Re:Can we stop this? by The+Vulture · · Score: 4, Insightful

      To some extent that is true, but not always. The sticky issue is that of device drivers. Device drivers hook into the kernel, and their licensing as such has never really been clear. The general consensus seems to be that as long as you mark your module as non-GPL in the declaration, which excludes your use of some GPL'd code, your module is okay.

      Userspace applications don't suffer from these restrictions - glibc is LGPLd, as is uClibc for these reasons - you don't have to abide by the GPL in order to have a C runtime library.

      Where I see this going (as I stated in another post) is that whether Linux or BSD is used will likely depend on the hardware designers (companies like Broadcom, who make the reference designs, not companies like Linksys, D-Link or Netgear, who just base their work on reference designs).

      The sky is not falling, I agree. We'll continue see substandard products from el-cheapo manufacturers no matter what underlying OS is used. I am going to go out on a limb and say that if FreeBSD can be used in these low-power, slower CPU, small RAM/flash footprint devices, and it performs as well as Linux, then the designers will do so. It gives them that much more protection against violations of the GPL (accidental or not).

      -- Joe

  5. Re:Why lose a stepping stone to freedom preservati by larkost · · Score: 3, Insightful

    Umm... I think you got the point reversed. The poster was talking about the fact that you can take BSD licensed code, make changes to it to support your product, and not be forced to give your work to anyone else (for example your competition).

    While we all understand the idea behind the GPL, many businesses will simply not even consider using OS's based on it because of the forced nature of it. FreeBSD stands to get a lot of users because of this in the embedded space.

    Now, the gamble with the BSD license is that people might use the code without ever contributing back. But the bet is that the big companies will give some sort of kickback to the projects, even if it is not the complete solution.

    An example of this is practice would be Apple and KHTML. While Apple has not completely given everything it could have given, the KHTML project has benefited from Apple using a derivative of KHTML. We can argue about whether it is enough, but it is benefit that Apple would not have contributed if KHTML were GPL rather than BSD. Management would not have touched it with a 10 foot pole.

  6. Proprietary source is not the reason.. by willy_me · · Score: 4, Insightful

    Well, it might be for some, but I think that most companies would be fine with publishing any minor kernel modifications made to Linux. The real reason why companies are a little afraid of the GPL is that there is always the potential for lawsuits. Granted, it's a remote possibility, but a possibility all the same; most companies would rather not be bothered with the GPL if given a choice.

    And this is where FreeBSD can give people a choice. And assuming it's just as good as Linux, it's a better choice due to legal issues.

    One last thing about the GPL is that most companies don't see distributing changes as a free endeavor. Someone has to be in charge of overseeing the process - and labour isn't free. In addition, distributing the changes requires other resources (like bandwidth) which, while not very expensive, just add to the complexity of using Linux. While this might be a minor issue, it's still an issue that companies would rather avoid.

    And what happens when the slashdot community burns a company for forgetting to post something, or posting modifications that are difficult to utilize. Remember Apple and Konqueror?

    Oh well, but to respond to your last point, I don't think there will be many adverse consequences. The work currently being paid for by these companies is under the BSD license and I don't see them being that protective of the kernel. The GUI however is another story.

    Willy

  7. Re:Why lose a stepping stone to freedom preservati by SillyNickName4me · · Score: 4, Insightful

    You may have your doubts but history simply proves that they do (not all of them, but quite a few still)

    FreeBSD has a thing called netgraph, from its manpage:

    HISTORY
              The netgraph system was designed and first implemented at Whistle Commu-
              nications, Inc. in a version of FreeBSD 2.2 customized for the Whistle
              InterJet.

    Then, from man jail:

    AUTHORS
              The jail feature was written by Poul-Henning Kamp for R&D Associates
              http://www.rndassociates.com/ who contributed it to FreeBSD.

    Of course PHK is a core member of the fbsd team, but that doesn't change that it was written and payed for by a commercial user of the system and then contributed to it.

    There is a simple very good reason for companies to contribute their changes, given that they get accepted:

    It saves them the cost on maintaining such a component and keeping up with the development of the system.