Well, distributing the computation over several boxes still has its inefficiences. Often programs will for speed's sake store position evaluations in a central hash table, or a history heuristic matrix or somesuch. Some of these techniques can be extremely useful in pruning the tree to be searched. One problem (I would imagine) is finding the tradeoff between communicating enough of this kind of information to nodes that could use it, and the network overhead it takes to do so. A simpler task would be taking advantage of multiple threads on an SMP box, like craftycan.
Apparently this hasn't stopped some people from doing the totally distributed approach though; try googling on "zugzwang chess program" for an example.
Mmmph. Maybe it was supposed to be funny. In any case, any time you have a heat differential (between the inside of the craft and the outside, heated by atmospheric friction) you can theoretically use that to create power. But unless it's nescessary, adding that ability would
only increase weight, which is the problem aerobraking is supposed to be solving in the first place.
Simply, the CD boots, I can partition and all. But the install craps out when you are trying to install the base system. Basically I've got a CD worth nothing... coaster.
Perhaps you could use it as a crappy rescue disk, if you can get to a prompt (redhat would):)
If anything Unix needs to push it over the top as far as a secure server operating systems isthe ability to tell the OS that "This File can never be deleted and can only be appended to by Postmaster. Forever. No matter what. Even if I want to get rid of it later."
It's hard to know you *never* want to get rid of a file, or even rename it or move it somewhere else.
New viruses would just create a bunch of humongo crap files in your home directory (maybe called hardcoreporn.jpg for any admin/boss types happening to peruse your files) and then mark them undeletable.
Finally, if you want to achieve a crude approximation of your goal just chown the files to root and chmod them to 444 or something. Of course this scheme fails when you're running as root..
Dear troll, one of the interesting things about the Y chromo is that most of it is there just to make sure you're male. Diseases like color blindness, hemophilia etc. strike males *almost* exclusively because males have no good X chromo to cover for their screwed up one. To use a somewhat apt term, females have 'backups'.
For example, if mental prowess were controlled by the X chromo, and you got the stupid gene, it would be nice to have a backup to bring you back up to par. Judging by the nature of your post however, I'm guessing you got good ol' "Y" instead.
Tidal energy is energy none the less, but it's too limited, even coming from Jupiter.
This is the same tidal energy that causes Io to radiate excess heat in the form of volcanic eruptions. Certainly the effect is less near Europa, but according to this
page your assertion is still up in the air.
Mensuration (which generally means the act or process of measuring) specifically means figuring out how tall buildings or features are from satellite photographs.
I'm being a pedantic bastard, but according to
webster it doesn't specifically mean that. Where are you getting your definition from? Maybe I'll learn something..
if you had an inside "source" would you reveal it?
Yes. Not the identity of the source, but the fact that there is one. You just say "according to an anonymous source/expert," like a TV network might. It shows that you tried to do research at least.
But in the first line the interviewer says that he's into UNIX, but isn't UNIX the proprietary version that we all want to get away from?
Well, depends. *BSD could be considered flavors of UNIX. If you're speaking trademark-wise, the
Unix Trademark Page basically says they're not.. OTOH that same page also says you can't use UNIX in the generic sense, so prepare to be sued:)
First link's worthlessness conceded in another post.
Second link: hats off to those who don't run wu-ftpd. I would never claim that all linux systems are alike. As for those who do (run wu-ftpd), arguing over whether a given windows or linux combo is worse is almost pointless.. they're both buggy POSs and it takes one crack to ruin the box.
As for the third link..
A design flaw, rather than a true "bug"
I do program, and where I come from, design flaws usually count as bugs. Usually they're the hardest ones to fix
There is absolutely NO evidence that this vulnerability has ever been exploited
You could apply that statement to MS's latest problem, and you'd be equally foolish
HOW LONG was it, after the design flaw became known, that the flaw was fixed and new releases made to fix it. A day or two?
This is just from the searching I have done, and it's so ridiculous I actually don't believe it myself; somebody *please* correct the errors here, but AFAICT: Flaw
published1/4/01,
apparently
fixed by redhat 4/10/01 (debian nailed this on 4/16). Somebody
noticed on the kernel mailing list 7/24/01 that there was still a problem (improved exploit perhaps?), and this was fixed by redhat on 10/09/01. I can't find a second debian fix; maybe they got it right the first time. Anyway to answer your question, not quite.
Depends on your point of view. I'll give you the AC link now that I think coherently it. As for the second story, RH broke the news only when they had a patch. (but, bully to them for at least coming out then.)
As for the last story, I was attempting to compare timescale, not magnitude of the bug. You may accuse me of generalizing and I may accuse you of picking nits; the truth probably lies somewhere in between. Anyway, if you'd like an example of a long-lived *remote* root exploit,
this should probably do the trick.
4) Ignore the linked article, and claim something stupid. In this case that MS isn't in a hurry to release a patch when in fact they have been testing a patch.
5) Jump to conclusions, like " It's a fundamental design issue".
6) Somehow tie the whole thing into the anti-trust suit.
Slashdot Mirror
You both forgot the posts detailing what the parent posts forgot.. ooh! self-referential humor!
Apparently this hasn't stopped some people from doing the totally distributed approach though; try googling on "zugzwang chess program" for an example.
Speak for yerself, man. I'm just toggling a flashlight into a stray optical pipe here. Kids these days..
(yeah, yeah, lasers, blah, blah)
There goes the neighborhood. Time to move to Flatland.
NIH (not invented here)
According to the liner notes, the observatory would detect black holes, not create them.
Mmmph. Maybe it was supposed to be funny. In any case, any time you have a heat differential (between the inside of the craft and the outside, heated by atmospheric friction) you can theoretically use that to create power. But unless it's nescessary, adding that ability would only increase weight, which is the problem aerobraking is supposed to be solving in the first place.
Perhaps you could use it as a crappy rescue disk, if you can get to a prompt (redhat would) :)
A google on "nt ppc" will do that for you. I think I actually saw a box running it at my last workplace. It didn't get used much.
It's hard to know you *never* want to get rid of a file, or even rename it or move it somewhere else.
New viruses would just create a bunch of humongo crap files in your home directory (maybe called hardcoreporn.jpg for any admin/boss types happening to peruse your files) and then mark them undeletable.
Finally, if you want to achieve a crude approximation of your goal just chown the files to root and chmod them to 444 or something. Of course this scheme fails when you're running as root..
Now that's a business strategy.
(/meta-humor)
Dear troll, one of the interesting things about the Y chromo is that most of it is there just to make sure you're male. Diseases like color blindness, hemophilia etc. strike males *almost* exclusively because males have no good X chromo to cover for their screwed up one. To use a somewhat apt term, females have 'backups'.
For example, if mental prowess were controlled by the X chromo, and you got the stupid gene, it would be nice to have a backup to bring you back up to par. Judging by the nature of your post however, I'm guessing you got good ol' "Y" instead.
This is the same tidal energy that causes Io to radiate excess heat in the form of volcanic eruptions. Certainly the effect is less near Europa, but according to this page your assertion is still up in the air.
Of course not. Take Cybertron for example. Life evolved from naturally occuring gears, wheels, and pulleys.
It's entirely likely that if we were to discover life, we wouldn't actually recognize it as such
Exactly. They just look like small plastic toys to us. But remember, they're "more than meets the eye".
I'm being a pedantic bastard, but according to webster it doesn't specifically mean that. Where are you getting your definition from? Maybe I'll learn something..
Yes. Not the identity of the source, but the fact that there is one. You just say "according to an anonymous source/expert," like a TV network might. It shows that you tried to do research at least.
Windows Update? Yeah I prefer rpms, but it could be worse. It could be Sun.
2). Once you know what you need you still have to go box to box to box to patch (in *most* cases).
Try Back Orifice, I hear it works great.
Well, depends. *BSD could be considered flavors of UNIX. If you're speaking trademark-wise, the Unix Trademark Page basically says they're not.. OTOH that same page also says you can't use UNIX in the generic sense, so prepare to be sued :)
I think (s)he meant to say "best candidate for *intelligent* life"..
s?ignore?forget?g
Second link: hats off to those who don't run wu-ftpd. I would never claim that all linux systems are alike. As for those who do (run wu-ftpd), arguing over whether a given windows or linux combo is worse is almost pointless.. they're both buggy POSs and it takes one crack to ruin the box.
As for the third link..
A design flaw, rather than a true "bug"
I do program, and where I come from, design flaws usually count as bugs. Usually they're the hardest ones to fix
There is absolutely NO evidence that this vulnerability has ever been exploited
You could apply that statement to MS's latest problem, and you'd be equally foolish
HOW LONG was it, after the design flaw became known, that the flaw was fixed and new releases made to fix it. A day or two?
This is just from the searching I have done, and it's so ridiculous I actually don't believe it myself; somebody *please* correct the errors here, but AFAICT: Flaw published1/4/01, apparently fixed by redhat 4/10/01 (debian nailed this on 4/16). Somebody noticed on the kernel mailing list 7/24/01 that there was still a problem (improved exploit perhaps?), and this was fixed by redhat on 10/09/01. I can't find a second debian fix; maybe they got it right the first time. Anyway to answer your question, not quite.
As for the last story, I was attempting to compare timescale, not magnitude of the bug. You may accuse me of generalizing and I may accuse you of picking nits; the truth probably lies somewhere in between. Anyway, if you'd like an example of a long-lived *remote* root exploit, this should probably do the trick.
Ouch! Nice :).. although my intent was to criticize the reaction rather than to justify all the crap MS has done. Sorry I didn't make it clear.
1) Take MS exploit.
2) Rail about security through obscurity. Ignore similar linux issues.
3) Rail about how long a bug has been open. Ignore similar linux issues.
4) Ignore the linked article, and claim something stupid. In this case that MS isn't in a hurry to release a patch when in fact they have been testing a patch.
5) Jump to conclusions, like " It's a fundamental design issue".
6) Somehow tie the whole thing into the anti-trust suit.
Did I miss anything?