Announcement

Collapse
No announcement yet.

FreeBSD 12.0 Faces A Minor Setback But Still Should Be Out Ahead Of Christmas

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • FreeBSD 12.0 Faces A Minor Setback But Still Should Be Out Ahead Of Christmas

    Phoronix: FreeBSD 12.0 Faces A Minor Setback But Still Should Be Out Ahead Of Christmas

    The big FreeBSD 12.0 release still is expected to happen in December but will be a bit later than originally planned...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Extremely minor typo at the end of the article (greater than sign instead of a dot).

    Comment


    • #3
      Is there any news on the 5GHz Wi-Fi support? I know that *BSD development is mostly concerned with servers nowadays, but 802.11ac is nowadays a rather old technology – with a successor for it arriving soon – and AFAIK there is still no support for that on any of the *BSDs.

      Comment


      • #4
        Originally posted by 0Yg7pQpFGiwcw View Post
        Is there any news on the 5GHz Wi-Fi support? I know that *BSD development is mostly concerned with servers nowadays, but 802.11ac is nowadays a rather old technology – with a successor for it arriving soon – and AFAIK there is still no support for that on any of the *BSDs.
        802.11an has been long supported (could not figure out if you were asking about 5-5,8GHz band, or more specifically about 802.11ac)

        Adrian Chadd's blog often has interesting reading materiel (one of the FreeBSD devs)
        I've been chipping away at bringing up 802.11ac on FreeBSD. I've been meaning to write this post for a while, but you know, life got in the ...


        Why lots of stuff is not there..
        http://adrianchadd.blogspot.com/2018/03/not-merging-stuff-from-freebsd-head.html

        I get asked all the time why I don't backport my patches into stable FreeBSD release branches. It's a good question, so let me explain it here.

        I don't get paid to do it.

        Ok, so now you ask "but wait, surely the users matter?" Yes, of course they do! But, I also have other things going on in my life, and the stuff I do for fun is .. well, it's the stuff I do for fun. I'm not paid to do FreeBSD work, let alone open source wireless stuff in general.

        So then I see posts like this:



        I understand his point of view, I really do. I'm also that user when it comes to a variety of other open source software and I ask why features aren't implemented that seem easy, or why they're not in a stable release. But then I remember that I'm also doing this for fun and it's totally up to me to spend my time however I want.

        Now, why am I like this?

        Well, the short-hand version is - I used to bend over backwards to try and get stuff in to stable releases of the open source software I once worked on. And that was taken advantage of by a lot of people and companies who turned around to incorporate that work into successful commercial software releases without any useful financial contribution to either myself or the project as a whole. After enough time of this, you realise that hey, maybe my spare time should just be my spare time.

        My hope is that if people wish to backport my FreeBSD work to a stable release then they'll either pay me to do it, pay someone else to do it, or see if a company will sponsor that work for their own benefit. I don't want to get into the game of trying to backport things to one and potentially two stable releases and deal with all the ABI changes and support fallout that happens when you are porting things into a mostly ABI stable release. And yes, my spare time is my own.

        Comment

        Working...
        X