"the media" doesn't have ANY SORT of Internet Envy, though I'll agree that they do have Broadband Envy. If "the media" knew how to truly define and differentiate the Internet, they'd do everything in their power to shut it down. Oops, they already are.
Make no mistake, what "the media" wants out of the Internet is an on-demand distribution channel, and NOTHING more. A little trickle, upstream, and a firehose downstream. Anything else enables NASTY stuff like peer-to-peer and other "uncontrolled publication." Isn't the phrase "uncontrolled publication" what the ??AA problems are really all about?
Most of the posts haven't really been answering the question. Most of the posts have been helpful advice about how to stop being a spam-zombie, but haven't been answering whether or not he currently is one.
With apologies, because the connection I just made to them was a bit slow, there are: http://openrbl.org/ http://moensted.dk/spam / http://www.dnsstuff.com/tools/ip4r.ch
Unfortunately my domain is in there, because it really refers to my ISP-assigned IP, and their whole block is listed.
Are you suggesting that the first FCS test deployment might be against a target in Utah? Somehow I imagine that the Washington target is too hardened with it's $force$ $field$ able to deflect nearly anything.
Which version of.doc has your office standardized on? I have next-to-no experience with MS Word, but from what I've heard every release tweaks.doc a little.
I've also heard (much less reliably) that even Microsoft doesn't have a good document of the.doc format, they just have the golden source code. While the source IS the ultimate reference, for something that purports to be a Standard, there SHOULD be a document that is the ultimate reference, and code should be considered broken if it doesn't follow the standard. By the same token, if there are significant 'implementation dependent' issues, perhaps the documentation is broken, and needs to nail things down better. Can someone from MS cloak and answer?
As for me, I use AbiWord. I'm one of those cavemen elsewhere referred to, with little experience and use of word processors. I like AbiWord because it's simple and discoverable. I've done a little with Star/Open Office, but it's harder to do something simple with them, and what little I've seen of MS Word suggests the same.
Years back I read an article about a flame loudspeaker. The flame is pretty well ionized to begin with, so add an electrode at the bottom and top to inject the audio voltage. The envelope of the flame is modulated and it produces sound. Now that I think of it, the raw ionization of the flame was a bit weak, so they seeded some sodium (I forget if it was sodium glass or a wick into salt water.) into the bottom and got much better volume out.
About as close to zero mass as you can get. By no means stiff at all, but equally driven over its entire surface, so stiffness isn't important in this case.
Well, I guess Intel's recent habit of clocking at Ludicrous Speed does have some effect on the issue.
It's just that for decades you had active power and standby power, and CV**2 and leakage. The formers fit together, and so did the latters, and they DIDN'T interfere with each other. Maybe leakage doesn't dominate active power, but to even have it become significant was a rude change.
I know Prescott isn't in SOI. But that's a capacitive issue, and we were talking about leakage. Peaches, Pears.
Within the realm of SOI there may be some things that can also be done to reduce leakage. Since as you say, the capacitance is lower, you elect to lengthen the channel slightly and give up a little performance, just to reduce leakage. Also in SOI you can modulate the body under the channel, and play some leakage games that way.
In either technology you can sprinkle your shortest channels into the critical path, and back off elsewhere, again reducing leakage. I know AMD has done this in the past, sprinkling 'next generation' channel lengths into later revisions of the current generation. On Usenet they get criticized for 'not really being XXnM technology,' but for anyone with real experience, you know enough to control your design aggressiveness, and sprinkling can be a Good Thing.
Bzzzt.
90nM appears to be at the turning point where leakage becomes a significant part of total power. In prior generations leakage was only significant with clock reduced or stopped, but negligible compared to active power. It's still much lower than active power, but no longer negligible. Try a simple search on the terms "prescott", "leakage", and "power" for a little flavor.
Besides, the chads in 2000 were sleight-of-hand, with differences in the few hundred to few thousand votes. Somehow they distracted us from the systematic disenfranchisement of tens of thousands of black voters by mis-classifying them as felons. The story I read on the topic, link lost, but easy to find on google, made it seem deliberate. But even if it wasn't, it was badly WRONG. Malfeasance or Misfeasance, take your pick. Both are cause for impeachment. Instead, the person at the top of the process is a Party Hero.
Never heard of a 'hardware' router getting cracked before. Was it truly a crack, or was it something like bogus default settings that were never changed?
Because he secretly heard that if he can detect 10 other idiots, and pass the mystery on to them, and if each of them detects 10 idiots... that in 1 month he will receive $10e6 from an account in Nigeria.
I wasn't speaking on any relative merits of Clinton's health care plan. Rather that there was no national debate, no alternate proposal. Even discussion was shut down flat. I kept my job through the bust, but my pay has stayed pretty well flat, while my health care keeps rising, and the company keep whining about their share rising.
As for expiration, IMHO it's the arrogance of NO provisions at all. That DVD may wear out, but how about the stamper/master/master-mother? Those have longer lives, and those have no expiration, either. The same argument was once made about two-digit dates, Cobol, etc.
And that's just the thing that is going to kill the competitive posture of the US. Copyright extension and Draconian Media Contoll Authority doesn't really help the media industries, in the long run. It just helps them get lazy, and prevents them from adapting their business model to the realities of electronic distribution.
More nimble companies will arise in Asia (and no doubt elsewhere) that will have new business models that both allow for electronic distribution and keep artists paid/creating.
OK. Show me the 'copyright expiration field' in the DVD/CSS format.
Actually, I don't KNOW that it's not there, because I've never looked at the specs. But I'm absolutely sure it's not, because otherwise we'd have seen 'clock hacks' to bypass "protection" long ago. The lack of a 'copyright expiration field' might be taken as an indication of intent to keep extending copyrights forever. (I suspect it's really negligence, but I'll bet the MPAA never gets sued over their negliegnce, only chipmakers.)
I don't disagree with you. This is indicative of another problem the US is refusing to face. Back in 1992, Clinton tried to make health care reform a national focus. AS A NATION, we turned our backs on the whole issue, and it has come back to bite us badly. IMHO, health care costs are in large responsible for migration of jobs overseas. Not that I necessarily cared for Clinton's plan, BUT WE REFUSED TO EVEN DEBATE THE MATTER! Our bad!
The entire field of intellectual property NOW needs the same kind of national debate. We are in the process of screwing over our national competitive posture by pretending to stay with existing ways.
For more, see my other response on this tree. In short, I've played with Ada, and it fails my "2 week test" because there's a lot there to learn. Other tasks distract me before I've learned enough to be useful. Programming is not my job, it's what I sometimes use to do my job.
As I said elsewhere, I usually use Python. For the types of jobs I do, the performance of an interpreted language is entirely adequate. The ability to drop the code for weeks at a time, then return to it for a few days is critical, for me. If I ever get over the hump on Ada, it would fill my bill, though it's not as readily available.
I do quite a bit of Python. Actually, any programming for me is a sideline, since I'm primarily in chip design. So programming languages have to pass the "2 week test" for me. I seldom/never do any programming for more than about 2 weeks in a row, then some other firedrill comes along.
I NEED something I can get somewhere with within that two weeks. I NEED to have readable code, so when I get back to it, I can figure out what the heck I was doing several weeks ago, and continue. Obscure syntax doesn't hack it. Clarity does.
I used to use Pacal and Modula2, with various extensions, but Wirth is so far out of favor these days that it's hard to find. (Oberon (and/2) followers have an IMHO self-limiting attitude, too.) I've dabbled a bit with Ada, but to be honest, it goes too far the other way. It fails the "2 week test" with more "clarity" than I can readily learn how to use.
For the moment, Python and bash get most of my programming part-time.
Even if there are command line tools for manipulating the registry, it's still a specialized tool. You don't even need a text editor for/proc, just shell built-ins. This becomes more significant on a rescue diskette, though I guess we're getting to the era of rescue CDs, where space is much less a problem.
I'm not sure I see anything wrong with that, though I guess really you have to examine "cheapest" very carefully. I'm sure that the Slashdot crowd is even less likely to program in Ada than in Java, and gripe even harder about the higher "overhead" in Ada than even Java has, and how it gets in the way of their coding.
Yet you have to look at the initial assumption of Ada as a programming language *for embedded systems.* For the Ada target market, they had studies indicating that 90% of the programming "cost" was spent in maintenance. From this perspective, initial coding is a nit. Even debug was rated as more expensive than initial coding.
So you have to look at the meaning of the word, "cheapest." (If they mean cheapest tools, regardless of suitability to the job, I have to agree with your attitude, though.)
AMD has the NX bit, and ISTR that Intel doesn't have it on their IA32e, or whatever the heck they call it, and that they reserved NX for IA-64. The NX bit makes the job more demanding for virus and worm writers, so I would expect AMD to give them additional concerns.
I understand your position. You gotta do what you gotta do, and you were trying to achieve the same results in Windows that you had in Linux.
It's just that most times apples-to-apples comparisons come up, it's in the desktop arena and we get the cry, "Gimp ain't no Photoshop!" or "It's not Word!" So here's an apples-to-apples comparison, and granted it's not really desktop, but it IS a user interface issue.
"REGEDIT " isn't the obscure part. Just IMHO everything about the bits and handles after that is about equally obscure between regedit and/proc. Both are equally unfriendly. But you can do/proc without a special GUID program, so also IMHO it wins the toss.
Because of course using regedit to tweak the value of HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters is MUCH more intuitive and user friendly than doing something in/proc/sys/net/ipv4. Actually, I don't see any sort of tcp_fin_wait_2_timeout in there, nor do I see anything that looks like an equivalent parameter in the Windows help page. At least I see tcp_fin_timout in/proc, but don't see anything like it in the registry documentation page.
On a slightly more usable scale, if I'm going to use an obscure interface, at LEAST I'd prefer it be in cleartext than some odd binary thingy that can only be edited with a special tool. OK, perhaps/proc and the Registry are equally binary, since the tools let you plug in equivalent numbers. But it remains that I can do directory navigation on/proc, and must use a special tool for the Registry.
Even better, looking in/usr/src/linux/Documentation/networking/ip-sysctl. txt I find that tcp_fin_timeout is indeed used to control the time to hold the socket in FIN-WAIT-2, so it turns out that it is indeed the correct parameter. That still doesn't help me find the same parameter in the Microsoft documentation, which is on the web, not on the system, and if I can't get the networking running, how do I search?
Slashdot Mirror
"the media" doesn't have ANY SORT of Internet Envy, though I'll agree that they do have Broadband Envy. If "the media" knew how to truly define and differentiate the Internet, they'd do everything in their power to shut it down. Oops, they already are.
Make no mistake, what "the media" wants out of the Internet is an on-demand distribution channel, and NOTHING more. A little trickle, upstream, and a firehose downstream. Anything else enables NASTY stuff like peer-to-peer and other "uncontrolled publication." Isn't the phrase "uncontrolled publication" what the ??AA problems are really all about?
Most of the posts haven't really been answering the question. Most of the posts have been helpful advice about how to stop being a spam-zombie, but haven't been answering whether or not he currently is one.
m /
With apologies, because the connection I just made to them was a bit slow, there are:
http://openrbl.org/
http://moensted.dk/spa
http://www.dnsstuff.com/tools/ip4r.ch
Unfortunately my domain is in there, because it really refers to my ISP-assigned IP, and their whole block is listed.
Are you suggesting that the first FCS test deployment might be against a target in Utah? Somehow I imagine that the Washington target is too hardened with it's $force$ $field$ able to deflect nearly anything.
Which version of .doc has your office standardized on? I have next-to-no experience with MS Word, but from what I've heard every release tweaks .doc a little.
.doc format, they just have the golden source code. While the source IS the ultimate reference, for something that purports to be a Standard, there SHOULD be a document that is the ultimate reference, and code should be considered broken if it doesn't follow the standard. By the same token, if there are significant 'implementation dependent' issues, perhaps the documentation is broken, and needs to nail things down better. Can someone from MS cloak and answer?
I've also heard (much less reliably) that even Microsoft doesn't have a good document of the
As for me, I use AbiWord. I'm one of those cavemen elsewhere referred to, with little experience and use of word processors. I like AbiWord because it's simple and discoverable. I've done a little with Star/Open Office, but it's harder to do something simple with them, and what little I've seen of MS Word suggests the same.
Years back I read an article about a flame loudspeaker. The flame is pretty well ionized to begin with, so add an electrode at the bottom and top to inject the audio voltage. The envelope of the flame is modulated and it produces sound. Now that I think of it, the raw ionization of the flame was a bit weak, so they seeded some sodium (I forget if it was sodium glass or a wick into salt water.) into the bottom and got much better volume out.
About as close to zero mass as you can get. By no means stiff at all, but equally driven over its entire surface, so stiffness isn't important in this case.
Might involve stem cells. Can't have that. Nope. Nope.
Well, I guess Intel's recent habit of clocking at Ludicrous Speed does have some effect on the issue.
It's just that for decades you had active power and standby power, and CV**2 and leakage. The formers fit together, and so did the latters, and they DIDN'T interfere with each other. Maybe leakage doesn't dominate active power, but to even have it become significant was a rude change.
I know Prescott isn't in SOI. But that's a capacitive issue, and we were talking about leakage. Peaches, Pears.
Within the realm of SOI there may be some things that can also be done to reduce leakage. Since as you say, the capacitance is lower, you elect to lengthen the channel slightly and give up a little performance, just to reduce leakage. Also in SOI you can modulate the body under the channel, and play some leakage games that way.
In either technology you can sprinkle your shortest channels into the critical path, and back off elsewhere, again reducing leakage. I know AMD has done this in the past, sprinkling 'next generation' channel lengths into later revisions of the current generation. On Usenet they get criticized for 'not really being XXnM technology,' but for anyone with real experience, you know enough to control your design aggressiveness, and sprinkling can be a Good Thing.
Bzzzt. 90nM appears to be at the turning point where leakage becomes a significant part of total power. In prior generations leakage was only significant with clock reduced or stopped, but negligible compared to active power. It's still much lower than active power, but no longer negligible. Try a simple search on the terms "prescott", "leakage", and "power" for a little flavor.
Besides, the chads in 2000 were sleight-of-hand, with differences in the few hundred to few thousand votes. Somehow they distracted us from the systematic disenfranchisement of tens of thousands of black voters by mis-classifying them as felons. The story I read on the topic, link lost, but easy to find on google, made it seem deliberate. But even if it wasn't, it was badly WRONG. Malfeasance or Misfeasance, take your pick. Both are cause for impeachment. Instead, the person at the top of the process is a Party Hero.
Never heard of a 'hardware' router getting cracked before. Was it truly a crack, or was it something like bogus default settings that were never changed?
Because he secretly heard that if he can detect 10 other idiots, and pass the mystery on to them, and if each of them detects 10 idiots... that in 1 month he will receive $10e6 from an account in Nigeria.
I wasn't speaking on any relative merits of Clinton's health care plan. Rather that there was no national debate, no alternate proposal. Even discussion was shut down flat. I kept my job through the bust, but my pay has stayed pretty well flat, while my health care keeps rising, and the company keep whining about their share rising.
As for expiration, IMHO it's the arrogance of NO provisions at all. That DVD may wear out, but how about the stamper/master/master-mother? Those have longer lives, and those have no expiration, either. The same argument was once made about two-digit dates, Cobol, etc.
And that's just the thing that is going to kill the competitive posture of the US. Copyright extension and Draconian Media Contoll Authority doesn't really help the media industries, in the long run. It just helps them get lazy, and prevents them from adapting their business model to the realities of electronic distribution.
More nimble companies will arise in Asia (and no doubt elsewhere) that will have new business models that both allow for electronic distribution and keep artists paid/creating.
OK. Show me the 'copyright expiration field' in the DVD/CSS format.
Actually, I don't KNOW that it's not there, because I've never looked at the specs. But I'm absolutely sure it's not, because otherwise we'd have seen 'clock hacks' to bypass "protection" long ago. The lack of a 'copyright expiration field' might be taken as an indication of intent to keep extending copyrights forever. (I suspect it's really negligence, but I'll bet the MPAA never gets sued over their negliegnce, only chipmakers.)
I don't disagree with you. This is indicative of another problem the US is refusing to face. Back in 1992, Clinton tried to make health care reform a national focus. AS A NATION, we turned our backs on the whole issue, and it has come back to bite us badly. IMHO, health care costs are in large responsible for migration of jobs overseas. Not that I necessarily cared for Clinton's plan, BUT WE REFUSED TO EVEN DEBATE THE MATTER! Our bad!
The entire field of intellectual property NOW needs the same kind of national debate. We are in the process of screwing over our national competitive posture by pretending to stay with existing ways.
For more, see my other response on this tree. In short, I've played with Ada, and it fails my "2 week test" because there's a lot there to learn. Other tasks distract me before I've learned enough to be useful. Programming is not my job, it's what I sometimes use to do my job.
As I said elsewhere, I usually use Python. For the types of jobs I do, the performance of an interpreted language is entirely adequate. The ability to drop the code for weeks at a time, then return to it for a few days is critical, for me. If I ever get over the hump on Ada, it would fill my bill, though it's not as readily available.
I do quite a bit of Python. Actually, any programming for me is a sideline, since I'm primarily in chip design. So programming languages have to pass the "2 week test" for me. I seldom/never do any programming for more than about 2 weeks in a row, then some other firedrill comes along.
/2) followers have an IMHO self-limiting attitude, too.) I've dabbled a bit with Ada, but to be honest, it goes too far the other way. It fails the "2 week test" with more "clarity" than I can readily learn how to use.
I NEED something I can get somewhere with within that two weeks. I NEED to have readable code, so when I get back to it, I can figure out what the heck I was doing several weeks ago, and continue. Obscure syntax doesn't hack it. Clarity does.
I used to use Pacal and Modula2, with various extensions, but Wirth is so far out of favor these days that it's hard to find. (Oberon (and
For the moment, Python and bash get most of my programming part-time.
Even if there are command line tools for manipulating the registry, it's still a specialized tool. You don't even need a text editor for /proc, just shell built-ins. This becomes more significant on a rescue diskette, though I guess we're getting to the era of rescue CDs, where space is much less a problem.
Oh, the GUID was a typo.
Depends on if you're using -Os, -O2, or -O3.
I'm not sure I see anything wrong with that, though I guess really you have to examine "cheapest" very carefully. I'm sure that the Slashdot crowd is even less likely to program in Ada than in Java, and gripe even harder about the higher "overhead" in Ada than even Java has, and how it gets in the way of their coding.
Yet you have to look at the initial assumption of Ada as a programming language *for embedded systems.* For the Ada target market, they had studies indicating that 90% of the programming "cost" was spent in maintenance. From this perspective, initial coding is a nit. Even debug was rated as more expensive than initial coding.
So you have to look at the meaning of the word, "cheapest." (If they mean cheapest tools, regardless of suitability to the job, I have to agree with your attitude, though.)
AMD has the NX bit, and ISTR that Intel doesn't have it on their IA32e, or whatever the heck they call it, and that they reserved NX for IA-64. The NX bit makes the job more demanding for virus and worm writers, so I would expect AMD to give them additional concerns.
I understand your position. You gotta do what you gotta do, and you were trying to achieve the same results in Windows that you had in Linux.
It's just that most times apples-to-apples comparisons come up, it's in the desktop arena and we get the cry, "Gimp ain't no Photoshop!" or "It's not Word!" So here's an apples-to-apples comparison, and granted it's not really desktop, but it IS a user interface issue.
"REGEDIT " isn't the obscure part. Just IMHO everything about the bits and handles after that is about equally obscure between regedit and /proc. Both are equally unfriendly. But you can do /proc without a special GUID program, so also IMHO it wins the toss.
Because of course using regedit to tweak the value of HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters is MUCH more intuitive and user friendly than doing something in /proc/sys/net/ipv4. Actually, I don't see any sort of tcp_fin_wait_2_timeout in there, nor do I see anything that looks like an equivalent parameter in the Windows help page. At least I see tcp_fin_timout in /proc, but don't see anything like it in the registry documentation page.
/proc and the Registry are equally binary, since the tools let you plug in equivalent numbers. But it remains that I can do directory navigation on /proc, and must use a special tool for the Registry.
/usr/src/linux/Documentation/networking/ip-sysctl. txt I find that tcp_fin_timeout is indeed used to control the time to hold the socket in FIN-WAIT-2, so it turns out that it is indeed the correct parameter. That still doesn't help me find the same parameter in the Microsoft documentation, which is on the web, not on the system, and if I can't get the networking running, how do I search?
On a slightly more usable scale, if I'm going to use an obscure interface, at LEAST I'd prefer it be in cleartext than some odd binary thingy that can only be edited with a special tool. OK, perhaps
Even better, looking in
Your title reminded me of a line from Kieth Laumer's "Retief" books.
"Gentlemen! The purpose of diplomacy is to maintain tensions at a level short of War!"
It was meant as a joke, but I suspect it's the same justify-your-existence practiced by every level of management, and many workers.