You think nobody living there means it's safe? You're going to look pretty silly when half an ice sheet slides into the ocean, and even sillier when your city is inundated.
Linked from a Slashdot article, According to a study recently published online by the Journal of Environmental Science and Technology, the manufacturing of a typical two-gram chip takes 1.6 kilograms of fossil fuel, 72 grams of chemicals and 32 kilograms of water.
2500 machines is a BIG rollout. If you get it wrong (which you will first time) users will hate you.
One career-saving idea is to first roll out 25 machines in a friendly department as a "beta-test", and when that works, roll out to 250 machines, then 2500 machines. Use the scaling technologies (LDAP, CODA, scripts, turnkey installation and more) that others have written about here. Also, set up web services for support tracking and help.
If you wanted to offer your users a very Windows-like environment, try the QVWM window manager (http://www.qvwm.org). It doesn't have the integration features of GNOME/KDE/E/Sawmill etc, but it is VERY light on resources, very fast, and Windows users will feel quite at home.
One of the reasons people are looking at Linux for installing on hundreds of machines (eg, Beowulf-style clusters) is that it reduces the capital software cost. The same is true for your office suite - Applixware or WordPerfect x2500 will cost heaps. I have used Star Office 5.1 (free from Sun) for some time with good results. Not resource-frugal or quirk-free, but pretty complete. I'm itching for SO 5.2....
And of course, this is just my 2c. YMMV. All the best!
In the quest for cheaper handheld devices, manufacturers are looking at using GPLed code such as Linux. They also want to use mask ROM. But this would mean that even though the manufacturer releases the source code, the end-user can't make changes and run it on their device.
Is this allowed under the GPL? How can manufacturers use mask ROMs and fulfill their obligations under the GPL?
You think nobody living there means it's safe? You're going to look pretty silly when half an ice sheet slides into the ocean, and even sillier when your city is inundated.
> You can drag one out of its den by the legs,
> take blood samples, and weigh its cubs before
> they're awake enough to maul you.
Gee, the things you have to do to get a decent mauling!!!
Electronics is a dirty business.
> ALways something is breaking on it.
Oh great, Yoda drives a Honda.
> great for navigating congested cities with street
> grids designed in the middle ages.
They were designed???
> what they have is a GIGANTIC
> WATER-BASED TIME BOMB.
Or a GIGANTIC TIME-BASED WATER BOMB....
The DreamCast is powered by a Hitachi SuperH processor, not a MIPS.
Mitch.
(For the Linux on SuperH team)
2500 machines is a BIG rollout. If you get it wrong (which you will first time) users will hate you.
One career-saving idea is to first roll out 25 machines in a friendly department as a "beta-test", and when that works, roll out to 250 machines, then 2500 machines. Use the scaling technologies (LDAP, CODA, scripts, turnkey installation and more) that others have written about here. Also, set up web services for support tracking and help.
If you wanted to offer your users a very Windows-like environment, try the QVWM window manager (http://www.qvwm.org). It doesn't have the integration features of GNOME/KDE/E/Sawmill etc, but it is VERY light on resources, very fast, and Windows users will feel quite at home.
One of the reasons people are looking at Linux for installing on hundreds of machines (eg, Beowulf-style clusters) is that it reduces the capital software cost. The same is true for your office suite - Applixware or WordPerfect x2500 will cost heaps. I have used Star Office 5.1 (free from Sun) for some time with good results. Not resource-frugal or quirk-free, but pretty complete. I'm itching for SO 5.2....
And of course, this is just my 2c. YMMV. All the best!
In the quest for cheaper handheld devices, manufacturers are looking at using GPLed code such as Linux. They also want to use mask ROM. But this would mean that even though the manufacturer releases the source code, the end-user can't make changes and run it on their device.
Is this allowed under the GPL? How can manufacturers use mask ROMs and fulfill their obligations under the GPL?