Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
X Operating Systems GUI BSD

FreeBSD Moves to X.Org 428

Nirbo writes "FreeBSD switches to X.Org, The 'HEADSUP' can be found here, and on the -x11, -current, and -ports mailing lists. Very good news for those FreeBSD users who have either changed to X.Org in anticipation, or have been waiting in hope for this momentous change."
This discussion has been archived. No new comments can be posted.

FreeBSD Moves to X.Org

Comments Filter:
  • make.conf (Score:4, Informative)

    by wassy121 ( 446363 ) on Saturday July 24, 2004 @06:34PM (#9791076)
    This is only in -CURRENT. For those of you in 5.2.1, or 4.10, you can add:

    X_WINDOW_SYSTEM=xorg

    in /etc/make.conf. For those of you running -CURRENT that want the old X, make it:

    X_WINDOW_SYSTEM=xfree86-4
  • Re:I wonder... (Score:5, Informative)

    by foidulus ( 743482 ) * on Saturday July 24, 2004 @06:41PM (#9791104)
    Heh, well all OS X users use a port of it, but who knows if they will switch too when Apple releases Tiger next year.
  • Re:Who's Left? (Score:5, Informative)

    by Homology ( 639438 ) on Saturday July 24, 2004 @06:46PM (#9791119)
    So, what major linux distributions, BSD variants, or other operating systems are still using the XFree86 code base? Is the transition essentially complete?

    OpenBSD [openbsd.org] is still using the latest XFree86 4.4 release candidate with the old license+drivers. And NetBSD [netbsd.org] incorporated XFree86 4.4 with the new license.

  • by wirelessbuzzers ( 552513 ) on Saturday July 24, 2004 @06:54PM (#9791150)
    Too bad that you can't upgrade an existing system without using portupgrade, though. I hate to see portupgrade drifting closer and closer to being a required part of the system.

    No. It says in the post:

    To upgrade, you must remove your XFree86 ports and install the xorg
    ports. It couldn't be done with portupgrade, unfortunately, because we
    are keeping the XFree86 ports around.


    In other words, you cannot automatically upgrade all the ports using portupgrade.

    As for portupgrade becoming necessary, I don't know what you're talking about. While I use it (to keep my -CURRENT current), this is merely for convenience: I haven't seen any ports that depend on it.
  • Re:Who is left...? (Score:3, Informative)

    by gabbarbhai ( 719706 ) on Saturday July 24, 2004 @06:59PM (#9791169)
    The free Bitstream fonts are not all that bad for the desktop..
  • by Anonymous Coward on Saturday July 24, 2004 @07:00PM (#9791171)
    Thew new X license blocks anyone from linking a GPL program to it.

    So they basically assed out gnome and even freebsd doesn't want to dump gnome so some asspuppy at X can have his ego stroked when there is a fine alternative.
  • Re:Who is left...? (Score:1, Informative)

    by Anonymous Coward on Saturday July 24, 2004 @07:03PM (#9791193)
    http://www.bitstream.com/categories/products/fonts /vera/
  • by nathanh ( 1214 ) on Saturday July 24, 2004 @07:18PM (#9791266) Homepage
    But I'm curious what restrictions the XFree people added and why it caused all this ruckus. It doesn't seem to have made any difference to my ability to get the source or play with it. What am I missing?

    They added an advertising clause. Similar to the old BSD license.

    There's a reasonable argument that the license change by itself didn't cause the exodus. It was simply the straw that broke the camel's back. There has been friction between the XFree developers and the rest of the FLOSS community for quite some time. There has even been considerable friction within the XFree team which led to the infamous "eviction" of Keith. But until recently there haven't been any realistic alternatives to XFree.

    It remains to be seen whether Xorg can deliver better than XFree. Initial signs are promising; the codebase is being broken up and autotooled, cutting edge extensions like Xcomposite are being integrated, some of the best and brightest have committed themselves to Xorg instead of XFree, the distributions are backing Xorg over XFree, and (most important of all) the Xorg developers are COMMUNICATING with the rest of freedesktop.org (eg, the projects that build upon X11/XFree/Xorg). Those changes alone are a significant improvement over XFree.

  • by marcello_dl ( 667940 ) on Saturday July 24, 2004 @07:22PM (#9791283) Homepage Journal
    I agree on the AC post about bitstream vera fonts. They look very good on the notoriously unforgiving notebook screens. I prefer them over the standard ms fonts i had to install to check compatibility of web page layouts. Try them for yourself.
  • Re:Xorg vs XFree86 (Score:4, Informative)

    by erikharrison ( 633719 ) on Saturday July 24, 2004 @08:22PM (#9791547)
    This is semi objective. I have a very minor presence in the X.org mailing lists.

    XFree86 seems to be mostly listing, with it's major focus being drivers. It was always easier to get new extensions in XFree than in the reference implementation, but that was still hard, so driver's and performance were much of it's force and they seem to think that it still will be. XFree seems to think that they will be the application that people upgrade to from X.org for their value added improvements. Short term assessment, this is a load of crap. People are moving from distro's X.org and XFree ONLY for stability concerns, and those are easily assuaged.

    X.org is all about two things. One, take the protocol to the next level, through the judicious use of extensions. X.org has support from Sun and HP, for example, Sun is moving much of their Looking Glass work into the tree.

    Second, get the implementation out of the stone age. Modularize the build, and use a more modern build system. Clean up the DDX (device dependent X) get extensions playing well with each other, havea faster release cycle and get security and bug fixes from vendors incorperated more quickly. All of this seems to be happening. Hop on the X.org mailing lists and take a look.
  • Re:Who is left...? (Score:3, Informative)

    by Jah-Wren Ryel ( 80510 ) on Saturday July 24, 2004 @08:28PM (#9791571)
    I haven't looked at the SVG spec for a long, long time, but last I remember it was simply a way to specify vectors. The other reason that postscript fonts are programs and not just tables of vectors is that they really work is in the "hinting" such that a font rendered at 9 points needs to look substantially different from the same font rendered at 72 points.

    The good postscript fonts "know" things about human perception and thus render themselves in different fashions based on that knowledge. Simple vectors can't do that because vectors aren't just for fonts and human perceptual tricks that apply to fonts don't necessarily apply to other kinds of vectorish information.
  • Re:What about Apple? (Score:3, Informative)

    by mattkinabrewmindspri ( 538862 ) on Saturday July 24, 2004 @08:52PM (#9791683)
    Apple includes an X11 implementation with OS X, and programs that use X11 can run side-by-side under OS X.

    You can get X11 for OS X here. [apple.com]

  • by Rasta Prefect ( 250915 ) on Saturday July 24, 2004 @09:05PM (#9791730)
    Though I did have a big ass problem with Debian refusing to let apt do it's things the right way when I "broke" the X installation by installing a source-built XFree 4.3.0 over the then-Debian-supplied XFree 4.2.0. This is when I discovered that (a) dpkg sucks (b) Debian's X installation is a spaghetti mess (c) it's virtually impossible to remove XFree packages from a Debian installation and not remove every other program that uses X on the system, which is why I had to just plain install source-built XF over the top of the Debian installed one.

    Generally, building from a source package or building your own package (not that difficult if you're up to compiling from source anyway) works a _lot_ better.

  • Re:Who's Left? (Score:2, Informative)

    by Anonymous Coward on Saturday July 24, 2004 @09:45PM (#9791917)
    Actually, OpenBSD has brought in changes from freedesktop.org into their copy of the X sources. They've always maintained a local modified version anyhow, and they have already said nothing else will come from xfree86, just freedesktop and local work.
  • Re:Name change... (Score:2, Informative)

    by jbardell ( 677791 ) <jbardell86@noSpam.yahoo.com> on Saturday July 24, 2004 @11:14PM (#9792272)
    The start of the project to develop a 'free' version of the X server was called X386, named after the target CPU. The re-name became a play on this, XFree86. Getcherself a copy of the book 'Rebel Code' and enjoy all of the interesting little tidbits within.
  • by runderwo ( 609077 ) <runderwoNO@SPAMmail.win.org> on Sunday July 25, 2004 @12:19AM (#9792494)
    (c) it's virtually impossible to remove XFree packages from a Debian installation and not remove every other program that uses X on the system, which is why I had to just plain install source-built XF over the top of the Debian installed one.
    You're talking crazy talk. The client-side libraries are the only thing that X clients depend upon. You can have X applications installed on a Debian system with _no_ X server. An X application only needs the client libraries to talk to whatever server it feels like.
    I've never even cracked the bindings of XFree source. I imagine, that it's probably a myriad of horrible hacked crap dating back 10-15 years or more in several places.
    No, actually most of the code (excepting the display drivers) is quite clean, modular, and well-documented. But you couldn't be bothered to look before spouting off a sensational opinion, could you now?

  • by dwheeler ( 321049 ) on Sunday July 25, 2004 @12:45AM (#9792600) Homepage Journal
    To my knowledge, they'll continue to use the original MIT/X license. It's known to be GPL-compatible (the main point of contention), and it's the license they've been using all along in general. It's certainly the direction of least resistance.

    It turns out a few files have slipped in with licenses other than the MIT/X licenses. My appendix links to a detailed license analysis (I didn't do the analysis, kudos to the person who did!). But there aren't many such files, and it wouldn't take much to fix them. It's likely that some weren't even intentional, and contacting the authors would be all that's needed in some cases.

    I very much doubt that they'd move to the GPL. This is a project shared between GPL'ed operating systems, *BSDs, proprietary X vendors, and proprietary OS vendors; a GPL move would break that. I guess it's conceivable they'll later move parts to the LGPL, particularly easily separable parts (like a sound server). Mesa was originally LGPL, for example. And the commercial environment has changed since X was started; some projects like Wine [winehq.org] have decided to switch from MIT/X/BSD-like licenses to the LGPL, because they believed that too many commercial companies would take but not give back otherwise (rendering the project unable to continue). So you could argue that the changed environment might encourage them to use a different license to keep the project more viable. But I suspect that won't happen, at least in the short term. Most people seem to be interested in keeping the "status quo" MIT/X license, and more interested in rearchitecting and adding new features. I don't speak from special authority, just as someone who occasionally follows the discussions.

  • by TheRaven64 ( 641858 ) on Sunday July 25, 2004 @08:17AM (#9793791) Journal
    Of course the backend is important, but to most it's not important enough to care about.

    ...

    Hell, most linux users won't ever know they're running xorg until they have to edit their xorg.conf to get those NVIDIA drivers working.

    These sentences seem to contradict slightly. You know Linux is just a kernel, right? As in as far to the back end as it's possible to get without touching actual hardware?

Solutions are obvious if one only has the optical power to observe them over the horizon. -- K.A. Arsdall

Working...