Many people see companies and industry as this large immovable object, and we in the linux community can have our fun, but ultimately we need to make concessions in order to "fit in".
I would have to agree. Gentleman like Mr. Gates, Mr. Glass, and other license 'viewholders' share the common belief of corporations not being able to use GPL'ed code. They would lead us to believe a company is going to be ever-profitable and ever-wonderful, but an evil engineer slips in 'print "Hello World!\n" and all of a sudden, Capitolism, Bambi's mom, and eveything nice dies.
I can't see why people get so offended by the GPL. There is no example of an individual ever having been forced to use the GPL in a project. Somehow I still have the freedom to either a.) not use the code, b.) write my own code (perish the thought), or c.) find other code.
The LGPL is a very generous comprimise. You get protected code that you can link against, allowing you to keep your project as seperate as you wish.
Wasn't this the Wine development team's decision? Isn't that all that matters?
If *BSD were to take over the desktop that would be wonderful. However, Apple employees telling a conference that thier OSX is number one so *BSD is number one is misleading. True that you can get Darwin under the APSL, but the version that is so popular on the desktop is only available for cold hard cash.
Apple uses good code in MacOS X but it seems telling people *BSD is #1 is an attempt to keep the developer community busy working on Darwin so Apple remains the true victor.
So whats the progress of the Sorenson codec on non-OSX UNIX? How about Aqua themes? How is Apple helping me again?
Supposedly, the manufacturer reimburses the company the full cost of the items once they're destroyed.
Ah, I will bet that publishers are afraid that if leftovers aren't destroyed, the publisher would have no way of knowing if the item was paid for later on. Thats significant because I am sure companies don't want to guarantee/support something that they didn't get any revenue for.
Also, I think giving away leftovers could be thought of encouraging unpopularity. IE, hide an item so nobody can buy it. I know that happens at places like Target because Target gives employees breaks on leftovers.
I could be wrong, but what your saying would seem logical.
Talk to anyone that works in a bagel or donut shop and they will tell you that they throw away hundreds/thousands of units a week. Basically what isn't purchased is discarded. Surely we can think to give the units to the homeless/hungry/needy-cause, but there is apparently a legal reason not to do so. Perhaps fear of a lawsuit or maybe fear of propagating freeloading?
Forgive me if I am wrong about the uprades. I thought for sure they were premium, but I stand corrected.
For bang-for-your-buck, I feel Linux on x86 is hard to beat. However, PowerPC (in my opinion) is much better hardware-wise and better for reliability. OpenFirmware is much more flexible than an normal PC BIOS. The hardware holds ties to IBM and the RS line, which has generally been known to be solid.
So for my money, I will buy x86 because I feel I get better value. If I can afford to be a little more picky on hardware, I will buy SPARC. Still, if I work in a shop that only has PowerPC I will throw Linux on it.
I don't think anyone will argue that x86 is better hardware. It just isn't. I think you will find some argument on whether OSX is fit to serve.
Having choices with hardware always makes it more attractive. Some of us don't really feel that OSX is the best option for every use. For servers, I would prefer Linux over OSX due based on maturity and speed. Does anyone really want Aqua on a server?
I ran Debian Linux on a 'New World' G4. It took a little tweaking to install to bootloader but once installed, I had no other issues. Why would I put Linux on it? For one, Linux screams on PowerPC. Linux and G4s make an excellent server combo. OpenFirmware is also server-class, adding to the enterprise-nature of the hardware.
Another reason is speed and maturity. Linux has run on PowerPC for years, and is well supported. I was able to run XFree86, Enlightenment, and instant-message apps with ease. These were readily available via apt. Just about every piece of OSS/FS I was accostomed to on x86 was there.
Final reason is cost. OSX isn't free of charge and you must pay for upgrades. Im not really into piracy, so spending hundreds of Dollars on a new software didn't make much sense.
Don't get me wrong. MacOS X was very attractive and neat. However, some features/differences (netinfo or whatever its called management, GUI by default, weird / layout) didn't leave me happy with its ability to serve. OSX is great for a desktop Mac user but needs a little more time to prove its worth as a server OS.
1.) This is an Athlon bug in handling 4M pages when dealing with Intel's extended-paging.
2.) This bug becomes apparent when using Pentium-class optimizations in the kernel.
3.) I never said this was not an Athlon bug.
4.) You *will not* have this issue if you do not compile as a Pentium.
5.) Calm down and stop acting like a child/children.
Have you ever compiled a kernel?
on
2.5.4 Kernel Out
·
· Score: 2
And Athlon falls under the category "Pentium-Classic or higher Processor".
Why you threw a hissy originally is beyond me... especially over something as trivial as this argument. Go to/usr/src/linux. Type make menuconfig. The third option down is 'Processor type and features'. Within that submenu, hit 'enter' and choose 'Athlon/Duron/K7'. Athlon falls under the category 'Athlon'. You are clearly wrong. Booya grandma, booya.
You still didn't answer why I can run in AGP4x with an Athlon and 2.4.17. From the page that started it all:
However, with the introduction of the Pentium processor, Intel added a new feature called extended paging, which allows 4Mb pages to be used instead. Here's the problem -- many Athlon and Duron CPUs experience memory corruption when extended paging is used in conjunction with AGP. And, this problem hits us because Linux 2.4 kernels compiled with a Pentium-Classic or higher Processor family kernel configuration setting will automatically take advantage of extended paging (for kernel hackers out there, this is the X86_FEATURE_PSE constant defined in include/asm-i386/cpufeature.h.)
Notice the line explaining the kernel configuration? I do not compile as Pentium* therefore I do not have this issue. Nor does anyone else who follows in my footsteps. Shows over. Nothing to see here.
Looks like your no longer namecalling, so at least thats good. Perhaps you can tell my why I run 2.4.17 with an Athlon T-Bird 800 using AGP 4x? Hmm? Hint: I compiled my CPU for Athlon, which as the link I provided in my first post clearly states, was never where the issue resided. Thanks for being rude, but it wasn't needed.
Thanks for the namecalling, but your wrong.
on
2.5.4 Kernel Out
·
· Score: 2
If you download and compile a kernel for your machine, you compile for your CPU. Why would you not take advantage of processor-specific optimizations? Do you compile for the least common denominator on your own machine? Did you read the parent? Is he not compiling for his own machine?
You should *not* be having issues.
on
2.5.4 Kernel Out
·
· Score: 2
I run an AMD Athlon with an AGP4x video card on 2.4.17 with no issues whatsoever. I also compiled the kernel as an Athlon which is not affected by the issue. Gentoo describes the bug in kernels running on Athlons that were compiled for Pentiums. Pentiums builds enable 'extended paging', where the issue resides. In short: compile your kernel as an Athlon (which you should do anyway) and you will not have issues.
I compiled this into 2.4.17 with the preempt-kernel-rml-2.4.17-1 patch. When i booted i got PPP module errors, and when i tried to install the NVIDIA (2314/2313) drivers it gave me more errors. So i went back and disabled it...
Hrm... I am running that exact setup, and due to ISP/CLEC madness, I am also using PPP for connectivity. In fact, I am writing this dialed in with a 2.4.17-preempt kernel. No issues with all of the above plus a GeForce3 with the newest NVidia drivers.
So far, I have to say I am very impressed with the performance. I do notice a difference because I have taken to creating Divx;-) movies which proves to be a loborious task. I can rip a DVD and preview the.avi being created with no apparent latency with the preempt patch. Without the patch, previewing the avi is not at all realistic. Hats off to RML and Linus.
You will complain that Katz is off-topic while you probably didn't even see Collateral Damage? Just be sure to paint yourself with that same hypocritical brush for using this as a forum for expelling your anti-war views, which (I may add) are a little too much based on speculation.
Management is one reason I like SPARC so much. IE, connect a serial line to even a decade+ old Sun Pizzabox and manage via OpenPrompt. Even if the operating system is hosed you can still reach the OK prompt and reboot, or perform other tasks. Further, you can use the OK prompt to do network boots out of the box.
The Compaq cards do have an upside, however, in that the way you describe them it seems that you can foobar the 'parent' machine and still use the card. It does use power from the parent machine, so both SPARC's OpenPrompt and this card will be null if the host machine loses power.
I really wish x86 engineers would develop something similar to a server-class BIOS implementation. Don't get me wrong, modern x86 CPUs are great, but the BIOS has got to grow up.
Not insane... actually happening.
on
A Loki Timeline
·
· Score: 3, Informative
I invite you to get acquainted with an ex-Loki employee named 'Icculus' located at icculus.org. Among his famous Loki work is a port of Serious Sam, a port of the Build engine of 3dRealms/Duke Nukem/Shadow Warrior/... Not to mention hosting of former Loki technologies all for free.
We love our platform. Commercial support or not, we will make happen what we want to happen... Even if that means playing games.
What's more important, selling an item, or getting page views?
For one, none of us have access to AOL's strategy. Second, in this case they could better 'sell an item'. Their network is huge, their marketshare is monopolistic, and their public opinion isn't good among technical types. They must nurture those concerns, and trying to kill non-AOL clients will eventually complicate official AOL clients.
AOL can block clients for the time being and have more banner impressions. The competition, however, isn't stupid and will trample AOL if AOL doesn't find a better strategy with thier network.
I worked for Broadwing, and though we had some Linux for internal work, we ran Solaris for the machines in the POPs. Also, if HP were going to switch they would use their own HPUX.
It's AOL's software, AOL's servers and AOL's IM protocol. Why should they feel compelled to allow 3rd party software to access their network?
Because thats the attitude that kills companies in this market. The global economy is moving from goods to services, and that applies to software as well. AOL would better serve their revenues and public image by finding ways to get money from 3rd parties instead of trying to fight them.
Trillian is a great program. I don't use the AOL IM portion of it,...
On the one had I agree that Trillion should keep trying. That way more attention can be shed on just how childish this company can be and how if they react this way to IM clients, how will they react on larger issues that affect the public?
Conversely, why use up all of your resources reinventing somebody else's wheel?
Corel Linux was/is a desktop OS and by making that choice Corel could configure a Debian box for an intended use.
I have no qualms there. Debian is *ultra* flexible, to the point where some people think it is... gasp... difficult to install! But then most users don't feel it necessary to install via CD then be asked later where to get the packages to install. That is good, in my opinion, because you can mix all kinds of installs and media types during installation. Normal users, however, may think it is a redundant step.
For 90% of computer users Corel Linux kicked Debian's ass simply because they would never have been able to work on a Debian system (what do you mean "edit/etc/samba/smb.conf to suit my windows network", "what do you mean man 5 smb.conf"?)
This is where I disagree. Yes, Corel made certain things like installation easier but Corel gave up quickly after the distro was released. Users wanting security upgrades were up the creek. So even if users knew about security it was by no means easy to get updates from Corel.
For the parent, I will have to agree. I think that Debian-based distros have an uphill battle to fight when competing against normal Debian, but in all fairness, thats not who they compete against. The Debian developers just make a solid distro regardless of deadlines and marketing. Thats great for us knowledgeable folk, but newer users need a little more help.
More than that will live on.
on
Last Word on Loki
·
· Score: 3, Interesting
SDL is wonderful, and is evidence that Loki's existance was good for Linux as well as other platforms. But also don't forget about the Loki Installer, used by Codeweavers for the Crossover plugin (as well as RTCW, among countless others), SMPEG, OpenAL, and *free* binaries to Quake3 and Unreal Tournament. Yes, there was a time when Q3 was box-only, but Loki supported Q3 well after that point.
It brings me great sadness Loki is going. But thanks to Icculus, id Software, Loki, and all the countless volunteers we now have a much better platform.
That Linux has to kludge in a feature that Windows has had for seven years?
So basically, we are still waiting for it to be a standard feature?
What I think people should keep in mind is that you are comparing a multi-billon-dollar corporation with access to all kinds of patents and trade secrets to what *volunteers* do in their spare time. Keep in mind access to good fonts are what corporations like Microsoft and Apple *slow down* to keep people on their platforms.
If you want to stick your head out against possible liability so others can *freely* use something be my guest. At least don't criticize when others do.
* Packet Chain ProtocolTM : PCP chaining allows users to 'piggy back' a download off another user. For example, person A downloads a fileset from the host, person B will then download from person A, person C will download from Person B, etc.. This allows everyone download a show at once.
Though I am no byte-level expert, this isn't really anything new or its misleading. What this seems to refer to is how the traffic would be routed. IE, if "Joe" has live Pearl Jam and 3 people request it, the network is smart enough to take bytes from people farther along in the download. Even then, thats more load-balancing.
Otherwise, this is no different from any other P2P filesharing mechanism where files naturally propagte from a source and are eventually downloaded from other nodes. Still, if your network were *smart* enough to resend packets as little as possible (IE, if the network would multicast concurrently-requested packets) then this would be leaps-and-bounds above current P2P.
Slashdot Mirror
I would have to agree. Gentleman like Mr. Gates, Mr. Glass, and other license 'viewholders' share the common belief of corporations not being able to use GPL'ed code. They would lead us to believe a company is going to be ever-profitable and ever-wonderful, but an evil engineer slips in 'print "Hello World!\n" and all of a sudden, Capitolism, Bambi's mom, and eveything nice dies.
I can't see why people get so offended by the GPL. There is no example of an individual ever having been forced to use the GPL in a project. Somehow I still have the freedom to either a.) not use the code, b.) write my own code (perish the thought), or c.) find other code.
The LGPL is a very generous comprimise. You get protected code that you can link against, allowing you to keep your project as seperate as you wish.
Wasn't this the Wine development team's decision? Isn't that all that matters?
If *BSD were to take over the desktop that would be wonderful. However, Apple employees telling a conference that thier OSX is number one so *BSD is number one is misleading. True that you can get Darwin under the APSL, but the version that is so popular on the desktop is only available for cold hard cash.
Apple uses good code in MacOS X but it seems telling people *BSD is #1 is an attempt to keep the developer community busy working on Darwin so Apple remains the true victor.
So whats the progress of the Sorenson codec on non-OSX UNIX? How about Aqua themes? How is Apple helping me again?
Also, I think giving away leftovers could be thought of encouraging unpopularity. IE, hide an item so nobody can buy it. I know that happens at places like Target because Target gives employees breaks on leftovers.
I could be wrong, but what your saying would seem logical.
Talk to anyone that works in a bagel or donut shop and they will tell you that they throw away hundreds/thousands of units a week. Basically what isn't purchased is discarded. Surely we can think to give the units to the homeless/hungry/needy-cause, but there is apparently a legal reason not to do so. Perhaps fear of a lawsuit or maybe fear of propagating freeloading?
Forgive me if I am wrong about the uprades. I thought for sure they were premium, but I stand corrected.
For bang-for-your-buck, I feel Linux on x86 is hard to beat. However, PowerPC (in my opinion) is much better hardware-wise and better for reliability. OpenFirmware is much more flexible than an normal PC BIOS. The hardware holds ties to IBM and the RS line, which has generally been known to be solid.
So for my money, I will buy x86 because I feel I get better value. If I can afford to be a little more picky on hardware, I will buy SPARC. Still, if I work in a shop that only has PowerPC I will throw Linux on it.
I don't think anyone will argue that x86 is better hardware. It just isn't. I think you will find some argument on whether OSX is fit to serve.
Having choices with hardware always makes it more attractive. Some of us don't really feel that OSX is the best option for every use. For servers, I would prefer Linux over OSX due based on maturity and speed. Does anyone really want Aqua on a server?
I ran Debian Linux on a 'New World' G4. It took a little tweaking to install to bootloader but once installed, I had no other issues. Why would I put Linux on it? For one, Linux screams on PowerPC. Linux and G4s make an excellent server combo. OpenFirmware is also server-class, adding to the enterprise-nature of the hardware.
Another reason is speed and maturity. Linux has run on PowerPC for years, and is well supported. I was able to run XFree86, Enlightenment, and instant-message apps with ease. These were readily available via apt. Just about every piece of OSS/FS I was accostomed to on x86 was there.
Final reason is cost. OSX isn't free of charge and you must pay for upgrades. Im not really into piracy, so spending hundreds of Dollars on a new software didn't make much sense.
Don't get me wrong. MacOS X was very attractive and neat. However, some features/differences (netinfo or whatever its called management, GUI by default, weird / layout) didn't leave me happy with its ability to serve. OSX is great for a desktop Mac user but needs a little more time to prove its worth as a server OS.
Facts:
1.) This is an Athlon bug in handling 4M pages when dealing with Intel's extended-paging.
2.) This bug becomes apparent when using Pentium-class optimizations in the kernel.
3.) I never said this was not an Athlon bug.
4.) You *will not* have this issue if you do not compile as a Pentium.
5.) Calm down and stop acting like a child/children.
Why you threw a hissy originally is beyond me... especially over something as trivial as this argument. Go to
Notice the line explaining the kernel configuration? I do not compile as Pentium* therefore I do not have this issue. Nor does anyone else who follows in my footsteps. Shows over. Nothing to see here.
Looks like your no longer namecalling, so at least thats good. Perhaps you can tell my why I run 2.4.17 with an Athlon T-Bird 800 using AGP 4x? Hmm? Hint: I compiled my CPU for Athlon, which as the link I provided in my first post clearly states, was never where the issue resided. Thanks for being rude, but it wasn't needed.
If you download and compile a kernel for your machine, you compile for your CPU. Why would you not take advantage of processor-specific optimizations? Do you compile for the least common denominator on your own machine? Did you read the parent? Is he not compiling for his own machine?
I run an AMD Athlon with an AGP4x video card on 2.4.17 with no issues whatsoever. I also compiled the kernel as an Athlon which is not affected by the issue. Gentoo describes the bug in kernels running on Athlons that were compiled for Pentiums. Pentiums builds enable 'extended paging', where the issue resides. In short: compile your kernel as an Athlon (which you should do anyway) and you will not have issues.
Hrm... I am running that exact setup, and due to ISP/CLEC madness, I am also using PPP for connectivity. In fact, I am writing this dialed in with a 2.4.17-preempt kernel. No issues with all of the above plus a GeForce3 with the newest NVidia drivers.
So far, I have to say I am very impressed with the performance. I do notice a difference because I have taken to creating Divx;-) movies which proves to be a loborious task. I can rip a DVD and preview the
You will complain that Katz is off-topic while you probably didn't even see Collateral Damage? Just be sure to paint yourself with that same hypocritical brush for using this as a forum for expelling your anti-war views, which (I may add) are a little too much based on speculation.
Management is one reason I like SPARC so much. IE, connect a serial line to even a decade+ old Sun Pizzabox and manage via OpenPrompt. Even if the operating system is hosed you can still reach the OK prompt and reboot, or perform other tasks. Further, you can use the OK prompt to do network boots out of the box.
The Compaq cards do have an upside, however, in that the way you describe them it seems that you can foobar the 'parent' machine and still use the card. It does use power from the parent machine, so both SPARC's OpenPrompt and this card will be null if the host machine loses power.
I really wish x86 engineers would develop something similar to a server-class BIOS implementation. Don't get me wrong, modern x86 CPUs are great, but the BIOS has got to grow up.
I invite you to get acquainted with an ex-Loki employee named 'Icculus' located at icculus.org. Among his famous Loki work is a port of Serious Sam, a port of the Build engine of 3dRealms/Duke Nukem/Shadow Warrior/... Not to mention hosting of former Loki technologies all for free.
We love our platform. Commercial support or not, we will make happen what we want to happen... Even if that means playing games.
AOL can block clients for the time being and have more banner impressions. The competition, however, isn't stupid and will trample AOL if AOL doesn't find a better strategy with thier network.
I worked for Broadwing, and though we had some Linux for internal work, we ran Solaris for the machines in the POPs. Also, if HP were going to switch they would use their own HPUX.
Because thats the attitude that kills companies in this market. The global economy is moving from goods to services, and that applies to software as well. AOL would better serve their revenues and public image by finding ways to get money from 3rd parties instead of trying to fight them.
Aol may soon cut their nose off entirely...
On the one had I agree that Trillion should keep trying. That way more attention can be shed on just how childish this company can be and how if they react this way to IM clients, how will they react on larger issues that affect the public?
Conversely, why use up all of your resources reinventing somebody else's wheel?
This is where I disagree. Yes, Corel made certain things like installation easier but Corel gave up quickly after the distro was released. Users wanting security upgrades were up the creek. So even if users knew about security it was by no means easy to get updates from Corel.
For the parent, I will have to agree. I think that Debian-based distros have an uphill battle to fight when competing against normal Debian, but in all fairness, thats not who they compete against. The Debian developers just make a solid distro regardless of deadlines and marketing. Thats great for us knowledgeable folk, but newer users need a little more help.
SDL is wonderful, and is evidence that Loki's existance was good for Linux as well as other platforms. But also don't forget about the Loki Installer, used by Codeweavers for the Crossover plugin (as well as RTCW, among countless others), SMPEG, OpenAL, and *free* binaries to Quake3 and Unreal Tournament. Yes, there was a time when Q3 was box-only, but Loki supported Q3 well after that point.
It brings me great sadness Loki is going. But thanks to Icculus, id Software, Loki, and all the countless volunteers we now have a much better platform.
What I think people should keep in mind is that you are comparing a multi-billon-dollar corporation with access to all kinds of patents and trade secrets to what *volunteers* do in their spare time. Keep in mind access to good fonts are what corporations like Microsoft and Apple *slow down* to keep people on their platforms.
If you want to stick your head out against possible liability so others can *freely* use something be my guest. At least don't criticize when others do.
Though I am no byte-level expert, this isn't really anything new or its misleading. What this seems to refer to is how the traffic would be routed. IE, if "Joe" has live Pearl Jam and 3 people request it, the network is smart enough to take bytes from people farther along in the download. Even then, thats more load-balancing.
Otherwise, this is no different from any other P2P filesharing mechanism where files naturally propagte from a source and are eventually downloaded from other nodes. Still, if your network were *smart* enough to resend packets as little as possible (IE, if the network would multicast concurrently-requested packets) then this would be leaps-and-bounds above current P2P.