SGI's Altix handles up to 64 processors on a Linux kernel using the patches they release as opensource. As SGI hacks away at their bigmem and numa patches, they'll be able to handle more and more processors. The plan is to eventually graft enough IRIX technology to support just as many processors on Altix as they do with MIPS processors in Origin with IRIX.
Even if you aren't a fan of Itanium2, Linux, or NUMA, these patches are bringing some nifty high-end tech to the free software arena.
That's Spamcop's list of spam-vertised web sites. All of those sites have submission forms; just put the email address in there and you'll be rockin' and rollin' within a few hours. I got into a 'spam war' with one of my roommates back in college, and with that Spamcop list I was able to render his email account COMPLETELY useless within a couple of hours (If you're reading this, sorry 'bout that Brian... )
Speaking of spam, on a random side note, I've recently started checking all of my email accounts with Shadango.com. Anybody else tried that yet? Shadango allows you to have advanced filtering applied to ALL of your existing accounts (both POP and IMAP). It's frickin' great. So now I don't get any more spam, plus I can check all 5 of my email accounts from one place. They've also got file storage, a calendar, etc. It's money. Check it out.
The most impressive thing about it is how small it is. over 280 blades + disk server in a single rack.
then you realize its sitting in an uncooled ordinary room shared by people. its not putting out hardly any heat the building air cant keep up with. its plugged into a normal building power strip, and its not making much noise.
then you see the benchmarks. this thing runs faster than the equivalent pentium on scientific codes. How is this possible you wonder if its doing this code morphing. the answer is that the transmeta JIT code morph results in code that executes faster on the transmeta than the original pentium code. On scientific code with lots of long tight loops the overhead of the code morph goes away and it runs faster. (the opposite is true for GUI desktop apps where it is constantly jumping around and not spending time in small sections of code.).
finally they show you the uptime. forever. no dead units. (on our other pentium cluster form the same manufacturuere we replace as mauch as blade a day)
these things are way better price performance ratio than pentiums when you factor in the total lack of building infrastructure, and maintainence. low heat keeps them stable.
1) shared nothing: in this, each computer is only connected to each other via simple IP network. no disks are shared. each machine serves part of data. these cluster doesn't work reliably when you have to aggregations. e.g. if one of the machine fails and you try to to "avg()" and if the data is spread across machines, the query would fail, since one of the machine is not available. most enterprise apps cannot work in this config without degradation. e.g. IBM study showed that 2 node cluster is slower and less reliable than 1 node system when running SAP.
IBM on windows and unix and MS uses this type of clustering (also called federated database approach or shared nothing approach).
2) shared disk between two computers: in this case, there are multiple machines and multiple disks. each disk is atleast connected to two computers. if one of the computer fails, other takes over. no mainstream database uses this mode, but it is used by hp-nonstop. still, each machine serves up part of the data and hence standard enterprise apps like SAP etc cannot take clustering advantage without lot of modification.
3) shared everything: in this, each disk is connected to all the machines in the cluster. any number of machines can fail and yet the system would keep running as long as atleast one machine is up. this is used by Oracle. all the machine sees all the data. standard apps like SAP etc can be run in this kind of configs with minor modification or no modification at all. this method is also used by IBM in their mainframe database (which outsells their windows and unix database by huge margine). most enterprise apps are deployed in this type of cluster configuration.
the approach one is simpler from hardware point of view. also, for database kernel writers, this is the easiest to implement. however, the user would need to break up data judiciously and spread acros s machines. also adding a node and removing a node will require re-partitioning of data. mostly only custom apps which are fully aware of your partitioning etc will be able to take advantage. it is also easy to make it scale for simple custom app and so most of TPC-C benchmarks are published in this configuration.
approach 3 requires special shared disk system. the database implementation is very complex. the kernel writers have to worry about two computers simultaneously accessing disks or overwriting each others data etc. this is the thing that Oracle is pushing across all platforms and IBM is pushing for its mainframes.
approach 2 is similar to approach 1 except that it adds redundancy and hence is more reliable.
I was an electronics tech for the Navy. Did maintenance on comm gear and other electronic equipment. Went through a variety of schools. I feel the education is very good and the hands on experience is great. I worked with a variety of test equipment, receivers, transmitters, communication gear, etc.
When I was in, the most technologically advanced jobs were CTM (Crypto Tech Maintenance), ET (Electronics Tech), DS (Data Systems), among others (more specialized).
One individual I met while in was a Senior Chief ET at Treasure Island. As far as I know, he was one of the people to first develop laser listening devices for civilian purchase, or at least one of the first that I've heard of. I didn't see a working model, but he explained what it was and how it worked to me.
At yet another installation, I met a group of Navy Petty Officers and Air Force Sgt's that were developing a means to render video to CD, at the time, it wasn't common place (I hadn't even heard of the technology at the time) to find video on CD's.
There's many "cutting edge" tech gadgets being used in the.mil, of course these are the ones you never hear about until they're released to civilian use.
It's like the old story about the guy that invented the first "radar gun" for highway patrolmen, he also invented the first "radar detector" for civilians.:-)
I've always wondered about people like Darl McBride. Obviously, they are paid a great deal of money to put a certain spin on things, and they try very hard to do it. What I've never understood about the psychology of it is this: do they actually believe themselves? Do they start out knowing they are lying, then convince themselves about it along the way? Or does the notion of truth not even cross their minds, as they are busy trying to define the reality they want?
Typical Linux Geek thinking ease-of-use = dumbing down and that a good interface means pretty icons.
Ease of use means making the computer work the way PEOPLE think, not forcing people to work the way COMPUTERS think.
Linux geeks and other developers, who have been conditioned to think like the computer because of the work they do, have the mistaken notion that advanced computer user means a user who has learned to force the natural human way of doing things into the artificial machine way a computer does things.
Any interface that doesn't force this paradigm is "dumbed down."
The truth is, the Linux geek has simply been conditioned to do things the difficult way, not the natural way. Designing the interface to do things the natural way is not dumbing it down, it's making the Linux Geek's paradigm obsolete. Of course, the Linux Geek doesn't like this, so in a fit of human ego, he looks his nose down on anything that points out the stupidity of his position (working the way the computer demands; being the tool of the computer), and calls it "dumbing down."
Especially for legal content... bit torrent has made it so that you can get all sorts of legal content like game demos, linux distros, etc. off p2p without having to be on horribly slow ftp servers.
Part of the problem is that Kasparov is this generation's GM. Kasparov plays very emotional games. He's not just looking to beat you in his first match; he's looking to utterly destroy, smash and humiliate you with a dramatic and embarrassing win.
This is a great strategy against people, but it's not so effective against computers. Kasparov is probably the worst chess master to pit against a machine since Ruy Lopez (I think he's won with the Ruy Lopez opening a few times, case in point: it's a brutal and humiliating play for the losing opponent).
Kasparov knows that the computer can "think through" future moves better than he can. Computers, in fact, do the opposite of human chess players: we set goals and try to find ways to get there while computers search through various ways to find a satisfactory goal they can achieve. So, Kasparov plays it very conservative and keeps himself out of any situations that give the computer too much range of foresight, which is why the Kasparov/computer matches tend to look like Verdun (though he's been surprised a few times).
Personally I'd like to see some of the younger generation take on the big programs. They tend to play more technically and less passionately than Kasparov and his generation.
I read several of the reviews, and all stuck with 32 bit code for the comparition between the Intel P4 and the AMD Athalon 64. Linux runs on the Atahlon in 64 bit mode, wouldn't be hard to compile PovRay and Doom on a 64 bit compiler and see if anything changes. Thats just for an easy test.
Many real world (science?) applications benifit from 64 bit processors, find some (presumably running on UltraSparc, PPC, Alpha, or such) and port them over to see how the 64bit abilities of this chip compares to the other existing chips.
I run open source OSes, and open Source applications. I don't care about 32 bit performance because I'm fairly sure that if I did have an Athalon 64 I wouldn't run 32 bit code very often. I can choose between many chips, compatable instruction sets to me means gcc (or other compiler) has an output for them. 32 bit x86 compatiabily is nice for the few times I have to run something 32 bit (normally in Wine) and that doesn't happen very often.
I run several domains and use multiple blacklists. The blacklists are incredibly effective, especially those which are country-wide like taiwan.blackholes.us and china.blackholes.us. I, and the other users of my domain, don't communicate with people in China or Taiwan. If I disable the blacklists, the ONLY thing that comes to us from those countries is spam. It has a tremendous impact on the amount that I get. Because of those punitive "broadlists", many ISPs like AT&T and PSI who used to write "pink contracts" and host spammers no longer will. The broadlisting makes harboring spammers unsafe. AT&T is not going to piss off their entire subscriber base just to get one big pink contract from some spam house. It's not worth it to them. Many ISPs, especially dial-up ISPs have blocked outgoing port 25 so spammers can't use them for throwaway accounts from with to spam. No ISP wants to risk some spammer paying $9.99 for a month of service which will get the ISP blacklisted.
See what really frustrates the hell out of me is that I want artists to succeed. I don't want them to be slaves to the RIAA, and I don't want them getting screwed over by pirates. The problem is that in the RIAA's efforts to protect their profits (they don't give a hoot about artists), they are making it much harder for me to listen to music the way most people want to.
Linux Conference 2003 The NX Project What is NX? - NX is a remote desktop system based on X-Window - Adds features to X-Window usually found in proprietary systems like MS RDP and Citrix ICA - Makes possible to run contemporary Unix applications over the Internet - Compresses the X protocol by an average factor of 50:1 and more - Allows users to work comfortably on 28.8Kbps or even 9.6 Kbps modem connections - Reduces X protocol round-trips nearly to zero - Implements image streaming algorythms to reduce the perceived latency - Is able to translate RDP and RFB foreign remote desktop protocols to X - Runs these foreign remote desktop sessions faster than their native protocols - It integrates with SMB to provide access to the client's file systems - It integrates with ARTSD and ESD to allow media playback - Adds server management tools to handle X, RDP and RFB sessions run by users - Architecture is designed to distribute the server workload between multiple nodes - It leverages SSH remote execution capabilities to avoid the need to run a new network server - It is able to encrypt and protect the network traffic by tunneling the connections through SSH - Server is intended to run on any Unix OS - Client runs on Linux, Windows, Solaris, Mac OS/X, Sony Playstation/2, MS Xbox and embedded devices like HP/Compaq iPAQ and Sharp Zaurus - NX core components and X compression libraries are released under the GPL license - NX client GUI (nxclient) and the NX server manager (nxserver) are commercial software - The NX client-server protocol is open - A library handling the client-server protocol and a compatible command-line NX client have been released under the GPL license - NoMachine has publicly offered its help to let OSS developers build a free implementation of both the nxclient GUI and the nxserver NX System Architecture X NX "protocol" (internet, modem) Local X display Local NX proxy system Remote NX proxy system Remote X application Windows Terminal Server, XP Prof. (Tight) VNCServer nxagent (based on Xnest) nxdesktop (based on rdesktop) nxviewer (based on vncviewer) RDP X RFB What features are missing? - X session persistence and reconnection - Better support of RENDER extension - Better support of X applications in seamless mode - Better support of SMB file-sharing and printing - Seamless access to client's peripherals and devices - A new multimedia architecture with native streaming of media formats - Better integration with Unix and Windows desktop environments to allow point-and-click remote execution of applications - Better server management tools, including a Web administration interface - An open API to let customers and developers to write server extensions What NX would like to become? - A convenient way to let users of mobile phones and other thin devices to get access to complex, rich applications - A server infrastructure by which people can easily run applications regardless they reside on the local machine or a remote server - A peer-to-peer computing environment where users can easily access computing resources, like storage and printers, on any server available on the Internet - A step in the direction of the "network desktop" envisioned by many
Homer: [reading screen] "To Start Press Any Key". Where's the ANY key? I see Esk ["ESC"], Catarl ["CTRL"], and Pig-Up ["PGUP"]. There doesn't seem to be any ANY key. Woo! All this computer hacking is making me thirsty. I think I'll order a TAB. [presses TAB key] Awp...no time for that now, the computer's starting. Blatanly stolen from Simpsons episode 3f05.
I would like to see a highly publicized case of holding some home broadband user responsible for the fact that their machine was hijacked to send spam or participate in some DDoS.
I've talked to too many people who've said, "I don't need to bother securing my home system because I've got nothing anyone would want." I've answered, "They want to use your machine to attack me." But the message doesn't sink in.
While these end users are being provided with crap systems, there is a market out there. If their choice of bad systems gets them severly spanked, they will start making demands of their providers.
All it would take would be a couple of high profile cases.
SCO goes after Linux as a marketing/gain money tool.
They get hated.
Opposing SCO becomes popular.
SCO has just handed people a new marketing tool - oppose/stand up to SCO, get attention, customers, etc.
Though in reflection, their egregeous approach to an unsubstantiated claim was bound to provoke a backlash. And it was bound to be something that people would take advantage of.
Did SCO even see this? My guess, no. They're up their in their own little world.
Slashdot Mirror
How IRONIC that you are an AC yourself!
How is space trivial?! Besides, they have done a pretty good job of exploring the nearest objects.
SGI's Altix handles up to 64 processors on a Linux kernel using the patches they release as opensource. As SGI hacks away at their bigmem and numa patches, they'll be able to handle more and more processors. The plan is to eventually graft enough IRIX technology to support just as many processors on Altix as they do with MIPS processors in Origin with IRIX.
Even if you aren't a fan of Itanium2, Linux, or NUMA, these patches are bringing some nifty high-end tech to the free software arena.
So you want a lot of spam, do ya?
p e= www
http://www.spamcop.net/w3m?action=inprogress&ty
That's Spamcop's list of spam-vertised web sites. All of those sites have submission forms; just put the email address in there and you'll be rockin' and rollin' within a few hours. I got into a 'spam war' with one of my roommates back in college, and with that Spamcop list I was able to render his email account COMPLETELY useless within a couple of hours (If you're reading this, sorry 'bout that Brian... )
Speaking of spam, on a random side note, I've recently started checking all of my email accounts with Shadango.com. Anybody else tried that yet? Shadango allows you to have advanced filtering applied to ALL of your existing accounts (both POP and IMAP). It's frickin' great. So now I don't get any more spam, plus I can check all 5 of my email accounts from one place. They've also got file storage, a calendar, etc. It's money. Check it out.
The most impressive thing about it is how small it is.
over 280 blades + disk server in a single rack.
then you realize its sitting in an uncooled ordinary room shared by people. its not putting out hardly any heat the building air cant keep up with. its plugged into a normal building power strip, and its not making much noise.
then you see the benchmarks. this thing runs faster than the equivalent pentium on scientific codes. How is this possible you wonder if its doing this code morphing. the answer is that the transmeta JIT code morph results in code that executes faster on the transmeta than the original pentium code. On scientific code with lots of long tight loops the overhead of the code morph goes away and it runs faster. (the opposite is true for GUI desktop apps where it is constantly jumping around and not spending time in small sections of code.).
finally they show you the uptime. forever. no dead units. (on our other pentium cluster form the same manufacturuere we replace as mauch as blade a day)
these things are way better price performance ratio than pentiums when you factor in the total lack of building infrastructure, and maintainence. low heat keeps them stable.
there are basically three type of clusters:
1) shared nothing: in this, each computer is only connected to each other via simple IP network. no disks are shared. each machine serves part of data. these cluster doesn't work reliably when you have to aggregations. e.g. if one of the machine fails and you try to to "avg()" and if the data is spread across machines, the query would fail, since one of the machine is not available. most enterprise apps cannot work in this config without degradation. e.g. IBM study showed that 2 node cluster is slower and less reliable than 1 node system when running SAP.
IBM on windows and unix and MS uses this type of clustering (also called federated database approach or shared nothing approach).
2) shared disk between two computers: in this case, there are multiple machines and multiple disks. each disk is atleast connected to two computers. if one of the computer fails, other takes over. no mainstream database uses this mode, but it is used by hp-nonstop. still, each machine serves up part of the data and hence standard enterprise apps like SAP etc cannot take clustering advantage without lot of modification.
3) shared everything: in this, each disk is connected to all the machines in the cluster. any number of machines can fail and yet the system would keep running as long as atleast one machine is up. this is used by Oracle. all the machine sees all the data. standard apps like SAP etc can be run in this kind of configs with minor modification or no modification at all. this method is also used by IBM in their mainframe database (which outsells their windows and unix database by huge margine). most enterprise apps are deployed in this type of cluster configuration.
the approach one is simpler from hardware point of view. also, for database kernel writers, this is the easiest to implement. however, the user would need to break up data judiciously and spread acros s machines. also adding a node and removing a node will require re-partitioning of data. mostly only custom apps which are fully aware of your partitioning etc will be able to take advantage.
it is also easy to make it scale for simple custom app and so most of TPC-C benchmarks are published in this configuration.
approach 3 requires special shared disk system. the database implementation is very complex. the kernel writers have to worry about two computers simultaneously accessing disks or overwriting each others data etc. this is the thing that Oracle is pushing across all platforms and IBM is pushing for its mainframes.
approach 2 is similar to approach 1 except that it adds redundancy and hence is more reliable.
I was an electronics tech for the Navy. Did maintenance on comm gear and other electronic equipment. Went through a variety of schools. I feel the education is very good and the hands on experience is great. I worked with a variety of test equipment, receivers, transmitters, communication gear, etc.
.mil, of course these are the ones you never hear about until they're released to civilian use.
:-)
When I was in, the most technologically advanced jobs were CTM (Crypto Tech Maintenance), ET (Electronics Tech), DS (Data Systems), among others (more specialized).
One individual I met while in was a Senior Chief ET at Treasure Island. As far as I know, he was one of the people to first develop laser listening devices for civilian purchase, or at least one of the first that I've heard of. I didn't see a working model, but he explained what it was and how it worked to me.
At yet another installation, I met a group of Navy Petty Officers and Air Force Sgt's that were developing a means to render video to CD, at the time, it wasn't common place (I hadn't even heard of the technology at the time) to find video on CD's.
There's many "cutting edge" tech gadgets being used in the
It's like the old story about the guy that invented the first "radar gun" for highway patrolmen, he also invented the first "radar detector" for civilians.
I've always wondered about people like Darl McBride. Obviously, they are paid a great deal of money to put a certain spin on things, and they try very hard to do it. What I've never understood about the psychology of it is this: do they actually believe themselves? Do they start out knowing they are lying, then convince themselves about it along the way? Or does the notion of truth not even cross their minds, as they are busy trying to define the reality they want?
Typical Linux Geek thinking ease-of-use = dumbing down and that a good interface means pretty icons.
Ease of use means making the computer work the way PEOPLE think, not forcing people to work the way COMPUTERS think.
Linux geeks and other developers, who have been conditioned to think like the computer because of the work they do, have the mistaken notion that advanced computer user means a user who has learned to force the natural human way of doing things into the artificial machine way a computer does things.
Any interface that doesn't force this paradigm is "dumbed down."
The truth is, the Linux geek has simply been conditioned to do things the difficult way, not the natural way. Designing the interface to do things the natural way is not dumbing it down, it's making the Linux Geek's paradigm obsolete. Of course, the Linux Geek doesn't like this, so in a fit of human ego, he looks his nose down on anything that points out the stupidity of his position (working the way the computer demands; being the tool of the computer), and calls it "dumbing down."
Especially for legal content... bit torrent has made it so that you can get all sorts of legal content like game demos, linux distros, etc. off p2p without having to be on horribly slow ftp servers.
Part of the problem is that Kasparov is this generation's GM. Kasparov plays very emotional games. He's not just looking to beat you in his first match; he's looking to utterly destroy, smash and humiliate you with a dramatic and embarrassing win.
This is a great strategy against people, but it's not so effective against computers. Kasparov is probably the worst chess master to pit against a machine since Ruy Lopez (I think he's won with the Ruy Lopez opening a few times, case in point: it's a brutal and humiliating play for the losing opponent).
Kasparov knows that the computer can "think through" future moves better than he can. Computers, in fact, do the opposite of human chess players: we set goals and try to find ways to get there while computers search through various ways to find a satisfactory goal they can achieve. So, Kasparov plays it very conservative and keeps himself out of any situations that give the computer too much range of foresight, which is why the Kasparov/computer matches tend to look like Verdun (though he's been surprised a few times).
Personally I'd like to see some of the younger generation take on the big programs. They tend to play more technically and less passionately than Kasparov and his generation.
I read several of the reviews, and all stuck with 32 bit code for the comparition between the Intel P4 and the AMD Athalon 64. Linux runs on the Atahlon in 64 bit mode, wouldn't be hard to compile PovRay and Doom on a 64 bit compiler and see if anything changes. Thats just for an easy test.
Many real world (science?) applications benifit from 64 bit processors, find some (presumably running on UltraSparc, PPC, Alpha, or such) and port them over to see how the 64bit abilities of this chip compares to the other existing chips.
I run open source OSes, and open Source applications. I don't care about 32 bit performance because I'm fairly sure that if I did have an Athalon 64 I wouldn't run 32 bit code very often. I can choose between many chips, compatable instruction sets to me means gcc (or other compiler) has an output for them. 32 bit x86 compatiabily is nice for the few times I have to run something 32 bit (normally in Wine) and that doesn't happen very often.
I run several domains and use multiple blacklists. The blacklists are incredibly effective, especially those which are country-wide like taiwan.blackholes.us and china.blackholes.us. I, and the other users of my domain, don't communicate with people in China or Taiwan. If I disable the blacklists, the ONLY thing that comes to us from those countries is spam. It has a tremendous impact on the amount that I get. Because of those punitive "broadlists", many ISPs like AT&T and PSI who used to write "pink contracts" and host spammers no longer will. The broadlisting makes harboring spammers unsafe. AT&T is not going to piss off their entire subscriber base just to get one big pink contract from some spam house. It's not worth it to them. Many ISPs, especially dial-up ISPs have blocked outgoing port 25 so spammers can't use them for throwaway accounts from with to spam. No ISP wants to risk some spammer paying $9.99 for a month of service which will get the ISP blacklisted.
See what really frustrates the hell out of me is that I want artists to succeed. I don't want them to be slaves to the RIAA, and I don't want them getting screwed over by pirates. The problem is that in the RIAA's efforts to protect their profits (they don't give a hoot about artists), they are making it much harder for me to listen to music the way most people want to.
Linux Conference 2003
The NX Project
What is NX?
- NX is a remote desktop system based on X-Window
- Adds features to X-Window usually found in proprietary systems like MS RDP and Citrix ICA
- Makes possible to run contemporary Unix applications over the Internet
- Compresses the X protocol by an average factor of 50:1 and more
- Allows users to work comfortably on 28.8Kbps or even 9.6 Kbps modem connections
- Reduces X protocol round-trips nearly to zero
- Implements image streaming algorythms to reduce the perceived latency
- Is able to translate RDP and RFB foreign remote desktop protocols to X
- Runs these foreign remote desktop sessions faster than their native protocols
- It integrates with SMB to provide access to the client's file systems
- It integrates with ARTSD and ESD to allow media playback
- Adds server management tools to handle X, RDP and RFB sessions run by users
- Architecture is designed to distribute the server workload between multiple nodes
- It leverages SSH remote execution capabilities to avoid the need to run a new network server
- It is able to encrypt and protect the network traffic by tunneling the connections through SSH
- Server is intended to run on any Unix OS
- Client runs on Linux, Windows, Solaris, Mac OS/X, Sony Playstation/2, MS Xbox and embedded devices like HP/Compaq iPAQ and Sharp Zaurus
- NX core components and X compression libraries are released under the GPL license
- NX client GUI (nxclient) and the NX server manager (nxserver) are commercial software
- The NX client-server protocol is open
- A library handling the client-server protocol and a compatible command-line NX client have been released under the GPL license
- NoMachine has publicly offered its help to let OSS developers build a free implementation of both the nxclient GUI and the nxserver NX System Architecture X NX "protocol" (internet, modem) Local X display Local NX proxy system Remote NX proxy system Remote X application Windows Terminal Server, XP Prof. (Tight) VNCServer nxagent (based on Xnest) nxdesktop (based on rdesktop) nxviewer (based on vncviewer) RDP X RFB
What features are missing?
- X session persistence and reconnection - Better support of RENDER extension - Better support of X applications in seamless mode
- Better support of SMB file-sharing and printing
- Seamless access to client's peripherals and devices
- A new multimedia architecture with native streaming of media formats
- Better integration with Unix and Windows desktop environments to allow point-and-click remote execution of applications
- Better server management tools, including a Web administration interface
- An open API to let customers and developers to write server extensions What NX would like to become?
- A convenient way to let users of mobile phones and other thin devices to get access to complex, rich applications
- A server infrastructure by which people can easily run applications regardless they reside on the local machine or a remote server
- A peer-to-peer computing environment where users can easily access computing resources, like storage and printers, on any server available on the Internet
- A step in the direction of the "network desktop" envisioned by many
Homer:
[reading screen] "To Start Press Any Key". Where's the ANY key? I see Esk ["ESC"], Catarl ["CTRL"], and Pig-Up ["PGUP"]. There doesn't seem to be any ANY key. Woo! All this computer hacking is making me thirsty. I think I'll order a TAB. [presses TAB key] Awp...no time for that now, the computer's starting.
Blatanly stolen from Simpsons episode 3f05.
I would like to see a highly publicized case of holding some home broadband user responsible for the fact that their machine was hijacked to send spam or participate in some DDoS.
I've talked to too many people who've said, "I don't need to bother securing my home system because I've got nothing anyone would want." I've answered, "They want to use your machine to attack me." But the message doesn't sink in.
While these end users are being provided with crap systems, there is a market out there. If their choice of bad systems gets them severly spanked, they will start making demands of their providers.
All it would take would be a couple of high profile cases.
This thought occurred to me:
SCO goes after Linux as a marketing/gain money tool.
They get hated.
Opposing SCO becomes popular.
SCO has just handed people a new marketing tool - oppose/stand up to SCO, get attention, customers, etc.
Though in reflection, their egregeous approach to an unsubstantiated claim was bound to provoke a backlash. And it was bound to be something that people would take advantage of.
Did SCO even see this? My guess, no. They're up their in their own little world.