Using cooler chips to begin with? This seems like a lot of effort and expense to go through instead of using low power/heat processors such as mobile Pentiums or Crusoes.
Tim Janik came out with a utility called
Gerd a while back that lets you script GTK+ applications. It appears to have been abandoned at version 0.0.3, however.
Another major consideration would be weight. Most PalmPilots weigh about 1/2 a pound (200g). That's a huge weight penalty, especially considering most people do everything they can to lighten their bikes.
I never understood why so many people worry about the weight of their componentry (for casual riders at least). I can can spend $1000 to $2000 shaving five pounds off my bike, or I can just lose five pounds.
"With the conservative estimates of the Internet usage doubling every six months, the need for bandwidth at the core of the Internet is outpacing the ability of the conventional router technology to keep up."
Am I the only one, or did this make anyone else nostalgic for the mid-90s?
I don't think that anybody would break ABI compatibility intentionally.
I don't think so, either. However, intentionally or not, they do exactly that. And the SNMP example I provided is evidence. They changed the API/ABI in the SNMP packages for 7.2, as well as in the updates released a couple of months ago for 7.1, 7.0, and 6.2. Run a search for "red hat" on http://www.ethereal.com for more examples.
The point I was trying to make (and ended up ranting instead) was that I don't think the ultimate goal of the LSB (compile a binary on one distro, run it on another) is very likely given the way distros are currently produced.
How are they doing? Piss-poorly, if this
is any indication. Red Hat (and several other Linux vendors, apparently)
recently diverged from the published API and ABI
for a couple of routines in the UCD/Net-SNMP library. The result? Any
application that calls these routines core dumps on these
systems. They do this sort of thing a lot.
The result is that most major Linux distros can't keep binary
compatibility between updates and errata on the same OS release,
much less between releases. Even with the LSB, I think it will be a while
before we see binary compatibility between distros.
Slashdot Mirror
I wonder about the quality of his plaster, given that there are speakers vibrating the heck out of it.
If, by "differently" you mean "not in the slightest eensy bit" then yeah, VMS does simple things like command line piping "differently."
What's a hypocracy? Some new form of government? Maybe you guys are thinking of hypocrisy .
Using cooler chips to begin with? This seems like a lot of effort and expense to go through instead of using low power/heat processors such as mobile Pentiums or Crusoes.
Tim Janik came out with a utility called Gerd a while back that lets you script GTK+ applications. It appears to have been abandoned at version 0.0.3, however.
People are already doing this. They're losing piles of money.
Try factoring in things like change control and QA. In many environments, this can take a bit of time and effort.
Or do you just apply the patches without any planning, notification or testing?
I never understood why so many people worry about the weight of their componentry (for casual riders at least). I can can spend $1000 to $2000 shaving five pounds off my bike, or I can just lose five pounds.
Am I the only one, or did this make anyone else nostalgic for the mid-90s?
I don't think that anybody would break ABI compatibility intentionally.
I don't think so, either. However, intentionally or not, they do exactly that. And the SNMP example I provided is evidence. They changed the API/ABI in the SNMP packages for 7.2, as well as in the updates released a couple of months ago for 7.1, 7.0, and 6.2. Run a search for "red hat" on http://www.ethereal.com for more examples.
The point I was trying to make (and ended up ranting instead) was that I don't think the ultimate goal of the LSB (compile a binary on one distro, run it on another) is very likely given the way distros are currently produced.
The result is that most major Linux distros can't keep binary compatibility between updates and errata on the same OS release, much less between releases. Even with the LSB, I think it will be a while before we see binary compatibility between distros.
(In case you're wondering, animations can be disabled via Preferences->Privacy and Security->Images.)
This isn't the first time this sort of thing has been done. Check out the Perl Filesystem.
"Computer reel tapes, VCR tapes, and audio tapes last about as long as a Chevy or a poodle."