Fedora Prepares For Xorg Instead of XFree86 491
ZuperDee writes "I noticed in the development branch of Fedora today that they appear to be in the process of creating new xorg RPMs, and from the looks of the changelogs in those RPMs, it looks like their ultimate plan is to switch from XFree86 to the XOrg Foundation's implementation of X11. Anyone else here think this could signal the beginning of a new trend in Linux distributions, and that XOrg could end up becoming the new de-facto X11 implementation?" (See this earlier story,too.)
drivers (Score:4, Interesting)
Is the driver support there? Will NVidia's and ATI's binary drivers work with the Xorg server? It could be a real problem if FC2 won't be able to do accelerated 3d under NVidia or ATI cards.
Re:drivers (Score:4, Insightful)
Re:drivers (Score:4, Insightful)
Would NVidia follow RedHat or XFree86. (Score:5, Insightful)
I think they'll follow whoever the biggest commercial Linux distros, and today that means RedHat and Novell/SuSE.
Why support XFree86 if the big distros are dropping it?
Re:drivers (Score:5, Informative)
Re:drivers (Score:3, Informative)
Re:drivers (Score:5, Informative)
The X.org X server is XFree84 4.4-RC2 + bits. It is hosted on freedesktop.org
The FD.O X server is KDrive (which is derived from XFree86, in part) + bits. It is also hosted on freedesktop.org.
Re:drivers (Score:5, Informative)
Re:drivers (Score:5, Insightful)
Re:drivers (Score:5, Insightful)
Re:drivers (Score:5, Informative)
The X.org X server is the XFree86 4.4 codebase, so it is binary-compatible with the ATI/NVIDIA drivers.
Y-Windows (Score:4, Interesting)
Re:Y-Windows (Score:5, Informative)
X-Windows is, just as it says, a server.
One of the greatest things about it is it's network transparency. X-Windows, is still ahead of it's time. Microsoft introduced Terminal Services back in 97 or 98 for Windows NT Server TSE, long time after X-Windows existed, and it still is not as powerfull as X11, it only draws the whole screen through a pipe, compresses it and sends-it to a client. X11 does a lot more than that, it has security is a number of forms (e.g. ACL based), it has support for extensions - which is soo great, and it tells the client which extensions it supports, it has speed (when not over the network) using UNIX Sockets instead of TCP. Even over the network it's fast. If you think that running mozilla remotely on a 56k is slow, think of the alternatives.
Also XFS is great. Imagine you're in a DTP office. You need hundreds of fonts, an UNICODE font can have 20MBytes, or more, why should those fonts be copied on all the stations? One central station for all of them is enough.
You want remote desktop? Just thing XDMCP.
X11 should NOT have an integrated widget set in it. That is because, it's multi-os, multi-platform, you can't expect all the platforms to have the same widget set, toolkit, just think embeded devices here. Not to mention that there is already a standard widget set as defined by IEEE(or was it ISO?) standards: motif. Unfortuantely motif is getting kinda old.
Answers, from the paper on the site (Score:4, Informative)
It's not one of the "greatest technologies ever created in computer world." You've got to be kidding me. Then you go into a long advertising spiel on X11.
Anyway, here are the reasons listed in Mark's paper:
"The X Window System [23] is the de facto standard graphical user interface (GUI) system on UNIX and UNIX-like platforms such as GNU/Linux. However, as X approaches its 20th year, signs of its age are beginning to show. Commonly cited problems with X include:
Aside from the user interface inconsistency, the lack of standard components also makes internationalisation difficult, particularly for languages which require a complex input method.
Although the X protocol supports extensions very well, some of the latest extensions have begun to interfere with each other. For example, when Xinerama (the extension which allows X desktops to span multiple monitors) was first released, it broke XVideo (the extension which allows X to use hardware accelerated overlays for video play back). The 'fix' for this was to allow XVideo to only work on the primary display. The latest extension, XRandR (Rotate and Resize), is also known to break many older applications which assume that the screen size will never change.
Further, the internal design of X itself is outdated. Even adding a simple feature, such a stranslucent windows, requires large changes to the server [17]. Because of the requirement to be backwardly compatible, these features must be implemented for everything that X works on, including two-colour displays.
Re:Y-Windows (Score:3, Informative)
While the freedesktop.org screenshots are pretty, they ignore that X11 was developed too long ago. To many of those items in the pretty pictures would, on most X servers, give messages ranging from "extension 'this_weeks_version_of_something_like_render' not found" to "SIGSEGV".
X has some serious problems. Too much functionality has been put into optional extensions. Not to mention that widgets and toolkits shou
Re:Y-Windows (Score:5, Insightful)
I think the optional extensions are great -- this allows for multiple implementations of X without an unbearable burden of supporting *everything*. If the process of natural selection is going to work, you want a protocol that's not overly demanding.
By separating the widgets and toolkits from the X server, you again reduce complexity and allow for multiple implementations at these different layers. I guess the widgets and themes could somehow be linked into the X server, but now I'm rapidly entering the realm of speculation.
I keep hearing the argument that X is bad because it's old. Unix is even older, and look what happened with it! I'm not saying you're wrong, I just want to hear about the details. Is it necessarily true that the entire protocol is insufficient and cannot be satisfactorily extended? Why not?
I guess efficiency could be the main issue. In part it's a matter of how the clients are designed. I've seen some relatively simple (just stock widgets) Java programs that, with Sun's VM, absolutely crawl over a 10 MBit connection. I mean that it takes half a minute to redraw a quarter of a window or pop up a menu. Compression seems not to help much because it's all limited by latency. (I can imagine the communique: "Can I draw this pixel here?" "What color?" "Red." "Okay." "You sure?" "pretty sure."
If they don't work, it will testify to... (Score:3, Insightful)
RE: Drivers (Score:5, Informative)
Re: Drivers (Score:4, Insightful)
At some level, all distros are forks, so they're all compatible, right? My worry is they'll put some wierd X extension in it, and then make GNOME require that extension.
Anyway, what was the big deal with the XFree86 license again? Buncha massive overreaction if you ask me, but I think certain groups were looking for any excuse to hijack XFree86.
Re: Drivers (Score:5, Informative)
The main problem was that many folks got fed up with the very closed nature of XFree86 development. Many decisions about the project were made by fiat in non-public mailing lists. These core group of developers were often unwilling to explore new features or allow new developers. The barrier to entry for obtaining CVS access to the source was high. Thus, many developers who were not part of the core group got annoyed and decided to stop submitting patches to XFree86. Thus, all these derivatives were born that promise a more community-oriented development process.
The license change was just the straw that broke the camel's back.
A good explanation (Score:5, Insightful)
Re:A good explanation (Score:5, Interesting)
Yup, there is only one development team that is more of a pain in the ass than XFree86. But in mplayer's case they actually have kept up with the evolving needs of their users and developers. XFree86 seems to have been stuck in a timewarp for a few years now. That's not to belittle the past accomplishements, but standing still is not an option. The licensing change is just something concrete to point to when recruiting developers for your fork. I for one have been waiting for a good fork for a few years... um, now I gotta get back to coding... and then deciding which fork to patch...
For the ignorant (like me) (Score:4, Interesting)
Thank you.
Re:For the ignorant (like me) (Score:5, Informative)
X11 is the 11th iteration of the X protocol. XOrg, XFree86, and most commercial X servers speak X11R6 these days. Speaking the X protocol is key to interoperability from Unix to Unix.
X11 as a protocol doesn't have a license issue that i am aware of. Did you by any chance mean the differences between XFree86 and XOrg?
If that is what you meant, then the answer is simple, XOrg is a branch right before the XFree86 license change, so it's pretty safe to say that XOrg isn't too different at all at this point in time.
Re:For the ignorant (like me) (Score:5, Informative)
How about "key to interoperability between X client and X server". Remember that X was implemented on VMS as well as on Unix, not to mention the version in X terminals and various emulators for MSWindows and Mac.
Re:For the ignorant (like me) (Score:3, Informative)
Jeroen
Re:For the ignorant (like me) origin of X11 name (Score:5, Informative)
X11 was X11 right from the start as far as I remember. The 11 stands for one megapixel (as in a display 1000x1000) and one MIP (million instructions per second).
Sorry, the 11 is a version. From "man X":
I'm guessing your megapixel*MIPS was a retcon. Some of us are actually old enough to barely remember when X10 was just passing out of relevance, and I'd imagine a few of us remember before that. Versions before X10 were never really relevant outside of MIT. X10 was 1986, X11 was 1987, and there's been various X11R*s since then. Today, we use X11R6.4, but many programs want lots of extensions on top of it (eg, XRender). Since many of these have only been implemented on XFree86, that's now a de-facto standard.
Re:For the ignorant (like me) (Score:5, Informative)
To expand more helpfully on the previous poster's comment...
XFree86 and XOrg are both implementations of X11. X11 is technically a protocol, not a particular program. This is why X11 has persisted for so long despite repeated attempts to dislodge it. Everybody who tries to do something better forgets that X11 is a protocol, and that's actually why it's so popular. They usually end up implementing something that's an API, which is just all wrong.
The XOrg implementation of X11 is a fork of the XFree86 codebase, just before XFree86 changed its license to be not quite free enough for most people to be comfortable using it.
Re:For the ignorant (like me) (Score:3, Insightful)
If you're going to state that X11 is slow, then I suggest that you rmember that on a local box, we're talking about unix sockets, which are mmaped in the kernel, hence 0 performance loss.
If your going to start asking about alpha blending etc then your confusing X11 and XFree, since their is no problem with haveing a blendable X server.
Please elaborate
Re:For the ignorant (like me) (Score:3, Interesting)
No, actually, there is a performance loss because every graphics operation involves a context switch from the process to the X server, even if there is no copying from user space to kernel space and back again.
Re:For the ignorant (like me) (Score:3, Insightful)
I can't see what you want me to think about. You've presented an assertion but provided no reasoning. If you could elaborate: why is X11 an obstacle to the desktop?
Re:For the ignorant (like me) (Score:3, Funny)
Personally, I think there should be a moderation score "+1, Misinformed". Combine it with "+1, Clueless" and "+1, Clueless and Proud of It", and you have an electronic recreation of the pillory!
Daniel
Re:For the ignorant (like me) (Score:4, Interesting)
This is a strength, not a weakness. If a project's licensing becomes a problem moving on from the last good version is a plus. I don't have to completely reinvent the wheel. I just have to get enough developers interested in the fork which in this case seems to not be an issue. I can't do that with a proprietary product. If MS becomes too odious to use and I decide to move to a Mac I now have to buy a new hardare platform and learn a new OS and have no guarantee that I will be able to move all my apps and games over to the Mac.
The licensing debate isn't the greatest thing to have happened but it is no way the showstopper you are portraying it out to be.
Re:For the ignorant (like me) (Score:3, Insightful)
Also, there has been some internal strife with the XFree86 organization. From my external viewpoint, it seems like the people own largely control the organization are somewhat slow about changing things or adopting new ideas into XFree86.
XFree86, up to this point, has been a defining implementation of the X11 protocol. Most new things in the X11 protocol have come from the XFree86 project. But, I suspect that's no longer going to be the case.
De Facto (Score:4, Interesting)
At least, in theory.
Re:De Facto (Score:5, Funny)
Re:De Facto (Score:3, Insightful)
A fork started over a minor difference of opinion is unlikely to get much backing...and it's existance does not really affect the main project.
The main difference between Free Software and Proprietry projects is that when a bunch of developers decide they don't like the way a proprietry project is being run - they either leave for good, or leave and start from scratch, with Free Software they can f
Re:De Facto (Score:5, Funny)
Hundreds of forks?! And I have trouble remembering which one is for the salad.
Re:De Facto (Score:3, Funny)
there is no fork...
ah, no.. i remember: it was a spoon
Re:De Facto (Score:5, Informative)
What it does do, is prevent non Free forks.
Re:De Facto (Score:5, Interesting)
On a more serious note, while this is not official dogma of the FSF, and never will be while they possess at least two brain cells, it has unfortunately become an uncommon but tenacious myth among the GNU discipleship. Peruse any Slashdot story on BSD and you're likely to discover an instance of it.
Re:De Facto (Score:3, Interesting)
I'm confused (Score:4, Insightful)
Is this the same thing as Xouvert, or something new?
Can someone give a ten second summary of the differences in the goals and developers of XFree86, Xouvert and Xorg?
Re:I'm confused (Score:5, Informative)
Re:I'm confused (Score:5, Informative)
Xouvert is also based on Xfree86, but it is a bit different than X.Org. Xouvert was started when it became apparent that XFree86 guys were too reluctant to change, and to commit new codes and technologies. If I am not mistaken, the Xouvert project started in summer of last year, with the goal of being a more experimental branch of Xfree86 i.e: they would accept code more easily than XFree86 guys. They also stated that they want to seperate the drivers from other parts, so that one can add a driver of a new chip, to a old release of X. I don't know how succesful they have been in this front.
And aside from all of these, is the Free Desktop.org's X Server. This X Server, mostly written by Keith Packard is not mature for every-day use yet, but I think of it as the future of Open Source X. It is mostly a complete rewrite, and it is not a fork of XFree86, though it has borrowed some libraries from the latter one.
Re:I'm confused (Score:3, Informative)
Re:I'm confused (Score:5, Informative)
XFree86, Inc. - The old organization, mainly consisting of David Dawes at this point.
Xouvert - Splinter group that forked X awhile ago, with the intention of being a cooperative competitor.
X.org - Formerly X Consortium. Bunch of companies and developers working on the X11R6.x reference codebase.
Freedesktop.org - Umbrella project for various desktop-related Linux projects
Now, there are some implementations:
XFree86 - De-facto standard on Linux, by XFree86, Inc. Based on the X11R6.x reference codebase.
Xouvert - Fork of XFree86 (circa 4.3?) by the Xouvert project.
X.org server - Don't confuse this with the X.org reference codebase. This is a fork of XFree86 4.4-RC2 (before the license change). Now its under the X.org umbrella, and is hosted on freedesktop.org (that's the confusing part
FD.O X - Keith Packard and friend's new, fancy X server. Development hotbed for new technologies like transparency, OpenGL-acceleration, etc.
There are a couple of seperate sub-components to note here. The FD.O X server supports a number of DDXs (basically, driver layers). There is the kdrive-based DDX, the XFree86-based DDX (called Xizzle, theoretically compatible with XFree86 drivers).
There will eventually be another DDX designed from the ground-up for OpenGL acceleration. The device-independent portion of the FD.O server is, IIRC, derived from an older version of XFree86.
Re:I'm confused (Score:4, Funny)
Xizzle? Fashizzle?
De Facto Standards (Score:5, Insightful)
Fedora switching just means we have more choice. This is a good thing, just like KDE vs. Gnome is a good thing.
Most people will settle for whatever comes with their distro, so maybe this will give an impetus for the X group to clean up the licensing issue :-)
Re:De Facto Standards (Score:5, Funny)
In the case of open source software, sometimes I think it is more accurate to speak of "the standard du jour."
Re:De Facto Standards (Score:3, Insightful)
*grumble*
A nit: Standards are based on specifications. Implementations of specs are called 'Standard' by convention but are implementations, not standards. The implementation can shape an existing standard or even create a de-facto standard.
A popular de-facto standard is Microsoft's .doc format
Re:De Facto Standards (Score:3, Insightful)
Dictatorships tend to be more efficient than democracies (especially representative democracies), but democracies tend to be more pleasant for everyone outside of the ruling class.
Re:De Facto Standards (Score:3, Insightful)
Really? Many closed, undocumented APIs. Inconsistent behaviour across versions. An environment that is constantly changing w. every new virus, worm and trojan. DLL hell. Patch-o-matic games. Registry corruption.
Developers write an app, and are SURPRISED when it runs ... on non-developer machines.
Re:De Facto Standards (Score:3, Insightful)
Many open, undocumented APIs. Inconsistant behaviour within the *same* version on different distros. An environment that is completely different between machines. Package dependency hell. Patchy driver support. Config files that only programmers can understand.
Developers write an app, and have to work their asses off to make sure it runs on anything besides their machine.
I'm not saying Windows is perfect in this regard, but Linux ain't much better. It's just representative of
Re:De Facto Standards (Score:5, Interesting)
And thus it should stay. No, really.
Linux -- aw hell, just for the ability to distinguish between the kernel and the OS in this post, let me throw my lot in with RMS and say, "GNU/Linux" -- is not a platform, it's a concept. The concept is "you take a little bit of this and a little bit of that and add it to the Linux kernel and it looks a whole lot like UNIX, but
That's all GNU/Linux is. Now let me ask you a follow-up question: What is Red Hat Enterprise Linux? Aha! You know that, don't you? You can point at a THING and say "I know what this is, and what its message is." Red Hat Enterprise Linux should have a message. GNU/Linux should not. Get the difference?
It's good, therefore, that GNU/Linux is targetted by both Gnome and KDE (as well as other desktops of varying quality, scope and goals). It's good because the operating systems that start with GNU/Linux (e.g. FC1, RHEL, SuSE, Debian, etc.) can take from those what they please, and leave what they do not. Red Hat, for the most part, stresses Gnome as the desktop where, for example, Mandrake does not.
This is what defines a distribution: what tools it includes, what it emphasises and what it contributes to. You may think Debian is too generic and will never gain mainstream adoption. That's cool, because that's not Debian's goal. Debian's goal is to be a haven for free software. It does this admirably. And you can say that about every distribution, only it's a different set of priorities which are and which are not met by each.
"I must say to everyone that if you really want to see Linux take off on the desktop"
No one wants to see GNU/Linux on the desktop any more than Microsoft wants to see Spyglass Mosaic on the desktop. That just happens to be the software that IE started out life as, but it's not MS' goal to put Spyglass on the desktop. It's not Fedora's goal to put GNU/Linux on the desktop, just Fedora.
PS: Posted from a Linux desktop in a company staffed almost entirely by people who use nothing else. We're fine with the state of affairs today, thanks. Oh, and no the only thing holding back Linux on the desktop is distribution and supply channels which are locked in by MS and will take a decade or more to unlock.
Re:De Facto Standards (Score:3, Informative)
I've neather installed, and everything I run runs fine. All you need is the qt and gtk libs and you're fine.
Path of least resistance (Score:5, Informative)
Of course! (Score:3)
Of course this marks the start of a new trend, Red Hat just beat Mandrake to it. After the announcement last month about XFree86's license change and the very negative response for everyone, this was expected. It's only surprising because it happened so quick
De-facto? (Score:3, Insightful)
It's X, X is for the most part X whichever X you run. If feature y on server z of X doesn't make it the standard, what make anyone think license clause w for server v will?
Having two equally used Xes would be better I'd think, after all they follow the same X standard.
If it's compatible, they will use it ... (Score:5, Insightful)
It's a little early to make that kind of prediction. However, the key is compatibility. If XORG maintains full compatibility such that it's still X11 and we can just a recompile and go on our merry way, then anything is possible. Personally, I don't think people care which code base their X server uses so long as it's an X11 server. Reality is that the XF86 group will wake up an smell the coffee sooner rather than later, they're expendable, they just don't know it yet.
Re:If it's compatible, they will use it ... (Score:5, Informative)
Re:If it's compatible, they will use it ... (Score:3, Informative)
Stick a Done in me, I'm Forked (Score:3, Funny)
Either way, how about brainstorming-up a better project name? I personally like "Product X" but that may already be taken.
N
OK listen up (Score:5, Informative)
First off, this new server is a snapshot of XFree86 just prior to the licence change. Basically a fork.
Second, it basically has nothing to do with X.org - I don't know why they call it that, most likely due to the licence.
Third, X11 is the protocol that X servers speak nowadays. X version 11 release 6.6 to be more precise.
Fourth, nvidia and ati drivers will work.
I hope this clears it up somewhat.
Corrections (Score:5, Informative)
First its based on XFree86 4.4 just before the change, with the non-contaminated further changes added and other stuff not in XFree 4.4
Secondly it has a _lot_ to do with X.org. The wheel has turned full cicle from when years back OpenGroup/X.org tried to change the license and XFree basically told them to go away to today where X.org is doing the same thing the other way around and keeping it free. X.orgi is part of this now.
NVidia and ATI drivers may work. The Nvidia ones at least are reported ot do so, although they have chronic problems working with the preferred kernel build settings like 4K stacks.
How to kill your prjoect... (Score:4, Insightful)
As I understand it, Xfree changed their license to make sure more credit is given to its developers. But who gives a crap when no one will use because of the license itself.
The only thing necessary for Micro$oft to triumph is for a few good programmers to do nothing". North County Computers [nccomp.com]
Simplistic Explanation (Score:5, Insightful)
I've read and re-read various threads on the XFree86 mailing list (please look it up in archives and past posts on
Would that be sufficient reason for a project to fail? In this case, I would say so. He insists on having and keeping all control of the project to himself. If he had good sense, that wouldn't be a problem, but he's already shown that all he's interested in is recognition and retaining control over the project (rather than the project's welfare).
Past posts have shown that several suggestions and patches had been ignored which led to the project's stagnation. You may argue that the project is successful and works even now, but the point is it could have been so much better under a different type of leadership.
The recent license change is but one manifestation of how callous the head developers are.
Re:Simplistic Explanation (Score:5, Interesting)
But before jumping all over DD, have a quick look at the CVS commits for XFree86 over the years. He certainly has contributed a lot to the free X Server we have been using for years. Despite his abrasiveness I don't think it's fair for all his hard work to be disregarded.
Cheers
Stor
at least an option.. (Score:3, Insightful)
What happens to the XFree86 Team? (Score:3, Interesting)
What distros will continue to use XFree86? Any?
It just goes to show... (Score:3, Insightful)
(yes, I know that X is hardly Linux-specific...)
As an end user, I don't care which license it has! (Score:3, Insightful)
If it doesn't have accelerated support for video card X (and forking the tree will have that effect as development resources get divided), I don't care how open it is.
Does is matter how far you can open the hood of the car? I'd rather be able to open it three quarters of the way open to see a nice eight cylinder 450 than to be able to open it compeletely and see the hamster and his wheel.
too bad we're talking about X and not OSX (Score:5, Insightful)
For the user, OSX it is a dream. But for developers, it's a wet dream. Creating slick interfaces is simple, the PDF-inspired graphical model is a breath of fresh air, and the interfaces inherit impressive functionality automatically. Because its code-development process leverages effort powerfully, perhaps more so than for the comparable GNOME/KDE tools, I think OSX offers good potential for the open-source movement, given well-fashioned attitudes and licenses.
I make these remarks with some trepidation, since I think the fragmentation across GNOME and KDE dilutes developer momentum. Also, I make these remarks to evoke discussion by those more technically-aware than myself.
Re:too bad we're talking about X and not OSX (Score:5, Interesting)
You must be looking for GNUstep then.
It doesn't have many developers but it's just as well since although hoards of developers have made not one but two half-assed clones of Windows the small number of developers working on GNUstep are nearly finished implementing OpenStep true to specifications.
What's exciting about GNUstep is that Cocoa is also an implementation of OpenStep with some additions. With a little spit and polish GNUstep running on Linux would make a great clone of OS X.
However, OS X is not all about the GUI. OS X also has some kernel facilities and user tools to go with it which make the OS more suitable for desktop use. For one thing, Apple has a devfs so devices show up in a sane manner and there are no extraneous entries. There is also the automounter and associated tools (comamnd line and GUI) to go with it.
Probably the most important thing about OS X that should be brought to Linux is the BSD style of an administrators group. On OS X you can have multiple admin level accounts which can sudo things as root. The root account doesn't even have a password and is entirely disabled. This makes it easier for joe user. Joe can run as an "administrator" which is actualy a fairly unpriviledged account which can gain access only if Joe enters his own password. That makes one less password for Joe to remember and prevents Joe from just giving up and running as root all the time.
What this means... (Score:4, Interesting)
To be honest, the only difference between XF86 4.4 and X.org (that I can tell) at this time is the new XF86 license...
So, as to how all of this will pan out...it will be left to the individual distros and developers. If they see promise and innovation in the X.org project, they will go with it, and on they other hand, the new license shouldn't cause a problem for any distro that already includes Apache...because the change to the XF86 license is pretty much the same thing as the Apache license requires.
xorg-x11 works great (Score:5, Informative)
Re:First X Sucks Post! (Score:5, Informative)
Of course, Gosling was never an X architect. Those were Scheifler, Gettys and Newman. Gosling was the architect of NeWS, a competing windowing system that ultimately lost out to X. Yes, IHBT. Thank you and good night.
Re:First X Sucks Post! (Score:3, Funny)
Re:First X Sucks Post! (Score:4, Informative)
Proper Context (Score:5, Informative)
C'mon now...
Besides, if you never read the articles, and just look at the exceprts, you'd never know about the asparagus. What asparagus, I hear you ask? My point exactly.
Re:This is great news. (Score:3, Informative)
Hmm, the link is to xorg.freedesktop.org. Are you sure you got what you wanted? It looks like they ARE using the fork.
Re:This is great news. (Score:5, Informative)
Kind of strange, but not really. Just one project (freedesktop.org) providing excellent free CVS hosting for free desktop projects, and two very similar projects with very different leadership joining.
Re:This is great news. (Score:5, Informative)
Re:you might want to check this out (Score:5, Informative)
Re:Great (Score:5, Informative)
X11 is a standard, not an implementation! Just like HTML is a standard!
That distro A uses XFree86 and distro B uses XOrg means absolutely nothing to end users. Everything's still interoperable because X11 is a standard. Everything will still Just Work(tm) and the end user won't even notice something has changed.
Re:Uh (Score:3, Insightful)
Hmmm, let's review a little history here...
For some time now, I have been able to login to a Solaris box from a Linux box, start an Xterm on one and display it on the other. *Gasp* Interoperability! And these don't even have much common history (except, of course, the Solaris distros that use XFree86, before some pedant points it out). And you know what, the exact same thing works with Tru64 Unix... and NT X servers... gosh, just about the whole X11 world is interoperable! Conspiracy theorists, arise!
Re:Great (Score:4, Insightful)
I wouldn't dare to imagine the number of times that MS has replaced or retrofitted (read: ugly hacks) technologies found in previous versions of Windows. Only in there case, its all closed so you aren't aware of it. In all liklihood, the MS situation is worse, since it leads to bloat and security risks.
Just because open source development airs its dirty laundry in the wind does not mean it yeilds worse software than closed source development. Quite the contrary, I think if you researched your position you would find better software.
Re:Great (Score:4, Interesting)
What about X? That's 20+ years, and now extensions are beginning to conflict with each other. For instance, Xinerama broke XVideo. Solution? XVideo only works on the primary display. Look at the complexity of ICCCM, or the fact that Xine simulates a shift key press every 30 seconds to disable the screensaver since it gave up trying to figure out the window manager it's running under. Yes, Virgina, sometimes endless choice is bad.
These examples, of course, were taken from the Y-Windows paper [ic.ac.uk] describing all the reasons to get rid of X and replace it with Y (which is also network transparent). I fully expect Y to be the superior replacement to X. They're at 0.2 now and are targetting a 1.0 release in a year.
Re:Drivers could be a problem for a long time. (Score:3, Informative)
Re:Drivers could be a problem for a long time. (Score:4, Informative)
Re:Drivers could be a problem for a long time. (Score:3, Informative)
Probably not. (Score:4, Informative)
I know for a fact that Debian, Gentoo, and a few others are specifically NOT touching XFree86 4.4 (i.e. post-license-change), and are looking for alternatives.
X.org sounds like it is currently the most mature alternative, and will likely have the marketshare XFree86 does within months, unless David Dawes pulls his head out of his ass and stops shooting himself in the foot. He doesn't seem to realize that his license change is going to make XFree86 a defunct project VERY quickly.
Re:Probably not. (Score:4, Funny)
He must be flexible. And good at blind shooting.
Re:Drivers could be a problem for a long time. (Score:3, Interesting)
I wish they and ATI would do open source 3D but thats not going to happen for the later cards until people like Intel simply commoditze them and turn them into the next version of the SGI graphics division or until software gets so fast that we don't care about
Re:Drivers could be a problem for a long time. (Score:4, Informative)
Re:Will THIS be the wakeup call to XFree86? (Score:3, Insightful)
Furthermore, should we care any more? With XOrg, xserver and xouvert all at different and useful stages of maturity, and apparently enough developers now working on each to guarantee that they won't stagnate too soon, XF86 is looking increasingly irrelevant.
Re:The Lowdown (Score:5, Informative)
There are two X servers at freedesktop.org now, both with stupid and confusing names but hey :)
1) Xserver - this is the new experimental one that does pretty drop shadows and stuff. Not really mainstream yet. This is the fork of kdrive.
2) Xorg - this is the fork of XFree before the licensing change. It's not experimental and is usable just like XFree is.
Hope that helps
Re:Ad-hoc Standard (Score:3, Informative)
On other distribututions, rpm (yes, rpm) works fine. it doesn't strip binaries it shouldn't touch (arm for instance in an x86 package), it doesn't add depenedencies it doesn't need, it basically just works as advertised.
Have you used the 'AutoReqProv: no' line in RPM? Works fine for me in preventing spurious dependancies.
there is no such thing as a minimal redhat9 installation. all we wanted was to build packages for redhat9, 2gig was as small as I could get the build.
Have we not heard of "Select ind
Flame with more fire and less smokescreen, please (Score:4, Insightful)
I'm the maintainer of CSCVS, a tool for breaking CVS repositories into changesets, reporting on them, and importing those changsets into TLA. As such, my familiarity with CVS (and Arch) goes beyond that of the average user.
Now, about the issues that Arch is designed to fix: Revisioning renames and moves is not something that comes up only infrequently. Revisioning metadata is not something that comes up only infrequently. Mutually merged branches are not something that come up only infrequently. Taking forever to do a "cvs update" on a 10,000 file tree because the tree needs to be walked to look for updates is not something that comes up only infrequently. I've had the lead developer at work bitching in my direction because CVS is coming up with spurious conflicts that Arch would ignore.
I have a leg to stand on right now, and if you'd care to stand up and try to argue your position on its merits rather than firing off some angry rant, I'd absolutely love to do so.
Not all about licenses (Score:4, Informative)
This is not all (directly) about licenses. Keith Packard has done most of the new, interesting functionality in XFree86 for some time. By going with him, they are aiming for more modern functionality in their X server. XFree86 is very conservative about new functionality.