XFree86 4.4 Released 531
puriots0 writes "XFree86 version 4.4 is finally out! Grab it while it's still hot, if you don't mind the recent licensing changes... And if you don't care about the license, but the maintainers of your distribution do, this might be the only way to get it for the moment." The XFree86 people seem very eager to claim that the new license is nothing bad; see their FAQ. However, people who have reviewed it, such as RMS and Branden Robinson, think differently. It looks as if the XFree86 people have a short timespan to either rethink their license changes or be dropped from every/almost every Linux distribution in favor of a forked codebase.
From the FAQ (Score:5, Interesting)
So, it seems that the main reason for a fork is no longer an issue ? No-one is going to be writing a new X-Server (well, I guess some of the embedded folks might, but that's about all I can think of), and they state that there's no issues with any client programs that you link with
My position is that if you write/own the code you get to say how it's used. I don't think there's *any* argument against that, and I can see why they want to promote themselves in this world where perception is all. The issue is that all decisions have consequences - which may be why client-programs are not part of the deal
I wonder if the forking argument itself (please say that correctly
Simon.
Re:From the FAQ (Score:5, Informative)
Interesting that the FAQ now acknowledges that the 1.1 licence does not permit redistribution under the GPL; before, the XFree86 people were insisting that in their opinion it was allowed. Unless I'm confusing two different licences here.
Re:From the FAQ (Score:5, Informative)
Re:From the FAQ (re GPL + APL-2.0) (Score:5, Interesting)
Unfortunately not. Instead of fixing the problem, the Apache group made a public statement to say that the incompatibility doesn't exist. - The problem arose from the press release of the Apache License-2.0, in which they gave "GPL compatibility" as a justification for the new license. Note that if you combine a GPL'd and an APL'd work, it's the GPL'd works license that is infringed, so the decision isn't up to the Apache group. The Apache guys might need a good clothes line.
From FSF's license list [gnu.org]: The Apache Software License, version 2.0: This is a free software license but it is incompatible with the GPL. The Apache Software License is incompatible with the GPL because it has a specific requirement that is not in the GPL: it has certain patent termination cases that the GPL does not require. (We don't think those patent termination cases are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL.)
Some clarifications (Score:5, Informative)
One important point: GPL-compatibility was not the only "justification for the new license" by a long shot. That was one of many goals [apache.org], but not the main point of the license.
So, there has been progress on this issue, but it's not as clear cut as you make it out.
Debian avoiding the new release?? (Score:5, Funny)
Re:Debian avoiding the new release?? (Score:5, Insightful)
Re:Debian avoiding the new release?? (Score:5, Informative)
Re:From the FAQ (Score:5, Funny)
> XFree86; that is enough reason for Debian to avoid the new release, it seems.
Debian just moved X 4.3.0 into the unstable tree about a week and a half ago; I don't think any of us Debianistas were really worried about seeing XFree 4.4 in any of the three main Debian trunks this year anyway.
Re:From the FAQ (Score:5, Interesting)
I find it ironic that they choose a license that specificly allows relicensing and brag about its abilities and at the same time complain when somebody actually does it.....
BTW since microsoft used the BSD license ip stack doesn't that make their EULA just as viral by this logic?
Jeroen
Re:From the FAQ (Score:5, Insightful)
BTW since microsoft used the BSD license ip stack doesn't that make their EULA just as viral by this logic?
Yes, you cannot take any Microsoft changes to the BSD tcp/ip stack and re-introduce them back into BSD code bases, since the EULA prevents that.
Re:From the FAQ (Score:5, Informative)
Except that Microsoft does not use the BSD IP stack.
Re:From the FAQ (Score:5, Funny)
Yeah, and now so do we.
Re:From the FAQ (Score:5, Informative)
No, it's not `well known', and in fact, it's not true!
The revised (`3 clause') BSD license is perfectly compatible with the GPL. Since 99.9% of all `BSD licensed' code uses the revised BSD license, there's basically no problem at all.
Of course the resulting aggregate program must have its source distributed (&c) as part of its source uses the GPL, but that's pretty obvious if you're using GPL'd source code.
[The original (`4 clause') BSD license is indeed incompatible with the GPL, but that's largely academic, as no one actually uses that anymore.]
Re:From the FAQ (Score:5, Informative)
The revised BSD license [gnu.org] -- which almost all current `BSD licensed' software uses -- deleted the advertising clause, removing the conflict with the GPL.
Re:From the FAQ (Score:5, Insightful)
Similarly, if I had some code that said 'you can use this but only while doing a handstand' and tried to combine it with GPL'd code, I couldn't distribute the resulting work under the GPL because people receiving it wouldn't know about the handstand condition. I would have to distribute it under 'GPL plus handstand' - but then this wouldn't be allowed by the GPLd code I started with, since you're not allowed to add extra restrictions.
The actual problem is... (Score:5, Informative)
I would be happy to see the licence backed out and the major distributors voluntarily add a splash screen giving major credits and referring the viewer to a website with extended acknowledgements.
I would be just as happy to see a GPL "A" variant arise which was GPL plus advertising clause. This would allow you to GPLA-license BSD code which you are modifying, effectivly getting the GPL's sterner protection but without treading on the intentions and rights of the original authors.
Of course, if you're working from a no-advertising BSD licence, these problems evapourate. Personally, I'd like to see XFree86 with a splash screen since it'd give you something to read while KDE (or whatever) starts, and it'd overwrite the splash screen from NVidia (or other manufacturer) who are not at all shy about claiming credit for stuff.
Re:From the FAQ (Score:5, Informative)
Xouvert [xouvert.org]
Freedesktop [freedesktop.org]
Cygwin X [cygwin.com]
Personally I don't see myself ever using XFree 4.4 and am looking forward to a complete release of fd.o. When that happens, I'll likely be moving everything I can off XFree but that's just me.
Re:From the FAQ (Score:5, Interesting)
Re:From the FAQ (Score:4, Informative)
Re:From the FAQ (Score:5, Insightful)
More than simple attitude, the 1.1 license is a bold declaration that you can't trust them.
Re:From the FAQ (Score:5, Interesting)
On the contrary, FreeDesktop.org is writing one, and it's A. much more promising (supports some neat things too like drop shadows and translucent menus), and B. based on the original XFree86 libraries.
Re:From the FAQ (Score:5, Informative)
Re:From the FAQ (Score:5, Insightful)
Re:From the FAQ (Score:5, Insightful)
Hmmm, where is this `useful documentation' you speak of? The windows documentation I'm familiar with (not happily, but sometimes you gotta do unpalatable things) is for the most part completely useless, e.g., it simply restates what is already obvious, without giving any deeper insight or addressing common problems...
Re:From the FAQ (Score:5, Informative)
- OpenGL will be used for drawing, so you can have very rich, yet fast, vector-graphics based applications.
- Back-buffering each window (which is what enables transparency and shadows) allows you to eliminate all sorts of flicker and lag during resizing and window moving.
- New extensions (Composite + XDamage) allow for clever window managers to do useful things like Expose-style features, screen-scrapers (for things like VNC), magnification tools, etc.
Re:From the FAQ (Score:5, Funny)
You're right, of course. As the project manager of Anyone Anywhere Who Has Ever Written Any Free Software, I will make sure to let them know that shadows and transparency are officially pushed back to 2005, and all man hours are to be spent on Robustosity.
I'll also redirect the efforts of those guys in France who were writing ANOTHER image gallery program. Seriously, don't we have enough? We're working on Robustness now, guys! Pay attention!
Re:From the FAQ (Score:5, Insightful)
Ah yeah, because Windows 95 never had a chance did it? Not MacOS before X? You have no idea what you're talking about. Desktop success comes via a strong application base, reliability, ease-of-updating and other factors.
It's in no way "critical", as other OSes have shown. Besides, your "even a chance" is nonsensical, as Linux desktop adoption has surpassed Apple's. It's still small, but it's growing rapidly.
Confused with the window manager again (Score:5, Informative)
Enlightenment (www.enlightenment.org) has been around for quite a few years now, and can look like a lot of different things - but if you give it 64 virtual desktops with a different background image on each and turn on all special effects it will run very slowly. If you use a sane configuration it will run OK on a pentium 90 with 32MB.
There are also many others which have been developed since then - there is more software available than what comes with your distribution.
One final thing - gnome is not X, it is a whole suite of different programs, which is why it takes so long to start up. The whole idea of there being one program that does everything is just an artifact of the Microsoft court case - your web browser is NOT part of your operating system, and the gnome panel is NOT part of X, they are seperate programs.
Re:From the FAQ (Score:5, Insightful)
I think part of the concern is over long-term intent. Mr. Dawes says [xfree86.org] applying the license to client-side libraries is "deferred", implying that it might be applied sometime later, though it appears that he thinks GPL compatibilty for the client-side libraries is somewhat important.
Apache used to have an advertising clause and dropped it, yet people still know about Apache. Moreover, the number of people who will even notice these "advertisements" are fairly few -- how many ordinary folk are going to read and understand these lists of attributions? If they want XFree86.org to be on everyone's lips (for positive reasons), they'll need something more than this clause.
Re:From the FAQ (Score:5, Insightful)
An XFree86 logo during the X server startup would get noticed!
What other alternatives? (Score:5, Interesting)
Re:What other alternatives? (Score:5, Informative)
y windows [y-windows.org]
Re:What other alternatives? (Score:5, Insightful)
Re:What other alternatives? (Score:5, Informative)
Andy Suffield has been working on the project; he's got some stuff up at http://people.debian.org/~asuffield/ [debian.org].
By the way, the modifications to libiterm required to support Y have already entered Debian Unstable, so you don't have to install that seperately now.
Re:What other alternatives? (Score:4, Informative)
PicoGUI and Berlin (or whatever they renamed themselves this week) are still in the development stage. GTK and some games can run under direct vga acess too.
It's Fresco (Score:4, Informative)
Re: None, for users. (Score:5, Informative)
There are not suitable alternatives for end-users on Linux and BSD on recent hardware. freedesktop.org [freedesktop.org] is an experimental play-area for developers where exciting new features are currently being developed not mundane things like updated drivers for newer video cards (Radeon 9600, 3rd party 9200LE, newer Intel 845 series, etc.), not robust "production quality" software for end-users, Xouvert doesn't actual have any unique code of their own the last time I looked, and Y Window system is more an idea and a work in progress.
For users too (Score:5, Funny)
"Careful with that X eugene"
Re:What other alternatives? (Score:5, Informative)
Re:What other alternatives? (Score:5, Informative)
> freedesktops server is just build on xfree86. same drivers.
I think you've confused freedesktop with Xouvert. Xouvert is a fork from XFree86, but they don't appear to have any of their own code yet, and people have been questioning if the project is still alive. The freedesktop Xserver is an independent implementation, based on Keith Packard's Kdrive Xserver. From the freedesktop Xserver FAQ [freedesktop.org]:
Re:What other alternatives? (Score:5, Funny)
Windows, but if the license of X is what really bugs you...
Xserver (Score:5, Interesting)
Re:Xserver (Score:5, Informative)
1) An experimental driver architecture
2) An expertimental set of X extensions, dependent on the new driver architecture for performance reasons
3) The umbrella for the Keiths more mainstream extensions to X, including XDamage (which is a dependency for the compositing extension).
According to the guys on the XServer list, the XServer is not only not ready for prime time, but it may not ever be a real canidate for an XFree replacement because of it's experimental nature.
X servers on Freedesktop (Score:5, Informative)
The x.org server is very much ready for prime time
So they stick to the new license... (Score:5, Insightful)
Re:So they stick to the new license... (Score:5, Insightful)
"why doesn't the XFree group revert ot the old one?"
Let's not please. Have you seen how fast the latest Linux 2.6.3 kernel is? Now imagine combining that with the speed of the latest KDE 3.2.0. What ingredient is still missing? A forked, reworked, optimized Xserver perhaps? Please Xfree group, for the love of God, keep the license as it is.
Re:So they stick to the new license... (Score:5, Informative)
Re:So they stick to the new license... (Score:5, Insightful)
The FSF doesn't like the new license and begins telling people that it is incompatible with the GPL. Does that mean they are right? Does the GPL mean whatever the FSF decides it means that week? Or, in a country governed by the rule of law, does it mean no more and no less that what it be proven to mean in court? I don't know about you, but I tend to believe the latter
More importantly, what exactly is the FSF supposed to do about people who don't agree with their current take and make use of Apache/XFree86-4.4 anyway? Are they going to sue them? Do they have the money, let alone the ability convince a court that the suit isn't frivilous? More importantly, can they afford the ill will that would result?
I personally don't understand why XFree considers this change so important, but neither do I see it as a harmful one. They are not attempting to make any changes to how anyone uses their code, only asking that they receive recognition for their work. Isn't that something that RMS has been whining about for years with his GNU/Linux nonsense? He "corrects" people for calling Linux Linux every chance he gets. In fact I read an article where the author claimed that RMS refused to give an interview unless the article used his preferred terminology.
What's good for the goose is good for the gander.
Lee
Re:So they stick to the new license... (Score:5, Informative)
Re:So they stick to the new license... (Score:5, Funny)
Re:So they stick to the new license... (Score:5, Informative)
Well, the FSF did a very good job of backing up their claim that it is incompatible with the GPL. They pointed to the exact sections where the incompatibility occurs. Most people, including a number of the major Linux distributions, seem to agree with the FSF on this interpretation.
The "this week" comment is misleading. The FSF has never changed their opinion on the correct interpretation of the GPL and has tried to make the implications of this interpretation as clear as possible from day one.
More importantly, what exactly is the FSF supposed to do about people who don't agree with their current take and make use of Apache/XFree86-4.4 anyway? Are they going to sue them?
If someone alters a GPL program such that the code is linked with code from an incompatible license, the copyright holder of that code is within their rights to order the distributor of the mixed code to stop. If that distributor does not stop, the copyright holder is within their rights to sue the distributor to make them stop.
If the FSF were the copyright holder, they probably would sue if they absolutely had to in order to ensure compliance with the GPL. The FSF does hold the copyright on many open source projects, so this is a possibility.
Do they have the money, let alone the ability convince a court that the suit isn't frivilous?
Actually, yes, the main function of the FSF is to serve as a central copyright repository for open source and trust fund for the legal defense of those copyrights.
More importantly, can they afford the ill will that would result?
Can the open source software community afford to exist in a manner in which licenses are addressed in a slapdash, "oh that's close enough" manner? Since the nature of Open Source is to coordinate input from many contributors, the exact manner in which the rights and licensing to that input is marshalled is of extreme importance. The rights framework for open source needs to be clear and solid.
Moreover, I'm not sure exactly how much ill will the FSF would garner for enforcing the requirement that if you redistribute GPLed code you follow the terms of the GPL, especially since, well, if the GPL isn't going to be complied with then why does it exist in the first place? The only ill will this would generate is among people who don't think anything should be GPLed ever, and they hate the FSF anyway, so what's the loss?
Re:So they stick to the new license... (Score:5, Insightful)
Perhaps it is a big deal after all. Pure speculation, but it is possible that incompatability with the GPL is a deliberate attempt to prevent future changes to Xlib from being used by the freedesktop.org project now that they have packaged the library separately. I don't really see what useful purpose that would serve, but maybe things just got very, very bitter between the various personalities involved.
Aarrr... (Score:5, Funny)
Lets make it as complex as possible for everyone (Score:4, Insightful)
Question (Score:5, Interesting)
Have any of the individual XF86 *contributors* come forward and said their portions of 4.4 may be used under the previous license at the user's option?
Re:Question (Score:5, Informative)
Oh REALLY?!?!? (Score:5, Interesting)
Am I the only one here who thinks it is possible that license change or not, some distributions are getting ready to dump XFree86 in ANY case, due to the other problems it has, like the general arrogance of the core developers, and the lack of a truly open development community, which is largely their doing?
Seriously, I don't think the license change is the major reason, but simply the right occasion for dumping XFree86. Even if they were to revert the license change tomorrow, I for one would still favor seeing forks like Freedesktop.org's server make it into distros, because I believe the license change is only one of MANY indications that XFree86 has far deeper problems that I'm not so sure can be fixed so easily. Just like many organizations and projects in real life, the PEOPLE behind the project are the greatest asset, and I think the XFree86 core team has failed to recognize this. Unless the core team gets a total attitude makeover, I doubt this will ever change.
Re:Oh REALLY?!?!? (Score:4, Informative)
The last version of X? (Score:5, Insightful)
Hopeful about the post-X era (Score:5, Insightful)
Can we get rid of the X11R6 subdir? (once again, stop thinking X is a world to itself)?
Just two suggestions for the post-XFree86 era.
Re:Hopeful about the post-X era (Score:5, Informative)
Re:Hopeful about the post-X era (Score:5, Informative)
Yes. This is being done for the Freedesktop.org X server. See here for more information [freedesktop.org]. And about time! Another thing is that the horrible imake system is being removed (I personally would like to see it taken out behind the barn and shot). Looks like these guys are serious about dragging X into the 21st century.
And XFree86 Inc. has shown to be willing to talk (Score:4, Interesting)
It is not clear why XFree86 has to modify their license to suit a Linux distribution [debian.org], which is suppose to be a compilation of Free/Open Source Linux software, not a dictator of Open Source.
If these arm chair lawyers are so concerned about GPL, why don't they write a new X Window System from scratch, and release it for free/Free under the GPL.
And you realize... (Score:5, Funny)
But if we have to f'up the server right, how about linking to the release notes [xfree86.org]?
XFree86 and licensing (Score:5, Informative)
XFree86 is the reason we have a free software X server today. It is quite ironic that slashdot is now hating XFree86 because of licensing.
Re:XFree86 and licensing (Score:5, Interesting)
Not quite. I had a sideline participation at the time, emailing the X folks and putting them in contact with RMS.
In fact RMS and X were working out an agreement to GNU GPL the whole shebang, thus keeping it free while preserving The Open Group's interests, but XFree was adamant against it.
That move at the time would have preserved X.org, which today is basically a non-entity.
So we stick with 4.3. Big deal. (Score:5, Insightful)
As long as someone still develops drivers for 4.3, its not the end of the world. ( yes, its a major speed bump and makes the OSS world look stupid for the bickering.. but its not a show stopper )
And remember its just the XF86Free implementation that is hosed up now, not the X11 protocol..
When Announcing A New Version Of Something (Score:5, Insightful)
another nice article... (Score:5, Informative)
there's a nice article [osnews.com] on OSnews which looks back on the whole XFree86 affair of past year ...
About the ad clause (Score:5, Insightful)
Seems to me, credit is given where credit is due. If they actually were doing something worth really knowing about, wouldn't they actually get it? We have been seeing little spats happen for long enough now to raise a few eyebrows. Personally, I suspect some deeper problems behind this.
We need an active X development group that does everything it can to enable *nix systems to continue to develop. We don't need these petty squabbles.
Those of us who know what X brings to the table are happy using X. Replacing it really should not be an option at this point; however, I see plenty of folks not happy with X as it is today.
This is exactly why they are not getting the attention they crave. The job is not being done well enough plain and simple.
Fork or no, this is going to continue to be a problem until a group forms that can step up to the plate and hit a few home runs. Will it be the XFree guys or somebody else?
Whoever gets X development moving as it needs to will get all the attention they need. Stupid license clauses won't cut it.
Just Wondering If This Is What Dawes et al. Want? (Score:5, Interesting)
I noticed when Googling around about Dawes that (besides the fact that apparently he lives rather close to me) he is running a business based on X, offering stuff like automagic configuration (at least some of which has made it into the X CVS). Could dropping the latest X from the major Linux distros leave Dawes as the only game in town for enterprises seeking the most enterprise-ready solution? And he wouldn't have to take responsibility for pulling it from his competition....
Remember XFree... (Score:5, Interesting)
Most say that it sucks. I say it's not perfect but check this website : http://www.lynucs.org/ [lynucs.org]
and you'll see that X can really make your desktop very eye-candy. (well, perhaps you already knew
Don't blame XFree too much.. we're pretty all using it, even it may be the time to move on.
The fork has already happened. (Score:5, Informative)
RMS doesn't like it? (Score:5, Interesting)
Re:RMS doesn't like it? (Score:5, Insightful)
The problem with the license is one of changes. You can't go around springing new licensing suprises on people without expecting them to be upset - whatever the license (as MS themselves have found
Now its over everyone can back to work sanely and Dave Dawes can go and do his own thing in Dawes-space, or throw in the towel and contribute to the X.org tree. I still hope the latter because I don't think Dave Dawes did anything maliciously or without belieiving he was doing the right thing for X, he just seems to have been wrong.
Alan
Alan
XFree86/freedesktop-kernel interaction? (Score:5, Interesting)
I dunno how much you dabble with the related code, but how likely is a fork of X going to be to cause issues with the fact that X interfaces with kernel modules...say, freedesktop.org wants to go one way, and XFree86 wants to go another...which supporting code goes in the kernel, or is that a non-issue? I know that it's already caused fun for the Red Hat packagers, who never really expected to have to support multiple XFree86-libs-style packages...
With my tinfoil hat on... (Score:5, Insightful)
Graphics card makers refuse to release info allowing Open Source drivers to take full advantage of their hardware; heck, people gush over the major proctalgia of NVidia's driver that you get to recompile every time there's a kernel upgrade.
Now XFree86 decides to change its license in a way that is incompatible with GPL, so that Linux distributions refuse to use XFree86 4.4. The free alternatives (freedesktop.org, Y, etc.) need rewritten drivers. Does anyone think the hardware vendors will write multiple drivers when it's hard enough to pry one out of them?
PCI Express is on its way, and the claim is that it will kill AGP. How long will one be able to survive with a free X, or XFree86 4.3? (Not a rhetorical question; I don't know enough about the hardware to say, and really would like an answer.)
Let's talk about something other than the licence (Score:5, Insightful)
Re:Let's talk about something other than the licen (Score:5, Insightful)
And THAT is why there is nothing big in this release.
Re:Licensing (Score:5, Insightful)
Re:Licensing (Score:5, Insightful)
The great thing about free software is that you can only be in control as long as you don't piss off a critical set of developpers.
Jeroen
Re:Licensing (Score:5, Insightful)
If the company doesn't wan't to develop anymore your screwed, otherwise they would have to hire new programmers....
The free software alternative is better:
No matter what the original author does, you can always do (or have done) it yourself. And that is just asuming you are the only one that cares.
If the project is really interesting someone will eventually pick it up or replace it.
A rational person that doesn't see that is blind.
Jeroen
Re:Licensing (Score:5, Insightful)
You see software as a product, you should regard is as infrastructure. Somehow a society manages to build and support a road system.... and its not by magic.
When the original builder is gone you can still use the road, and if you don't know how to fill a hole you get somebody to do it for you. And if you are really lucky you will get some community of road users to do it collectivly (something like a government perhaps?)
Jeroen
Re:Licensing (Score:5, Insightful)
You're always dependent on some developers, not necessarily the same developers as you've always had.
What happens if the developers just stop developing?
What happens if the developers just stop developing a closed-source product?
With an abandoned closed-source product, you've got nothing to do except look for an alternative, use the old version, or write one yourself from scratch.
With an abandoned open-source product, you can get new devs on your team, or the code can be forked. No open source project is truly abandoned if there is continued interest in developing it.
What??? (Score:5, Insightful)
Sure, it seems bad while it's happening, but in the end you get a better product. Often projects get way too political and forking is a way to bypass that bureaucratic nightmare.
Re:What??? (Score:5, Insightful)
Sure, it seems bad while it's happening, but in the end you get a better product. Often projects get way too political and forking is a way to bypass that bureaucratic nightmare.
Do you get a better product? Maybe...BUT, and this a big but, what about the products that have to choose which fork to follow when they've diverged far enough to be incompatible? Which version of X am I going to write GeeWhizMaGraph to use? These forks are even worse overall than distro fragmentation looking at linux at a macro level.
Whoever modded my original post as flamebait can bite me. Get a clue.
Re:What??? (Score:5, Informative)
Its called a 'standard' and its a nice thing to have.
The only thing you will have to choose is the library you compile your app against. Very vew apps use the xlibs directly. And even then the various forks of xlib are still compatible.
Jeroen
Re:Licensing (Score:5, Insightful)
I'd call forking natural selection... and while it can be painful, I would say it makes things stronger. Projects that head out into the weeds loose mind share (developers, users, 'buzz' if you will..) and disappear. The beauty of Linux is you get to scratch your itch. Often others share the same problem, and may share a solution. Someone running the project goes off into a wild tangent, good for them. Might be a little pain as you switch to something that is more aligned to what you were after, but odds are you can.
A personal example? I let myself get lulled into the RPM package management and really felt like I got the shaft when RH dropped the 'non-enterprise' user who did not have mad cash for per machine/per year subscriptions. All the packaged distros seemed to share the same Achilles heel (in my mind). Hunkered down and went Gentoo rather than putting energy into Fedora. If ebuilds fade away, I'll look at the app-get thing...
Forking thins the hurd (-1, terrible joke)
I've said it before and I'll say it again (Score:5, Insightful)
Re:It's time for a redesign, anyway. (Score:5, Informative)
The average person doesn't need to know about xfs, or font dirs etc. Their distribution vendor takes care of this.
Again, the distribution vendor takes care of this.
Printing is not an X issue, for the same reason that embroidering is not. It's a completely different medium.
Again, the average user does not need to know about this. The distribution vendor chooses a default, and if the user has a reason to prefer a different one (which implies they already know about them), they may select a different environment. KDE software runs in GNOME, and vice-versa, and motif/CDE/XLib, etc software still runs in either, or neither, or twm, fvwm, etc.
XFree86 runs on a lot more platforms than just x86, which is a good thing now that 64 bit commmodity CPUs are coming out. Even AMD64 is likely to break those optimizations.
What does "safe mode" have to do with XFree86? Most of the users are on UNIX-like systems (Linux, FreeBSD, OpenBSD, Solaris, etc). If you want to run an X Server on Windows 95, you're free to try one of the commercial implementations.
Embroidering! (Score:5, Funny)
Re:It's sad ... (Score:5, Insightful)
RMS designed the GPL to be hard to work with. It seems a bit myopic to now act all surprised that it is working as designed and to try to blame everyone else for its inflexible nature.
That the GPL can't coexist with other licenses was a design goal of the GPL. It's unreasonable to be upset with deverlopers using other licenses for this fact which is beyond their control.
Re:It's sad ... (Score:5, Insightful)
Either you believe that programmers should be free to license their code as they see fit, or you don't. It's not Freedom if the community is going to deny the legitimacy of licenses that RMS didn't write.
Re:It's sad ... (Score:4, Insightful)
It's one thing to not accept a license because headstands are uncomfortable. It's an entirely different and worse thing to denounce a developer for choosing a license that isn't the one you favor. I see far more of the latter going on here than I see the former.
Finally, The GPL does demand more than your vague perception of it appears to encompass. However, that's not really relevant to my point.
Re:It's sad ... (Score:5, Insightful)
It predated the name "Open Source", but it did not predate all other Free and Open Source licenses. The BSD and MIT licenses are two that predated the GPL. In addition, the idea of Free Software predates the GPL by at least two decades, though it was RMS who first insisted on the capitalization of the term.
if you Beleive in Free Software, there is no real reason to use a license other than the GPL.
If you believe in Democracy, there is no real reason to vote for any but the Democrat Party candidate! Now be a good citizen and vote like I tell you to vote...
Re:As someone who cares not about the license (Score:5, Informative)
* The nv driver for NVIDIA cards has been updated as follows:
* Support added to the nv driver for the GeForce FX 5700, which didn't work with XFree86 4.3.
* The driver now does a much better job of auto-detecting which connector of dual output cards the monitor is attached to, and this should reduce or eliminate the need for manual XF86Config overrides.
* The 2D acceleration for TNT and GeForce has been completely rewritten and its performance should be substantially improved.
* TNT and GeForce cards have new XvPutImage adapter which does scales YUV bit blits.
The SiS driver has seen major updates, including:
* Support for 661/741/760 and support for 330 (Xabre).
* Merged Framebuffer mode.
* Support for DVI, and much more.
* DRI for 300 series (300/305, 540, 630, 730) is supported again.
A new driver for several VIA integrated graphics chipsets has been added.
* The mouse driver has some support on Linux and FreeBSD for auto-detecting the device to use. This makes it unnecessary to supply this information in the XF86Config file in most cases.
* XFree86 4.4 supports IPv6, based on the code contributed by Sun Microsystems, Inc. to X.Org.
* The Mesa version used for OpenGL(R) 1.3 and DRI driver support has been updated to 5.0.2.
* FreeType 2 updated to version 2.1.4.
Re:features? (Score:5, Informative)
X is a low-level windowing system, not a desktop environment like CDE, KDE, GNOME, (or twm
It's new features are support for newer video cards, bug fixes and work arounds for broken video cards (and Dell laptop BIOSes with regards to VESA modes and 845 chipsets), IPv6 support, new version of Mesa (OpenGL 3D support), and FreeType (font library).
Re:It won't hurt them. (Score:5, Informative)
No (Score:5, Insightful)
* One: the GPL covers *far*, *far* more software than XFree86. The XFree86 codebase, large as it is perhaps a hundredth of a percent of the GPLed software out there.
* Two: This is not about the license so much as political crap about XFree86. Some people have wanted to fork for a while and are just looking for a reason.
Frankly, I think XFree86 is a lousy thing to fork, because it's the sort of software that's a bitch to maintain, but if KP is up to it, freedesktop.org may be worthwhile. He certainly has the backing of a lot of people, and RH's been making moves towards switching to freedesktop.org for a while.