No one is trying to create an Iron Curtain. Security departments (most of them hopefully) are taking numerous measures to prevent breaches. Including access controls preventing one compromised computer from getting all the marbles via role-based or well-configured discretionary access controls, appropriate traffic filtering and intrusion detection techs.
Risk management is the specific practice of minimizing the greatest risks (what will do the most harm and will be the most likely to happen). And for the most part everyone realizes that no risk can be completely eliminated, so we mitigate them as best we can and rely on fundamentally sound access controls et. al. to limit the effect of any breach and hopefully know about and plan for unforeseen circumstances by planning for certain categories of attacks.
Hopefully I'm right, because if I'm not... I'm scared.
Unless the blurb is incorrect i read that there were 2 extra states that were discovered. Once we get more than 2 states per "unit" we stop counting in binary, ones and zeros are purely a representation of "on" and "off" (and typically cited in theory since it's the smallest positive integer exponentiation).
If they can represent 4 different states in the same physical component then each bit becomes a 0, 1, 2, or 3. So we will count up as 0, 1, 2, 3, 10=4, 11=5, 12=6, 13=7, 20=8, 21=9, 23=10, 23=11, 30=12, 31=13, 32=14, 33:15, 100, 101, 102, 103, 110, 111, 112, 113, 120, 121, 122, 123, etc.. as we see 2 bits can
Similar to how we represent roughly a 5v current as high, and a.5v current as low, if one could reliable generate and observe signals of.5, 2, 3.5, and 5, then we would be able to compute in base 4.
If it requires the technology more space (or time) to switch between the space then the gains will be diminished or even counterproductive but from a purely discrete theory perspective with no performance analysis and extra state changes the alphabet, and the resulting language gets more done with shorter strings (finite length members of the source alphabet).
I agree, so we are in base 4. So there is double the exponential growth rate, so using this type of memory we can store not twice the amount of data, but rather the square of the amount of data.
So while it's not an exponential growth, it's not linear either (twice the amount). Linear would look like 2*2^n. What we have is 4^n, or (2*2)^n, which is the same as (2^(n*2)), which is the same as (n^2)^2.
So it's actually a polynomial increase in overall storage, not just a linear doubling. This squaring is the effect of 4 / 2 (base 4 to base 2). In order to square the amount of data again, we would need 8 new states (base 8 from base 4), which is a byproduct of this being only a polynomial increase of exponential space.
The problem is that computer classes are typically teaching some specific skill (VB programming, MS Office, CAD, etc..) and teachers are trained in that skill. The teachers rarely have inclination to fully master the art of computing because: (1) it's not going to net them any more money (arguable) and (2) they have a family to tend to and don't have the time to study up on best practices.
The truth remains, s/he should have been a little more patient; but another truth remains that kids need to be a little more submissive. There is no reason a student should feel that they are not under the authority of a teacher and mouthing off, talking back, or disregarding instructions is punishable by... *gasp* detention.
You also get detention for being late to class even if it was because you were firing a particularly stubborn rocket in the b-room.
It was entertaining. But out of curiosity, how do you think the information gets onto ROM?;)
First line from wikipedia (the ultimate source of misinformation): Because data stored in ROM cannot be modified (at least not very quickly or easily), it is mainly used to distribute firmware (software that is very closely tied to specific hardware, and unlikely to require frequent updates).
I guess the "bricked" puritans can hold out for this hardware or "too hard to overwrite the ROM software" definition.
Just remember that many of the items that are "bricked" are not suffering from firmware failure, but rather software errors resulting from firmware conflicts that don't allow them to perform a subset of their functionality (i.e. iPhones can be used for all functionality except calls).
My cousin fixed his "bricked" X-Box 360 (ring of death) by cracking it open, soldering a couple wires he noticed were fried, and modding it to include better heat-sinks. Pretty simple for an engineer or hardware buff, but I wouldn't know how to do it. Bricking is a relative term. If the average user machine has to go to a specialist (even for us non-MAC users), it's bricked.
If the machine tells you how to fix it on boot, and/or you can retain your data without additional hardware (as second MAC), it may not be bricked.
Bricking: (common definition) rendering something useless due to a hardware or firmware failure.
Bricking: (software spin) rendering something useless due to software failure.
What is the difference here? If I'm not knowledgeable enough to affect change in my system (either hardware or software fiddling) I'm still taking my bricked item up to the store and dealing with some d-bag (forgot they were called geniuses) with a nasally voice telling me either it's under warranty or I have to pony up $100.
The MAC itself isn't giving me any options, it's just sitting on my desk like an over-sized 5-letter word.
Slashdot Mirror
No one is trying to create an Iron Curtain. Security departments (most of them hopefully) are taking numerous measures to prevent breaches. Including access controls preventing one compromised computer from getting all the marbles via role-based or well-configured discretionary access controls, appropriate traffic filtering and intrusion detection techs.
Risk management is the specific practice of minimizing the greatest risks (what will do the most harm and will be the most likely to happen). And for the most part everyone realizes that no risk can be completely eliminated, so we mitigate them as best we can and rely on fundamentally sound access controls et. al. to limit the effect of any breach and hopefully know about and plan for unforeseen circumstances by planning for certain categories of attacks.
Hopefully I'm right, because if I'm not... I'm scared.
Unless the blurb is incorrect i read that there were 2 extra states that were discovered. Once we get more than 2 states per "unit" we stop counting in binary, ones and zeros are purely a representation of "on" and "off" (and typically cited in theory since it's the smallest positive integer exponentiation).
.5v current as low, if one could reliable generate and observe signals of .5, 2, 3.5, and 5, then we would be able to compute in base 4.
If they can represent 4 different states in the same physical component then each bit becomes a 0, 1, 2, or 3. So we will count up as 0, 1, 2, 3, 10=4, 11=5, 12=6, 13=7, 20=8, 21=9, 23=10, 23=11, 30=12, 31=13, 32=14, 33:15, 100, 101, 102, 103, 110, 111, 112, 113, 120, 121, 122, 123, etc.. as we see 2 bits can
Similar to how we represent roughly a 5v current as high, and a
If it requires the technology more space (or time) to switch between the space then the gains will be diminished or even counterproductive but from a purely discrete theory perspective with no performance analysis and extra state changes the alphabet, and the resulting language gets more done with shorter strings (finite length members of the source alphabet).
I agree, so we are in base 4. So there is double the exponential growth rate, so using this type of memory we can store not twice the amount of data, but rather the square of the amount of data.
So while it's not an exponential growth, it's not linear either (twice the amount). Linear would look like 2*2^n. What we have is 4^n, or (2*2)^n, which is the same as (2^(n*2)), which is the same as (n^2)^2.
So it's actually a polynomial increase in overall storage, not just a linear doubling. This squaring is the effect of 4 / 2 (base 4 to base 2). In order to square the amount of data again, we would need 8 new states (base 8 from base 4), which is a byproduct of this being only a polynomial increase of exponential space.
The problem is that computer classes are typically teaching some specific skill (VB programming, MS Office, CAD, etc..) and teachers are trained in that skill. The teachers rarely have inclination to fully master the art of computing because: (1) it's not going to net them any more money (arguable) and (2) they have a family to tend to and don't have the time to study up on best practices. The truth remains, s/he should have been a little more patient; but another truth remains that kids need to be a little more submissive. There is no reason a student should feel that they are not under the authority of a teacher and mouthing off, talking back, or disregarding instructions is punishable by... *gasp* detention. You also get detention for being late to class even if it was because you were firing a particularly stubborn rocket in the b-room.
I object to this motion on the grounds that it may allow the defense to finally prove that I'm a heinous bitch.
New account; I'm miserable at managing all my log/pass combos.
It was entertaining. But out of curiosity, how do you think the information gets onto ROM? ;)
First line from wikipedia (the ultimate source of misinformation): Because data stored in ROM cannot be modified (at least not very quickly or easily), it is mainly used to distribute firmware (software that is very closely tied to specific hardware, and unlikely to require frequent updates).
I guess the "bricked" puritans can hold out for this hardware or "too hard to overwrite the ROM software" definition.
Just remember that many of the items that are "bricked" are not suffering from firmware failure, but rather software errors resulting from firmware conflicts that don't allow them to perform a subset of their functionality (i.e. iPhones can be used for all functionality except calls).
My cousin fixed his "bricked" X-Box 360 (ring of death) by cracking it open, soldering a couple wires he noticed were fried, and modding it to include better heat-sinks. Pretty simple for an engineer or hardware buff, but I wouldn't know how to do it. Bricking is a relative term. If the average user machine has to go to a specialist (even for us non-MAC users), it's bricked. If the machine tells you how to fix it on boot, and/or you can retain your data without additional hardware (as second MAC), it may not be bricked.
Bricking: (common definition) rendering something useless due to a hardware or firmware failure. Bricking: (software spin) rendering something useless due to software failure. What is the difference here? If I'm not knowledgeable enough to affect change in my system (either hardware or software fiddling) I'm still taking my bricked item up to the store and dealing with some d-bag (forgot they were called geniuses) with a nasally voice telling me either it's under warranty or I have to pony up $100. The MAC itself isn't giving me any options, it's just sitting on my desk like an over-sized 5-letter word.