I worked at Sears in high school. Someone came in to get an oil change and tune up on an AMC, told where in the lot it was parked. When the mechanics put the car back in the parking lot, there were police investigating a car theft, and a different man wanting to know why the mechanic was driving his car. Two spots away was the car they were supposed to work on, same model and color.
Ignition locks provode little protection without a steering lock. On my Fords and Chryslers built before ignition locks, you could start them by connecting a wire from the battery to the ignition coil and shorting two terminals on the starter solenoid. GM's with automatic transmissions were a little harder, because the solenoid was attached to the starter under the car instead of near the battery. On Dad's VW van you could easily unplug the ignition switch and plug your own in--This would start it, but wouldn't unlock the steering.
Oversimplification--it's not the sensor type, it's the size of the sensor. The sensors in most digital SLR's are physically larger--the chart I'm looking at says that most digital SLR's have a sensor around 28-30mm diagonal, compared to 4-10mm for most standard digital cameras and 43mm for standard 35mm and full-frame SLR digitals. Bigger sensor effectively means less depth of field, although there are other factors involved.
The big difference is really the sensors used in the two types. The sensors used in SLR's have a lot of optical advantages over standard digitals--More control of depth of field, less noise, etc. However, they have one disadvantage--they cannot show a current constantly updating picture on the LCD screen, so they require some of the mechanics of a film camera in order to work, and SLR is the most practical type to start with.
I'd settle for a decent SU, instead of the frequent situation where a user account is locked down to the point that it can't change it's own settings. Apparently in our environment, the easiest solution is logging the user off off, logging on as admin, upgrading that user's rights, logging off, logging on as the user, making the changes, downgrading the user's rights, logging him off, then logging on again to test that the changes themselves work with his standard rights.
Or just giving up, and giving most of the users local admin to begin with.
While it's possible for a skilled individual to hunt down many of the places malware hides itself, it's a lot easier to leverage the efforts of others. I'm convinced it's a much more effective use of my time to let Adaware and/or SS&D do most of the work so I can spend my time on problems that can't be automated. This is especially true when I'm not going to see the computer in question until it's hosed enough for the user to notice. My better users are able to run anti-spyware programs themselves, but there's no way I want even them mucking around in the registry.
"voter-verifiable". Paper in a format that the voter can read, saying who he voted for. He reads (hopefully) and if it's wrong, he calls a pollworker. If it's right, he puts it in a ballot box. If there is a question on the machine's accuracy, there's now a way to check.
That's a huge problem--Even if the average accident/death rate of computer-controlled cars is considerably less than that of human-controlled, each individual crash will result in deep-pocket lawsuits.
The XMMS version I use (whatever came with Mandrake 10, I'm not there so I can't check) does Winamp skins and I think visualization plugs, but not audio plugs.
Toss who off the network when? I'd agree if the insecurity only affected the customer that didn't secure their box, but by the time the ISP sees the problem that box has adversly affected the rest of us. I'm advocating the ISP version of OS best practices: Defaults are sensible and safe, unneeded and potentially harmful services and networking are turned off until the user decides otherwise. If someone isn't smart enough to flip a switch to the direct connection position, they aren't smart enough to handle their own security where it affects others.
Broadband ISP's should include a router in whatever they use to convert to ethernet. This router should be set up with reasonable security by default, and have physical switches to lock out "advanced mode" settings that can lead to bypassing the built-in security.
The eventual goal might be to switch to an all-Linux environment, but in the meantime Linux users need access to all the things they use now. Microsoft would love it if the only practical way to switch to a Linux desktop was to throw out all your existing backend software and start over.
I do most of my own auto work because I've had a hard time finding someone capable of competently fixing common problems on my low-performance sedan. I can usually do better with a few hours and a Hayne's or Chilton's manual.
There are plenty of tuner shops around, but I bet Sturgeon's law is even worse than with general mechanics.
Even if you are going to pay someone else, you need enough clue to know what to ask for.
However, it never excuses a specific instance of rule-breaking.
The problem with selective enforcement is that there is no pressure to legally overturn a bad regulation unless it is generally enforced. There are also cases of mutually-exclusive regulations from different agencies that businesses are expected to follow.
The airwaves ought to server everyone. The commerical stuff can be done over satelitte or on other mediums.
Commercial stuff does serve the needs and wants of some, but that's a whole different issue.
Selective enforcement of vague rules gives regulators too much power. The rules need to be clear enough that professionals in the field know where the limit is, and the limit should be the same for everyone. If the defacto rules change (as they did post-JanetBreast) there needs to be clear notification, and the new standards should not be enforced retroactively.
If it's true that Stern is suddenly being fined for 3 year old bits, that's wrong. If they were indecent 3 years ago, he should have been fined then, otherwise the FCC should concentrate on his current actions. On the other hand, if they wait before complaining, they've got 3 years worth of material to levy fines on before Stern can adapt.
And I don't see how most current music is of any more public value than Stern or Janet's breast
General Motors says software and electronics already are responsible for more than one-third of the cost of a typical automobile, and an IBM executive predicted this week that the figure will be closer to 90 percent in five years.
And I thought a license for Windows on a PC was expensive...
I think they were talking about more than a 2-5% improvement in throughput, but I couldn't find any specifics in the article to see if the increase is actually worthwhile. A transition to a TCP replacement should be a lot easier than an IP replacement, if they can run side-by-side and the gain is big enough.
It took (too much) time for webmail providers to limit how much mail could be sent from their web interface, but that was mostly taken care of years ago. Any increase you saw was likely someone using a webmail drop-box for mail sent from somewhere else.
With scoring systems, the critical mass isn't very big--If adopting DK will give legit AOL messages a few bonus points towards being "not spam" and the cost is just admin time, AOL (or any other big, often-forged provider) is likely to strongly consider DK.
Spam is rarely sent from an actual webmail account, but it's fairly common to forge a webmail address. If I knew that all mail that makes it through with a hotmail.com address is from hotmail.com, I'm less likely to treat it as spam, and I can quit requiring hotmail addresses to be whitelisted.
The other thing is, why would you need Yelp! to ask your friends to recommend a restaurant or tailor or whatever. If they are your friends, why not just ask them to their face?
Without knowing the implementation details, I can see potential benefits: Results can be cached and aggrigated within your group, and you can get friend-of-friend recomendations, potentially with an estimate of the liklihood that their ratings will agree with yours.
The chance of them getting the size card I want is fairly small, and if they get it wrong, I'm either paying too much or I'm going to have to buy another card.
Slashdot Mirror
I worked at Sears in high school. Someone came in to get an oil change and tune up on an AMC, told where in the lot it was parked. When the mechanics put the car back in the parking lot, there were police investigating a car theft, and a different man wanting to know why the mechanic was driving his car. Two spots away was the car they were supposed to work on, same model and color.
Ignition locks provode little protection without a steering lock. On my Fords and Chryslers built before ignition locks, you could start them by connecting a wire from the battery to the ignition coil and shorting two terminals on the starter solenoid. GM's with automatic transmissions were a little harder, because the solenoid was attached to the starter under the car instead of near the battery. On Dad's VW van you could easily unplug the ignition switch and plug your own in--This would start it, but wouldn't unlock the steering.
Geo, was GM rebrand of cars made by Toyota I beleive
Geo was GM rebrand of lots of different makes--Toyota, Suzuki and Isuzu that I know of, maybe more.
It's pretty good, but it still hasn't figured out that Rolex=spam.
Oversimplification--it's not the sensor type, it's the size of the sensor. The sensors in most digital SLR's are physically larger--the chart I'm looking at says that most digital SLR's have a sensor around 28-30mm diagonal, compared to 4-10mm for most standard digital cameras and 43mm for standard 35mm and full-frame SLR digitals. Bigger sensor effectively means less depth of field, although there are other factors involved.
The big difference is really the sensors used in the two types. The sensors used in SLR's have a lot of optical advantages over standard digitals--More control of depth of field, less noise, etc. However, they have one disadvantage--they cannot show a current constantly updating picture on the LCD screen, so they require some of the mechanics of a film camera in order to work, and SLR is the most practical type to start with.
I'd settle for a decent SU, instead of the frequent situation where a user account is locked down to the point that it can't change it's own settings. Apparently in our environment, the easiest solution is logging the user off off, logging on as admin, upgrading that user's rights, logging off, logging on as the user, making the changes, downgrading the user's rights, logging him off, then logging on again to test that the changes themselves work with his standard rights.
Or just giving up, and giving most of the users local admin to begin with.
While it's possible for a skilled individual to hunt down many of the places malware hides itself, it's a lot easier to leverage the efforts of others. I'm convinced it's a much more effective use of my time to let Adaware and/or SS&D do most of the work so I can spend my time on problems that can't be automated. This is especially true when I'm not going to see the computer in question until it's hosed enough for the user to notice. My better users are able to run anti-spyware programs themselves, but there's no way I want even them mucking around in the registry.
"voter-verifiable". Paper in a format that the voter can read, saying who he voted for. He reads (hopefully) and if it's wrong, he calls a pollworker. If it's right, he puts it in a ballot box. If there is a question on the machine's accuracy, there's now a way to check.
That's a huge problem--Even if the average accident/death rate of computer-controlled cars is considerably less than that of human-controlled, each individual crash will result in deep-pocket lawsuits.
The XMMS version I use (whatever came with Mandrake 10, I'm not there so I can't check) does Winamp skins and I think visualization plugs, but not audio plugs.
Toss who off the network when? I'd agree if the insecurity only affected the customer that didn't secure their box, but by the time the ISP sees the problem that box has adversly affected the rest of us.
I'm advocating the ISP version of OS best practices: Defaults are sensible and safe, unneeded and potentially harmful services and networking are turned off until the user decides otherwise. If someone isn't smart enough to flip a switch to the direct connection position, they aren't smart enough to handle their own security where it affects others.
Broadband ISP's should include a router in whatever they use to convert to ethernet. This router should be set up with reasonable security by default, and have physical switches to lock out "advanced mode" settings that can lead to bypassing the built-in security.
The eventual goal might be to switch to an all-Linux environment, but in the meantime Linux users need access to all the things they use now. Microsoft would love it if the only practical way to switch to a Linux desktop was to throw out all your existing backend software and start over.
I do most of my own auto work because I've had a hard time finding someone capable of competently fixing common problems on my low-performance sedan. I can usually do better with a few hours and a Hayne's or Chilton's manual.
There are plenty of tuner shops around, but I bet Sturgeon's law is even worse than with general mechanics.
Even if you are going to pay someone else, you need enough clue to know what to ask for.
However, it never excuses a specific instance of rule-breaking.
The problem with selective enforcement is that there is no pressure to legally overturn a bad regulation unless it is generally enforced. There are also cases of mutually-exclusive regulations from different agencies that businesses are expected to follow.
The airwaves ought to server everyone. The commerical stuff can be done over satelitte or on other mediums.
Commercial stuff does serve the needs and wants of some, but that's a whole different issue.
Selective enforcement of vague rules gives regulators too much power. The rules need to be clear enough that professionals in the field know where the limit is, and the limit should be the same for everyone. If the defacto rules change (as they did post-JanetBreast) there needs to be clear notification, and the new standards should not be enforced retroactively.
If it's true that Stern is suddenly being fined for 3 year old bits, that's wrong. If they were indecent 3 years ago, he should have been fined then, otherwise the FCC should concentrate on his current actions. On the other hand, if they wait before complaining, they've got 3 years worth of material to levy fines on before Stern can adapt.
And I don't see how most current music is of any more public value than Stern or Janet's breast
General Motors says software and electronics already are responsible for more than one-third of the cost of a typical automobile, and an IBM executive predicted this week that the figure will be closer to 90 percent in five years.
And I thought a license for Windows on a PC was expensive...
That will USUALLY override everything, but it's still software, so it isn't completely reliable.
I think they were talking about more than a 2-5% improvement in throughput, but I couldn't find any specifics in the article to see if the increase is actually worthwhile. A transition to a TCP replacement should be a lot easier than an IP replacement, if they can run side-by-side and the gain is big enough.
The key word here is Useable. Xerox wasn't available to normal people, and the Wikipidia link shows that Amiga and GEOS were released after the Mac.
It took (too much) time for webmail providers to limit how much mail could be sent from their web interface, but that was mostly taken care of years ago. Any increase you saw was likely someone using a webmail drop-box for mail sent from somewhere else.
With scoring systems, the critical mass isn't very big--If adopting DK will give legit AOL messages a few bonus points towards being "not spam" and the cost is just admin time, AOL (or any other big, often-forged provider) is likely to strongly consider DK.
Spam is rarely sent from an actual webmail account, but it's fairly common to forge a webmail address. If I knew that all mail that makes it through with a hotmail.com address is from hotmail.com, I'm less likely to treat it as spam, and I can quit requiring hotmail addresses to be whitelisted.
The other thing is, why would you need Yelp! to ask your friends to recommend a restaurant or tailor or whatever. If they are your friends, why not just ask them to their face?
Without knowing the implementation details, I can see potential benefits: Results can be cached and aggrigated within your group, and you can get friend-of-friend recomendations, potentially with an estimate of the liklihood that their ratings will agree with yours.
The chance of them getting the size card I want is fairly small, and if they get it wrong, I'm either paying too much or I'm going to have to buy another card.