Scatter a bunch of fake corpses around your room. Splatter a little fake blood and gibs around for good measure, and then put a radial arm saw and sausage grinder off in a corner.
If you suspect the cam is active, throw on a bloody goalie mask and say into the camera... "I know where you live...."
Hehehe.... Getting a good arch isn't going to help much up at that altitude. But think of the possibilities....
* Finding the spot would be just a *tad* tricky.
* Naked spacediving would be *strongly* discouraged -- lest some, um, appendages break off.
* You could get a good 2000-way going without much trouble at all.
* You could skysurf across the continent.
* Two words -- freestyle fireball.
Sure they generate tons of power & are less prone to malfunction, but the problem is that a race car has to be able to handle extremes in decelleration as well as accelleration. So while the turbine car was fast -- but it had to maintain a steady speed because the turbine couldn't speed up, slow down, & speed up again through the turns the way "standard" cars could.
A turbine-powered Indycar would be toast on a road course, let alone an oval.
If./ gives in to M$ on this, you think they'll stop there? You think other companies won't try the same thing? If it worked once, it'll work again. They'll try the legal nastygram tactic on things which are further & further removed from what was originally intended (as if they haven't already) under the DMCA. Down the slippery slope we go!
Fact of the matter is, whether it's now or later, this issue is going to wind up in court. Better to fight it now than to set a precedent and try to work your way out of it later.
1. This has all the markings of a typical M$ vaporware announcement designed to stave off any mindshare Corel might garner with Corel Office 2000. If CO2K gets established in the Linux market, it might generate enough momentum to start making inroads in the Windoze realm, and eventually compete head-to-head with WinOffice. M$ will do everything in their power to make sure that doesn't happen.
2. If M$ *does* decide to write stuff for Linux, it be with the intent to "pollute" the Linux platform with all sorts of new , proprietary and incompatible-with-everything-else APIs and services -- just as they tried to do with that "other" rival platform: Java.
Either way, they're up to no good. Don't trust 'em. Even if they release the source, don't trust 'em.
In reading this and reading some material over at the Human Genome project, I can't help but wonder if we're going to see a *major* shift in the way medicine is practiced within out lifetime.
Now, we visit specialists who have expertise in a particular system of the body and it's afflictions: gastroenterologists, dermatologists, cardiologists, etc. Once the genome is mapped out, and we dicover that certain ailments are controlled by particular chromosomes, I wouldn't be surprised at all to see medicince shift from the current systemic approach to a chromosome-based approach.
Because each cromosome is so complex, you'd have specializations in particular chromosomes (or maybe groups of related chromosomes). So you'd go to see your doctor, who would then refer you not to a cardiologist, but a chromologist (?) who had expertise in, say Chromosome 11, which appears to control the problems your having.
I'm not an "old curmudgeon" and I still prefer the CLI over any GUI for file management. With a few keystrokes and some wildcards, I can do in a couple of seconds what would require 10x as much time and energy with a GUI. 3D would only be worse.
OK. Lemme get this straight. The SIS feature is going to have to perform file monitoring to see if a file matches any existing files and then set up the symbolic links. It's still going to have to do a comparison search and relink every time a file anywhere is created/changed/deleted. If that isn't a resource-suck, I haven't seen one.
Oh, wait! I have! Can anyone say Fast Find? Most of us know what a performance boon to our machine *that* is. First thing I do when I have a fresh Office install is disable that CPU/RAM/disk-hogging piece of #*@*$.
If they've figured out a way of doing this without significant system overhead, I'd be impressed, but this just sounds like yet more bloatware coming out of Redmond...
There's evidence to suggest that they control the Mac. How can anybody want them to get equivalent leverage (and ability to decree the killing of competing technology) on Linux?
Well, I doubt that they could get "leverage" over Linux, as they could with Apple. In a nutshell, M$ gets leverage because they enter into relationships wherein companies cater to their whim lest they suffer dire financial consequences.
So if they do have leverage over Apple, it's because Apple perceives that it could suffer financial hardship if M$ pulled the plug on Office for the Mac. Fewer people may buy Macs knowing there's no Office support.
You don't really have that with Linux for several reasons:
1. Linux isn't a single entity. There's no (real) centralized decisionmaker so there's really no one for M$ to get leverage over.
2. The Linux community, being pretty much M$-agnostic (if not largely anti-M$), began without M$ and will continue without M$. If more people adopt Linux because there's now an Office suite for them. Great. If those people go away when M$ pulls the plug on their Office suite. Great. The core will still remain & thrive.
I'm more worried about M$ motivations toward companies that are now developing (if not delivering or close to delivering) commercial office suites for Linux: Corel, Sun, Applixware, etc. I really fear that Corel could put out a great product, only to be stomped into the ground by M$, and then have M$ pull the plug on their own product ("Oh, that was just an experiment"). Too many great companies with great products have shrivelled up and died after M$ barged in & took over their market.
OK. Color me clueless, but how might one go about doing this?
It can't be as simple as mapping a network drive to that address.... can it? If he has file sharing turned on for his whole danged machine, then he's even a bigger fool than I previously thought from just reading the IRC logs.
Anyhoo, I honestly don't have any intention of poking around the guy's hard drive. I have ADSL myself and sure would like to plug a security hole as gaping as that. Any resources?
Another thought just came to me. In addition to those factors already mentioned (DoS attacks of unprecedented magnitude on multiple targets, all US targets, Clinton Administration just recently calling for increased regulation, etc.) there's another factor lends credence to the "the NSA did it" theory -- wasn't Congress just recently looking into reigning in the NSA in a *big* way with new regs?
What better ammunition to bring to Congress to argue *against* budget cuts and oversight than "Oh look! Hackers are bringing down computers all over the place! We need *more* power and money, not less!"
Seems to me if a bunch of script kiddies were doing a full scale assault, they'd go all over the place. Why limit yourself to the US?
The fact(?) that all of the sites are US lends further credence to the Oliver Stone theory. It would be an awfully nasty domestic scandal if the NSA/CIA/FBI were busted, but it would be an even worse international incident (if not an act of war) that I'm sure a government agency (as opposed to script kiddies) would be very careful to avoid.
God knows I'm no fan of M$, but last time I checked the Beta period was the time that bugs such as these were *supposed* to be flushed out and fixed(?).
So, as much as I'd love to, I can't feel too much glee over a security hole found in a Beta operating system. Of course, when they (prematurely) release Win2K and the gazillion other security holes rear their nasty little heads, I'll be right there with everyone else laughing my butt off.
The virtual first-down line is something that adds real value and enjoyment to watching football.
I'll say. I can't count how many times I've caught myself ready to scream: "You IDIOT! At least get past the yellow line before running out of bounds!";)
Seems to me the time is ripe for a book on the second wave of "Hackers". I've already got chapters laid out:
The Free Software Revolutionaries --------------------------------- Linus Torvalds & Linux Richard Stallman, Eric S. Raymond & GNU Phil Zimmerman & PGP
The Internet Hackers -------------------- Tim Berners-Lee & the WWW Scott Andreesen & Netscape James Gosling, Sun & Java
More Game Hackers ---------------- John Carmack, John Romero & Id
The Where Are They Now Files ---------------------------- Gate$ & Jobs
I've been typing like mad for almost 15 years now and never had wrist problems. In reading a lot of this stuff, I'm fairly convinced that my typing style has a lot to do with it.. i.e. I hunt & peck.
Speed really isn't an issue because after doing it for that long, I practically have the keyboard memorized. Plus, you start to see a lot of patterns to keystrokes. I have all sorts of funky finger/key combos depending on the word. So I've never really had much of an incentive to lear to type the "right" way.
Turns out that may be a good thing.
My wrists never touch because they can't. I type primarily with the middle 3 fingers (pinky every now & then -- thumb only on the spacebar) of both hands and have to move my hands around the keyboard to get to the keys I need.
This would make an interesting poll. how many type the 'right" way vs. how many hunt & peck. I'll be there are more "peckers" out there (heh heh) than you might think.
Slashdot Mirror
Give 'em something REALLY good to look at.
Scatter a bunch of fake corpses around your room. Splatter a little fake blood and gibs around for good measure, and then put a radial arm saw and sausage grinder off in a corner.
If you suspect the cam is active, throw on a bloody goalie mask and say into the camera... "I know where you live...."
Pray I don't alter it any further...
>
Hehehe.... Getting a good arch isn't going to help much up at that altitude. But think of the possibilities....
* Finding the spot would be just a *tad* tricky.
* Naked spacediving would be *strongly* discouraged -- lest some, um, appendages break off.
* You could get a good 2000-way going without much trouble at all.
* You could skysurf across the continent.
* Two words -- freestyle fireball.
:)
Turbine-powered Indycars died for a reason.
Sure they generate tons of power & are less prone to malfunction, but the problem is that a race car has to be able to handle extremes in decelleration as well as accelleration. So while the turbine car was fast -- but it had to maintain a steady speed because the turbine couldn't speed up, slow down, & speed up again through the turns the way "standard" cars could.
A turbine-powered Indycar would be toast on a road course, let alone an oval.
-----
Zennie
Oh I dunno, how 'bout looking for lines such as...
/* They should be using Media Player anyway */
if(realAudio())
breakRealAudio();
/* Dang hippie OS */
if(linuxPartition())
corruptRandomLinuxBlock();
-----
Zennie
They've got it all wrong.
We all know that Al Gore started the Open Source movement.
----
Dharma
Seriously.
./ gives in to M$ on this, you think they'll stop there? You think other companies won't try the same thing? If it worked once, it'll work again. They'll try the legal nastygram tactic on things which are further & further removed from what was originally intended (as if they haven't already) under the DMCA. Down the slippery slope we go!
If
Fact of the matter is, whether it's now or later, this issue is going to wind up in court. Better to fight it now than to set a precedent and try to work your way out of it later.
Just my $0.02
If they *do* go ahead and start porting to Linux, every service (which will be closed source, naturally) will *have* to run as root.
... I know it....
They're up to no good.... I know it
-----
Your friendly neighborhood
Oliver Stone theorist
1. This has all the markings of a typical M$ vaporware announcement designed to stave off any mindshare Corel might garner with Corel Office 2000. If CO2K gets established in the Linux market, it might generate enough momentum to start making inroads in the Windoze realm, and eventually compete head-to-head with WinOffice. M$ will do everything in their power to make sure that doesn't happen.
2. If M$ *does* decide to write stuff for Linux, it be with the intent to "pollute" the Linux platform with all sorts of new , proprietary and incompatible-with-everything-else APIs and services -- just as they tried to do with that "other" rival platform: Java.
Either way, they're up to no good. Don't trust 'em. Even if they release the source, don't trust 'em.
In reading this and reading some material over at the Human Genome project, I can't help but wonder if we're going to see a *major* shift in the way medicine is practiced within out lifetime.
Now, we visit specialists who have expertise in a particular system of the body and it's afflictions: gastroenterologists, dermatologists, cardiologists, etc. Once the genome is mapped out, and we dicover that certain ailments are controlled by particular chromosomes, I wouldn't be surprised at all to see medicince shift from the current systemic approach to a chromosome-based approach.
Because each cromosome is so complex, you'd have specializations in particular chromosomes (or maybe groups of related chromosomes). So you'd go to see your doctor, who would then refer you not to a cardiologist, but a chromologist (?) who had expertise in, say Chromosome 11, which appears to control the problems your having.
Booting Win2K: 100000 sec
I'm not an "old curmudgeon" and I still prefer the CLI over any GUI for file management. With a few keystrokes and some wildcards, I can do in a couple of seconds what would require 10x as much time and energy with a GUI. 3D would only be worse.
OK. Lemme get this straight. The SIS feature is going to have to perform file monitoring to see if a file matches any existing files and then set up the symbolic links. It's still going to have to do a comparison search and relink every time a file anywhere is created/changed/deleted. If that isn't a resource-suck, I haven't seen one.
Oh, wait! I have! Can anyone say Fast Find? Most of us know what a performance boon to our machine *that* is. First thing I do when I have a fresh Office install is disable that CPU/RAM/disk-hogging piece of #*@*$.
If they've figured out a way of doing this without significant system overhead, I'd be impressed, but this just sounds like yet more bloatware coming out of Redmond...
While I don't advocate this kind of conduct either, I can't help but sit back and think "That's the beauty of Karma ...." :)
There's evidence to suggest that they control the Mac. How can anybody want them to get equivalent leverage (and ability to decree the killing of competing technology) on Linux?
Well, I doubt that they could get "leverage" over Linux, as they could with Apple. In a nutshell, M$ gets leverage because they enter into relationships wherein companies cater to their whim lest they suffer dire financial consequences.
So if they do have leverage over Apple, it's because Apple perceives that it could suffer financial hardship if M$ pulled the plug on Office for the Mac. Fewer people may buy Macs knowing there's no Office support.
You don't really have that with Linux for several reasons:
1. Linux isn't a single entity. There's no (real) centralized decisionmaker so there's really no one for M$ to get leverage over.
2. The Linux community, being pretty much M$-agnostic (if not largely anti-M$), began without M$ and will continue without M$. If more people adopt Linux because there's now an Office suite for them. Great. If those people go away when M$ pulls the plug on their Office suite. Great. The core will still remain & thrive.
I'm more worried about M$ motivations toward companies that are now developing (if not delivering or close to delivering) commercial office suites for Linux: Corel, Sun, Applixware, etc. I really fear that Corel could put out a great product, only to be stomped into the ground by M$, and then have M$ pull the plug on their own product ("Oh, that was just an experiment"). Too many great companies with great products have shrivelled up and died after M$ barged in & took over their market.
OK. Color me clueless, but how might one go about doing this?
It can't be as simple as mapping a network drive to that address.... can it? If he has file sharing turned on for his whole danged machine, then he's even a bigger fool than I previously thought from just reading the IRC logs.
Anyhoo, I honestly don't have any intention of poking around the guy's hard drive. I have ADSL myself and sure would like to plug a security hole as gaping as that. Any resources?
Thanx
Another thought just came to me. In addition to those factors already mentioned (DoS attacks of unprecedented magnitude on multiple targets, all US targets, Clinton Administration just recently calling for increased regulation, etc.) there's another factor lends credence to the "the NSA did it" theory -- wasn't Congress just recently looking into reigning in the NSA in a *big* way with new regs?
What better ammunition to bring to Congress to argue *against* budget cuts and oversight than "Oh look! Hackers are bringing down computers all over the place! We need *more* power and money, not less!"
Seems to me if a bunch of script kiddies were doing a full scale assault, they'd go all over the place. Why limit yourself to the US?
The fact(?) that all of the sites are US lends further credence to the Oliver Stone theory. It would be an awfully nasty domestic scandal if the NSA/CIA/FBI were busted, but it would be an even worse international incident (if not an act of war) that I'm sure a government agency (as opposed to script kiddies) would be very careful to avoid.
Things that make you go "Hmmmmmm....."
Pretty much describes me except for the "elite" part. Being part of any "elite" class makes my skin crawl. :p
God knows I'm no fan of M$, but last time I checked the Beta period was the time that bugs such as these were *supposed* to be flushed out and fixed(?).
So, as much as I'd love to, I can't feel too much glee over a security hole found in a Beta operating system. Of course, when they (prematurely) release Win2K and the gazillion other security holes rear their nasty little heads, I'll be right there with everyone else laughing my butt off.
The virtual first-down line is something that adds real value and enjoyment to watching football.
;)
I'll say. I can't count how many times I've caught myself ready to scream: "You IDIOT! At least get past the yellow line before running out of bounds!"
Oh! That's right! Time Warner. How 'bout that?
Seems to me the time is ripe for a book on the second wave of "Hackers". I've already got chapters laid out:
The Free Software Revolutionaries
---------------------------------
Linus Torvalds & Linux
Richard Stallman, Eric S. Raymond & GNU
Phil Zimmerman & PGP
The Internet Hackers
--------------------
Tim Berners-Lee & the WWW
Scott Andreesen & Netscape
James Gosling, Sun & Java
More Game Hackers
----------------
John Carmack, John Romero & Id
The Where Are They Now Files
----------------------------
Gate$ & Jobs
Any names I forgot?
Can you imagine Q3 or Unreal on one of these bad boys? Add surround sound and.... and...
*Drool*
I've been typing like mad for almost 15 years now and never had wrist problems. In reading a lot of this stuff, I'm fairly convinced that my typing style has a lot to do with it.. i.e. I hunt & peck.
Speed really isn't an issue because after doing it for that long, I practically have the keyboard memorized. Plus, you start to see a lot of patterns to keystrokes. I have all sorts of funky finger/key combos depending on the word. So I've never really had much of an incentive to lear to type the "right" way.
Turns out that may be a good thing.
My wrists never touch because they can't. I type primarily with the middle 3 fingers (pinky every now & then -- thumb only on the spacebar) of both hands and have to move my hands around the keyboard to get to the keys I need.
This would make an interesting poll. how many type the 'right" way vs. how many hunt & peck. I'll be there are more "peckers" out there (heh heh) than you might think.