Slashdot Mirror


XFree86 4.3.0 in FreeBSD Ports Tree

Dan writes "Eric Anholt has committed the long awaited XFree86 4.3.0 to the FreeBSD ports tree. Please report any issues, bugs, etc. directly to him. The port appears to have support for popular cards such as NVidia, ATI, etc. Eric suggests that you use portupgrade to ensure you update fully from an earlier version of XFree86."

23 comments

  1. Only Post by Anonymous Coward · · Score: -1, Offtopic

    Only Post! Woooooooooooooo!
    BSD is a zombie - half dead, eats brains.

  2. *BSD is dying by Anonymous Coward · · Score: -1, Troll
    It is official; Netcraft now confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

    FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dying

  3. Developer lashes out: What Killed FreeBSD by Anonymous Coward · · Score: -1, Offtopic
    The End of FreeBSD

    [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

    When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

    Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

    FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

    It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

    So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

    Discussion

    I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

    From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

    There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

    Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

    Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

    Shouts

    To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

    To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.

    To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.

    To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.

    To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.

    Future

    I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.

    However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.

    You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.

    = Mike

    --

    To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt
  4. agp support? by RLiegh · · Score: 0

    I have a weird gateway astro that freebsd wouldn't do x in, I wonder if this version of FreeBSD will fix that.

    Oh well, if not, there's still [b]vmware[/b]. ;)

    1. Re:agp support? by essdodson · · Score: 1

      This is not a new version of FreeBSD. This is an update to a port. However you can expect FreeBSD 4.8 to be released in the coming week.

      --
      scott
  5. Portupgrade is my hero by Anonymous Coward · · Score: 0

    n/t.

  6. A pleasant surprise... by CoolVibe · · Score: 3, Informative
    Heck, I did a portupgrade after cvsupping my ports and hey presto, new X. Woohoo! What a nice present.

    Oh, I have to remark that the nvidia drivers for FreeBSD work surprisingly well under Xfree 4.3. So far no problems. My Geforce 4 is happily screaming away at 1600x1200. Life is good :)

    1. Re:A pleasant surprise... by Anonymous Coward · · Score: 0

      do you exploit the GeForce's 3d powers in any way?

    2. Re:A pleasant surprise... by CoolVibe · · Score: 1

      well, the opengl screensavers in kde 3.1 are quite snazzy, yes. :-)

  7. matrox g550 didn't work for me by TheGratefulNet · · Score: 3, Informative

    I had to use the linux tarball of the matrox supplied *drv.o files.

    the bsd ones (from the ports) just kept giving weird errors.

    the port maintainer knows this now, but if you are running a dual-dvi system (which NEEDS the matrox HAL lib) then maybe try getting the linux .o files and putting them in the /modules/lib... area instead of the port-built ones.

    fyi.

    --

    --
    "It is now safe to switch off your computer."
    1. Re:matrox g550 didn't work for me by CoolVibe · · Score: 1
      Hmm, odd. I seem to remember that the Xfree86 port had an WITH_MATROX_GXX_DRIVER (or somesuch) knob you could twiddle, but looking at the port Makefile, it seems to be gone.

      Basically, what it did was download the Matrox Gxx source drivers and build them with X11. It's how I got my dual-head Matrox G400 working under FreeBSD on my other workstation.

      Oh well... Guess I'd have to wait with updating X on that box.

    2. Re:matrox g550 didn't work for me by TheGratefulNet · · Score: 1

      that knob DID produce a few .o files.

      but those files DIDN'T WORK! don't know why - its beyond me - but I know for a fact they didn't work and that the 'linux' .o files (from the matrox site) did work.

      weird. but true.

      also, dualhead and dualhead DVI are quite diff. I run dual dvi. for that, you need the HAL lib. for regular dual, you don't (AFAIK)

      --

      --
      "It is now safe to switch off your computer."
  8. Elegy for *BSD by Anonymous Coward · · Score: -1, Troll

    Elegy For *BSD


    I am a *BSD user
    and I try hard to be brave
    That is a tall order
    *BSD's foot is in the grave.

    I tap at my toy keyboard
    and whistle a happy tune
    but keeping happy's so hard,
    *BSD died so soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am I a zit faced slob
    but *BSD is dying.

  9. *BSD is dying by Anonymous Coward · · Score: -1, Flamebait
    It is now official; Netcraft confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

    FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dying

  10. Why no DRM? by Piquan · · Score: 1

    From the article:

    graphics/drm-kmod isn't going to be updated for 4.3.0.

    Anybody know why not? And why no HAL support?

    1. Re:Why no DRM? by Arandir · · Score: 1

      Anybody know why not?

      Because graphics/drm-kmod is sort of deprecated. It only exists for the 4.x tree, because the drm stuff is now in the kernel sources for the 5.x tree. I noticed that the kernel sources weren't updated either, so maybe an update just isn't needed.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Why no DRM? by anholt · · Score: 1

      The kernel sources were updated on 2003-03-09, two days before 4.3.0 hit the ports tree.

      I'm not updating drm-kmod because it's annoying to have these open-source, mit-licensed kernel modules outside of the tree. It means that as the port maintainer I have to apply patches to it every time someone changes the kernel API and all the users have to manually update it. If it's in the tree, there's no synchronization problem (except in DRI CVS).

  11. Hard times for *BSD by Anonymous Coward · · Score: -1, Troll
    So why now? Why did *BSD fail? Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?

    The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.

    1. Re:Hard times for *BSD by Anonymous Coward · · Score: -1, Troll

      It is official; Netcraft confirms: Linux is dying

      One more crippling bombshell hit the already beleaguered Linux community when IDC confirmed that Linux market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that Linux has lost more market share, this news serves to reinforce what we've known all along. Linux is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

      You don't need to be a Kreskin to predict Linux's future. The hand writing is on the wall: Linux faces a bleak future. In fact there won't be any future at all for Linux because Linux is dying. Things are looking very bad for Linux. As many of us are already aware, Linux continues to lose market share. Red ink flows like a river of blood.

      Redhat is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time Redhat developers Michael Evans and Timothy Buckley only serve to underscore the point more clearly. There can no longer be any doubt: Redhat is dying.

      Let's keep to the facts and look at the numbers.

      Mandrake leader Jacques states that there are 7000 users of Mandrake. How many users of Slackware are there? Let's see. The number of Mandrake versus Slackware posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Slackware users. SuSE posts on Usenet are about half of the volume of Slackware posts. Therefore there are about 700 users of SuSE. A recent article put Debian at about 80 percent of the Linux market. Therefore there are (7000+1400+700)*4 = 36400 Debian users. This is consistent with the number of Debian Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, Mandrake went out of business and was taken over by Redhat who sell another troubled OS. Now Redhat is also dead, its corpse turned over to yet another charnel house.

      All major surveys show that Linux has steadily declined in market share. Linux is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among OS dilettante dabblers. Linux continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Linux is dead.

      Fact: Linux is dying

  12. Is XF86-4.3.0 compatiable with NVIDIA's drivers? by KiwiSurfer · · Score: 1

    Does the new version of XFree86 work fine with NVIDIA's offical drivers?

  13. Broken FreeBSD Alpha port !!! by Anonymous Coward · · Score: 0

    Why are the FreeBSD 4.7 Alpha port boofloppies broken ?

    They do not boot at all.
    4.62 boots, but fails, 5.0 works.

    It makes me think that FreeBSD on Alpha is poorly done, is this the case ??

    1. Re:Broken FreeBSD Alpha port !!! by minektur · · Score: 1

      Because code sizes are much larger on the alpha architecture, boot-floppy support was dropped a while back - at least I think this was the conclusion of the long thread. It is less of an issue than I thought it would be for me as my miata boots just fine off of an ide cdrom drive...

  14. Re:Is XF86-4.3.0 compatiable with NVIDIA's drivers by CoolVibe · · Score: 1

    Yes, so far no problems here with the drivers for nvidia in the FreeBSD ports.