BU's home grown time sharing VPS (nee RAX) timesharing system had an email program called $mail created by Michael Krugman before 1978 (1975?). I know because I worked at the BU computing center at the time and used $mail. If I recall, it had CC capabilities, etc.
A friend of mine has an unlimited data plan and regularly gets spammed by AT&T that he's [in effect] "a data hog". Trouble is, his biggest usage is to listen to NPR [audio only]. They can't really do anything about it because he's grandfathered in on his plan, but this hasn't stopped them from trying.
VM guests for Linux are what we use, and presumable most shops. z/OS, with UNIX file services does the bulk of the work though. We do have the specialized DB2 and Linux engines as well. You can get a Linux instance up and running in minutes.
For disk drives we have 130 TB in raid 5+1 emulating about 7300 3390 volumes, all mirrored at a backup site. The disk drives are in the same SANs used by the server people.
Although I asked the question about native, I was assuming guest mode. It makes more sense, because VM already has the drivers for the hardware. Porting a native driver to Linux is just extra work, particularly for "big iron" hardware. If Linux is "hypervisor aware" it can issue "diagnose" instructions ("hypervisor syscalls"???) to VM to be much more efficient.
I've even worked on an OS (circa 1978) that made full use of guest mode. The equivalent is to imagine that each Linux user process/group gets its own VM. Each Linux process is not scheduled by Linux, but by the hypervisor. The process is unaware that it's in a separate VM (and can not do guest OS operations). It's equivalent to a multicore machine where each core is a VM
Thus, if you had say 20 CMS users, 24 OS/VS1 instances, and a Linux instance with 10 users, ordinarily, the Linux users would be dividing up 1/25th of the available time (e.g. 1/250th per Linux user). However, with the approach I just described, each Linux user would have parity, so each would get 1/34th of the time, a better result.
BTW, my home desktop is 6TB with 3 disks in a raid 0 and I'm having a hard time filling it. Just curious, what does one do with 130TB?
I hadn't used a mainframe (370/145) since 1977, but I was curious so I did some reading over the holidays. From IBM's doc pages, FTP is an option for the OS load. No wonder about 2400 tape. Circa 1995, I was using DDS/DAT (digital audio tape, which was helical scan). It was half the size of a pack of cigarettes and would hold several GB.
---
The legacy surrounding the IBM ecosystem is astonishing. Beyond raw [virtual] tape records/blocks, you still have things like: The raw block is 800 bytes with a blocking factor of 10 [or equiv]. A fancy way of saying card images (at 80 columns per).
I'm not even sure if hierarchical filesystems are supported. From what little I read, it seemed like things were still "volume" oriented, possibly with an OS partitioned dataset on top. That's what I imagine for the OS/VS1 OS/MVS descendents. For the VM/CMS, you can have your S (system) drive, and your A (personal) drive [and others]. I'm assuming that if VS1 is a guest OS of VM, its volumes are VM virtual drives.
No wonder the current/future emphasis on Linux--it's a clean slate. I don't know whether the preferred mode for Linux on zSeries is VM guest or native install, but the guest approach allows migration without disrupting the straggler VS1-like apps.
"Even if it's on a punched card deck and you don't have card deck reader hardware anymore, IBM does." ehhh..not so much. I know ten years ago they couldn't find a card punch machine for where I worked. (Don't ask lol). Anyways, cards are readable by looking at them.
They may not have a punch card reader, but if you really had to get the data read in, and you had a lot of it, you could optically scan the cards with a flat bed scanner, and with some custom software, you could restore the data. IBM will do that sort of thing (if the price is right). It's all about service.
They probably do still have magtape. I took a look recently, and the zOS system load comes on magtape, or a special "tape file" disk file format. The latter was originally developed for OS2, so OS2 could simulate magtape. The format has little headers embedded within that demarcate tape records, tape marks, end-of-tape, etc.
So, even without a physical tape, they still rely on the concept of magtapes. And virtual card deck readers (in the latest incarnation of VM/CMS).
And JCL is still alive and well... [Hmm... I think that rhymes--I must be a poet]
And backward compatibility and service. Write once, run forever. You can take a binary program compiled in 1975 and it will run unchanged on the latest mainframe.
---
Even if it's on a punched card deck and you don't have card deck reader hardware anymore, IBM does. Its support group will transfer the card deck to whatever media your current hardware can handle.
Also, if a mainframe ever does go down, IBM's service escalation policy is unbelievable (e.g. that's what you pay for). I remember when my datacenter's mainframe went down [circa 1975]. The following numbers aren't exact, but similar.
The local rep must be onsite within a fixed period of time (e.g. 2 hours). He has [say] 4 hours to diagnose/fix the problem. If he is unable to do so, the regional hotshot is called in. If more time goes by, the national service rep and one or more of the system architects must arrive. After 24 hours, an executive vice president must be onsite and stay until the problem is resolved.
When we had our problem, the onsite VP had the entire mainframe replaced, by diverting a system scheduled to go to a new customer and airfreighting it up. Total round trip time [for complete replacement/install]: 72 hours
Also, the mainframes in those days were much bigger iron than the one pictured in the article. You could fit five z9's into the space of a single s/370
Most "old school" programmers have some interpreted language in their toolkit. People who think "old" means 40 probably have Python/Perl/etc. People who are really old probably had Basic/Awk/etc. So, nothing to do with how long you've been programming, more to do with how narrow your background is. As with learning any new language, there's no getting around the basic advice of: Write More Code.
I've been programming for 40 years. I was doing Basic circa 1972-1973, did tcsh/awk circa 1983-1991, discovered perl and used it ever since. I did write some JS code circa 1997. But, the JS was autogenerated by my perl code...
"This action will destroy the cloud storage/computing industry before it gets off the ground."
You say that as though it's a bad thing.
If you give your data to someone else, it's no longer your data and there's no guarantee you'll get it back. Either deal with that, or keep your data locally.
Personally, I've never been a fan of cloud storage for the reasons you mentioned. I do my own backups. Still, others may wish to choose otherwise and avail themselves of cloud storage. The FBI action merely demonstrates [in a stark manner] why cloud storage is a bad idea.
The analogy: An apartment complex with 20 units. 15 house drug dealers and 5 house innocent people. The FBI determines that the entire building is a "drug haven" and must be razed immediately. No time for the innocent people to get their possessions out.
Believe you me, if YouTube hadn't been bought by Google, this would have happened to them. The various Copyright Cartels would still love to do this to them, but can't because Google is too big.
Viacom tried [and failed]. They were even so bold as to demand that Google hand over its search algorithm [a closely held trade secret] to prove infringement [or under the guise of infringment--if they had succeeded, we'd have viacom_new_and_improved_search.com].
It doesn't matter. The business, "Megaupload", is gone, the guys running it have spent time in jail. Even if the FBI drops the charges, Megaupload is screwed.
Actually, Megaupload [I use the term for the business or the "guys"] can claim that by the destruction of the [possibly] exculpatory evidence, they can't get a fair trial. They could easily be acquitted on these grounds.
This action will destroy the cloud storage/computing industry before it gets off the ground. Who will be able to trust their data to any cloud storage provider [used for disaster backup] that can be subject to such seizures/destruction?
---
If you use a provider to archive old data to free up some space, how would you get it back if it's destroyed?
It is also destruction of exculpatory evidence. If Megaupload makes the claim [true or not] that the majority of the content was non-infringing, how will they be able to prove/disprove this? Or, the reverse argument as well.
Imagine if this was done to YouTube. YouTube has at least one infringing clip, but it also has a lot of original content that would be lost.
It matters because the "white space" spectrum guys are poaching the term/trademark "Super WiFi" because they couldn't come up with a word like Bluetooth, LTE, WiMax, etc. How about WiSpace or WiSpectrum?
---
It's as bad as Ethernet calling itself "Super USB" (or vice versa). All of the above have separate standards bodies that set the names/versions (and thus compatibility--or not). The USB people don't have to live in fear that the next version of Ethernet will be called USB 4.0. USB 3.0 operating at its highest speed is called "super speed" mode.
It would appear that the white space spectrum stuff is so much lower speed [and they know it], compared to 802.22 that they are trying to co-opt the name to get some of the glory before 802.22 comes online. However, it's dumb because it's a trademark violation and they can [easily] be shut down from using the term.
I've talked to a number of [only] mildly computer literate people and even they know that:
USB connects mice, keyboards, and backup hard drives to their computer;
Ethernet connects their computer to their home router;
WiFi connects their computer when they're at Starbuck's;
and Bluetooth connects their headset to their cell phone.
AT&T took its profits and gave too much to shareholders and not enough investment in building out their network. They relied on the [outdated] oversubscription model (e.g. assume nobody will actually use their unlimited plan 24x7 [or fraction thereof]) and failed to build out properly to accomodate the load. Now, they're caught behind the eight ball and are trying to backpedal.
---
A friend of mine has a grandfathered unlimited wireless data plan for his iPhone that he uses [primarily] to listen to NPR. This is voice only, and he still gets spam from AT&T telling him that he's in the top Nth percentile of data users [and they're "unhappy" about it] even though, under his plan, he has the right to do this [and has told them so].
I have an 6 Mbps "elite" DSL landline from AT&T with a purported 150GB cap. Originally, it was unlimited. The AT&T FUD was that they wanted to avoid "congestion". Well, since my maximum data usage can be calculated, the copper to the CO is not a shared resource (like a cable connection or wireless), my [maximum] theoretical loading of the backbone can be calculated beforehand. This means that it is easy to factor the cost of my line's loading of the backbone into my monthly bill.
In other words, I expect that the money I pay is divided to pay for: local loop maintenance, my percentage of usage of backbone switches, and other infrastructure in between. If AT&T has [say] 10,000,000 subscribers, their network should be able to handle all 10,000,000 connections simultaneously. But, they can't because they've been siphoning off this money as profits instead of investing.
AT&T failed to plan properly and are now coming up short. As part of the FUD, they also try to label people that try to use the [full] capacity that they've already paid for as "hogs". Or, impose caps or usurious pricing.
Actually, when done professionally, the object isolation is done automatically. It's a variation on motion compensation. As the object moves, frame-to-frame, the object edges are revealed (e.g. an edge that becomes apparent at frame N, this info can be applied for frames N-10... N+10).
As the edges and shading change, this reveals the 3D structure.
Even in a single frame, inference of object depth/texture is possible by application of [inverse] shading models.
That said, it needs a bit of a render farm to pull off in a reasonable amount of time. Also, since there is no clear consensus on the algorithms that work best, a fair number are proprietary to a given design house that is doing this. Because it is a laborous/intense process, it will be used on high value targets (e.g. blockbusters).
Twenty years from now, when the dust settles, 2D to 3D conversion will be a freshman class at a university film school.
In the past 5 minutes there have been no additional signatures.
13,801 to go.
Apparently I'm not the only/. who doesn't trust the government enough to "Create an Account" at this point.
I had the same mistrust [more of the site's security than the govt itself] but created the account and signed anyway. No worries. All that is displayed is <first name>, <Last initial>, <date of signing>, <signature #>.
A day later and there are ~10,000 more signatures.
the cache is there because the speed of DRAM, regardless of how fast you can communicate with it, still has latency issues on addressing.
Combining this with memristor memory would solve this, which is what HP is doing. From their roadmap, they're going to roll out memristor replacement for flash this year. Next round is to replace DRAM. Then SoC combined CPU and memristor. Memristor memory is as fast as cache.
This architecture has promise as a replacement for FPGA/ASIC designs for realtime video encoding.
The tech industry kills off competition with a stock pile of shitty patents and then claims hollywood is stifling innovation with copyrights. I think copyright is getting out of hand but this reeks of hypocrisy to me. All I suspect that would come out of Silicon Valley killing Hollywood is that Silicon Valley just becomes worse than Hollywood.
Many in Silicon Valley loathe the current patent system as it does stifle innovation. The tech industry's efforts to effect reform have fallen on deaf ears (in Congress). The patent portfolios that are amassed are largely for defense against patent trolls and patent abusers (e.g. Apple, which apparently, has a patent on rounding the corners of a smartphone, that they're actively trying to use against Samsung).
WTF??? Giving authors and inventors EXCLUSIVE rights is exactly what copyright does. What are these 'other permutations'?
Permutations such as allowing public domain works to be placed back under copyright (as SCOTUS just ruled on Wednesday), and Congress periodically extending the time limit so high that it is [in effect] perpetual.
Disney got Congress to extend the length of time [to protect Mickey Mouse as a character, that was due to come out of copyright--from the 1920's]. At the time of the Disney coup, even SCOTUS was dismayed, but felt they didn't have the right to intervene.
Granting multiple types of "sub rights" as was done by Congress in 1973 (e.g. [This may not be precise--I'm too tired to look up the case law] That's why a novel has a right, a screenplay from the novel has one, the movie itself has one, etc.)
You're also mixing your metaphors. In general, copyrights protect authors and inventors are protected by patents.
From Article 8: [Congress shall have the power] To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries;
---
Notice the word limited anyone [on the Supreme Court]?
At 34 I've re-entered the job market myself after giving my own business a shot and I landed a job as CTO of a start-up game company. We're developing a couple of games now (one while will be in beta tomorrow) and when I look for programmers, I could care less about a space in employment as long as they can demonstrate the skills needed for the job.
Maybe you could give the original poster an interview?
If you look at all the possible attack vectors and scenarios changing your passwords once a year change your statistical chances of being hacked or losing data very little. The ROI is low enough I wouldn't recommend changing your passwords on a regular schedule.
Picking good (as in hard to crack) passwords is more important. For random web properties using different passwords for each so when one is compromised and caught storing passwords in plain text only one account is compromised is key.
This is an excellent case for a PKI. Users should generate a public-private key pair, and provide the public key to the web site upon sign up. Extra authentication steps could be done at setup (web of trust a la PGP, known entities, a la X.509, callback texts, whatever). Users would sign a login blob with their private key to authenticate.
Using the same key for many web sites is much less dangerous. Compromising the web sites, and all the public keys, gets the attacker approximately nothing. They can be stored in plain (unencrypted) format on the web server. The only attack is to get the users private key, which can be encrypted on their machine behind passwords, biometrics, or whatever. Getting one user's private key gets you only one user, it's a low value attack.
What's needed is a standard format for this encrypted exchange, and then support by clients (from web browsers to ssh clients) and their corresponding server services. This is where the industry is letting us down.
If the big 15-20 web properties could get together with the big 4 browsers and make this happen it would be huge leap forward.
I read an article recently that posited that hard passwords weren't as necessary as non-obvious login names (e.g. If you're John Smith, don't use "jsmith" but js987) if you're on a closed system. For a website, if it permits, use a different nickname (that will show up for everybody like "rodeocowboy"), but the login for this should be completely different (e.g. "zDltH")
I just keep all my website login/pw in a file on my home desktop. I also use Firefox's password manager. The only was to get to this is to physically break into my place. If somebody does that, I've got much bigger problems than losing passwords. I print the list and keep a copy in my wallet.
For my home system, I noticed I was getting a lot of random login/password attempts via ssh. What I did was add the PAM access module [to/etc/pam.d/sshd] and configured this [/etc/security/access] to disallow anything but a console login (e.g./etc/securetty) or the local LAN. But, I also had ssh public/private keys on all my systems (different keys) and each system had the public keys of the others in the authorized_keys file. Because ssh will skip PAM authentication if it gets a PKI match first, this means I can login seamlessly but crackers can try all the random login/pw they want. Even if they hit a valid user/pw combination, they still won't be logged in because the PAM access will disallow it. That is, the only way to get in is to have the remote system with a recognizable private key.
Thus, I can have my laptop at my local Starbuck's, log into my home system directly (no password challenge), but the home system is totally secured. For website passwords, I use non-obvious login names and the "hard" passwords, but my home systems have passwords that please me (and are dictionary words). My desktop has the same password my personal account for the last 20 years.
Just for fun, I wrote an additional PAM module to track the [pathetic] random crack attempts. Turns out that most do a login of [say] "susan" with a password of "susan". Other popular ones are postgres, sales, oracle, test, admin, rootadmin. Or root with equally simplistic passwords (e.g. qwerty123, einstein, master). Or a few bizarre ones like root with a 27 char random password. The bizarre ones appear to be that a login/pw database has b
Slashdot Mirror
BU's home grown time sharing VPS (nee RAX) timesharing system had an email program called $mail created by Michael Krugman before 1978 (1975?). I know because I worked at the BU computing center at the time and used $mail. If I recall, it had CC capabilities, etc.
A friend of mine has an unlimited data plan and regularly gets spammed by AT&T that he's [in effect] "a data hog". Trouble is, his biggest usage is to listen to NPR [audio only]. They can't really do anything about it because he's grandfathered in on his plan, but this hasn't stopped them from trying.
VM guests for Linux are what we use, and presumable most shops. z/OS, with UNIX file services does the bulk of the work though. We do have the specialized DB2 and Linux engines as well. You can get a Linux instance up and running in minutes. For disk drives we have 130 TB in raid 5+1 emulating about 7300 3390 volumes, all mirrored at a backup site. The disk drives are in the same SANs used by the server people.
Although I asked the question about native, I was assuming guest mode. It makes more sense, because VM already has the drivers for the hardware. Porting a native driver to Linux is just extra work, particularly for "big iron" hardware. If Linux is "hypervisor aware" it can issue "diagnose" instructions ("hypervisor syscalls"???) to VM to be much more efficient.
I've even worked on an OS (circa 1978) that made full use of guest mode. The equivalent is to imagine that each Linux user process/group gets its own VM. Each Linux process is not scheduled by Linux, but by the hypervisor. The process is unaware that it's in a separate VM (and can not do guest OS operations). It's equivalent to a multicore machine where each core is a VM
Thus, if you had say 20 CMS users, 24 OS/VS1 instances, and a Linux instance with 10 users, ordinarily, the Linux users would be dividing up 1/25th of the available time (e.g. 1/250th per Linux user). However, with the approach I just described, each Linux user would have parity, so each would get 1/34th of the time, a better result.
BTW, my home desktop is 6TB with 3 disks in a raid 0 and I'm having a hard time filling it. Just curious, what does one do with 130TB?
---
The legacy surrounding the IBM ecosystem is astonishing. Beyond raw [virtual] tape records/blocks, you still have things like: The raw block is 800 bytes with a blocking factor of 10 [or equiv]. A fancy way of saying card images (at 80 columns per).
I'm not even sure if hierarchical filesystems are supported. From what little I read, it seemed like things were still "volume" oriented, possibly with an OS partitioned dataset on top. That's what I imagine for the OS/VS1 OS/MVS descendents. For the VM/CMS, you can have your S (system) drive, and your A (personal) drive [and others]. I'm assuming that if VS1 is a guest OS of VM, its volumes are VM virtual drives.
No wonder the current/future emphasis on Linux--it's a clean slate. I don't know whether the preferred mode for Linux on zSeries is VM guest or native install, but the guest approach allows migration without disrupting the straggler VS1-like apps.
"Even if it's on a punched card deck and you don't have card deck reader hardware anymore, IBM does." ehhh..not so much. I know ten years ago they couldn't find a card punch machine for where I worked. (Don't ask lol). Anyways, cards are readable by looking at them.
They may not have a punch card reader, but if you really had to get the data read in, and you had a lot of it, you could optically scan the cards with a flat bed scanner, and with some custom software, you could restore the data. IBM will do that sort of thing (if the price is right). It's all about service.
They probably do still have magtape. I took a look recently, and the zOS system load comes on magtape, or a special "tape file" disk file format. The latter was originally developed for OS2, so OS2 could simulate magtape. The format has little headers embedded within that demarcate tape records, tape marks, end-of-tape, etc.
So, even without a physical tape, they still rely on the concept of magtapes. And virtual card deck readers (in the latest incarnation of VM/CMS).
And JCL is still alive and well ... [Hmm ... I think that rhymes--I must be a poet]
You could literally step inside an IBM 3090.
The size changes kinda remind me of Christopher Reeve in his first Superman movie when he is looking for a phone booth to change his clothes ...
---
Even if it's on a punched card deck and you don't have card deck reader hardware anymore, IBM does. Its support group will transfer the card deck to whatever media your current hardware can handle.
Also, if a mainframe ever does go down, IBM's service escalation policy is unbelievable (e.g. that's what you pay for). I remember when my datacenter's mainframe went down [circa 1975]. The following numbers aren't exact, but similar.
The local rep must be onsite within a fixed period of time (e.g. 2 hours). He has [say] 4 hours to diagnose/fix the problem. If he is unable to do so, the regional hotshot is called in. If more time goes by, the national service rep and one or more of the system architects must arrive. After 24 hours, an executive vice president must be onsite and stay until the problem is resolved.
When we had our problem, the onsite VP had the entire mainframe replaced, by diverting a system scheduled to go to a new customer and airfreighting it up. Total round trip time [for complete replacement/install]: 72 hours
Also, the mainframes in those days were much bigger iron than the one pictured in the article. You could fit five z9's into the space of a single s/370
Most "old school" programmers have some interpreted language in their toolkit. People who think "old" means 40 probably have Python/Perl/etc. People who are really old probably had Basic/Awk/etc. So, nothing to do with how long you've been programming, more to do with how narrow your background is. As with learning any new language, there's no getting around the basic advice of: Write More Code.
I've been programming for 40 years. I was doing Basic circa 1972-1973, did tcsh/awk circa 1983-1991, discovered perl and used it ever since. I did write some JS code circa 1997. But, the JS was autogenerated by my perl code ...
"This action will destroy the cloud storage/computing industry before it gets off the ground."
You say that as though it's a bad thing.
If you give your data to someone else, it's no longer your data and there's no guarantee you'll get it back. Either deal with that, or keep your data locally.
Personally, I've never been a fan of cloud storage for the reasons you mentioned. I do my own backups. Still, others may wish to choose otherwise and avail themselves of cloud storage. The FBI action merely demonstrates [in a stark manner] why cloud storage is a bad idea.
The analogy: An apartment complex with 20 units. 15 house drug dealers and 5 house innocent people. The FBI determines that the entire building is a "drug haven" and must be razed immediately. No time for the innocent people to get their possessions out.
Believe you me, if YouTube hadn't been bought by Google, this would have happened to them. The various Copyright Cartels would still love to do this to them, but can't because Google is too big.
Viacom tried [and failed]. They were even so bold as to demand that Google hand over its search algorithm [a closely held trade secret] to prove infringement [or under the guise of infringment--if they had succeeded, we'd have viacom_new_and_improved_search.com].
It doesn't matter. The business, "Megaupload", is gone, the guys running it have spent time in jail. Even if the FBI drops the charges, Megaupload is screwed.
Actually, Megaupload [I use the term for the business or the "guys"] can claim that by the destruction of the [possibly] exculpatory evidence, they can't get a fair trial. They could easily be acquitted on these grounds.
---
If you use a provider to archive old data to free up some space, how would you get it back if it's destroyed?
So, bye bye, iCloud et. al. ...
Wouldn't that be destruction of evidence?
Captcha: retrieve
It is also destruction of exculpatory evidence. If Megaupload makes the claim [true or not] that the majority of the content was non-infringing, how will they be able to prove/disprove this? Or, the reverse argument as well.
Imagine if this was done to YouTube. YouTube has at least one infringing clip, but it also has a lot of original content that would be lost.
The us is loosing ground fast
s/us is loosing/US is losing/
---
It's as bad as Ethernet calling itself "Super USB" (or vice versa). All of the above have separate standards bodies that set the names/versions (and thus compatibility--or not). The USB people don't have to live in fear that the next version of Ethernet will be called USB 4.0. USB 3.0 operating at its highest speed is called "super speed" mode.
It would appear that the white space spectrum stuff is so much lower speed [and they know it], compared to 802.22 that they are trying to co-opt the name to get some of the glory before 802.22 comes online. However, it's dumb because it's a trademark violation and they can [easily] be shut down from using the term.
I've talked to a number of [only] mildly computer literate people and even they know that:
USB connects mice, keyboards, and backup hard drives to their computer;
Ethernet connects their computer to their home router;
WiFi connects their computer when they're at Starbuck's;
and Bluetooth connects their headset to their cell phone.
---
A friend of mine has a grandfathered unlimited wireless data plan for his iPhone that he uses [primarily] to listen to NPR. This is voice only, and he still gets spam from AT&T telling him that he's in the top Nth percentile of data users [and they're "unhappy" about it] even though, under his plan, he has the right to do this [and has told them so].
I have an 6 Mbps "elite" DSL landline from AT&T with a purported 150GB cap. Originally, it was unlimited. The AT&T FUD was that they wanted to avoid "congestion". Well, since my maximum data usage can be calculated, the copper to the CO is not a shared resource (like a cable connection or wireless), my [maximum] theoretical loading of the backbone can be calculated beforehand. This means that it is easy to factor the cost of my line's loading of the backbone into my monthly bill.
In other words, I expect that the money I pay is divided to pay for: local loop maintenance, my percentage of usage of backbone switches, and other infrastructure in between. If AT&T has [say] 10,000,000 subscribers, their network should be able to handle all 10,000,000 connections simultaneously. But, they can't because they've been siphoning off this money as profits instead of investing.
AT&T failed to plan properly and are now coming up short. As part of the FUD, they also try to label people that try to use the [full] capacity that they've already paid for as "hogs". Or, impose caps or usurious pricing.
As the edges and shading change, this reveals the 3D structure.
Even in a single frame, inference of object depth/texture is possible by application of [inverse] shading models.
That said, it needs a bit of a render farm to pull off in a reasonable amount of time. Also, since there is no clear consensus on the algorithms that work best, a fair number are proprietary to a given design house that is doing this. Because it is a laborous/intense process, it will be used on high value targets (e.g. blockbusters).
Twenty years from now, when the dust settles, 2D to 3D conversion will be a freshman class at a university film school.
Seriously, what's the difference between lobbying and bribery?
It's like the difference between capitalism and communism. With capitalism, man exploits man. With communism, it's the other way 'round ...
In the past 5 minutes there have been no additional signatures.
13,801 to go.
Apparently I'm not the only /. who doesn't trust the government enough to "Create an Account" at this point.
I had the same mistrust [more of the site's security than the govt itself] but created the account and signed anyway. No worries. All that is displayed is <first name>, <Last initial>, <date of signing>, <signature #>.
A day later and there are ~10,000 more signatures.
the cache is there because the speed of DRAM, regardless of how fast you can communicate with it, still has latency issues on addressing.
Combining this with memristor memory would solve this, which is what HP is doing. From their roadmap, they're going to roll out memristor replacement for flash this year. Next round is to replace DRAM. Then SoC combined CPU and memristor. Memristor memory is as fast as cache.
This architecture has promise as a replacement for FPGA/ASIC designs for realtime video encoding.
The tech industry kills off competition with a stock pile of shitty patents and then claims hollywood is stifling innovation with copyrights. I think copyright is getting out of hand but this reeks of hypocrisy to me. All I suspect that would come out of Silicon Valley killing Hollywood is that Silicon Valley just becomes worse than Hollywood.
Many in Silicon Valley loathe the current patent system as it does stifle innovation. The tech industry's efforts to effect reform have fallen on deaf ears (in Congress). The patent portfolios that are amassed are largely for defense against patent trolls and patent abusers (e.g. Apple, which apparently, has a patent on rounding the corners of a smartphone, that they're actively trying to use against Samsung).
WTF??? Giving authors and inventors EXCLUSIVE rights is exactly what copyright does. What are these 'other permutations'?
Permutations such as allowing public domain works to be placed back under copyright (as SCOTUS just ruled on Wednesday), and Congress periodically extending the time limit so high that it is [in effect] perpetual.
Disney got Congress to extend the length of time [to protect Mickey Mouse as a character, that was due to come out of copyright--from the 1920's]. At the time of the Disney coup, even SCOTUS was dismayed, but felt they didn't have the right to intervene.
Granting multiple types of "sub rights" as was done by Congress in 1973 (e.g. [This may not be precise--I'm too tired to look up the case law] That's why a novel has a right, a screenplay from the novel has one, the movie itself has one, etc.)
You're also mixing your metaphors. In general, copyrights protect authors and inventors are protected by patents.
---
Notice the word limited anyone [on the Supreme Court]?
At 34 I've re-entered the job market myself after giving my own business a shot and I landed a job as CTO of a start-up game company. We're developing a couple of games now (one while will be in beta tomorrow) and when I look for programmers, I could care less about a space in employment as long as they can demonstrate the skills needed for the job.
Maybe you could give the original poster an interview?
If you look at all the possible attack vectors and scenarios changing your passwords once a year change your statistical chances of being hacked or losing data very little. The ROI is low enough I wouldn't recommend changing your passwords on a regular schedule.
Picking good (as in hard to crack) passwords is more important. For random web properties using different passwords for each so when one is compromised and caught storing passwords in plain text only one account is compromised is key.
This is an excellent case for a PKI. Users should generate a public-private key pair, and provide the public key to the web site upon sign up. Extra authentication steps could be done at setup (web of trust a la PGP, known entities, a la X.509, callback texts, whatever). Users would sign a login blob with their private key to authenticate.
Using the same key for many web sites is much less dangerous. Compromising the web sites, and all the public keys, gets the attacker approximately nothing. They can be stored in plain (unencrypted) format on the web server. The only attack is to get the users private key, which can be encrypted on their machine behind passwords, biometrics, or whatever. Getting one user's private key gets you only one user, it's a low value attack.
What's needed is a standard format for this encrypted exchange, and then support by clients (from web browsers to ssh clients) and their corresponding server services. This is where the industry is letting us down.
If the big 15-20 web properties could get together with the big 4 browsers and make this happen it would be huge leap forward.
I read an article recently that posited that hard passwords weren't as necessary as non-obvious login names (e.g. If you're John Smith, don't use "jsmith" but js987) if you're on a closed system. For a website, if it permits, use a different nickname (that will show up for everybody like "rodeocowboy"), but the login for this should be completely different (e.g. "zDltH")
I just keep all my website login/pw in a file on my home desktop. I also use Firefox's password manager. The only was to get to this is to physically break into my place. If somebody does that, I've got much bigger problems than losing passwords. I print the list and keep a copy in my wallet.
For my home system, I noticed I was getting a lot of random login/password attempts via ssh. What I did was add the PAM access module [to /etc/pam.d/sshd] and configured this [/etc/security/access] to disallow anything but a console login (e.g. /etc/securetty) or the local LAN. But, I also had ssh public/private keys on all my systems (different keys) and each system had the public keys of the others in the authorized_keys file. Because ssh will skip PAM authentication if it gets a PKI match first, this means I can login seamlessly but crackers can try all the random login/pw they want. Even if they hit a valid user/pw combination, they still won't be logged in because the PAM access will disallow it. That is, the only way to get in is to have the remote system with a recognizable private key.
Thus, I can have my laptop at my local Starbuck's, log into my home system directly (no password challenge), but the home system is totally secured. For website passwords, I use non-obvious login names and the "hard" passwords, but my home systems have passwords that please me (and are dictionary words). My desktop has the same password my personal account for the last 20 years.
Just for fun, I wrote an additional PAM module to track the [pathetic] random crack attempts. Turns out that most do a login of [say] "susan" with a password of "susan". Other popular ones are postgres, sales, oracle, test, admin, rootadmin. Or root with equally simplistic passwords (e.g. qwerty123, einstein, master). Or a few bizarre ones like root with a 27 char random password. The bizarre ones appear to be that a login/pw database has b