That doesn't work for bubblegum acts like Britney and boy bands and bubblegum acts seem to be where most of the money is. That isn't the only problem the talent pool capable of consistently producing albums where every song is good even if not related to each other is small. If we're talking concept albums where the songs are thematically related then the talent pool is smaller still. And the audience for such is discriminating and won't buy just any old crap you're shoveling.
Whooooooooosh! They can digest it but corn is much "richer" than what they should be eating. Cows are ruminants which means their digestive tracts are optimized for mostly cellulose things like grasses and their stomachs are almost pH neutral. A corn diet drives them into acidosis that causes problems with sores in their digestive tracts. The sores make them susceptible to illness so they also require antibiotics.
I wouldn't call it ear rape but I surely got tired of their top-40 hits years ago. But then the sad state of American broadcast radio is another rant entirely.
I seriously doubt Apple is going pepper unbypassable ads all through the iPhone interface. More than likely they are blue-skying their own take on Hulu or some other optional video service. So if one doesn't use the ad-supported features then the ads won't be seen. I also suspect that Apple will be happy, more than happy, to license this patent under less than draconian terms to other content providers. So the iPhone won't be rendered a banner ad flashing brick and the idea won't be safely locked up in such a way that any other phone becomes an oasis from it.
Umm. Apparently one could still develop in machine code for the C-64 and this emulator would execute that. And that is far more fertile ground for breaking out of the sandbox and attacking the emulator and then iPhone itself (yes, yes, it isn't a GREAT attack vector but work with me here.....). Of course they could require signing the C-64 binaries but then what would be point? You may as well re-implement the C-64's Greatest Hits in native code for the phone itself.
Printing works on the newest builds of google-chrome and chromium-browsrer but it can be buggy. It seems to get a little bit better steadily as more releases come out.
I think he means applications where Linux or a BSD is the primary development environment and those APIs were the target. Agreed it is a sloppy use of "native". In the case of Firefox, XP is a the primary dev environment and it also benefits from Profile Guided Optimizations when compiled. The Linux port could in principle but the work hasn't been done (and probably won't be).
So now I just skip any of the scanners and opt for a pat down. It slows down security, it appears to make them uncomfortable, and if I'm lucky it'll be someone attractive patting me down.
In IBM's terms, the money involved for them to litigate SCO isn't terribly substantial. However, the damage they did to IBM's reputation and some of IBM's investments wasn't trivial. SCO has even claimed to be able to terminate IBM's rights in AIX. IBM isn't after a quick end to the litigation. They are after vindication and making an example out of SCO to deter any other pipsqueaks from peeing in their Wheaties. Buying them out even at this late degraded date only rewards them.
Given how they wanted to feed off the hard work of Linux developers, companies, and users my method of choice would a stake through the heart in the center of a crossroads just prior to daybreak.
I followed and read that. It is one of the most stupid things I've ever read in my life. 4Front believes they can restrict the use of OSS4 on Linux only to GPL apps. In their view, if you fire up Doom3 and play the sound through OSS4 then you are in "violation the terms we choose to distribute under". They furthermore believe they can impose this restriction in addition to the GPL. Even RMS doesn't have such an expansive idea of what incurs GPL restrictions. Come to think of it, the GPL goes to some length to explain that restrictions only apply to distribution and not to mere use at all.
I can't see that anyone other than a paying 4Front customer who has accepted a proprietary EULA has any rights to use OSS4 at all. Their public statements + GPL would not appear to be a viable license to either use or distribute.
There are more and less correct ways to go about running "non-stable" packages. Just jamming in a foreign binary deb and it's deps is generally the wrong way to do it. The right way to do it is to basically do what backports.org does....and check if backports has it first. If you're not running a Debian derivative then research the equivalent for your distro or BSD flavor:
1. add an apt-src line from the "non-stable" distro. I've even done this when Ubuntu had the latest SpamAssassin and I wanted a late model debianized SpamAssassin. Note well I said "apt-src" and NOT an "apt" line. apt-get update, yadda yadda
2. mkdir package-of-interest; cd package-of-interest; apt-get build-dep package-of-interest. If you're lucky this pulls in everything needed to build the package. If not you'll have to recurse with apt-get build-dep package-of-interest-newer-dependency; apt-get source package-of-interest-newer-dependency and come back to step 2 until you have everything you need to build your "non-stable" package.
4. cd package-of-interest-version; fakeroot dpkg-buildpackage -b. If all goes well a backport of the newer software that is built against your nice stable distro's libraries will be built one directory level up.
5. If you had to build a newer library your package needs install it then go back to #2. rinse and repeat until you have your newer software. Myself, I'll build one or two before giving it up as a bad job. Generally I succeed at this. Bread and butter stuff like Clamav and SpamAssassin that is well behaved tends to work well with this procedure.
The point of this is to avoid having to replace heeby jeeby inducing things like glibc, libstdc++, or even Perl since half your system scripts depend on such things. You avoid replacing packages that are contributing to the stability of the rest of the system and that are still getting critical bug and security updates. It keeps the "foreign" footprint to a middle and gives you a "foreign" package that is more or less compliant with the rest of the system.
The patent nastiness was only a month or two ago. I'm not judging MS on what they might do or on what their PR says about being chummy with Open Source. Their actions lately are consistent with a history of hostile actions. If MS accumulates a long long of positive actions while refraining from negative ones my mind will change about them. But until they actually do I maintain that mistrust of MS is reasonable. Note well that I'm not unwilling to change my mind about MS but I currently see no reason to do so.
The leadership of MS is on record as calling FOSS Un-American, a cancer, and other pejoratives. Their leadership has also been caught red-handed more than once attempting to sabotage FOSS. The recent nastiness with the anti-Linux patent package intended for troll use comes to mind. The actions of MS' leadership are far more relevant than the fact a few coders in cubicles don't bear FOSS any particular ill will. Now I don't hate MS but distrusting MS isn't in the least unreasonable.
I don't know how much I buy that. Game engines and other such plumbing works well enough but even fan generated content for most games relies hugely on resources supplied by the base game. I've been watching attempts to replace the base wads and paks that are supplied with even super old stuff like Doom and Quake. The goal of those projects is a complete replacement that would allow among other things existing fan generated content to run. None have been complete enough to do this. There is an awful lot of artistic scutwork that has to go into making large games work these days and FOSS communities only seem to go so far in producing it.
I can see small original even innovate things being done on PCs but big productions that contain DVDs worth on content are only going to come out on the platforms the majors want to support. I'd love to be proven wrong on this but.....
I have EEE PC 4G that can boot to a Debian Sid LXDE desktop in less than 30 seconds. Maybe even twenty though I haven't bothered to time it. I can tell you that the OS boot takes only slightly longer than the BIOS to load and initialize. Efforts to lower "real world" Linux boot times ARE paying off.
The Twilight Hack has been obsoleted by System Updates; if the Homebrew channel or other loader was installed then updates didn't remove it. Nonetheless, the Twilight Hack won't work on a Wii that is patched up current. The current exploit du jour is Bannerbomb; it doesn't require a copy of Twilight Princess and works even on current versions of the System Menu.
I will say this for a well exploited Wii. I can select any title that I own from a menu and play it without getting up to change discs as all the titles I own have been ripped to a USB hard drive. Nintendo and the other consoles should have enabled something like that from the get go. I have no problem with serializing such a scheme so that your rips won't work on another console. It should also be possible to do something to distinguish rental titles so that one can't compile a library super cheap from GameFly.
I haven't touched physical media for years for music. This will soon be true of my video as well. And I would like that to continue to be true of any console gaming I do as well. If the console makers don't step up, I'll go with the thoroughly pwned consoles where homebrewers have.
I think he's advocating morals based on reason. Reason doesn't mean some form of social darwinism. It means that we have a solid ethical foundation behind the morals that have been thought out. Many morals boil down to "Because it's always been that way!". At one time owning a slave was a perfectly moral act. It took questioning that to end slavery in many places and that was an act of reason.
In the case of Turing, the morals of others justified grievous injury. It is reason that gives us the capacity to judge the morals themselves.
Everyone knew it was a 32-bit 68000 CPU - same thing that ran the five-year-old Sega Genesis and the 10 year old Macintosh or Amiga. The Jaguar has a better GPU, but that was its only advantage over those other machines.
The 68000 was over relied on. Some of the better and homebrew titles only use it for io and initialization purposes. It is indeed possible to create code for the machine that is mostly being executed by 64 bit parts using 64 bit pathways. But then the dev tools didn't lend themselves easily to that style of programming and the finer points of relying mainly on the Jaguar's chipset weren't truly appreciated until after the death of the console. So it's still Atari's fault.
Slashdot Mirror
That doesn't work for bubblegum acts like Britney and boy bands and bubblegum acts seem to be where most of the money is. That isn't the only problem the talent pool capable of consistently producing albums where every song is good even if not related to each other is small. If we're talking concept albums where the songs are thematically related then the talent pool is smaller still. And the audience for such is discriminating and won't buy just any old crap you're shoveling.
That's why I go around randomly shooting people in the face. But the big fun is spraying a dojo down with a BAR.
Whooooooooosh! They can digest it but corn is much "richer" than what they should be eating. Cows are ruminants which means their digestive tracts are optimized for mostly cellulose things like grasses and their stomachs are almost pH neutral. A corn diet drives them into acidosis that causes problems with sores in their digestive tracts. The sores make them susceptible to illness so they also require antibiotics.
I wouldn't call it ear rape but I surely got tired of their top-40 hits years ago. But then the sad state of American broadcast radio is another rant entirely.
I seriously doubt Apple is going pepper unbypassable ads all through the iPhone interface. More than likely they are blue-skying their own take on Hulu or some other optional video service. So if one doesn't use the ad-supported features then the ads won't be seen. I also suspect that Apple will be happy, more than happy, to license this patent under less than draconian terms to other content providers. So the iPhone won't be rendered a banner ad flashing brick and the idea won't be safely locked up in such a way that any other phone becomes an oasis from it.
Umm. Apparently one could still develop in machine code for the C-64 and this emulator would execute that. And that is far more fertile ground for breaking out of the sandbox and attacking the emulator and then iPhone itself (yes, yes, it isn't a GREAT attack vector but work with me here.....). Of course they could require signing the C-64 binaries but then what would be point? You may as well re-implement the C-64's Greatest Hits in native code for the phone itself.
Printing works on the newest builds of google-chrome and chromium-browsrer but it can be buggy. It seems to get a little bit better steadily as more releases come out.
I think he means applications where Linux or a BSD is the primary development environment and those APIs were the target. Agreed it is a sloppy use of "native". In the case of Firefox, XP is a the primary dev environment and it also benefits from Profile Guided Optimizations when compiled. The Linux port could in principle but the work hasn't been done (and probably won't be).
So now I just skip any of the scanners and opt for a pat down. It slows down security, it appears to make them uncomfortable, and if I'm lucky it'll be someone attractive patting me down.
http://www.metrolyrics.com/security-joan-lyrics-fagen-donald.html
chuckle...snort!
In IBM's terms, the money involved for them to litigate SCO isn't terribly substantial. However, the damage they did to IBM's reputation and some of IBM's investments wasn't trivial. SCO has even claimed to be able to terminate IBM's rights in AIX. IBM isn't after a quick end to the litigation. They are after vindication and making an example out of SCO to deter any other pipsqueaks from peeing in their Wheaties. Buying them out even at this late degraded date only rewards them.
Given how they wanted to feed off the hard work of Linux developers, companies, and users my method of choice would a stake through the heart in the center of a crossroads just prior to daybreak.
.....is if the news was delivered to Darl in an Austrian accent by a huge guy in sunglasses and black leather.
I followed and read that. It is one of the most stupid things I've ever read in my life. 4Front believes they can restrict the use of OSS4 on Linux only to GPL apps. In their view, if you fire up Doom3 and play the sound through OSS4 then you are in "violation the terms we choose to distribute under". They furthermore believe they can impose this restriction in addition to the GPL. Even RMS doesn't have such an expansive idea of what incurs GPL restrictions. Come to think of it, the GPL goes to some length to explain that restrictions only apply to distribution and not to mere use at all.
I can't see that anyone other than a paying 4Front customer who has accepted a proprietary EULA has any rights to use OSS4 at all. Their public statements + GPL would not appear to be a viable license to either use or distribute.
Great. Now I have to worry about getting pwned by Frankie and Benjy.
There are more and less correct ways to go about running "non-stable" packages. Just jamming in a foreign binary deb and it's deps is generally the wrong way to do it. The right way to do it is to basically do what backports.org does....and check if backports has it first. If you're not running a Debian derivative then research the equivalent for your distro or BSD flavor:
1. add an apt-src line from the "non-stable" distro. I've even done this when Ubuntu had the latest SpamAssassin and I wanted a late model debianized SpamAssassin. Note well I said "apt-src" and NOT an "apt" line. apt-get update, yadda yadda
2. mkdir package-of-interest; cd package-of-interest; apt-get build-dep package-of-interest. If you're lucky this pulls in everything needed to build the package. If not you'll have to recurse with apt-get build-dep package-of-interest-newer-dependency; apt-get source package-of-interest-newer-dependency and come back to step 2 until you have everything you need to build your "non-stable" package.
3. apt-get source package-of-interest (or -newer-dependency)
4. cd package-of-interest-version; fakeroot dpkg-buildpackage -b. If all goes well a backport of the newer software that is built against your nice stable distro's libraries will be built one directory level up.
5. If you had to build a newer library your package needs install it then go back to #2. rinse and repeat until you have your newer software. Myself, I'll build one or two before giving it up as a bad job. Generally I succeed at this. Bread and butter stuff like Clamav and SpamAssassin that is well behaved tends to work well with this procedure.
The point of this is to avoid having to replace heeby jeeby inducing things like glibc, libstdc++, or even Perl since half your system scripts depend on such things. You avoid replacing packages that are contributing to the stability of the rest of the system and that are still getting critical bug and security updates. It keeps the "foreign" footprint to a middle and gives you a "foreign" package that is more or less compliant with the rest of the system.
The patent nastiness was only a month or two ago. I'm not judging MS on what they might do or on what their PR says about being chummy with Open Source. Their actions lately are consistent with a history of hostile actions. If MS accumulates a long long of positive actions while refraining from negative ones my mind will change about them. But until they actually do I maintain that mistrust of MS is reasonable. Note well that I'm not unwilling to change my mind about MS but I currently see no reason to do so.
The leadership of MS is on record as calling FOSS Un-American, a cancer, and other pejoratives. Their leadership has also been caught red-handed more than once attempting to sabotage FOSS. The recent nastiness with the anti-Linux patent package intended for troll use comes to mind. The actions of MS' leadership are far more relevant than the fact a few coders in cubicles don't bear FOSS any particular ill will. Now I don't hate MS but distrusting MS isn't in the least unreasonable.
Moonlight would actually have to be usable on J. Random Moonlight Site before I could even get dependency started.
I don't know how much I buy that. Game engines and other such plumbing works well enough but even fan generated content for most games relies hugely on resources supplied by the base game. I've been watching attempts to replace the base wads and paks that are supplied with even super old stuff like Doom and Quake. The goal of those projects is a complete replacement that would allow among other things existing fan generated content to run. None have been complete enough to do this. There is an awful lot of artistic scutwork that has to go into making large games work these days and FOSS communities only seem to go so far in producing it.
I can see small original even innovate things being done on PCs but big productions that contain DVDs worth on content are only going to come out on the platforms the majors want to support. I'd love to be proven wrong on this but .....
I always loved the punch line at the end of The Galaxy Song from The Meaning Of Life:
http://www.youtube.com/watch?v=buqtdpuZxvk
I also get a chuckle out of all those kids in Catholic schools who belted out Every Sperm Is Sacred to annoy the nuns.
I wouldn't use it for a main desktop but on a small machine that I have only a few targeted uses for it is desktop enough.
I have EEE PC 4G that can boot to a Debian Sid LXDE desktop in less than 30 seconds. Maybe even twenty though I haven't bothered to time it. I can tell you that the OS boot takes only slightly longer than the BIOS to load and initialize. Efforts to lower "real world" Linux boot times ARE paying off.
The Twilight Hack has been obsoleted by System Updates; if the Homebrew channel or other loader was installed then updates didn't remove it. Nonetheless, the Twilight Hack won't work on a Wii that is patched up current. The current exploit du jour is Bannerbomb; it doesn't require a copy of Twilight Princess and works even on current versions of the System Menu.
I will say this for a well exploited Wii. I can select any title that I own from a menu and play it without getting up to change discs as all the titles I own have been ripped to a USB hard drive. Nintendo and the other consoles should have enabled something like that from the get go. I have no problem with serializing such a scheme so that your rips won't work on another console. It should also be possible to do something to distinguish rental titles so that one can't compile a library super cheap from GameFly.
I haven't touched physical media for years for music. This will soon be true of my video as well. And I would like that to continue to be true of any console gaming I do as well. If the console makers don't step up, I'll go with the thoroughly pwned consoles where homebrewers have.
I think he's advocating morals based on reason. Reason doesn't mean some form of social darwinism. It means that we have a solid ethical foundation behind the morals that have been thought out. Many morals boil down to "Because it's always been that way!". At one time owning a slave was a perfectly moral act. It took questioning that to end slavery in many places and that was an act of reason.
In the case of Turing, the morals of others justified grievous injury. It is reason that gives us the capacity to judge the morals themselves.
Everyone knew it was a 32-bit 68000 CPU - same thing that ran the five-year-old Sega Genesis and the 10 year old Macintosh or Amiga. The Jaguar has a better GPU, but that was its only advantage over those other machines.
The 68000 was over relied on. Some of the better and homebrew titles only use it for io and initialization purposes. It is indeed possible to create code for the machine that is mostly being executed by 64 bit parts using 64 bit pathways. But then the dev tools didn't lend themselves easily to that style of programming and the finer points of relying mainly on the Jaguar's chipset weren't truly appreciated until after the death of the console. So it's still Atari's fault.