The night vision problem is caused by the way the surgery is performed, and it depends on which type of surgery is carried out. The problem that is caused is a "starburst" effect around the point where the front of the eye is opened and re-sealed, or around the points where modifications have been made to the eye.
Usually these effects wear off after a couple of weeks, and some people never experience them at all, but for a minority of patients, they are left with a permanent "starburst" effect, which is worst in any high-contrast light-on-dark situation, such as driving at night.
The problem is serious enough that some governments have banned any person who has had laser eye surgery from driving at all - which is annoying for those who had their vision corrected to bring it into the range acceptable for driving in the first place!
Why replace your real eye to do this if it is perfectly healthy? Take a look at EyeTap. This research, mainly by Professor Steve Mann at the University of Toronto has the potential to do everything you describe, and much more besides!
A broadcast television camera (which is really pretty low-resolution, unless it's a true HTDV camera) has three CCD sensors mounted to a prisim block that splits the image into the three component colors for television (RGB). The use of three CCDs for television is necessitated by the fact that the desired result is a color image without waiting to assemble a color composite from three black and whites. Broadcast television results in images that are pretty close to 640x480 (again, prety low res).
Close, but not quite...
A Broadcast Quality camera is usually capable of recording a substantially higher resolution of image than is eventually broadcast. This allows for much better editing facilities later on - ie. Cropping and resizing of the recorded images without loss of detail in the later broadcast. Final Broadcast (in the UK at least) is around 760x575 pixels (actual broadcast lines are 625, but several are taken by the Vertical Blanking Pulse, the Frame Field Markers and Teletext data) - but the camera definately records a much higher resolution than that.
For comparison, a standard Hi-8 Domestic Hand Camera records around 540 picture lines (about 720x540), and the picture quality from this kind of camera is much lower than that needed by the broadcast editing suites to work effectively - just watch any "home video" programme (such as "You've been Framed!") for proof!
Also, expensive professional broadcast cameras use "Dichromatic Mirrors", not prisms to do colour seperation. Prismatic seperation would lead to too much signal loss and colour bleed accross the image. The first mirror directs the Red image to the appropriate sensor, and also allows enough light of all wavelengths to pass to the next mirror, where the Green image is diverted to the appropriate sensor, and again, light of all wavelengths passes to the final sensor in the camera. Blue is never explicitly seperated from the incoming image, but is instead inferred from the intensity data from the three individual sensors.
I can be very certain of both of these facts because my dad was a Video Electronics Engineer for the BBC for a number of years...
If I recall correctly, the Shuttle has 5 GPC's (General Purpose Computers), three of which are "online" at any one time.
The online GPC's each carry out the same set of calculations (potentially each uses code designed to do the same thing, but written by different programmers), and they compare each others results. If any single GPC is considered to be too far wrong, the offline GPC's submit their answers. The three GPC's that are in closest agreement then become the new online GPC's, and the remaining two go offline. The GPC's can reboot themselves if they are too far out of whack, if they fail in one of the "results elections", and of course when they are told to do so by the crew.
Also, whenever a GPC is sent offline by one of the others, a specific caution indicator (and potentially the master caution indicator and klaxon) is activated, and the relevant error codes are shown on one of the forward CRT's. The error codes, along with other information such as the currently running program and the current mission phase, determine the crew's actions. Actions can be as simple as disabling the master caution klaxon for the current alert, all the way to hand-checking certain results and manual GPC restarts.
This is all from memory (from about 5 years back), so some of this may have changed recently, particularly on Atlantis with the "glass cockpit" upgrade that happened 18 months or so ago, but the general gist should be about right (and I'm sure I'll soon know if it isn't!!)
I see similar problems here with a Western Digital 250GB Dual USB2.0/Firewire drive under Slackware 9.1 with the stock 2.4.23 kernel.
The strangest thing I see is that the drive seems to disconnect from the USB bus, and then reconnects around 2 seconds later. I have still to work out if this is caused by a hardware problem with the drive, with the motherboard (an Abit AT7-MAX), or with the kernel.
I also see timeouts, failed sector reads/writes, and other errors from the SCSI Subsystem. These only seem to happen after the drive does it's first USB Disconnect/Reconnect, and then only if the drive was mounted at the time... The drive can go for hours with no problem, or it can drop out after 30 minutes or so. It doesn't seem to make any difference whether there is data heading to/from the drive or not!
When I get time, I'll be upgradeing the kernel to 2.4.24/25 to see if any of the USB / USB-Storage updates fix the problems. I would love to move to 2.6 to see if any of the changes there are of use, but I can't afford to put the 8-Disk 640GB RAID-0 array on the motherboard out of commission!
If that doesn't fix it, I guess it will come down to hardware... A quick post to LKML probably wouldn't hurt though...
I have set this up on both SuSE and Mandrake systems from source for a couple of friends who wanted to try Linux, but who didn't want to drop AOL... It can be a bit tricky to get working, but it does work (in the UK at least).
Hmm, Well it's not entirely true to say that water doesn't boil in a Microwave oven - nor is it true to say that the container does not get hot.
Think about it - Fill a (microwave save) plastic pint jug with cold water, and put the jug in your microwave for 5 minutes on full power. Now, is the water hot or cold? Is the jug hot or cold?
Of course, the answer to both questions is "hot". The energy from the Microwaves heated the water, and the heat from the water conducted from the surface of the water to the surface of the container, heating the container.
This heating of the container allows normal boiling to take place (as evidenced by the fact that the microwave will have been full of steam after heating a pint of water on full power for 5 minutes, and that during the heating time, the water can be clearly seen to bubble in the container!).
While it is definately true to say that water does not boil in the same way in a Microwave oven as it does when boiled in a pan on the hob, it is definately not true to say that water does not boil at all in a Microwave.
In fact, plain water is the best way of cleaning a Microwave Oven - a fact I have on good authority from my Dad, who services Microwave Ovens used in the catering industry. Simply place a pint of water in the Microwave on full power for 5 to 10 minutes, then carefully remove the jug from the oven, and wipe down the inside of the oven with a cloth.
Not only does this method make it very easy to clean the cooking part of the oven, it also helps to clean the inner workings of the oven, in particular the fans and air ducting from the main cooking area.
My first, and still my Favorite
on
Slackware Turns 10
·
· Score: 2, Flamebait
Slackware Linux was my first introduction to Linux way back in 1995, when I installed it on my Toshiba 486DX/25 Laptop, though it had reached Kernel 1.2.something by then!
I still prefer slackware to this day, particularly where I need to tweak and change things quickly and easily - it doesn't have any of the "newbie-helper" kruft which the big-brand distro's have, which tends to hinder more than it helps after a while. It is a small, fast, reliable distribution well suited to both Desktop and Server work.
Heck, I still run an old Slack-3 installation on a 486SX/25 with 12MB of RAM, a 250MB HDD, a 120MB HDD and a couple of ISA NIC's as a router, Firewall, Mailserver, Webserver, DNS server and some other odds-and-ends - though it has had a few upgrades (kernel, glibc, etc) over the years, it's still the same basic setup!
Way to go guys...:)
Keep up the fantastic work...
Re:Still not good enough for enterprise...
on
Opengroupware
·
· Score: 2, Interesting
I've been (forced into) using Domino/Notes for about 5 years now, mainly because at the time we migrated, the guy in charge saw Notes as the "easy" way to move away from cc:Mail.
I've been itching for something like this to come along for a long time, so I can show the Directors what they are missing. OGo, coupled with OTRS to replace our in-house fault-tracking system, and OOo to replace MS Office, and we'd be almost set. All that is left is somce decent Open Source CRM software to replace ACT! for Notes, and I could probably drop Notes on it's head! Heck, with all that, I could probably drop Windows on it's head for half the company!
Unfortunately, I may have to go with Exchange proper anyway - the management are planning a Microsoft Project server for centralised project scheduling of many projects and resources, so unless I can get Project server running an non-IIS platform, talking to OGo, or I can find a replacement for Project Server that talks to OGo, I'll be stuck
Bah! Management - what do they know anyway! Can't wait to try OGo out...
...logical history underlying the acronames "cd" and "ls" and how they are actually newmonic.... It's like Mensa--you have to have a certain amount of brains to get in the door, which makes for a more pleasant experience among the intelligentcia.
This goes to show a long-held belief of mine that the more someone knows the language of IT (for example someone knowledgable in a Unix environment, and most programmers) the less they can understand the basics of the English language (or any other spoken language).
this is why server chipsets often have two PCI busses.
Since PCI supports a maximum of 5 devices per bus (IIRC - I think I read that in the Anandtech article, though could have been elsewhere) I think you will find that almost ALL current motherboards have 2 PCI Busses. Usually you have 4 slots and one OnBoard device on one bus, and the rest of the OnBoard hardware sharing with any remaining slots on the board.
Server Motherboards are likely to have three, (or maybe more) PCI Busses - 2 32-bit/33 MHz, and one 64-bit/33 MHz.
Wait until one of your boxes gets r00ted, and you (or some other poor soul dealing with one of your mangled boxes) need to do some fairly in-depth forensic analysis on the box to work out exactly what was happening, to what file, in what order.
The Access Time attribute can yield some useful clues to what was going on during an attack when you are doing a forensic analysis. Sure, there are plenty of other things to look at before you get that deep into things, but it's still useful to have sometimes!
Well, just doing some basic math, not accounting for friction etc, and assuming a constant upwards accelleration of 3G for the 81 seconds before the impact, you can see that:
a = 3g = 3 x 9.81 = 29.43 meters per second per second
v = at = 29.43 x 81 = 2,383.83 meters per second
= 8,581,788 meters per hour
= 5,332 miles per hour (approx)
So, the orbiter would have been travelling at around 5,300 miles per hour at time of impact (probably faster, since fuel and air drag would have been rapidly reducing, and therefore accelleration would have been gradually increasing).
When the foam seperated from the ET during the launch phase, at that speed, downward drag due to air resistance, and the relatively light mass of the foam section would have been significant - certainly enough to give it a relative velocity in the 500 - 1000 mile per hour range!
(Of course, it's been 8 years or so since I did Physics, so my assumpsions in those calcs may be way off, but I think you get the general idea!!!)
OK, so Trend issued a ruleset which blocks all mail containing the letter 'P' - one and a half hours later, they fixed the problem, which is pretty good going IMHO.
I've been using Trend's Desktop solution (OfficeScan) at work for just over a year now, with no problems at all. Trend have a very good reputation for updating their rulesets very very quickly when a new virus hits the wild - for example in the case of "Love Bug" a couple of years back, they had a new pattern file available in less than 45 minutes, where other vendors took 24 to 36 hours.
Since OfficeScan (and AFAIK, all the Trend Products) can be configured to automatically update their Pattern, Engine and Core files whenever a new version becomes available, that effectively means that all desktop PC's and Servers can be running with suitable pattern files before you even see any incidence of a new virus.
People need to get some perspective on this issue - Yes, there was a problem, but it's fixed. Trend's product base is very stable, very fast and very effective. One small problem like this is just that: small!
Disclaimer: No, I don't work for Trend - I'm just a very happy end user
From the post, they are talking about around 10 Watts, Assuming that they are pushing that at 12V (Sorry, not read the spec - it's not worth the $80-odd the IEEE wants for it!!), that comes out at a little over 830mA.
I can't remember the Power / Voltage / Current ratings of 10/100/1000 Ethernet off the top of my head, but I'd say that a short accross Power to one of the Ethernet conductors should just cause data to 'stop' in the direction of the short (Rx / Tx).
I say this because I have frequently (accidentally) connected Ethernet cards to the POTS/PSTN Switch over the sturctured cabling at work, whilst the port I am connecting to is Ringing - which is usually pushing more power than is being talked about here - and the Ethernet cards still live on...
On the flip side, a Short between +Ve and 0V on the power could generate quite a bit of heat in the cable, until a breaker / fuse was tripped, which could be a fire hazard, but as long as the power 'output' device has a 1A 'fast-blow' type fuse in place, the cable will certainly live without causing major damage - the fuse would blow before the cable even started to get warm!
There is the potential for damage yes, but at the power levels being discussed, it's a very small potential...
But even there, you are forgetting to factor in Multiple Pipelineing (At best, the P4 can 'complete' 9 Instructions per Cycle, though it doesn't usually get that good), and shorter Instruction Execution times, for example, a 32-bit Relative CALL on a 386 takes a minimum of 7 Cycles, whereas on a Pentium Class system it takes only One Cycle...
So, it's a lot more complex than just comparing clock-for-clock, or even clock and bus-width... 10,000 times is probably a very low estimate of how much power has increased in 20 years, just for x86 alone - and that doesn't factor in other architectures such as SPARC or PPC!
Have a look at This Introduction to Very Long Baseline Interferometry at the Jodrell Bank Obervatory website - that will tell you (almost) everything you ever wanted to know about VLBI, and then some!!
Try Kopete (Project Homepage), it's a KDE/Qt based IM Client, which does Jabber, ICQ, AIM, MSN, IRC and a couple of less well-known's. It uses a plug-in based architechture, so adding new protocols is as easy as writing a plugin. (!)
I've been using it for a couple of weeks for ICQ, AIM, Jabber and IRC, and it's quite good, the interface is nice (needs a little polishing, but hey, it's still pre-1.0!). It's definately worth a look - and definately better than GAIM!!
And an IIS vulnerability has nothing to do with the NT Kernel, only that it's run on it. So if an IIS or SQL worm can be called a 'windows' bug, then an Apache or mySql one can be called a 'linux' bug, it's only fair.
Except for the fact that IIS can only run on windows, where Apache, MySQL, and many other OSS products can run on Linux, Windows, MacOS, *BSD, Solaris etc etc etc... So while it may be fair to say that an IIS bug is a 'windows' bug, I still don't see how it's fair to call a non-linux-kernel bug a 'linux' bug?
Slashdot Mirror
The night vision problem is caused by the way the surgery is performed, and it depends on which type of surgery is carried out. The problem that is caused is a "starburst" effect around the point where the front of the eye is opened and re-sealed, or around the points where modifications have been made to the eye.
Usually these effects wear off after a couple of weeks, and some people never experience them at all, but for a minority of patients, they are left with a permanent "starburst" effect, which is worst in any high-contrast light-on-dark situation, such as driving at night.
The problem is serious enough that some governments have banned any person who has had laser eye surgery from driving at all - which is annoying for those who had their vision corrected to bring it into the range acceptable for driving in the first place!
Why replace your real eye to do this if it is perfectly healthy? Take a look at EyeTap. This research, mainly by Professor Steve Mann at the University of Toronto has the potential to do everything you describe, and much more besides!
Current fusion techniques primarily revolve around deuterium, a forms of water which exist in nature.
Deuterium is not a form of water, but rather a stable isotope of hydrogen. When combined with Oxygen, Deuterium forms "heavy" water.
In Deuterium-Tritium Fusion reactions, the by-products are simply He-4 and a neutron, see here.
You are quite right - Thinko/Typo on my part!
A broadcast television camera (which is really pretty low-resolution, unless it's a true HTDV camera) has three CCD sensors mounted to a prisim block that splits the image into the three component colors for television (RGB). The use of three CCDs for television is necessitated by the fact that the desired result is a color image without waiting to assemble a color composite from three black and whites. Broadcast television results in images that are pretty close to 640x480 (again, prety low res).
Close, but not quite...
A Broadcast Quality camera is usually capable of recording a substantially higher resolution of image than is eventually broadcast. This allows for much better editing facilities later on - ie. Cropping and resizing of the recorded images without loss of detail in the later broadcast. Final Broadcast (in the UK at least) is around 760x575 pixels (actual broadcast lines are 625, but several are taken by the Vertical Blanking Pulse, the Frame Field Markers and Teletext data) - but the camera definately records a much higher resolution than that.
For comparison, a standard Hi-8 Domestic Hand Camera records around 540 picture lines (about 720x540), and the picture quality from this kind of camera is much lower than that needed by the broadcast editing suites to work effectively - just watch any "home video" programme (such as "You've been Framed!") for proof!
Also, expensive professional broadcast cameras use "Dichromatic Mirrors", not prisms to do colour seperation. Prismatic seperation would lead to too much signal loss and colour bleed accross the image. The first mirror directs the Red image to the appropriate sensor, and also allows enough light of all wavelengths to pass to the next mirror, where the Green image is diverted to the appropriate sensor, and again, light of all wavelengths passes to the final sensor in the camera. Blue is never explicitly seperated from the incoming image, but is instead inferred from the intensity data from the three individual sensors.
I can be very certain of both of these facts because my dad was a Video Electronics Engineer for the BBC for a number of years...
If I recall correctly, the Shuttle has 5 GPC's (General Purpose Computers), three of which are "online" at any one time.
The online GPC's each carry out the same set of calculations (potentially each uses code designed to do the same thing, but written by different programmers), and they compare each others results. If any single GPC is considered to be too far wrong, the offline GPC's submit their answers. The three GPC's that are in closest agreement then become the new online GPC's, and the remaining two go offline. The GPC's can reboot themselves if they are too far out of whack, if they fail in one of the "results elections", and of course when they are told to do so by the crew.
Also, whenever a GPC is sent offline by one of the others, a specific caution indicator (and potentially the master caution indicator and klaxon) is activated, and the relevant error codes are shown on one of the forward CRT's. The error codes, along with other information such as the currently running program and the current mission phase, determine the crew's actions. Actions can be as simple as disabling the master caution klaxon for the current alert, all the way to hand-checking certain results and manual GPC restarts.
This is all from memory (from about 5 years back), so some of this may have changed recently, particularly on Atlantis with the "glass cockpit" upgrade that happened 18 months or so ago, but the general gist should be about right (and I'm sure I'll soon know if it isn't!!)
I see similar problems here with a Western Digital 250GB Dual USB2.0/Firewire drive under Slackware 9.1 with the stock 2.4.23 kernel.
The strangest thing I see is that the drive seems to disconnect from the USB bus, and then reconnects around 2 seconds later. I have still to work out if this is caused by a hardware problem with the drive, with the motherboard (an Abit AT7-MAX), or with the kernel.
I also see timeouts, failed sector reads/writes, and other errors from the SCSI Subsystem. These only seem to happen after the drive does it's first USB Disconnect/Reconnect, and then only if the drive was mounted at the time... The drive can go for hours with no problem, or it can drop out after 30 minutes or so. It doesn't seem to make any difference whether there is data heading to/from the drive or not!
When I get time, I'll be upgradeing the kernel to 2.4.24/25 to see if any of the USB / USB-Storage updates fix the problems. I would love to move to 2.6 to see if any of the changes there are of use, but I can't afford to put the 8-Disk 640GB RAID-0 array on the motherboard out of commission!
If that doesn't fix it, I guess it will come down to hardware... A quick post to LKML probably wouldn't hurt though...
What will self-destruct? The disc? The player? The viewer? All three?
;)
Well, there's no profit in self-destructing the viewer, so that's not likely...
Yes, there is an AOL Client for Linux - though it's not an 'official' client.
Look at This Tutorial to see how to install the PengAOL Linux Dialer.
I have set this up on both SuSE and Mandrake systems from source for a couple of friends who wanted to try Linux, but who didn't want to drop AOL... It can be a bit tricky to get working, but it does work (in the UK at least).
Hmm, Well it's not entirely true to say that water doesn't boil in a Microwave oven - nor is it true to say that the container does not get hot.
Think about it - Fill a (microwave save) plastic pint jug with cold water, and put the jug in your microwave for 5 minutes on full power. Now, is the water hot or cold? Is the jug hot or cold?
Of course, the answer to both questions is "hot". The energy from the Microwaves heated the water, and the heat from the water conducted from the surface of the water to the surface of the container, heating the container.
This heating of the container allows normal boiling to take place (as evidenced by the fact that the microwave will have been full of steam after heating a pint of water on full power for 5 minutes, and that during the heating time, the water can be clearly seen to bubble in the container!).
While it is definately true to say that water does not boil in the same way in a Microwave oven as it does when boiled in a pan on the hob, it is definately not true to say that water does not boil at all in a Microwave.
In fact, plain water is the best way of cleaning a Microwave Oven - a fact I have on good authority from my Dad, who services Microwave Ovens used in the catering industry. Simply place a pint of water in the Microwave on full power for 5 to 10 minutes, then carefully remove the jug from the oven, and wipe down the inside of the oven with a cloth.
Not only does this method make it very easy to clean the cooking part of the oven, it also helps to clean the inner workings of the oven, in particular the fans and air ducting from the main cooking area.
Slackware Linux was my first introduction to Linux way back in 1995, when I installed it on my Toshiba 486DX/25 Laptop, though it had reached Kernel 1.2.something by then!
:)
I still prefer slackware to this day, particularly where I need to tweak and change things quickly and easily - it doesn't have any of the "newbie-helper" kruft which the big-brand distro's have, which tends to hinder more than it helps after a while. It is a small, fast, reliable distribution well suited to both Desktop and Server work.
Heck, I still run an old Slack-3 installation on a 486SX/25 with 12MB of RAM, a 250MB HDD, a 120MB HDD and a couple of ISA NIC's as a router, Firewall, Mailserver, Webserver, DNS server and some other odds-and-ends - though it has had a few upgrades (kernel, glibc, etc) over the years, it's still the same basic setup!
Way to go guys...
Keep up the fantastic work...
I've been (forced into) using Domino/Notes for about 5 years now, mainly because at the time we migrated, the guy in charge saw Notes as the "easy" way to move away from cc:Mail.
I've been itching for something like this to come along for a long time, so I can show the Directors what they are missing. OGo, coupled with OTRS to replace our in-house fault-tracking system, and OOo to replace MS Office, and we'd be almost set. All that is left is somce decent Open Source CRM software to replace ACT! for Notes, and I could probably drop Notes on it's head! Heck, with all that, I could probably drop Windows on it's head for half the company!
Unfortunately, I may have to go with Exchange proper anyway - the management are planning a Microsoft Project server for centralised project scheduling of many projects and resources, so unless I can get Project server running an non-IIS platform, talking to OGo, or I can find a replacement for Project Server that talks to OGo, I'll be stuck
Bah! Management - what do they know anyway! Can't wait to try OGo out...
...logical history underlying the acronames "cd" and "ls" and how they are actually newmonic. ... It's like Mensa--you have to have a certain amount of brains to get in the door, which makes for a more pleasant experience among the intelligentcia.
Perhaps you mean acronym, mnemonic and intelligentsia.
This goes to show a long-held belief of mine that the more someone knows the language of IT (for example someone knowledgable in a Unix environment, and most programmers) the less they can understand the basics of the English language (or any other spoken language).
this is why server chipsets often have two PCI busses.
Since PCI supports a maximum of 5 devices per bus (IIRC - I think I read that in the Anandtech article, though could have been elsewhere) I think you will find that almost ALL current motherboards have 2 PCI Busses. Usually you have 4 slots and one OnBoard device on one bus, and the rest of the OnBoard hardware sharing with any remaining slots on the board.
Server Motherboards are likely to have three, (or maybe more) PCI Busses - 2 32-bit/33 MHz, and one 64-bit/33 MHz.
Wait until one of your boxes gets r00ted, and you (or some other poor soul dealing with one of your mangled boxes) need to do some fairly in-depth forensic analysis on the box to work out exactly what was happening, to what file, in what order.
The Access Time attribute can yield some useful clues to what was going on during an attack when you are doing a forensic analysis. Sure, there are plenty of other things to look at before you get that deep into things, but it's still useful to have sometimes!
Well, just doing some basic math, not accounting for friction etc, and assuming a constant upwards accelleration of 3G for the 81 seconds before the impact, you can see that:
a = 3g = 3 x 9.81 = 29.43 meters per second per second
v = at = 29.43 x 81 = 2,383.83 meters per second
= 8,581,788 meters per hour
= 5,332 miles per hour (approx)
So, the orbiter would have been travelling at around 5,300 miles per hour at time of impact (probably faster, since fuel and air drag would have been rapidly reducing, and therefore accelleration would have been gradually increasing).
When the foam seperated from the ET during the launch phase, at that speed, downward drag due to air resistance, and the relatively light mass of the foam section would have been significant - certainly enough to give it a relative velocity in the 500 - 1000 mile per hour range!
(Of course, it's been 8 years or so since I did Physics, so my assumpsions in those calcs may be way off, but I think you get the general idea!!!)
OK, so Trend issued a ruleset which blocks all mail containing the letter 'P' - one and a half hours later, they fixed the problem, which is pretty good going IMHO.
I've been using Trend's Desktop solution (OfficeScan) at work for just over a year now, with no problems at all. Trend have a very good reputation for updating their rulesets very very quickly when a new virus hits the wild - for example in the case of "Love Bug" a couple of years back, they had a new pattern file available in less than 45 minutes, where other vendors took 24 to 36 hours.
Since OfficeScan (and AFAIK, all the Trend Products) can be configured to automatically update their Pattern, Engine and Core files whenever a new version becomes available, that effectively means that all desktop PC's and Servers can be running with suitable pattern files before you even see any incidence of a new virus.
People need to get some perspective on this issue - Yes, there was a problem, but it's fixed. Trend's product base is very stable, very fast and very effective. One small problem like this is just that: small !
Disclaimer: No, I don't work for Trend - I'm just a very happy end user
From the post, they are talking about around 10 Watts, Assuming that they are pushing that at 12V (Sorry, not read the spec - it's not worth the $80-odd the IEEE wants for it!!), that comes out at a little over 830mA.
I can't remember the Power / Voltage / Current ratings of 10/100/1000 Ethernet off the top of my head, but I'd say that a short accross Power to one of the Ethernet conductors should just cause data to 'stop' in the direction of the short (Rx / Tx).
I say this because I have frequently (accidentally) connected Ethernet cards to the POTS/PSTN Switch over the sturctured cabling at work, whilst the port I am connecting to is Ringing - which is usually pushing more power than is being talked about here - and the Ethernet cards still live on...
On the flip side, a Short between +Ve and 0V on the power could generate quite a bit of heat in the cable, until a breaker / fuse was tripped, which could be a fire hazard, but as long as the power 'output' device has a 1A 'fast-blow' type fuse in place, the cable will certainly live without causing major damage - the fuse would blow before the cable even started to get warm!
There is the potential for damage yes, but at the power levels being discussed, it's a very small potential...
But even there, you are forgetting to factor in Multiple Pipelineing (At best, the P4 can 'complete' 9 Instructions per Cycle, though it doesn't usually get that good), and shorter Instruction Execution times, for example, a 32-bit Relative CALL on a 386 takes a minimum of 7 Cycles, whereas on a Pentium Class system it takes only One Cycle...
So, it's a lot more complex than just comparing clock-for-clock, or even clock and bus-width... 10,000 times is probably a very low estimate of how much power has increased in 20 years, just for x86 alone - and that doesn't factor in other architectures such as SPARC or PPC!
Have a look at This Introduction to Very Long Baseline Interferometry at the Jodrell Bank Obervatory website - that will tell you (almost) everything you ever wanted to know about VLBI, and then some!!
One Parsec = 3.26 Light Years.
More technically, One parsec is the distance at which one astronomical unit subtends one second of arc.
See: This Site for a definition of the Parsec.
See: This Site for a definition of the Light Year
Better still: Try this for the project homepage
Forgot the darned 'http://'... Grrr...
Try Kopete (Project Homepage), it's a KDE/Qt based IM Client, which does Jabber, ICQ, AIM, MSN, IRC and a couple of less well-known's. It uses a plug-in based architechture, so adding new protocols is as easy as writing a plugin. (!)
I've been using it for a couple of weeks for ICQ, AIM, Jabber and IRC, and it's quite good, the interface is nice (needs a little polishing, but hey, it's still pre-1.0!). It's definately worth a look - and definately better than GAIM!!
And an IIS vulnerability has nothing to do with the NT Kernel, only that it's run on it. So if an IIS or SQL worm can be called a 'windows' bug, then an Apache or mySql one can be called a 'linux' bug, it's only fair.
Except for the fact that IIS can only run on windows, where Apache, MySQL, and many other OSS products can run on Linux, Windows, MacOS, *BSD, Solaris etc etc etc... So while it may be fair to say that an IIS bug is a 'windows' bug, I still don't see how it's fair to call a non-linux-kernel bug a 'linux' bug?
You are of course, quite correct... My Humblest of apologies...
If only I hadn't posted, I would moderate myself down!!!
Somebody shoot me! It's been one of those days!