The Cubs have not won the World Series and Duke Nukem 3D hasn't been released.
They didn't tell you? It has been released, even the source code... and there's also a Linux version! Now I just can't wait for this new Quake game from id, it must be even better than Doom 2!
And when he says that "component video (...) separates the video across red, green and blue" he probably meant YCrCb luminance-chrominance signals (unless the device has a SCART interface as well, which doesn't seem to be the case).
The point is, even though you and I know that a database and a web browser are two different things, Google doesn't.
Maybe google doesn't know the difference, but Vivissimo does. It clusters the results into categories like Mozilla, Pontiac, Database, and Paragliding, among others.
I'm playing it with Sarien (CVS version) and found two bugs:
Message boxes when talking to the tree
Restoring savegames when you're dead doesn't work very well (sometimes you need to restart the interpreter).
I'm investigating the savegame restore problem, I'll submit a patch soon. Other than that, the game seems to play very well (right now I'm on Mitos 15 with 83 of 101 points.)
In Brazilian portuguese, it's a slang term for "sissy" or "effeminate". The original meaning is "fresh", like in "fresh air".
This page contains an excerpt from Beyond Carnival by James N. Green and tells more about the term. I won't reproduce the text here, or I'll be sent to the Camp of Tolerance. (Hail Lemmiwinks the Gerbil King!)
It is compatible with all existing Amiga software.
Note that certain applications such as demos or games actually execute on UAE. According to the MorphOS overview page, they "believe that UAE is good enough to provide the functionality for applications that demand very true custom chip hardware emulation. Demos and Games are programs that are outdated very fast and they don't play such an important role to set the direction of future OS development", so no Protracker and Technological Death running in native mode. I wonder what happens with games/demos that require AGA?
Everaldo is a pro working in Linux themes and art and is IMHO doing a great job. Crystal was originally written by Everaldo as a custom KDE theme for the Conectiva linux distro, and later published under an open license. Everaldo also made the "big eight" wallpaper for Conectiva (also used by Mandrake 8 and others) and IIRC part of the YaST art for SuSE. His latest artwork is the "steel donut" theming for KDE and YaST in Conectiva's UnitedLinux-based distro.
Apple has an interesting pricing system. From the page you linked, we learn that it costs $799 with 128MB, $874 with 256MB and $1024 with 512MB, and for $40 you can "get twice the RAM".
In my opinion, what we really need is a single, standard package system for all linux-based distros. Chuck rpm, chuck deb, chuck them both and create a new one incorporating the best features of both, I don't care, but I think it really needs to be done.
I've said that before and I apologize to repeat myself, but I must insist in the fact that most people don't seem to understand the difference between mechanism and policy in package management. The package manager offers a mechanism, the distribution enforces policy.
That said, having a common package tool for all distributions wouldn't help. You can say most distros today standardized on rpm, but the packages are largely non-compatible because there's no common policy between them.
One of the policy rules could be, for example: "all runtime libraries must be packaged separately, and named differently according to binary compatibility". It makes sense, it works, Debian does that, Conectiva (which uses apt-get) does that, I think PLD and Mandrake are doing that. But for other distros it would mean a massive package layout change, and I doubt they would like to to that.
(The reason for that rule is: if you upgrade a binary that needs a new version of a library that breaks binary compatibility with the previous versions, other binaries can still use the old library.) Before you say anything, the rpm ability to keep multiple version of a package installed is largely useless for this case doesn't help here.
> I would just put a title at the top of it saying: > >"Why to use apt-get:"
The dependency mess is one of the reasons we had to add rpm support to apt. But if your package dependencies are really bad, just throwing apt in won't help much. In fact, you must build you packages based on a consistent policy in order to make apt work properly. Debian relies strongly on its policy because doing that you ensure that apt will work correctly later, it's not apt that magically fixes a bad packaging layout.
I maintain an RPM-based distribution and I can say that it took a long time to fix our package base in such a way that apt can work smoothly. And the real problem caused by a bad dependency layout is not on package installation, but in package upgrades. (Imagine two different hairy graphs and you must convert from one graph to the other without breaking anything.)
I would call it "why you need a good packaging policy". Once you implement it, apt will work as a consequence.
Just because rpm packages have the same name, it's not the "same package". Note that rpm is only a way to deploy software, think "tar with metadata" (or cpio, in this case). It's purpose is to offer a mechanism, the packaging politics is entirely up to the distribution.
It's a common mistake to imagine rpm packages as a big, uniform package base serving all distributions that use the format. It isn't. Each vendor can package software in a different way, built with different options and with different dependecies. Some distributions based on rpm are even migrating to a packaging layout more similar to Debian than Red Hat (e.g. libfoobar2 instead of foobar-libs).
So the answer is yes, you must have a different graph for each vendor.
As a side note, I've done that before using Gustavo Niemeyer's depmanager. If you don't work with a very restrict set of packages, the graph becomes very, very dense and confuse. But it's good to find dependency errors.
The Arecibo reply crop formation in Chibolton was one of the most interesting "crop circles" out there. Basically it's a 23x73 grid with "pixels" similar to the Arecibo message but with "alien" information instead of human. Very creative! (I'd say it's a great example of geek humour.)
The differences are: silicon added to the list of atomic numbers, different DNA and nucleotides, different "stick figure" and stats, other planets highlighted in the solar/star system and a completely different transmitter.
Slashdot Mirror
And when he says that "component video (...) separates the video across red, green and blue" he probably meant YCrCb luminance-chrominance signals (unless the device has a SCART interface as well, which doesn't seem to be the case).
I wonder if this version of Quake can be played using CABAL...
- Message boxes when talking to the tree
- Restoring savegames when you're dead doesn't work very well (sometimes you need to restart the interpreter).
I'm investigating the savegame restore problem, I'll submit a patch soon. Other than that, the game seems to play very well (right now I'm on Mitos 15 with 83 of 101 points.)There is a version of Sarien for PalmOS devices -- has anyone tested it with SQ0?
Let's play roshambo for it!
This page contains an excerpt from Beyond Carnival by James N. Green and tells more about the term. I won't reproduce the text here, or I'll be sent to the Camp of Tolerance. (Hail Lemmiwinks the Gerbil King!)
Indeed. It will probably look great with a chicken cooking screensaver.
Note that certain applications such as demos or games actually execute on UAE. According to the MorphOS overview page, they "believe that UAE is good enough to provide the functionality for applications that demand very true custom chip hardware emulation. Demos and Games are programs that are outdated very fast and they don't play such an important role to set the direction of future OS development", so no Protracker and Technological Death running in native mode. I wonder what happens with games/demos that require AGA?
Everaldo is a pro working in Linux themes and art and is IMHO doing a great job. Crystal was originally written by Everaldo as a custom KDE theme for the Conectiva linux distro, and later published under an open license. Everaldo also made the "big eight" wallpaper for Conectiva (also used by Mandrake 8 and others) and IIRC part of the YaST art for SuSE. His latest artwork is the "steel donut" theming for KDE and YaST in Conectiva's UnitedLinux-based distro.
I can see it turning about three axis and moving along one of the axis (for clicks), giving four DOF. Where is the fifth dimension?
Apple has an interesting pricing system. From the page you linked, we learn that it costs $799 with 128MB, $874 with 256MB and $1024 with 512MB, and for $40 you can "get twice the RAM".
(Taa-dada-dada dada-dada Bork! Bork! Bork!)
Poot ell zee ingredeeunts intu a cesserule-a deesh, preheet oofee tu ges merk 9. Vhee reedy plece-a cesserule-a deesh intu oofee und leefe-a unteel bleck ecreed smuke-a cumes oooot ooff zee oofee. It Fueela, yuoor DNA 'boorned' oontu a CD.
A neece-a keep seke-a fur yeers tu cume-a! Und es Neegella Levsun vuoold sey, "Ebsulootely Scroompteeuoos"!
Bork Bork Bork!
Of course, the only real solution for this case is to build a city wall. (Someone call the City Wok guy please.)
I've said that before and I apologize to repeat myself, but I must insist in the fact that most people don't seem to understand the difference between mechanism and policy in package management. The package manager offers a mechanism, the distribution enforces policy.
That said, having a common package tool for all distributions wouldn't help. You can say most distros today standardized on rpm, but the packages are largely non-compatible because there's no common policy between them.
One of the policy rules could be, for example: "all runtime libraries must be packaged separately, and named differently according to binary compatibility". It makes sense, it works, Debian does that, Conectiva (which uses apt-get) does that, I think PLD and Mandrake are doing that. But for other distros it would mean a massive package layout change, and I doubt they would like to to that. (The reason for that rule is: if you upgrade a binary that needs a new version of a library that breaks binary compatibility with the previous versions, other binaries can still use the old library.) Before you say anything, the rpm ability to keep multiple version of a package installed is largely useless for this case doesn't help here.
>
>"Why to use apt-get:"
The dependency mess is one of the reasons we had to add rpm support to apt. But if your package dependencies are really bad, just throwing apt in won't help much. In fact, you must build you packages based on a consistent policy in order to make apt work properly. Debian relies strongly on its policy because doing that you ensure that apt will work correctly later, it's not apt that magically fixes a bad packaging layout.
I maintain an RPM-based distribution and I can say that it took a long time to fix our package base in such a way that apt can work smoothly. And the real problem caused by a bad dependency layout is not on package installation, but in package upgrades. (Imagine two different hairy graphs and you must convert from one graph to the other without breaking anything.)
I would call it "why you need a good packaging policy". Once you implement it, apt will work as a consequence.
> the packaging politics is entirely up to the distribution.
That should be "packaging policy". Yeah, I know, preview, yadda yadda.
It's a common mistake to imagine rpm packages as a big, uniform package base serving all distributions that use the format. It isn't. Each vendor can package software in a different way, built with different options and with different dependecies. Some distributions based on rpm are even migrating to a packaging layout more similar to Debian than Red Hat (e.g. libfoobar2 instead of foobar-libs).
So the answer is yes, you must have a different graph for each vendor.
As a side note, I've done that before using Gustavo Niemeyer's depmanager. If you don't work with a very restrict set of packages, the graph becomes very, very dense and confuse. But it's good to find dependency errors.
No, it will run FlyBSD. Or FlyRIX. Maybe even BeeOS, but it was discontinued.
*runs*
There are spy flies in PKD's book A Maze of Death (which, along with Ubik, seems to have inspired the Matrix movie as well).
The differences are: silicon added to the list of atomic numbers, different DNA and nucleotides, different "stick figure" and stats, other planets highlighted in the solar/star system and a completely different transmitter.