Having a gun pointed your head is something that I'm sure that teller is liable to remember far less than pleasantly for a long, long, time to come.
This wouldn't have been a problem if society hadn't become so wussy.
In the US, pretty much every bank employee before about 1900 was carrying a weapon (especially west of the Mississippi), and this is one of the reasons the very few "successful" bank robbers are now mythical figures.
Um, if you fire person "A" for sharing a password, you'd have to have evidence that they shared it. For example, by knowing that person "B" logged in using credentials from person "A".
At that point, you fire person "B" as well, since they also violated the policy. You wouldn't know for sure if person "B" had more passwords, but you probably would be able to figure it out, based on login locations (e.g., person "C" logged into the workstation in the office of person "B" 20 times last month).
Of course two-factor authentication would solve all this.
I'm assuming you're talking about a quad core. What is faster, running 4 encoding threads or 8?
I'm curious how HT affects performance that way...
I have access to both 8 real cores (AMD) or 4 cores with HT (Intel).
For desktop apps, I find that HT scales pretty close to a real core, while on ESX, you really need the real cores to keep the system running quickly.
Since Xvid seems to run two threads when encoding plus some for the overhead of the OS, I can't really devote 8 threads to encoding. But, 3 instances of encoding run in almost exactly the same time as 2 instances, but do 50% more work. In this case, HT works very well.
to take them out even if they were wearing body armor.
These days, unless you are wearing almost video-game body armor, professional weapons (e.g., police or military) will generally be able to go right through the armor and still be lethal.
For example, weapons that fire 5.7x28mm ammunition are becoming more common in professional use precisely beause the projectile can penetrate kevlar while still having more than enough power afterward. In theory, this ammo could even pass completely through body armor and the chest cavity (assuming it didn't strike bone) and go out the other side. This would be unlikely, though, as there tends to be a lot of tumble after impact.
Recoil would tend to ruin the 'fun' of most games. A sniper rifle that gets you near-zero accuracy (floating barrel) when on the run / flying through the air would force those people to camp
Deus Ex has both of these built into the gameplay, and that's one of the many reasons it's still considered one of the best FPS of all time.
Machine guns are almost impossible to control, and pistols recoil fairly realistically. You can acquire improved weapons tech that reduces this. Likewise, until you build skill as a sniper, your sight point moves randomly to simulate muscle tension.
With over 60 characters (including lowercase and caps; various punctuation; selections from the extended ASCII character set; and no words from the dictionary), it looks like total gobbledygook.
Unfortunately, I've been at places where you had to use a password of exactly 8 characters with at least one each of an upper, lower, special, and number.
This was because the minimum password for some systems in the single-sign-on was 8 characters, while others only treated the first 8 as significant, so having more might cause issues.
If it's some news site or otherwise unimportant with no consequences, it'll have a weak password. If it's a password to your bank account, then you'll have something much stronger on it.
And, isn't it always the case that the unimportant site has restrictions that force you to use a much more complex password than you would like, while the bank won't let you use anything but letters and numbers.
Their accounts ARE terminated at the same moment as their employment. But if they know the passwords for several other people's accounts, that doesn't help any.
Sure it does, because those accounts were terminated too, when the employee who was not supposed to share their password did so and then was removed from employment for violating security.
Anyways, if someone gets terminated, and they remember the passwords, they pose a security risk. We had this issue come up last summer where a manager knew a few people's passwords, and after being fired, was using the webmail client to snoop on emails.
Where I work, sharing passwords is a termination offense. I can't tell from your post if that's the case (as you talk a lot about termination, but not whether it was directly related to the password sharing).
It only takes a couple of people who get fired for password sharing to make everyone else so paranoid they never even want a hint at what your password might be, then they learn how to use the tools to allow them to share files by approved methods.
The problem with all gps systems is too many drivers allow the machine to do their thinking for them.
Unfortunately, sometimes it's all you've got.
I was in rural Virginia using DeLorme and it directed me onto one of the service roads the GP mentioned. The problem is that the roads this service road connected were only about 20% wider and about 10% better maintained. It got me there, and I know now there were "real" roads I could have stayed on, but going in with no knowledge of the area there was no way to know that.
I assume that the use of "topped" in the past tense was intentional, as there are now quad-core Intel chips with 12MB L3 cache (like the Xeon E56xx line).
Reportedly (video is not my hobby) many video editing applications already scale well to multiple cores.
Running a single instance converting video to Xvid fully utlilizes 2 cores on my system, and part of a third. If I run 3 simultaneous instances, all eight cores are 100% utilized.
Actually, I never had anyone walk out. Since it was presented as roleplay of a real world situation, and I'd explain the details of the situation calmly and clearly, it was evident that it was an extreme example.
What a competent interviewer would do is set up a VM with the problem they want diagnosed. That way, there wouldn't be any need to set up a fake "situation" where the "real fault" can be any number of things, including ones that don't match what you have established in your head.
Of course, if you can't handle an environment with occasional actual preparation for your job (e.g., interviewing), I wouldn't want you to work with me.
That's the last thing I'd ever want is a stressful situation to come up, and an employee walking out because it was "too hard".
Being "yelled at" by a superior is not a "stressful situation". It's unprofessional behavior. Being told politely and calmly that there is a problem that needs to be fixed quickly because the company is losing $X million per hour is a "stressful situation".
It is a massive failure of the (civil) justice system that these laws are not enforced.
There is no failure of the justice system in this case. The laws say that the rights holder must sue to recover damages. If they don't choose to do this, then that's their problem. Likewise, if they choose to sue with shaky evidence, it's also their problem.
Meanwhile, look at the group that wants money in this case: songwriters and composers. These people already receive money from compulsory licensing, and generally receive nothing when a CD (or track) is sold.
So, this is just a money grab for these people because they aren't losing anything due to file sharing.
In the recording industry, any artist who wants to get their name and music widely known.
Who advises their client to sign such a contract?
Someone who understands the realities of the recording industry.
What are the lawyers getting paid for, anyhow?
To explain that to the artist that they have two choices:
Sign the contract and make their album with no money out of their pocket and possibly a few dollars more in their pocket than they now have.
Max out their credit cards, borrow from their friends and relatives, and generally owe everyone in the world money and then try to avoid being sued and/or lynched by ex-friends and relatives after they make their album with no massive distribution or publicity network and find that they can only sell 12 copies.
The Internet provides alternatives, but an artist would need to have a lot more groundswell to get the funding they would need. With a record contract, all they have to do is convince one A&R guy that they are worth the money, and this can be done with relatively little expense (the classic "hookers & blow").
- You're on Mars, and forgot to bring an atomic clock with you on the first colony ship...
Based on the article, without many "reference" clocks to use in the algorithm, you'd be SOL.
"RADclock" would only work where you have many clocks, most of which are trying to be somewhere close to accurate. As others have stated, if you have a bunch of clocks and all are between 1 and 5 minutes fast from "real" time, then you'd end up with convergence somewhere around 2-1/2 minutes ahead of "real" time. Yes, all the clocks would be the same, but if you needed the correct time for something external, you'd fail.
Also, it's pretty well known that the same type of RTC chip tends to have the same amount of drift, so you'd need to make sure that the "reference" machines have a wide variety of hardware. I really don't see any way for this (or any time sync software) to really work without at least one truly accurate clock as part of the reference group.
The statement is silly because latency isn't directly related to bandwidth. Switches, bridges, repeaters, modems, routers and other such devices all add latency. If FiOS reduces the number of these in the chain, the latency will be reduced.
Verizon is one of the few Tier 1 networks from which end users can buy direct ISP service. FiOS runs on the "business" network, as far as I can tell.
After the my router, and the Verizon router for my subnet, there are at most two hops inside Verizon for any traceroute (including to onlive.com). So, the fact that Verizon is so directly connected to all other networks does reduce latency as much as possible.
Taxes go up because the voters want more spending. Simple as that.
No, taxes go up because regardless of what the person you voted for promised to do, they end up raising taxes. Simple as that.
Once a politician is in office, it's very hard to remove them before the next election. In general, they need to be indicted for a crime. Sure, for a few states there are ways in theory to have a recall election, but the reality is that it's just not possible without major malfeasance that's close to criminal.
Likewise, once a law is on the books, it's hard to get politicians to repeal or amend it.
Slashdot Mirror
Having a gun pointed your head is something that I'm sure that teller is liable to remember far less than pleasantly for a long, long, time to come.
This wouldn't have been a problem if society hadn't become so wussy.
In the US, pretty much every bank employee before about 1900 was carrying a weapon (especially west of the Mississippi), and this is one of the reasons the very few "successful" bank robbers are now mythical figures.
Um, if you fire person "A" for sharing a password, you'd have to have evidence that they shared it. For example, by knowing that person "B" logged in using credentials from person "A".
At that point, you fire person "B" as well, since they also violated the policy. You wouldn't know for sure if person "B" had more passwords, but you probably would be able to figure it out, based on login locations (e.g., person "C" logged into the workstation in the office of person "B" 20 times last month).
Of course two-factor authentication would solve all this.
It also ensures that when the secretary who has a certain file is unexpectedly sick people will not be able to meet a deadline.
Unless the file is encrypted, any competent IT person will be able to copy it to where it is needed and give it the correct permissions.
If only the secretary knows where the file is (or if it's on a USB stick that she took home), then even sharing passwords won't help.
I'm assuming you're talking about a quad core. What is faster, running 4 encoding threads or 8?
I'm curious how HT affects performance that way...
I have access to both 8 real cores (AMD) or 4 cores with HT (Intel).
For desktop apps, I find that HT scales pretty close to a real core, while on ESX, you really need the real cores to keep the system running quickly.
Since Xvid seems to run two threads when encoding plus some for the overhead of the OS, I can't really devote 8 threads to encoding. But, 3 instances of encoding run in almost exactly the same time as 2 instances, but do 50% more work. In this case, HT works very well.
to take them out even if they were wearing body armor.
These days, unless you are wearing almost video-game body armor, professional weapons (e.g., police or military) will generally be able to go right through the armor and still be lethal.
For example, weapons that fire 5.7x28mm ammunition are becoming more common in professional use precisely beause the projectile can penetrate kevlar while still having more than enough power afterward. In theory, this ammo could even pass completely through body armor and the chest cavity (assuming it didn't strike bone) and go out the other side. This would be unlikely, though, as there tends to be a lot of tumble after impact.
Recoil would tend to ruin the 'fun' of most games. A sniper rifle that gets you near-zero accuracy (floating barrel) when on the run / flying through the air would force those people to camp
Deus Ex has both of these built into the gameplay, and that's one of the many reasons it's still considered one of the best FPS of all time.
Machine guns are almost impossible to control, and pistols recoil fairly realistically. You can acquire improved weapons tech that reduces this. Likewise, until you build skill as a sniper, your sight point moves randomly to simulate muscle tension.
The only thing that's at all interesting about this is watching so many people go completely off the rails in their criticism of BP.
It's probably true that this is an over-reaction, since people already have plenty of other reasons to legitimately criticize BP.
Trolling: When you do it right, nobody realizes you've done anything at all.
Hey, why do stars light up in my browser in time with the display of the words in your post?
With over 60 characters (including lowercase and caps; various punctuation; selections from the extended ASCII character set; and no words from the dictionary), it looks like total gobbledygook.
Unfortunately, I've been at places where you had to use a password of exactly 8 characters with at least one each of an upper, lower, special, and number.
This was because the minimum password for some systems in the single-sign-on was 8 characters, while others only treated the first 8 as significant, so having more might cause issues.
If it's some news site or otherwise unimportant with no consequences, it'll have a weak password. If it's a password to your bank account, then you'll have something much stronger on it.
And, isn't it always the case that the unimportant site has restrictions that force you to use a much more complex password than you would like, while the bank won't let you use anything but letters and numbers.
Their accounts ARE terminated at the same moment as their employment. But if they know the passwords for several other people's accounts, that doesn't help any.
Sure it does, because those accounts were terminated too, when the employee who was not supposed to share their password did so and then was removed from employment for violating security.
Anyways, if someone gets terminated, and they remember the passwords, they pose a security risk. We had this issue come up last summer where a manager knew a few people's passwords, and after being fired, was using the webmail client to snoop on emails.
Where I work, sharing passwords is a termination offense. I can't tell from your post if that's the case (as you talk a lot about termination, but not whether it was directly related to the password sharing).
It only takes a couple of people who get fired for password sharing to make everyone else so paranoid they never even want a hint at what your password might be, then they learn how to use the tools to allow them to share files by approved methods.
The problem with all gps systems is too many drivers allow the machine to do their thinking for them.
Unfortunately, sometimes it's all you've got.
I was in rural Virginia using DeLorme and it directed me onto one of the service roads the GP mentioned. The problem is that the roads this service road connected were only about 20% wider and about 10% better maintained. It got me there, and I know now there were "real" roads I could have stayed on, but going in with no knowledge of the area there was no way to know that.
4 Core systems topped out at 8Meg cache.
I assume that the use of "topped" in the past tense was intentional, as there are now quad-core Intel chips with 12MB L3 cache (like the Xeon E56xx line).
Reportedly (video is not my hobby) many video editing applications already scale well to multiple cores.
Running a single instance converting video to Xvid fully utlilizes 2 cores on my system, and part of a third. If I run 3 simultaneous instances, all eight cores are 100% utilized.
I hate to tell you, but if you have an asymmetric line like most Americans, the upload speed will only be a fraction of that.
Well, yeah. By definition, if you have an asymmetric line, the upload speed is lower than the download speed, and will thus be some fraction of it.
In my case, that fraction is 60% (25Mbps down, 15Mbps up).
Actually, I never had anyone walk out. Since it was presented as roleplay of a real world situation, and I'd explain the details of the situation calmly and clearly, it was evident that it was an extreme example.
What a competent interviewer would do is set up a VM with the problem they want diagnosed. That way, there wouldn't be any need to set up a fake "situation" where the "real fault" can be any number of things, including ones that don't match what you have established in your head.
Of course, if you can't handle an environment with occasional actual preparation for your job (e.g., interviewing), I wouldn't want you to work with me.
That's the last thing I'd ever want is a stressful situation to come up, and an employee walking out because it was "too hard".
Being "yelled at" by a superior is not a "stressful situation". It's unprofessional behavior. Being told politely and calmly that there is a problem that needs to be fixed quickly because the company is losing $X million per hour is a "stressful situation".
It is a massive failure of the (civil) justice system that these laws are not enforced.
There is no failure of the justice system in this case. The laws say that the rights holder must sue to recover damages. If they don't choose to do this, then that's their problem. Likewise, if they choose to sue with shaky evidence, it's also their problem.
Meanwhile, look at the group that wants money in this case: songwriters and composers. These people already receive money from compulsory licensing, and generally receive nothing when a CD (or track) is sold.
So, this is just a money grab for these people because they aren't losing anything due to file sharing.
If you don't leave the hat on all the time, "they" can read your thoughts and find out you planned the meeting at the docks.
Seriously, who signs such a contract?
In the recording industry, any artist who wants to get their name and music widely known.
Who advises their client to sign such a contract?
Someone who understands the realities of the recording industry.
What are the lawyers getting paid for, anyhow?
To explain that to the artist that they have two choices:
The Internet provides alternatives, but an artist would need to have a lot more groundswell to get the funding they would need. With a record contract, all they have to do is convince one A&R guy that they are worth the money, and this can be done with relatively little expense (the classic "hookers & blow").
man sed: "For all we know our love will grow", at least according to Paul McCartney.
- You're on Mars, and forgot to bring an atomic clock with you on the first colony ship...
Based on the article, without many "reference" clocks to use in the algorithm, you'd be SOL.
"RADclock" would only work where you have many clocks, most of which are trying to be somewhere close to accurate. As others have stated, if you have a bunch of clocks and all are between 1 and 5 minutes fast from "real" time, then you'd end up with convergence somewhere around 2-1/2 minutes ahead of "real" time. Yes, all the clocks would be the same, but if you needed the correct time for something external, you'd fail.
Also, it's pretty well known that the same type of RTC chip tends to have the same amount of drift, so you'd need to make sure that the "reference" machines have a wide variety of hardware. I really don't see any way for this (or any time sync software) to really work without at least one truly accurate clock as part of the reference group.
The statement is silly because latency isn't directly related to bandwidth. Switches, bridges, repeaters, modems, routers and other such devices all add latency. If FiOS reduces the number of these in the chain, the latency will be reduced.
Verizon is one of the few Tier 1 networks from which end users can buy direct ISP service. FiOS runs on the "business" network, as far as I can tell.
After the my router, and the Verizon router for my subnet, there are at most two hops inside Verizon for any traceroute (including to onlive.com). So, the fact that Verizon is so directly connected to all other networks does reduce latency as much as possible.
I can't seem to find the "+1 Yiddish" mod. I guess that'll be added to the 3.0 discussion system.
Taxes go up because the voters want more spending. Simple as that.
No, taxes go up because regardless of what the person you voted for promised to do, they end up raising taxes. Simple as that.
Once a politician is in office, it's very hard to remove them before the next election. In general, they need to be indicted for a crime. Sure, for a few states there are ways in theory to have a recall election, but the reality is that it's just not possible without major malfeasance that's close to criminal.
Likewise, once a law is on the books, it's hard to get politicians to repeal or amend it.