This $200 box does not have a NVidia GeForce4 bundled. I guess this is a very compealing reason to hack a XBox.:-)
No, but at the time they get the closed source binary NVidia drivers to play well on the modified GeForce4 chip in the XBox, the GeForce4 will be old and cheap!
Is this just YAGBB (Yet Another Gecko Based Browser) or will this be the start of a modularization of the Mozilla browser???
I am a happy user of Mozilla, but i dislike the monolithic approach of integrating browser, mailreader, newsreader, composer and you name it into one executable. What happened to the old and proven Unix approach of "Do only one thing, but do it well!"?
I hope Mozilla in the future will be split into a suite of components, that work well together and with a consistent interface.
Yes, you are right about the constant. But for a O(1) algorithm the constant is just that - a constant! So for a data set of arbitrary size the complexity or time to execute will be - constant!
This is like when you look up in an array with a pointer - it will take the same time no matter the data size.
For a linear function the complexity will be O(n) as the previous poster said. Just like when you want to get an arbitrary element in a linked list for example.
For an O(1) scheduler the tradeoff may be larger initial overhead (for few processes) or increased memory usage (for table lookups) or just a plain smarter algorithm:-)
I'm not sure how I would feel about being forced into 1600x1200 all the time.
I would feel good! Finally an LCD screen with a usable resolution. The resolution should preferrably be as high as possible. If you can't read the text then choose a larger font.
If you are into fast action games you should probably buy a CRT anyway.
Instead of Kazaa et al I have switched to Gnucleus. This is one of the only real Open Source Gnutella network clients for Windows. For Linux there are so many great Open Source Gnutella clients.
It works great. No spyware or addware, and since the Gnutella network is an open P2P network it can be expected to exist when all the other proprietary networks have been closed.
The problem is that the Linux kernel is currently missing a retrace interrupt counter...
The Amiga had a vertical refresh interrupt - actually you could even synchronize to an arbitrary (x,y) coordinate on the screen via the "copper" co-processor.
Some of the SGI graphics boards actually had an input jack called "genlock" into which you plugged a video signal... This meant that the graphics signal was perfectly in sync with other equipment in the facility and so could be "mixed" with other signals in the facility.
A "genlock" could be bought for the Amiga as an accessory for very little money (~100$ or so).
The Amiga was very well adapted to television display. So much that the CPU clock frequency was some multiple of the horizontal scan frequency of either PAL or NTSC! This made for incredibly smooth graphics on a standard television, and so with an Amiga you actually had a very cheap system for generating title screens etc. for your homevideo. And this was more than 10 years ago! Actually i believe that some of the cable companies here in Denmark are still using an Amiga for generating their "info channels".
Yes you are trolling! Especially since the original poster could not get the quote right.
Linus wrote: "...Which, btw, explains why I don't consider you a kernel maintainer, Rik,..."
See for yourself!
The reason was that Rik didn't care about everybody else if his bugfixes were not applied. Would YOU like a maintainer that didn't care about the rest of the world?
"I would tell Linus to fuck off"... who is being immature now?
I think you are right that Linus could probably have taken more patches from Rik than he did.
On the other hand you could argue, that too many patches are a sign of the VM not being stable enough. Therefore the VM should probably be matured in a seperate tree (as Rik himself suggests) instead of flooding Linus with bugfixes and tweaking. Then when the VM is stable and can be proven to perform better I am sure even Linus can be persuaded.
And yes a one man control system IS lossy but that is not a bug but a feature - because it ensures consistensy. In every project of this scale coordination is essential and the individual developers MUST be more thorough with their work before comitting it!!!
I think it was an excellent decision of Linus to remove Rik's VM from the mainline kernel. If not for technical reasons then for political reasons.
Rik's VM obviously needed to be fixed and/or tuned, but apparently lacked the necessary attention from Rik. If Linus had not removed the VM, it would probably have been the situation for a while. Instead we now have TWO VM's which are rather stable and Rik working full speed to make his VM the best.
Competition is good! Which VM will be the best for the future will be determined by Survival Of The Fittest(tm)
It can be argued though, that it was not the right time during 2.4, but Andreas VM seemed to stabilise rather quick with the high level of attention to the problem. Sometimes it takes drastic measures to get results...
Most./ readers seem to think that it is all about Servers vs. The Desktop.
I can safely say: IT IS NOT!!!
For a great deal of embedded applications it is a necessity to have lower and deterministic latency. Therefore these patches will raise the acceptance of Linux as an alternative embedded OS.
I guess it will be a long time though before Linux itself will have REALLY low (microseconds) latencies and hard real time behaviour. Right now this can only be achieved with addons like RTAI or RTLinux.
The RTAI and RTLinux addons are really real time schedulers that run the Linux kernel as lowest priority thread. This gives an added complexity for the real time programmer. But maybe this "sandbox" approach is really a good thing and the way to go for hard real time, as it will be almost impossible to guarantee hard real time with a complex beast like the Linux kernel.
But for many applications the latency and quality of service you can get with the patched kernel will probably be enough - so keep up the good work!!!:-)
...the original version was less than 16k compiled and out-performed DivX and was patent and copyright free.
Be sure to protect your ideas by either patenting them yourself or just by publicising them. As long as you have not yet publicised the codec and shown "prior art", someone else may beat you to it and patent the idea!
Then the project would surely be dead - so get it out in the light!
We have a finished product, but don't quite know what to do with it.
Not to be (overly) sarcastic, but maybe you should have thought of that before spending first your investors money and then your own? Isnt it a little late for that now?
MAGIC can transfer digitized sound without (excessive) jitter and latency like AES/EBU. But AES/EBU can only transfer a single stereo channel in 24 bit/92kHz whereas MAGIC can transfer 32 channels in 32 bit/192kHz!
MIDI only transfers information like notes, volume etc. Not the digitized sound itself. This enables you to connect a MIDI keyboard with a synthesizer and produce sound, but NOT to transfer digitized sound from e.g. a guitar to an amplifier or DAT.
The spec. for MAGIC allows for sending control packets containing MIDI information though. Therefore it can ultimately replace BOTH MIDI and AES/EBU etc.
When a piece of code is GPL'ed it can NEVER be closed source again. This is why several companies are using a dual/triple license trick to allow them to close the source under the other license. This is for example how Mozilla (MPL) and the Qt (QPL) library is developed.
But as long as the code is under the GPL it can always be forked.
What i cannot comprehend is how external contributions to the GPL'ed source can be embraced by the other incompatible licenses in this scheme???
NSPR is used in the Mozilla browser for x-platform threads and network/file I/O. It should basically cover all your needs, besides serial port I/O i guess.
You may have a look at their homepage: http://www.mozilla.org/projects/nspr/
You missed the 8088, which is important because it was the chip used in the first IBM PCs. It was actually a cost reduced version of the 8086, where the external databus was reduced from 16-bit to 8-bit in exchange for lower performance.
It is also slightly incorrect to list 386DX and 386SX as completely different processors, as the 386SX is just a cost reduced 386DX with the external databus reduced from 32-bit to 16-bit. (AFAIK the DX came before the SX).
The same is true of the 486 family, as the SX was a cost reduced version of the DX, missing the FPU. The DX2 and DX4 was a DX with a core frequency multiplier of 2x and 3x (Yes, marketing bluff!) respectively.
We're quickly moving back to the old notion of city-states with their own conflicting sets of laws.
Au contraire! The EU has its foundation in removing barriers of trade (primarily in Europe of course..). And the borders are getting less visible for every year.
You may also say, that removing barriers of trade is all about securing a healthy competition on a larger scale in a smaller world. This is exactly the same reason for which you have laws against monopolies - to secure a healthy competition.
Well, there is still one important issue left with KDE. The Qt library is released under a GPL license as opposed to the LGPL license for GTK+. This prohibits developers of commercial (non-GPL) applications from using the Qt library and therefore developing for KDE without paying royalties to TrollTech.
This might not be an issue for the OpenSource community, but it sure is an issue for all the companies that have to make a living. This is why companies like SUN, HP etc. has chosen GNOME as their next desktop.
Just my two bits "01" - It's a fact, like it or not.
Slashdot Mirror
AltaVista has actually had a "lite" version without the heavy commercial portal thingie for quite some time.
The link is/was: www.raging.com
But now I can see it has changed to point to the same renewed interface as www.altavista.com.
No, but at the time they get the closed source binary NVidia drivers to play well on the modified GeForce4 chip in the XBox, the GeForce4 will be old and cheap!
Is this just YAGBB (Yet Another Gecko Based Browser) or will this be the start of a modularization of the Mozilla browser???
I am a happy user of Mozilla, but i dislike the monolithic approach of integrating browser, mailreader, newsreader, composer and you name it into one executable. What happened to the old and proven Unix approach of "Do only one thing, but do it well!"?
I hope Mozilla in the future will be split into a suite of components, that work well together and with a consistent interface.
Yes, you are right about the constant. But for a O(1) algorithm the constant is just that - a constant! So for a data set of arbitrary size the complexity or time to execute will be - constant!
:-)
This is like when you look up in an array with a pointer - it will take the same time no matter the data size.
For a linear function the complexity will be O(n) as the previous poster said. Just like when you want to get an arbitrary element in a linked list for example.
For an O(1) scheduler the tradeoff may be larger initial overhead (for few processes) or increased memory usage (for table lookups) or just a plain smarter algorithm
I'm not sure how I would feel about being forced into 1600x1200 all the time.
I would feel good! Finally an LCD screen with a usable resolution. The resolution should preferrably be as high as possible. If you can't read the text then choose a larger font.
If you are into fast action games you should probably buy a CRT anyway.
Instead of Kazaa et al I have switched to Gnucleus. This is one of the only real Open Source Gnutella network clients for Windows. For Linux there are so many great Open Source Gnutella clients.
It works great. No spyware or addware, and since the Gnutella network is an open P2P network it can be expected to exist when all the other proprietary networks have been closed.
- Disclaimer: This is a nostalgic trip ;-)
... This meant that the graphics signal was perfectly in sync with other equipment in the facility and so could be "mixed" with other signals in the facility.
The problem is that the Linux kernel is currently missing a retrace interrupt counter...
The Amiga had a vertical refresh interrupt - actually you could even synchronize to an arbitrary (x,y) coordinate on the screen via the "copper" co-processor.
Some of the SGI graphics boards actually had an input jack called "genlock" into which you plugged a video signal
A "genlock" could be bought for the Amiga as an accessory for very little money (~100$ or so).
The Amiga was very well adapted to television display. So much that the CPU clock frequency was some multiple of the horizontal scan frequency of either PAL or NTSC! This made for incredibly smooth graphics on a standard television, and so with an Amiga you actually had a very cheap system for generating title screens etc. for your homevideo. And this was more than 10 years ago! Actually i believe that some of the cable companies here in Denmark are still using an Amiga for generating their "info channels".
Doooh!
Yes you are trolling! Especially since the original poster could not get the quote right.
..."
... who is being immature now?
Linus wrote: "...Which, btw, explains why I don't consider you a kernel maintainer, Rik,
See for yourself!
The reason was that Rik didn't care about everybody else if his bugfixes were not applied. Would YOU like a maintainer that didn't care about the rest of the world?
"I would tell Linus to fuck off"
I think you are right that Linus could probably have taken more patches from Rik than he did.
On the other hand you could argue, that too many patches are a sign of the VM not being stable enough. Therefore the VM should probably be matured in a seperate tree (as Rik himself suggests) instead of flooding Linus with bugfixes and tweaking. Then when the VM is stable and can be proven to perform better I am sure even Linus can be persuaded.
And yes a one man control system IS lossy but that is not a bug but a feature - because it ensures consistensy. In every project of this scale coordination is essential and the individual developers MUST be more thorough with their work before comitting it!!!
I think it was an excellent decision of Linus to remove Rik's VM from the mainline kernel. If not for technical reasons then for political reasons.
Rik's VM obviously needed to be fixed and/or tuned, but apparently lacked the necessary attention from Rik. If Linus had not removed the VM, it would probably have been the situation for a while. Instead we now have TWO VM's which are rather stable and Rik working full speed to make his VM the best.
Competition is good! Which VM will be the best for the future will be determined by Survival Of The Fittest(tm)
It can be argued though, that it was not the right time during 2.4, but Andreas VM seemed to stabilise rather quick with the high level of attention to the problem. Sometimes it takes drastic measures to get results...
Most ./ readers seem to think that it is all about Servers vs. The Desktop.
:-)
I can safely say: IT IS NOT!!!
For a great deal of embedded applications it is a necessity to have lower and deterministic latency. Therefore these patches will raise the acceptance of Linux as an alternative embedded OS.
I guess it will be a long time though before Linux itself will have REALLY low (microseconds) latencies and hard real time behaviour. Right now this can only be achieved with addons like RTAI or RTLinux.
The RTAI and RTLinux addons are really real time schedulers that run the Linux kernel as lowest priority thread. This gives an added complexity for the real time programmer. But maybe this "sandbox" approach is really a good thing and the way to go for hard real time, as it will be almost impossible to guarantee hard real time with a complex beast like the Linux kernel.
But for many applications the latency and quality of service you can get with the patched kernel will probably be enough - so keep up the good work!!!
The biggest problem with KDE (IMHO) is the unresponsive feeling - especially when starting up programs. Are there any changes to this in KDE 3.0?
I know it is mainly something about a compiler/linker issue, but what is the progress in that area?
...the original version was less than 16k compiled and out-performed DivX and was patent and copyright free.
Be sure to protect your ideas by either patenting them yourself or just by publicising them. As long as you have not yet publicised the codec and shown "prior art", someone else may beat you to it and patent the idea!
Then the project would surely be dead - so get it out in the light!
We have a finished product, but don't quite know what to do with it.
;-)
Not to be (overly) sarcastic, but maybe you should have thought of that before spending first your investors money and then your own? Isnt it a little late for that now?
Just a thought!
Given that Microsoft percieves Linux as Threat Number One one can't stop wonder what Microsofts hidden agenda is.
Why will Microsoft silently allow Mono or even collaborate?
But more along the line of AES/EBU or SPDIF.
MAGIC can transfer digitized sound without (excessive) jitter and latency like AES/EBU. But AES/EBU can only transfer a single stereo channel in 24 bit/92kHz whereas MAGIC can transfer 32 channels in 32 bit/192kHz!
MIDI only transfers information like notes, volume etc. Not the digitized sound itself. This enables you to connect a MIDI keyboard with a synthesizer and produce sound, but NOT to transfer digitized sound from e.g. a guitar to an amplifier or DAT.
The spec. for MAGIC allows for sending control packets containing MIDI information though. Therefore it can ultimately replace BOTH MIDI and AES/EBU etc.
When a piece of code is GPL'ed it can NEVER be closed source again. This is why several companies are using a dual/triple license trick to allow them to close the source under the other license. This is for example how Mozilla (MPL) and the Qt (QPL) library is developed.
But as long as the code is under the GPL it can always be forked.
What i cannot comprehend is how external contributions to the GPL'ed source can be embraced by the other incompatible licenses in this scheme???
NSPR is used in the Mozilla browser for x-platform threads and network/file I/O. It should basically cover all your needs, besides serial port I/O i guess.
You may have a look at their homepage: http://www.mozilla.org/projects/nspr/
You missed the 8088, which is important because it was the chip used in the first IBM PCs. It was actually a cost reduced version of the 8086, where the external databus was reduced from 16-bit to 8-bit in exchange for lower performance.
It is also slightly incorrect to list 386DX and 386SX as completely different processors, as the 386SX is just a cost reduced 386DX with the external databus reduced from 32-bit to 16-bit. (AFAIK the DX came before the SX).
The same is true of the 486 family, as the SX was a cost reduced version of the DX, missing the FPU. The DX2 and DX4 was a DX with a core frequency multiplier of 2x and 3x (Yes, marketing bluff!) respectively.
Kernel.org is running a VArServer 700 with a total of 400 GB of storage on a 100 Mbit/s line.
The OS is Linux with an Apache Webserver.
This is all according to http://www.kernel.org/powered.html. So the server is NOT running Windows and IIS as some (stupid) AC posted here!
No information about kernel version though....
TBL is absolutely right. The foundation for a free Internet is standard compliance. But where are we when not even Slashdot is W3C HTML compliant???
I tried to validate it at validator.w3c.org, but I got more than 600 errors!
Try for yourself
No Goat is hidden here
"If you fellas don't like the way we do business, we can go back to Seattle."
Heh, you make it sound like it is a threat....
We're quickly moving back to the old notion of city-states with their own conflicting sets of laws.
Au contraire! The EU has its foundation in removing barriers of trade (primarily in Europe of course..). And the borders are getting less visible for every year.
You may also say, that removing barriers of trade is all about securing a healthy competition on a larger scale in a smaller world. This is exactly the same reason for which you have laws against monopolies - to secure a healthy competition.
Well, there is still one important issue left with KDE. The Qt library is released under a GPL license as opposed to the LGPL license for GTK+. This prohibits developers of commercial (non-GPL) applications from using the Qt library and therefore developing for KDE without paying royalties to TrollTech.
This might not be an issue for the OpenSource community, but it sure is an issue for all the companies that have to make a living. This is why companies like SUN, HP etc. has chosen GNOME as their next desktop.
Just my two bits "01" - It's a fact, like it or not.