The dynamic linker is nothing more than a program that does the "same thing" every time it runs: what it does is equivalent to reading the requested executable, writing its contents to memory as data, then jumping to it. (The reality is both more and less complicated due to mmaping.) System-level programs and libraries, plus just-in-time environments like Java, do stuff like that all the time.
If MS-DOS is from QDOS, there will be some code in QDOS. QDOS is from CP/M so there must be some code from that in it as well. So some of the code was owned by SCO. Wich means that SCO ownes the code to all off MS codes.
Actually, QDOS just copied the "look and feel" of CP/M, not the code. That's like saying that Microsoft copied actual Apple code (Steve: "Oh, here Bill, go right ahead!") in making Windows, or that various X Window Managers copied actual Microsoft code (Bill: "Hey, this Linux thing is so spiffy, I'll just let you guys borrow my code. Here, I'll even make a tarball for you.").
YOU might want to listen to a concert via ionospheric bounce - I would not. For AM, you get far too much phase shift as the ionosphere fluxes, for FM that is going to show up as massive noise - only the new digital shortwave would worth listening to.
I didn't say it would be a *good* way of transmitting, just that it would take a comparable amount of time.;-) But yeah, compressed digital would be the ideal way to go for that, followed by more bandwidth-wasteful two-frequency simulcast (since the two freqs would rarely fade out at the same time).
There's only one thing that example overlooks - there is no straight-line path from New York to LA that a radio signal can follow. So either the signal would have to be carried over terrestrial fiber... or bounce off a sat and incur 44,000 miles of delay.
Or bounce off the ionosphere (wavelength and atmospheric conditions permitting).
For a long time sleep paralysis was treated with SSRI's, usually tricyclic antidepressants that, in light doses, would keep REM light enough to fully emerge from the paralysis stage. But if you've ever been on an SSRI, the side effects can be pretty miserable.
Um, SSRIs (Selective Serotonin Reuptake Inhibitors -- the new generation of antidepressants, of which Prozac is the most famous) are a completely different beast from the older generation of tricyclic antidepressants. I've previously been on Paxil before for social anxiety and depression, and the only noteworthy side-effect was decreased sex drive (and my experience was pretty typical).
Um. does anyone have a mnemonic for when to use "there" as opposed to "their" in a sentence? I've been having problems with it for like 30 years.
I just thought of one, so here ya' go. "Their" is the posessive of "they". Think tHEIR -> HEIR -> inHEIRitance -> ownership. Combine that with the tHERE -> HERE -> place association by another reply, and you should have a handy pair of 'em.
I would argue that abstraction is coding's answer to poetic metaphor and ambiguity. By choosing the right abstractions, you can have a large and complex program suddenly snap into place as a smaller, more understandable, and sometimes faster (due to cache locality) replacement. It's like prose becoming poetry by finding the right metaphor.
Running Apache in a chroot wouldn't have necessarily helped -- the spamming app could have been a self-contained statically-linked binary. Firewall rules, however, would have been a good idea, unless the mail daemon and web daemon were on the same server for cost reasons. Even so, a few iptables -m owner rules on the server could have helped.
Technically no, the spammer never got root. The spambot was sending spam as an unprivileged user (the same one that Apache ran as), which is still plenty to run a spambot.
Any user can chmod files that he/she/it owns, even to deny him/her/itself access and then chmod it back.
There isn't anything built in at the command line to do it for you (at least, in any distro I'm aware of). You can kinda kludge it by reading/proc/net/dev, waiting 5 seconds, reading it again, and dividing the difference in bytes by 5. Hell, in fact, here's a Perl script I just knocked out to do it: bw-usage.pl. (You'll need Time::HiRes from CPAN; you can install it with perl -MCPAN -e 'install("Time::HiRes")' as root.)
It's a form of compression, like Huffman coding. Frequently used commands get short names, rarely used commands get longer names. In that context, the Unix naming conventions mostly make sense.
Most software (pretends to be|is) protected by both EULA plus copyright. GPLed software is only protected by copyright, so it would be completely unaffected.
If you hear a hiss or have volume trouble, it means that the ALSA driver for your particular card you're using is buggy and not initializing the card correctly, and it has nothing to do with the ALSA core itself. File a bug report with ALSA, and include which driver you're using and what card you have, because it'll never get fixed if the developers are never told about it.
Voyager did in fact land on a planet during one of the inter-season cliffhangers (the one where Seska takes over Voyager with her Kazon boyfriend's help. Oh, here, I found a link. The episode was "Basics", and Seska landed so she could kick them all to the curb on a primitive planet.)
I, um, probably shouldn't know that, but it was back when it looked like the series might actually have a chance, so take pity. Looking around, "Basics" actually opened Season 3, which was IMO the least sucky Voyager season up to the time I stopped watching (shortly after Kes became a Vorlon and 44 of DD joined the crew).
Plutonium is a heavy metal, and thus has chemotoxicity in addition to the radiation. Thankfully, most of the radiation is alpha particles, which seriously mitigates the radioactive risk, and the plutonium itself has no salts with respectible solubility in water (and is therefore relatively safe to eat compared to other heavy metals). However, small-but-constant ingestion or skin contact over years can permit toxic accumulation in bones, and fine dust can get trapped inside the lungs long enough to heavily dose the lung cells with alpha particles at close range.
TLC was bought out by the Discovery Channel quite a few years back, before the fluff even. It was probably 1995-97ish when they merged. Hell, TLC's official website is tlc.discovery.com.
I'm sorry to hear that. Nutrasweet actually gives me the runs myself, if I drink more than about 30 oz of diet cola in a day. However, the fact that my sister's tongue swells up in allergic reaction to strawberries doesn't mean that we need a site called strawberrieskill.com spuriously claiming that strawberries outright cause a serious disease known to have a large genetic component.
2. Aspartame in MRPs : Almost ALL meal replacement powders sold in GNC have aspartame. Check aspartamekills.com for known risks. Lately, a few ( eg. MET-RX ) have switched to suclarose and prominently advertize "No aspartame", but doesn't that make then liable since they have sold aspartame-laced powders for so many years before making the switch.
I'd never heard of this, so I checked out the site and it set off my "Steve Gibson" meter. On a hunch, I did a google for "aspartame skeptic", and a few links in I found the following article:
http://www.csicop.org/cmi/reviews/aspartame.html. I'll wait a few years for the final verdict myself, by which time sucralosekills.org should be up and some new sweetener will be in vogue.
The rest of your post is a bit exaggerated in places but basically spot-on. Personally, I would have extended the ephedra rant to include all "thermogenic" products, as they're all going to (by definition) be similar in effect.
Although Doom's engine was sorta-2D, the user experience was strictly 3D, as are all FPS games. Calling Doom a 2D game is dishonest. It's just as dishonest as calling Super Smash Bros. a 3D game when it's a 2D game on a 3D engine.
Actually, antimatter has real, positive mass, so it behaves identically to matter w.r.t. gravity. Antimatter not only attracts itself gravitationally, but it also attracts matter (and vice versa). To get gravitational repulsion, you would need some form of matter with negative mass (at least for Newtonian physics).
A computer you can touch is a computer you can crack. It doesn't matter if it's Trusted Foonix with Mandatory Access Controls, Linux with shadow passwords, Windows 2009 on an NTFSv8 partition, or a ratty old Win95 box in single user mode and no password. If there's no physical security, the best you can hope for is a computer that self-destructs when tampered with, and even that's writing to Santa Claus.
Unfortunately, the mechanism by which esddsp and artsdsp redirect the audio can cause a few programs to crash. I'm not sure exactly what the deal is, but the more complex a program is the more likely it seems to be that it will crash under a wrapper. Sadly, the closed-source programs that most need a wrapper frequently fall under that category.
I wonder about the efficiency of H2 production every time some political yahoo, or tree-hunging greenie starts ranting about fuel cells. Breaking hydrogen out of its current chemical compounds; hydrocarbons, water, etc will require a substantial amount of energy. Then the hydrogen has to be stored, and it is notorious for being one of the most difficult to store compounds in existence. Then you have safety issues because H2 is also highly flammable. One poster pointed out that H2 will dissipate while gasoline forms a puddle, but its greater propensity to explode in the first place probably counteracts that benefit. Then you have the issues with H2O exhaust. Yes, it is water vapor we are talking about, but when 100 million americans drive to work everyday, that is a lot of water vapor, the potential for ecosystem impact is very real.
This link has some facts about hydrogen safety. Basically, for every safety problem hydrogen has, gasoline has it twofold or more. Re: water vapor, we already create an amount of water vapor on the same order of magnitude by burning gasoline, plus CO2 and traces of more exotic stuff like CO and hydrocarbon radicals. I, for one, welcome our new insect overlords.
Nuclear is non-renewable. Fission or fusion, it doesn't matter.
Well, if you're going to take the long view, nothing is renewable, not even sunlight. But on a much more reasonable scale of, say, billions of years, fusion does nicely. Just ask any star.
Furthermore, fusion presents a second problem in that a key fuel is hydrogen itself... Now if you're using electrolysis to get H out of water at about 10% efficiency, your reactor can't even generate enough power to buy its own fuel. The economics suck.
Since fusion takes place at extremes of temperatures, well into the gas/plasma transition, the reaction H2O + Heat -> 2H + O occurs spontaneously and you don't even need electricity.
The dynamic linker is nothing more than a program that does the "same thing" every time it runs: what it does is equivalent to reading the requested executable, writing its contents to memory as data, then jumping to it. (The reality is both more and less complicated due to mmaping.) System-level programs and libraries, plus just-in-time environments like Java, do stuff like that all the time.
If MS-DOS is from QDOS, there will be some code in QDOS. QDOS is from CP/M so there must be some code from that in it as well. So some of the code was owned by SCO. Wich means that SCO ownes the code to all off MS codes.
Actually, QDOS just copied the "look and feel" of CP/M, not the code. That's like saying that Microsoft copied actual Apple code (Steve: "Oh, here Bill, go right ahead!") in making Windows, or that various X Window Managers copied actual Microsoft code (Bill: "Hey, this Linux thing is so spiffy, I'll just let you guys borrow my code. Here, I'll even make a tarball for you.").
YOU might want to listen to a concert via ionospheric bounce - I would not. For AM, you get far too much phase shift as the ionosphere fluxes, for FM that is going to show up as massive noise - only the new digital shortwave would worth listening to.
I didn't say it would be a *good* way of transmitting, just that it would take a comparable amount of time. ;-) But yeah, compressed digital would be the ideal way to go for that, followed by more bandwidth-wasteful two-frequency simulcast (since the two freqs would rarely fade out at the same time).
There's only one thing that example overlooks - there is no straight-line path from New York to LA that a radio signal can follow. So either the signal would have to be carried over terrestrial fiber ... or bounce off a sat and incur 44,000 miles of delay.
Or bounce off the ionosphere (wavelength and atmospheric conditions permitting).
For a long time sleep paralysis was treated with SSRI's, usually tricyclic antidepressants that, in light doses, would keep REM light enough to fully emerge from the paralysis stage. But if you've ever been on an SSRI, the side effects can be pretty miserable.
Um, SSRIs (Selective Serotonin Reuptake Inhibitors -- the new generation of antidepressants, of which Prozac is the most famous) are a completely different beast from the older generation of tricyclic antidepressants. I've previously been on Paxil before for social anxiety and depression, and the only noteworthy side-effect was decreased sex drive (and my experience was pretty typical).
Um. does anyone have a mnemonic for when to use "there" as opposed to "their" in a sentence? I've been having problems with it for like 30 years.
I just thought of one, so here ya' go. "Their" is the posessive of "they". Think tHEIR -> HEIR -> inHEIRitance -> ownership. Combine that with the tHERE -> HERE -> place association by another reply, and you should have a handy pair of 'em.
I would argue that abstraction is coding's answer to poetic metaphor and ambiguity. By choosing the right abstractions, you can have a large and complex program suddenly snap into place as a smaller, more understandable, and sometimes faster (due to cache locality) replacement. It's like prose becoming poetry by finding the right metaphor.
C is heroic couplets. Java is blank verse. Perl is rhymed couplets. LISP is a haiku. Assembly is free verse. COBOL, of course, is a disaster.
Running Apache in a chroot wouldn't have necessarily helped -- the spamming app could have been a self-contained statically-linked binary. Firewall rules, however, would have been a good idea, unless the mail daemon and web daemon were on the same server for cost reasons. Even so, a few iptables -m owner rules on the server could have helped.
It's a form of compression, like Huffman coding. Frequently used commands get short names, rarely used commands get longer names. In that context, the Unix naming conventions mostly make sense.
Most software (pretends to be|is) protected by both EULA plus copyright. GPLed software is only protected by copyright, so it would be completely unaffected.
If you hear a hiss or have volume trouble, it means that the ALSA driver for your particular card you're using is buggy and not initializing the card correctly, and it has nothing to do with the ALSA core itself. File a bug report with ALSA, and include which driver you're using and what card you have, because it'll never get fixed if the developers are never told about it.
Voyager did in fact land on a planet during one of the inter-season cliffhangers (the one where Seska takes over Voyager with her Kazon boyfriend's help. Oh, here, I found a link. The episode was "Basics", and Seska landed so she could kick them all to the curb on a primitive planet.)
I, um, probably shouldn't know that, but it was back when it looked like the series might actually have a chance, so take pity. Looking around, "Basics" actually opened Season 3, which was IMO the least sucky Voyager season up to the time I stopped watching (shortly after Kes became a Vorlon and 44 of DD joined the crew).
Plutonium is a heavy metal, and thus has chemotoxicity in addition to the radiation. Thankfully, most of the radiation is alpha particles, which seriously mitigates the radioactive risk, and the plutonium itself has no salts with respectible solubility in water (and is therefore relatively safe to eat compared to other heavy metals). However, small-but-constant ingestion or skin contact over years can permit toxic accumulation in bones, and fine dust can get trapped inside the lungs long enough to heavily dose the lung cells with alpha particles at close range.
TLC was bought out by the Discovery Channel quite a few years back, before the fluff even. It was probably 1995-97ish when they merged. Hell, TLC's official website is tlc.discovery.com.
I'm sorry to hear that. Nutrasweet actually gives me the runs myself, if I drink more than about 30 oz of diet cola in a day. However, the fact that my sister's tongue swells up in allergic reaction to strawberries doesn't mean that we need a site called strawberrieskill.com spuriously claiming that strawberries outright cause a serious disease known to have a large genetic component.
I'd never heard of this, so I checked out the site and it set off my "Steve Gibson" meter. On a hunch, I did a google for "aspartame skeptic", and a few links in I found the following article: http://www.csicop.org/cmi/reviews/aspartame.html. I'll wait a few years for the final verdict myself, by which time sucralosekills.org should be up and some new sweetener will be in vogue.
The rest of your post is a bit exaggerated in places but basically spot-on. Personally, I would have extended the ephedra rant to include all "thermogenic" products, as they're all going to (by definition) be similar in effect.
Although Doom's engine was sorta-2D, the user experience was strictly 3D, as are all FPS games. Calling Doom a 2D game is dishonest. It's just as dishonest as calling Super Smash Bros. a 3D game when it's a 2D game on a 3D engine.
Actually, antimatter has real, positive mass, so it behaves identically to matter w.r.t. gravity. Antimatter not only attracts itself gravitationally, but it also attracts matter (and vice versa). To get gravitational repulsion, you would need some form of matter with negative mass (at least for Newtonian physics).
A computer you can touch is a computer you can crack. It doesn't matter if it's Trusted Foonix with Mandatory Access Controls, Linux with shadow passwords, Windows 2009 on an NTFSv8 partition, or a ratty old Win95 box in single user mode and no password. If there's no physical security, the best you can hope for is a computer that self-destructs when tampered with, and even that's writing to Santa Claus.
Unfortunately, the mechanism by which esddsp and artsdsp redirect the audio can cause a few programs to crash. I'm not sure exactly what the deal is, but the more complex a program is the more likely it seems to be that it will crash under a wrapper. Sadly, the closed-source programs that most need a wrapper frequently fall under that category.
This link has some facts about hydrogen safety. Basically, for every safety problem hydrogen has, gasoline has it twofold or more. Re: water vapor, we already create an amount of water vapor on the same order of magnitude by burning gasoline, plus CO2 and traces of more exotic stuff like CO and hydrocarbon radicals. I, for one, welcome our new insect overlords.
Nuclear is non-renewable. Fission or fusion, it doesn't matter.
Well, if you're going to take the long view, nothing is renewable, not even sunlight. But on a much more reasonable scale of, say, billions of years, fusion does nicely. Just ask any star.
Furthermore, fusion presents a second problem in that a key fuel is hydrogen itself... Now if you're using electrolysis to get H out of water at about 10% efficiency, your reactor can't even generate enough power to buy its own fuel. The economics suck.
Since fusion takes place at extremes of temperatures, well into the gas/plasma transition, the reaction H2O + Heat -> 2H + O occurs spontaneously and you don't even need electricity.
Nope, that's unbalanced. You have two H atoms on the left, but four H atoms on the right. The parent poster's equation is balanced correctly.