That's exactly what I'm implying, for several reasons. The primary reason is that because actions that are 'atomic', such as database write operations, are not 'atomic' as far as the filesystem is concerned. So operations that affect one part of the database and have not yet written to another part of the database will be inconsistently available on disk.
You've raised an interesting point, that dd'ing should be getting the data that has not yet been paged back to the disk from the page in RAM, not from the disk itself. That's a good point I'll have to think about.
Duplicating filesystems with dd does not allow resizing, myshandles database files that are in the midst of atomic operations, and only gets that data that has actually been written to disk. The fact that modern Linux kernels keep as much in possible paged out in RAM, to improvde access times, means that you can rely on nothing having been written to disk unless you go through additional, complex and service interrupting steps. It also doesn't compress well, since any unused bits on unused blocks also wind up read and included in the duplication.
No, dd is not a good backup or data transfer tool in most circumstances.
No, the most effective spam filter is CRM114, at http://crm114.sourceforge.net/. By training it to individual tastes, it's better than an average user detecting spam. It's just computationally a bit expensive, and awkward to set up.
No, it can't. Those people with 'a box of bullets' will hit innocent people with hijacked machines, and do you think your average 'vigilante' is prepared to take on the Russian mob, or Nigerian mail fraud practicioners with hooks into local corrupt police and use ill-gotten money to trade in credit cards and passports stolen from suckers who go there to collect their 'inherited money'? All of the spammers are crooks, but some of them are dangerous crooks making a bit of trade on the side just because it's there.
This sort of logic is a good reason to use swap. There is also another one: by using a / partition of, say, 16 Gig, and a swap partition of 16 Gig, in a pinch you can transfer your / partition to your swap partition in order to do an emergency backup or keep a copy around for upgrade procedures or to repartition your disk. This used to be much more difficult when filesystem changing tools were not so broadly availble, but a spare under-used partition space can be really useful in an odd moment. I've also taken advantage of it as a place to store a compressed copy of a database, while I rebuild the filesystem of the database to test something interesting for performance.
Swap space is a resource that can be used for other purposes on a temporary basis.
The blue screens are from backporting to 32-bit, from implementing broken DOS-style user interfaces and API's on top of VMS's much cleaner work, and from having to work with a bunch of experienced Microsoft developers who wrote the original blue screen creating nonsense in the first place.
But the kernel was a huge leap up in stability, and really was enterprise class. It's the applications on top of them that were so nutty and unstable.
Piffle yourself. The memory management, as an example, was definitely theft from DEC.
David was one of the three team leads on Starlet, which became VMS. And yes, according to DEC personnel of that era, he was very much a technical lead, if not the technical lead.
What? WinME was simply repackaged Win98. Windows _NT_ was built by David Cutler, on a VMS foundation rather than a DOS foundation, because Cutler was one of the core authors of VMS and there were some fascinating lawsuits about his duplicating his old VMS work for Microsoft.
Richard's paranoia is often well-founded. Many, though not all, cloud computing projects do present a serious set of security concerns, hidden behind closed source tools which may interfere with many other operations of your computer.
That's OK: it may e a footnote in scientific terms, but in *business* terms, it's a huge matter. It's an active embarassment to NASA, Boeing, McDonnell-Douglas, and the other big space businesses of the USA. Like PC's taking over the tasks of IBM and Cray big iron, it's a very exciting business shift away from Congress funded space endeavors.
That's vaguely funny, but completely wrong. The fat being transformed back to energy is quite inefficient: it's far more effective to send up the fat as food, and not pay the water and oxygen and space costs of storing it as live fat in the body, especially because it will change the size of their space suits. Also, a lot of midgets have a lot of other medical issues, and limited body strength. Sending up all that spare organ space just to get a really short pair of arms up there seems pretty inefficient.
Now, people with their legs chopped off might be more effective. I bet there are quite a few military veterans right now who'd be happy for the ride, and have a lot of upper body strength to bring to their efforts.
There are problems with women in space. The catheters they use for space suits are still pretty awkward, and menstruation is apparently very awkward. But heck yes, bring women. They're lighter and take less oxygen/kilo and fewer calories/workload.
Just because it comes from someone else's bank account does not make that 'cost' zero. Ignoring the 'cost' of that up-front investment, irrelevant of some unspecified 'income' that the project will generate, is how Dotcom companies go out of business: don't encourage that kind of sloppy thinking here.
It's also exactly the sort of question potential investors should be asking. Don't just blow it off with voodoo economics.
No, not necessarily. Aborted foetuses, and stem cells from umbilical cords, could easily be harvested and cultured. Cultured stem cells work just fine for implant tests, so far. There is _no_ need to harvest living for the stem cell work, even if the transplants are of physically significant volumes of cells. Cultures of such morally harvested single stem cell lines can easily serve hundreds if not millions of recipients.
Your ignorance of the biology is exactly why stem cell funding is so difficult to obtain: people hear the phrase and tar it with the brush of harvesting children's bodies, which it can be, in fact, mere recycling of discarded tissue samples.
Actually, keeping the army weak is pretty important to preventing martial law. Or haven't you been to Iraq, Iran, Argentina, or Russia in the last 20 years?
Lots of folks here need to review the Palladium toolkit, renamed 'Trusted Computing'. It's designed to lock files to applications to hardware, in a triad specifically set up to control what users can do with their files and make them unavailable except for owner authorized software with centralized key management. This sort of thing is _precisely_ what it was designed for: the security enhancements it provides are potentially useful, but DRM is clearly its fundamental purpose.
Cisco is affected by sales of bandwidth handling equipment. They would much rather sell new equipment, with new patents and computationally topheavy features such as sophisticated filtering, than another round of cheap GigE switches. And their customers would rather buy one smart unit, and pay lower bandwidth costs, than fill racks with P2P supporting hardware. For a business network, I'd buy it in a heartbeat: our employees have no business running Bittorrent from their desktop on the business network, even for legitimate traffic. I try to make sure there is *one* host for authorized Bittorrent, such as CentOS DVD images, but other than that, they can do it at home.
While spam is in fact most email, has P2P yet overtaken spam as the largest single bandwidth user at most ISP's?
Or Wikipedia, and the leaks there on Swiss banking systems and off-shore banking. Too many of the gambling businesses, incliding online casinos, are crooked to have sympathy for them as people. But like allowing the KKK to march in the name of free speech, this is an amazingly dangerous ruling.
The original system wasn't bad. But to get federal agreement, and international cooperation, you've got the human problem of getting the countries to accept it, and the tendency of people to compromise, and the individual nation's desire to have local censorship and monitoring.
The result is the US export encryption regulations, French's encryption policies, the whackiness with 80-bit SSL keys we had for years, etc.
Now, that's a fascinating question. But if the 'meta-universe' surrounding our 'closed universe' has any spare matter or energy to dump in, the extremely modest Hawking losses of a universize sized black hole would be trivially compensated. Given that the losses would be so grotesquely tiny anyway for such a large black hole, we're talking about _amazingly_ long timeperiods. I'm just guessing, but I think it's time enough for all the atoms of our hostess's underwear to jump to your computer, sit down, and randomly write forge Shakespeare's plays.
Halo was much, much more rooted in 'Marathon'. That was a Mac game, and one of the best Mac shooters ever. The plasma gun, in particular, and its charging up was a very Marathon touch. This is also because the same company, and many of the same employees, made both.
I was upset when Microsoft bought Bungie and kept it off the Mac: it would have been a 'must-have' application for Mac owners, and a real incentive to get Macintoshes.
No, our universe could be a black hole. In that case, the boundary or "bubble" has a much stronger meaning, and it could make more sense to talk about material 'outside' our universe.
Slashdot Mirror
That's exactly what I'm implying, for several reasons. The primary reason is that because actions that are 'atomic', such as database write operations, are not 'atomic' as far as the filesystem is concerned. So operations that affect one part of the database and have not yet written to another part of the database will be inconsistently available on disk. You've raised an interesting point, that dd'ing should be getting the data that has not yet been paged back to the disk from the page in RAM, not from the disk itself. That's a good point I'll have to think about.
Duplicating filesystems with dd does not allow resizing, myshandles database files that are in the midst of atomic operations, and only gets that data that has actually been written to disk. The fact that modern Linux kernels keep as much in possible paged out in RAM, to improvde access times, means that you can rely on nothing having been written to disk unless you go through additional, complex and service interrupting steps. It also doesn't compress well, since any unused bits on unused blocks also wind up read and included in the duplication. No, dd is not a good backup or data transfer tool in most circumstances.
No, the most effective spam filter is CRM114, at http://crm114.sourceforge.net/. By training it to individual tastes, it's better than an average user detecting spam. It's just computationally a bit expensive, and awkward to set up.
The results are quite impressive, though.
No, it can't. Those people with 'a box of bullets' will hit innocent people with hijacked machines, and do you think your average 'vigilante' is prepared to take on the Russian mob, or Nigerian mail fraud practicioners with hooks into local corrupt police and use ill-gotten money to trade in credit cards and passports stolen from suckers who go there to collect their 'inherited money'? All of the spammers are crooks, but some of them are dangerous crooks making a bit of trade on the side just because it's there.
This sort of logic is a good reason to use swap. There is also another one: by using a / partition of, say, 16 Gig, and a swap partition of 16 Gig, in a pinch you can transfer your / partition to your swap partition in order to do an emergency backup or keep a copy around for upgrade procedures or to repartition your disk. This used to be much more difficult when filesystem changing tools were not so broadly availble, but a spare under-used partition space can be really useful in an odd moment. I've also taken advantage of it as a place to store a compressed copy of a database, while I rebuild the filesystem of the database to test something interesting for performance.
Swap space is a resource that can be used for other purposes on a temporary basis.
The blue screens are from backporting to 32-bit, from implementing broken DOS-style user interfaces and API's on top of VMS's much cleaner work, and from having to work with a bunch of experienced Microsoft developers who wrote the original blue screen creating nonsense in the first place. But the kernel was a huge leap up in stability, and really was enterprise class. It's the applications on top of them that were so nutty and unstable.
Piffle yourself. The memory management, as an example, was definitely theft from DEC.
David was one of the three team leads on Starlet, which became VMS. And yes, according to DEC personnel of that era, he was very much a technical lead, if not the technical lead.
What? WinME was simply repackaged Win98. Windows _NT_ was built by David Cutler, on a VMS foundation rather than a DOS foundation, because Cutler was one of the core authors of VMS and there were some fascinating lawsuits about his duplicating his old VMS work for Microsoft.
Richard's paranoia is often well-founded. Many, though not all, cloud computing projects do present a serious set of security concerns, hidden behind closed source tools which may interfere with many other operations of your computer.
That's OK: it may e a footnote in scientific terms, but in *business* terms, it's a huge matter. It's an active embarassment to NASA, Boeing, McDonnell-Douglas, and the other big space businesses of the USA. Like PC's taking over the tasks of IBM and Cray big iron, it's a very exciting business shift away from Congress funded space endeavors.
Then please address that appropriately.
That's vaguely funny, but completely wrong. The fat being transformed back to energy is quite inefficient: it's far more effective to send up the fat as food, and not pay the water and oxygen and space costs of storing it as live fat in the body, especially because it will change the size of their space suits. Also, a lot of midgets have a lot of other medical issues, and limited body strength. Sending up all that spare organ space just to get a really short pair of arms up there seems pretty inefficient.
Now, people with their legs chopped off might be more effective. I bet there are quite a few military veterans right now who'd be happy for the ride, and have a lot of upper body strength to bring to their efforts.
There are problems with women in space. The catheters they use for space suits are still pretty awkward, and menstruation is apparently very awkward. But heck yes, bring women. They're lighter and take less oxygen/kilo and fewer calories/workload.
Just because it comes from someone else's bank account does not make that 'cost' zero. Ignoring the 'cost' of that up-front investment, irrelevant of some unspecified 'income' that the project will generate, is how Dotcom companies go out of business: don't encourage that kind of sloppy thinking here.
It's also exactly the sort of question potential investors should be asking. Don't just blow it off with voodoo economics.
No, not necessarily. Aborted foetuses, and stem cells from umbilical cords, could easily be harvested and cultured. Cultured stem cells work just fine for implant tests, so far. There is _no_ need to harvest living for the stem cell work, even if the transplants are of physically significant volumes of cells. Cultures of such morally harvested single stem cell lines can easily serve hundreds if not millions of recipients.
Your ignorance of the biology is exactly why stem cell funding is so difficult to obtain: people hear the phrase and tar it with the brush of harvesting children's bodies, which it can be, in fact, mere recycling of discarded tissue samples.
Actually, keeping the army weak is pretty important to preventing martial law. Or haven't you been to Iraq, Iran, Argentina, or Russia in the last 20 years?
Lots of folks here need to review the Palladium toolkit, renamed 'Trusted Computing'. It's designed to lock files to applications to hardware, in a triad specifically set up to control what users can do with their files and make them unavailable except for owner authorized software with centralized key management. This sort of thing is _precisely_ what it was designed for: the security enhancements it provides are potentially useful, but DRM is clearly its fundamental purpose.
Cisco is affected by sales of bandwidth handling equipment. They would much rather sell new equipment, with new patents and computationally topheavy features such as sophisticated filtering, than another round of cheap GigE switches. And their customers would rather buy one smart unit, and pay lower bandwidth costs, than fill racks with P2P supporting hardware. For a business network, I'd buy it in a heartbeat: our employees have no business running Bittorrent from their desktop on the business network, even for legitimate traffic. I try to make sure there is *one* host for authorized Bittorrent, such as CentOS DVD images, but other than that, they can do it at home.
While spam is in fact most email, has P2P yet overtaken spam as the largest single bandwidth user at most ISP's?
Or Wikipedia, and the leaks there on Swiss banking systems and off-shore banking. Too many of the gambling businesses, incliding online casinos, are crooked to have sympathy for them as people. But like allowing the KKK to march in the name of free speech, this is an amazingly dangerous ruling.
The original system wasn't bad. But to get federal agreement, and international cooperation, you've got the human problem of getting the countries to accept it, and the tendency of people to compromise, and the individual nation's desire to have local censorship and monitoring.
The result is the US export encryption regulations, French's encryption policies, the whackiness with 80-bit SSL keys we had for years, etc.
Ahh, the Iphone approach raises its ugly head.
They could play Counter-Strike, screaming 'Where's my bazoooka'.
http://www.youtube.com/watch?v=r7rkQwbY98s
Now, that's a fascinating question. But if the 'meta-universe' surrounding our 'closed universe' has any spare matter or energy to dump in, the extremely modest Hawking losses of a universize sized black hole would be trivially compensated. Given that the losses would be so grotesquely tiny anyway for such a large black hole, we're talking about _amazingly_ long timeperiods. I'm just guessing, but I think it's time enough for all the atoms of our hostess's underwear to jump to your computer, sit down, and randomly write forge Shakespeare's plays.
Halo was much, much more rooted in 'Marathon'. That was a Mac game, and one of the best Mac shooters ever. The plasma gun, in particular, and its charging up was a very Marathon touch. This is also because the same company, and many of the same employees, made both. I was upset when Microsoft bought Bungie and kept it off the Mac: it would have been a 'must-have' application for Mac owners, and a real incentive to get Macintoshes.
No, our universe could be a black hole. In that case, the boundary or "bubble" has a much stronger meaning, and it could make more sense to talk about material 'outside' our universe.