...only they have to worry about people stealing *children*, so count yourself lucky.:) So do hospital post-natal wards, for that matter.
On the way in, they put a uniquely ID'ed bracelet on the kids and the parents. There's only one way out, and on the way out a staffer checks that kids match parents. It's a nice way to reduce the amount of security needed.
Public works projects can help a slumping economy, but only if the public works project is needed, and absolutely helps expand the economy. There is more to it than that, but creating jobs does not necessarily expand the economy but can result in simple wealth redistribution. For example, if the government hired 10,000 people to dig a giant ditch, and than hired another 10,000 people to fill in the ditch, jobs would be created, but would it help the economy?
What was World War II, from a USA productivity point of view, if not a massive exercise in ditch digging/filling. Take a big chunk of the workforce and ship them to Europe and Asia to destroy the physical infrastructure there, supplied by people back home, building productively useless equipment. At the same time, as all that effort was going into guns and bombs, no civilian cars were manufactured, or buildings built, or highways built, or railways built. The USA neglected its physical infrastructure for 5 years, and the only reason that wasn't a competitiveness catastrophe was because they were bombing everyone else's infrastructure flat during the same period!
That said, if ditch digging/filling can jump start an economy, so can railway building or school building and the latter has long-term productivity improvement effect, so is vastly vastly preferable to undirected stimulus (like mailing out tax rebate checks, for example).
It's a myth, but I can believe it is a natural outgrowth of our tendency to think bigger-is-better.
Your study is just about vehicle collisions, and no surprise, when you hit a small thing with a big thing, the big thing comes out on top.
But big things are harder to drive, and when they roll over, all alone on the freeway, as they have a higher propensity to do, the people in them tend to die.
Why bother going to the trouble of milking high quality renewable energy from the environment if you're just going to waste it on something frivolous like keeping an empty expanse of pavement lit up for eight hours a day!? If we stopped frittering away energy on pointless things like lighting empty parking lots, we'd have a lot less to worry about in terms of energy security. Even the big G doesn't get it.
Or, taking the same facts and looking from a different, less prejudicial, angle: people who choose an education that is about *things* (engineers, physicists, geologists, computer scientists) tend to lean right; people who chose an educations that is about *people* (sociologists, psycologists, literature, languages) tend to lean left. Seems like the categories are self-selected to some degree.
What do all these stories of open source "innovation" have in common? They all include prominent mention of how much venture money the companies have raised. I can only assume this publication is Straight Out of Silicon Valley (tm).
The lineage of PostgreSQL and Ingres is pretty clear. They are descendents of separate research projects of Prof. Michael Stonebreaker at UC Berkeley. Ingres descends from the an earlier project, which was a proving ground for pure relational technology.
PostgreSQL (note the play on words, "post" gres comes after "in" gres) descends from the follow-up project which extended relational concepts into an early "object-relational" system. Stonebreaker lays out his goals for the Postgres project in this 1986 paper.
So, Ingres is based on an older design that PostgreSQL. It has also spent 20 years in the corporate world being changed, upgraded, and improved, so evaluating it based on its lineage is like evaluating Oracle 10g based on your knowledge of Oracle 1.0. Interesting historical note: one of Oracle's first substantial competitors (and an early market leader) was a company called "Relational Technologies" that sold a cutting edge relational database named... Ingres.
Think back, think waaaaay back, before packets, before computers. When you wanted the same music in all your rooms, what did you do? You tuned all your radios to the same station.
Buy an FM transmitter kit for a hundred bucks, and your problems are solved. Synchronization is perfect, price is low, deployment is trivial.
For an office sysadmin, using it at home is a start, but not the end of the journey. Get yourself a lab. You will need three computers, a linux to be your "server", a linux to be a "client" and a windows to be a "client". (If you have more than one Win32 OS in your office, add one client of each type to your lab.)
Now, start playing. Basic install on your server, play with the interface for a bit. Get out the "Linux Network Administrator's Guide" and read it cover to cover. Read the Samba documentation in equal detail. Make a checklist of all the services you will need to support (DHCP server, DHCP client, Samba, Mail, WWW, FTP) and try them out. Get your test lab working with them.
Now, play harder. Try to make Samba a domain controller. Set up RAID on your Linux server. Do some NFS to your Linux client. A big stack of Linux books, a personal lab, and a workplan of things to try and make work will get you fully trained up, probably several years faster than I took learning a little at a time.:)
I concur that Linux Software RAID performs quite wonderously. However, I recently had a bad experience which has soured me on it for all but "data-I-dont-need-no-steeeking-data" situations.
What happened is the machine in which the array lived started to degrade (it was old) in multiple ways. The result was getting bad superblocks on several disks at once, and an array which was theoretically unrecoverable. What it taught me is that software RAID has alot more failure paths than hardware RAID. Bad memory, bad motherboard, bad controller, all can affect the integrity of your array, because the array depends on the integrity of the kernel in order to maintain a self-consistent state.
So now all my important arrays are hardware RAID controllers. Yes, if the controller goes, I could still have a bad day, but at least it is just the one component, but the whole machine, which I am depending on.
Why would anyone need so much processing power in a web tablet? Let's be reasonable about what these devices can be conventiently used for: comfortable data retrieval (great form factor, no wires, very nice), and unobtrustive data entry (the electronic legal pad). People aren't going to be cruching numbers on them, writing novels, etc. Why a 10Gb harddrive?! A full desktop OS!? This is insanity!
You want a wireless web pad?
Buy one now. Buy an Epods. The EPods is a real live web pad, with all the functionality required of such a device: web browsing, simple data entry, and wireless capability (just shove a 802.11 PCMCIA card into it). And they don't cost an arm and a leg.
The kicker is that the epods runs on a low power MIPS chip, with great battery life, and uses flash memory for storage, so there is no harddrive. It is tough as nails and absolutely silent. Did I mention the battery life (8 hours)? Don't wait another year for a noisy, hot, short-lived "Tablet PC" from Brother Bill, get one now.
I have (just last night) two D-Link DWL-500 cards set up and running under the wvlan_cs PCMCIA driver. Alot of the new cheap 802.11 cards are just re-badged Lucent chips, so the wvlan_cs driver works for them! Check out the PCMCIA drivers page for up-to-date info on supported wireless cards.
Oh, the DWL-500's are just PCI adapters for the DWL-650 which is the PCMCIA card. You can get ISA/PCMCIA adaptors pretty cheap from all sorts of places.
Slashdot Mirror
...only they have to worry about people stealing *children*, so count yourself lucky. :) So do hospital post-natal wards, for that matter.
On the way in, they put a uniquely ID'ed bracelet on the kids and the parents. There's only one way out, and on the way out a staffer checks that kids match parents. It's a nice way to reduce the amount of security needed.
Public works projects can help a slumping economy, but only if the public works project is needed, and absolutely helps expand the economy. There is more to it than that, but creating jobs does not necessarily expand the economy but can result in simple wealth redistribution. For example, if the government hired 10,000 people to dig a giant ditch, and than hired another 10,000 people to fill in the ditch, jobs would be created, but would it help the economy?
What was World War II, from a USA productivity point of view, if not a massive exercise in ditch digging/filling. Take a big chunk of the workforce and ship them to Europe and Asia to destroy the physical infrastructure there, supplied by people back home, building productively useless equipment. At the same time, as all that effort was going into guns and bombs, no civilian cars were manufactured, or buildings built, or highways built, or railways built. The USA neglected its physical infrastructure for 5 years, and the only reason that wasn't a competitiveness catastrophe was because they were bombing everyone else's infrastructure flat during the same period!
That said, if ditch digging/filling can jump start an economy, so can railway building or school building and the latter has long-term productivity improvement effect, so is vastly vastly preferable to undirected stimulus (like mailing out tax rebate checks, for example).
It's a myth, but I can believe it is a natural outgrowth of our tendency to think bigger-is-better.
Your study is just about vehicle collisions, and no surprise, when you hit a small thing with a big thing, the big thing comes out on top.
But big things are harder to drive, and when they roll over, all alone on the freeway, as they have a higher propensity to do, the people in them tend to die.
Hence, the higher overall fatality rates for SUVs.
Why bother going to the trouble of milking high quality renewable energy from the environment if you're just going to waste it on something frivolous like keeping an empty expanse of pavement lit up for eight hours a day!? If we stopped frittering away energy on pointless things like lighting empty parking lots, we'd have a lot less to worry about in terms of energy security. Even the big G doesn't get it.
Or, taking the same facts and looking from a different, less prejudicial, angle: people who choose an education that is about *things* (engineers, physicists, geologists, computer scientists) tend to lean right; people who chose an educations that is about *people* (sociologists, psycologists, literature, languages) tend to lean left. Seems like the categories are self-selected to some degree.
What do all these stories of open source "innovation" have in common? They all include prominent mention of how much venture money the companies have raised. I can only assume this publication is Straight Out of Silicon Valley (tm).
PostgreSQL (note the play on words, "post" gres comes after "in" gres) descends from the follow-up project which extended relational concepts into an early "object-relational" system. Stonebreaker lays out his goals for the Postgres project in this 1986 paper.
So, Ingres is based on an older design that PostgreSQL. It has also spent 20 years in the corporate world being changed, upgraded, and improved, so evaluating it based on its lineage is like evaluating Oracle 10g based on your knowledge of Oracle 1.0. Interesting historical note: one of Oracle's first substantial competitors (and an early market leader) was a company called "Relational Technologies" that sold a cutting edge relational database named... Ingres.
Think back, think waaaaay back, before packets, before computers. When you wanted the same music in all your rooms, what did you do? You tuned all your radios to the same station.
Buy an FM transmitter kit for a hundred bucks, and your problems are solved. Synchronization is perfect, price is low, deployment is trivial.
Now, start playing. Basic install on your server, play with the interface for a bit. Get out the "Linux Network Administrator's Guide" and read it cover to cover. Read the Samba documentation in equal detail. Make a checklist of all the services you will need to support (DHCP server, DHCP client, Samba, Mail, WWW, FTP) and try them out. Get your test lab working with them.
Now, play harder. Try to make Samba a domain controller. Set up RAID on your Linux server. Do some NFS to your Linux client. A big stack of Linux books, a personal lab, and a workplan of things to try and make work will get you fully trained up, probably several years faster than I took learning a little at a time. :)
What happened is the machine in which the array lived started to degrade (it was old) in multiple ways. The result was getting bad superblocks on several disks at once, and an array which was theoretically unrecoverable. What it taught me is that software RAID has alot more failure paths than hardware RAID. Bad memory, bad motherboard, bad controller, all can affect the integrity of your array, because the array depends on the integrity of the kernel in order to maintain a self-consistent state.
So now all my important arrays are hardware RAID controllers. Yes, if the controller goes, I could still have a bad day, but at least it is just the one component, but the whole machine, which I am depending on.
You want a wireless web pad? Buy one now. Buy an Epods. The EPods is a real live web pad, with all the functionality required of such a device: web browsing, simple data entry, and wireless capability (just shove a 802.11 PCMCIA card into it). And they don't cost an arm and a leg.
The kicker is that the epods runs on a low power MIPS chip, with great battery life, and uses flash memory for storage, so there is no harddrive. It is tough as nails and absolutely silent. Did I mention the battery life (8 hours)? Don't wait another year for a noisy, hot, short-lived "Tablet PC" from Brother Bill, get one now.
Oh, the DWL-500's are just PCI adapters for the DWL-650 which is the PCMCIA card. You can get ISA/PCMCIA adaptors pretty cheap from all sorts of places.