Some form of cursive provides a more distinct signature that is harder to forge.
And more importantly: you can sign your name a lot more quickly if you don't have to lift your pen for each letter. So think about security and convenience...
Students benefit from knowing:
How to read cursive (people will write them a letter or note by hand, sometimes).. Yes electronic messages are common, that doesn't mean noone ever gets or sends manual messages though
How to jot down some basic notes in class -- students generally need a notepad to take these
How to sign their name, yep/li>
Cursive is indispensable for quick note-taking, and answering questions on tests.
Students generally aren't allowed to have electronic devices during a test, even an essay test.
This is especially true in colleges. Some tests may be administered electronically, but not all are, at least not today.
If students don't have the most rudimentary of cursive skills, they will be at a disadvantage in the current environment.
Because it will take them longer physically to write what they want to say, using print letters.
Learning and practicing Cursive writing has as much to do with the underlying skills of literacy, as proper Abacus operation and extensive practice solving problems with roman numerals has to do with the underlying skills of mathematics.
They will when there's a thirty second timer before they can do anything, they have to check a box that says "I understand", click OK, and type some text to confirm their choice.
It's up to the person deciding the app to provide an adequate description to convince the user to delete it.
If my car has to make such a noise;
I'll load my car up with Norman Martin's "The Song That Never Ends", and that's what the Pedestrians will get to hear.
This is the song that doesn't end,
Yes, it goes on and on, my friend.
Some people started singing it, not knowing what it was,
and they'll continue singing it forever just because...
It's like a giant refrigerator... we could store things that need to stay cold to be preserved, instead of wasting energy to refrigerate them.
Elimiante the ongoing cost of continued refrigeration
Not likely. They already use Captcha technology to protect their signup pages. It's just a matter of replacing their in-house custom built implementation with the reCaptcha one.
Latent disk errors are not one in a million events like winning the lottery. They are very common: the more storage you have, the more likely you will have one. CERN did some studies on Silent data corruption, because it's a real issue in scientific data collection.
They found 10^-14 error rate on Desktop hard drives (10^-15 on Enterprise disk), you expect to have 1 bit error for approximately every 11.3 Terabytes, and this is assuming good hardware, that you've qualified and verified clean, if you had a bad sector somewhere, it's a totally different story. And this is not including other sources of errors, such as RAM errors (the Backblaze chassis doesn't use ECC memory), or errors that can be introduced as a result of vibrations, due to the custom construction, or controller problems.
IF you are storing 63TB of data in RAID5
Simple. I'm saying software RAID5 on cheap disks is not a replacement for using high quality storage. When it comes to important data, all failures are major failures, even if you don't notice the failure.
Using two of these things is not nearly as reliable as using one good storage array, with proper disks and checksumming of data.
Reliability includes expected downtime.
Downtime of your secondary servers can be costly too. All servers have downtime, the question is just.. how much of that is there on average, per year.
Then it does exactly what you say you need. IE the backup raid will compare the stripe each time you calculate the rsync hash, rsync compares CRC as well
From the storage layer's point of view, RSYNC'ing to a destination on a local file system is no different than copying to a new file ordinarily on the array; the destination will most likely be in page cache, when RSYNC reads back bits to verify the content checksum, some of those bits will be read back from cache (not by having each physical disk read back all those bits).
RSYNC does not use raw disk I/O, it is unable to check what is stored on each stripe and actually do any RAID verification.
RSYNC is also unable to examine metadata.
If the ext4/ext2/ext3/JFS/XFS/Reiser/FAT metadata for the file or directory has latent errors, it may not cause issues until well into the future.
Latent errors do not consist of only a failed write. They may also be created by stray rights, stray reads. Just because a sector was good 15 seconds after you wrote to it, does not mean it will still contain good bits in 24 hours.
However, nothing prevents wasteful allocation from spending all those addresses.
A lot of "Critical infrastructure" are getting their own/32. Each root server. 4294967296/64s (65536/48s) allocated for each one. These are IPs that get permanently reserved, and can't be assigned to people on earth.
And root servers are just one example. There are a lot of other cases where/32s are being assigned to non-ISPs (including the registries direct-assigning/32s to themselves for their own use) who will never need that many addresses.
Major ISPs get a/32 or bigger. And are encouraged to give each customer a/48 for each physical location. That is, the smallest amount of space an end user gets is/48.
So the real question is... how does 281474976710656 compare to the world population?
Well, when the world population reaches 1 billion, each can have 200,000/48s; if they're distributed fairly, that is, and not tied up in wasteful/32 reservations to defunct or legacy ISPs as happened with IpV4 space, sometimes.
And 1208925819614629174706176 is a lot of ip addresses indeed... but individuals won't be numbering atoms or grains of sand.
There will likely not ever be an IPv7 release, because the IPv7 protocol one of the proposals a long time ago as the protocol designed to replace IPv4.
That is, unless the IETF continues the work on that protocol and implementations are made in such a way that it supercedes IPv6.
Still... after upgrading to 128-bit addresses, people are unlikely to want to downgrade back to 64-bit IP addresses.
It's funny though:
2.1 Is 64 Bits Enough?
Consider: (thought experiment) 32 bits presently numbers "all" of
the computers in the world, and another 32 bits could be used to
number all of the bytes of on-line storage on each computer. Most
have a lot less than 4 gigabytes on-line, the ones that have more
could be notionally assigned more than one address.)
Of course ultimately they missed the point that IP addresses have structure to them. Address spaces get divided into networks.. Having enough addresses for all hosts doesn't necessarily prevent shortages, if the networks aren't divided along the right lines.
Also, if the networks are divided at too small a level, you get fragmentation, and routing table explosion.
But then all that's why IPng became IPv6.... as far as V7 was concerned, good riddance:)
sort of reminds me of the joke by Mitch Hedberg, the "an escalator can never break, it can only become stairs."
If you don't believe in Byzantine failures, then sure. One way an Escalator can break is it suddenly starts running in the opposite direction, or it accelerates to a wild speed. Only manual intervention can stop it, and by the time you do so, someone might have gotten hurt.
IE if PC redundancy is done right, then yes (for example) it might have 6 smaller drives instead of 2 drives, and 2 controllers instead of 1, it will have some hardware failures more often than the simpler system.
The problem is not when 1 controller goes out perfectly. The problem is when 1 controller is disrupted in a way that breaks the other controllers, or breaks in a way that causes corrupt data to be written.
Single redundancy isn't enough.. You need either at least 3 copies of your data, or 2 copies on different systems, some very good checksums, and a reliable procedure for validating them.
Using Linux software RAID and RSYNC doesn't do that, even with 2 boxes.
When you use a controller with battery backed NVRAM, the in-flight stripe updates are held in memory until the disks report that they are successfully written.
The probability is reduced to 0, except if your controller itself fails, or the cache data is lost due to failure of the battery or NVRAM before your server and drives are powered back up.
A sample assists in making a decision to buy.
People may see advertising for a product, but that doesn't really tell them if they want it or not. A product sample or demo is one of the most important ways that a prospective customer learns about a product in order to make a purchase.
The shirts are sold as souvenirs for Coke fans.
Just like Microsoft has SoftWear, and just about every large company on the planet sells shwag.
The additional cost is about as much about the cost of imprinting the logo as it is about any "license" fees.
Coca-Cola has saturated the market, and their name is already famous, they have no need for you wearing a shirt with their name on it: it doesn't advertise or enhance the image of their brand at all.
This is very different from offering a sample of a product to see if consumers want it.
Heck... most software programs are available as a 30-day demo version, so possible customers can try the software. Even Windows itself is available in this way.
Windows doesn't need the extra advertising, everyone knows it exists.
The sample assists in making a decision to buy.
People see the advertising, but that doesn't really tell them if they want it or not.
Doesn't hurt Apple that much, if people still use their store and iTunes library to keep track of everything, to assure lock-in.
Maybe Apple can be kind and replace the "play 30 sec sample" link with a BitTorrent link, for those that choose not to let apple provide the sample for free.
A 512kbit BIOS difference, and how rigorously it is tested, how mature it is, and your ability to update that BIOS with field upgrades later, can be the difference between having all your data and having none of it.
Out of some 50 servers; i've only once or twice seen a RAM DIMM go bad in 5 years, and never had a RAID card fail. The place is well-cooled. hard drives, fans, power supplies, and batteries need replacement more often than any other component. There are approximately 300 hard drives in the environment, only about 30 of the drives in servers are 7200.11 drives, and yet in the past year 7 of the 7200.11 drives failed and TWO Enterprise class drive failed.
78% of the drive failures were Desktop class drives being used in servers.
If I had some mission critical data, with a server workload, I do believe I wouldn't want to stake it on 7200.11s. Maybe not all desktop drives fail so often, or maybe through some strange coincidence I got a bad batch, but that's pretty unlikely.
You think desktop hardware and server hardware is the same but they are really not.
Rotational speed is not the only difference. That is wishful thinking.
I can count on one hand the number of times i've seen a proper server PSU fail, among some 200 servers, all with dual PSU. If I wanted to count the number of times i've seen a Desktop PSU fail, even UPS-protected desktops, I would need a few dozen more hands.
Slashdot Mirror
You need to sign your name.
Some form of cursive provides a more distinct signature that is harder to forge. And more importantly: you can sign your name a lot more quickly if you don't have to lift your pen for each letter. So think about security and convenience...
Students benefit from knowing:
Cursive is indispensable for quick note-taking, and answering questions on tests.
Students generally aren't allowed to have electronic devices during a test, even an essay test. This is especially true in colleges. Some tests may be administered electronically, but not all are, at least not today.
If students don't have the most rudimentary of cursive skills, they will be at a disadvantage in the current environment.
Because it will take them longer physically to write what they want to say, using print letters.
Learning and practicing Cursive writing has as much to do with the underlying skills of literacy, as proper Abacus operation and extensive practice solving problems with roman numerals has to do with the underlying skills of mathematics.
It's under the CC-BY-SA license.
That means Apple could take up the ad and alter it to be pro-Apple.
Microsoft could use the very content of the ad to develop their own ad deriding Linux as low-grade
I'm hoping it won't happen, but Forkability of marketing materials can be a double-edged sword...
Better yet, tell them a URL they have to go to on a real computer.
They'll go to the URL read a disclaimer, type in their e-mail address, click a button.
Wait 2 hours to receive an e-mail with a confirmation code to re-enable the app.
They will when there's a thirty second timer before they can do anything, they have to check a box that says "I understand", click OK, and type some text to confirm their choice.
It's up to the person deciding the app to provide an adequate description to convince the user to delete it.
If you wear your seatbelt, you don't have to buy auto-insurance, or report a crash you are involved with.
Because if everyone was wearing their seatbelt, it's impossible for anyone to have gotten hurt.
Basically the same logic behind not reporting a data breach, if encryption was used.
*Not even considering how secure the keys are, and whether the intruder might be able to have gotten some usable data.
Businesses that use encryption for communications rarely encrypt everything.
They should use directional speakers. When you are going forward it only gets played in the forward direction.
When your vehicle is in reverse, it only gets played in the backward direction.
If my car has to make such a noise; I'll load my car up with Norman Martin's "The Song That Never Ends", and that's what the Pedestrians will get to hear.
It's like a giant refrigerator... we could store things that need to stay cold to be preserved, instead of wasting energy to refrigerate them. Elimiante the ongoing cost of continued refrigeration
We just gotta get them there. :)
the users will think that any level of control the operators have is far too much.
90% of the users won't care as long as the advertised speed is still 5 Megs, and they can still get to Youtube, Facebook, CNN, and Twitter.
It's caled Perpetual war
Oceania (commonly called the US and Britain) is at war with Terrorism. Oceania has always been at war with Terrorism.
I would think it's probable cause to get a search warrant, and scour the suspect's belongings for stolen property belonging to the victim..
Stolen property at the thief's house or in a storage locker they rented is the evidence to get.
Not likely. They already use Captcha technology to protect their signup pages. It's just a matter of replacing their in-house custom built implementation with the reCaptcha one.
Latent disk errors are not one in a million events like winning the lottery. They are very common: the more storage you have, the more likely you will have one. CERN did some studies on Silent data corruption, because it's a real issue in scientific data collection.
They found 10^-14 error rate on Desktop hard drives (10^-15 on Enterprise disk), you expect to have 1 bit error for approximately every 11.3 Terabytes, and this is assuming good hardware, that you've qualified and verified clean, if you had a bad sector somewhere, it's a totally different story. And this is not including other sources of errors, such as RAM errors (the Backblaze chassis doesn't use ECC memory), or errors that can be introduced as a result of vibrations, due to the custom construction, or controller problems.
IF you are storing 63TB of data in RAID5
Simple. I'm saying software RAID5 on cheap disks is not a replacement for using high quality storage. When it comes to important data, all failures are major failures, even if you don't notice the failure.
Using two of these things is not nearly as reliable as using one good storage array, with proper disks and checksumming of data.
Reliability includes expected downtime. Downtime of your secondary servers can be costly too. All servers have downtime, the question is just.. how much of that is there on average, per year.
Then it does exactly what you say you need. IE the backup raid will compare the stripe each time you calculate the rsync hash, rsync compares CRC as well
From the storage layer's point of view, RSYNC'ing to a destination on a local file system is no different than copying to a new file ordinarily on the array; the destination will most likely be in page cache, when RSYNC reads back bits to verify the content checksum, some of those bits will be read back from cache (not by having each physical disk read back all those bits).
RSYNC does not use raw disk I/O, it is unable to check what is stored on each stripe and actually do any RAID verification.
RSYNC is also unable to examine metadata. If the ext4/ext2/ext3/JFS/XFS/Reiser/FAT metadata for the file or directory has latent errors, it may not cause issues until well into the future.
Latent errors do not consist of only a failed write. They may also be created by stray rights, stray reads. Just because a sector was good 15 seconds after you wrote to it, does not mean it will still contain good bits in 24 hours.
However, nothing prevents wasteful allocation from spending all those addresses.
A lot of "Critical infrastructure" are getting their own /32. Each root server. 4294967296 /64s (65536 /48s) allocated for each one. These are IPs that get permanently reserved, and can't be assigned to people on earth.
And root servers are just one example. There are a lot of other cases where /32s are being assigned to non-ISPs (including the registries direct-assigning /32s to themselves for their own use) who will never need that many addresses.
Major ISPs get a /32 or bigger. And are encouraged to give each customer a /48 for each physical location. That is, the smallest amount of space an end user gets is /48.
So the real question is... how does 281474976710656 compare to the world population?
Well, when the world population reaches 1 billion, each can have 200,000 /48s; if they're distributed fairly, that is, and not tied up in wasteful /32 reservations to defunct or legacy ISPs as happened with IpV4 space, sometimes.
And 1208925819614629174706176 is a lot of ip addresses indeed... but individuals won't be numbering atoms or grains of sand.
There will likely not ever be an IPv7 release, because the IPv7 protocol one of the proposals a long time ago as the protocol designed to replace IPv4.
RFC1475, TP/IX: The Next Internet
The version number has been spent.
That is, unless the IETF continues the work on that protocol and implementations are made in such a way that it supercedes IPv6. Still... after upgrading to 128-bit addresses, people are unlikely to want to downgrade back to 64-bit IP addresses.
It's funny though:
Of course ultimately they missed the point that IP addresses have structure to them. Address spaces get divided into networks.. Having enough addresses for all hosts doesn't necessarily prevent shortages, if the networks aren't divided along the right lines.
Also, if the networks are divided at too small a level, you get fragmentation, and routing table explosion.
But then all that's why IPng became IPv6.... as far as V7 was concerned, good riddance :)
"Smart Grid" is a new fad. You can think of it as the 2009 equivalent to 1995's "Information Superhighway".
At a Hollywood collectibles event, it will probably go for $200k.
If they had listed it on eBay, and slashdotted the listing, they would probably get bids in amounts over $10 million+.
But I guess after eBay fees, they're better off selling it at the Hollywood collectibles event :)
You can't sync your iPhone from Songbird, you still need iTunes.
The lock-in is the iTunes software won't sync to competitors' hardware devices.
sort of reminds me of the joke by Mitch Hedberg, the "an escalator can never break, it can only become stairs."
If you don't believe in Byzantine failures, then sure. One way an Escalator can break is it suddenly starts running in the opposite direction, or it accelerates to a wild speed. Only manual intervention can stop it, and by the time you do so, someone might have gotten hurt.
IE if PC redundancy is done right, then yes (for example) it might have 6 smaller drives instead of 2 drives, and 2 controllers instead of 1, it will have some hardware failures more often than the simpler system.
The problem is not when 1 controller goes out perfectly. The problem is when 1 controller is disrupted in a way that breaks the other controllers, or breaks in a way that causes corrupt data to be written.
Single redundancy isn't enough.. You need either at least 3 copies of your data, or 2 copies on different systems, some very good checksums, and a reliable procedure for validating them.
Using Linux software RAID and RSYNC doesn't do that, even with 2 boxes.
When you use a controller with battery backed NVRAM, the in-flight stripe updates are held in memory until the disks report that they are successfully written.
The probability is reduced to 0, except if your controller itself fails, or the cache data is lost due to failure of the battery or NVRAM before your server and drives are powered back up.
A sample assists in making a decision to buy. People may see advertising for a product, but that doesn't really tell them if they want it or not. A product sample or demo is one of the most important ways that a prospective customer learns about a product in order to make a purchase.
The shirts are sold as souvenirs for Coke fans. Just like Microsoft has SoftWear, and just about every large company on the planet sells shwag. The additional cost is about as much about the cost of imprinting the logo as it is about any "license" fees.
Coca-Cola has saturated the market, and their name is already famous, they have no need for you wearing a shirt with their name on it: it doesn't advertise or enhance the image of their brand at all.
This is very different from offering a sample of a product to see if consumers want it.
Heck... most software programs are available as a 30-day demo version, so possible customers can try the software. Even Windows itself is available in this way.
Windows doesn't need the extra advertising, everyone knows it exists.
The sample assists in making a decision to buy. People see the advertising, but that doesn't really tell them if they want it or not.
Doesn't hurt Apple that much, if people still use their store and iTunes library to keep track of everything, to assure lock-in.
Maybe Apple can be kind and replace the "play 30 sec sample" link with a BitTorrent link, for those that choose not to let apple provide the sample for free.
A 512kbit BIOS difference, and how rigorously it is tested, how mature it is, and your ability to update that BIOS with field upgrades later, can be the difference between having all your data and having none of it.
Out of some 50 servers; i've only once or twice seen a RAM DIMM go bad in 5 years, and never had a RAID card fail. The place is well-cooled. hard drives, fans, power supplies, and batteries need replacement more often than any other component. There are approximately 300 hard drives in the environment, only about 30 of the drives in servers are 7200.11 drives, and yet in the past year 7 of the 7200.11 drives failed and TWO Enterprise class drive failed. 78% of the drive failures were Desktop class drives being used in servers.
If I had some mission critical data, with a server workload, I do believe I wouldn't want to stake it on 7200.11s. Maybe not all desktop drives fail so often, or maybe through some strange coincidence I got a bad batch, but that's pretty unlikely.
You think desktop hardware and server hardware is the same but they are really not.
Rotational speed is not the only difference. That is wishful thinking.
I can count on one hand the number of times i've seen a proper server PSU fail, among some 200 servers, all with dual PSU. If I wanted to count the number of times i've seen a Desktop PSU fail, even UPS-protected desktops, I would need a few dozen more hands.
The 'known' word wasn't necessarily OCR readable. And their methods of OCR are probably not quite the same as the attacker's.