Actually, you're conflating the history of the GM EV1 and the Toyota RAV4 EV. The GM EV1s were indeed rounded up after their leases ended, and most went to the crusher (although a few ended up being sent to university research labs, and one went to the Smithsonian (where it is no longer on display, for reasons unknown)). The Toyota RAV4 EV, on the other hand, was initially only available as a leased vehicle, but in 2002 Toyota sold around 300 RAV4 EVs to purchasers in California, and those vehicles were sold with no strings attached. Many of the leased RAV4 EVs also ended up in private hands after their leases ended.
"users cannot typically be granted any kind of admin access on a machine without granting them access on the network level"
Not so...I have set up Windows machines several times such that domain users (who do not have Administrator privs on the domain) have local Administrator access on their own machine. It's an ideal solution for more technically aware users, who can be trusted to install their own software.
As to someone infecting machines on the inside, well, that's a matter of network design. You have to plan not only for threats from the outside, but also for threats from the inside.
Finally, "ludicrously inefficient IT department[s]" are the norm rather than the exception. Unfortunate fact of life.
Agreed. This can become a serious problem, and frankly it smacks of egocentrism on the part of IT staff. The "user-presumed-guilty" mentality makes it very difficult for anyone to get anything done.
There isn't even a logical basis for it. If you have Ghost (or whatever else) images for your stock configurations, then if a user screws up their machine, you reimage it and you're done. Better yet, set something to work over the network with PXE, so all you have to do is reboot and tell the machine to boot from the network, and poof, it's reimaged.
Actually, as near as I can tell it doesn't "prove" anything. Anyone who learns or knows the URL can pretend to be me on this or any other site. Especially if you're dumb enough to use the subdomain format shown. (e.g. brad.livejournal.com)
Not really. After you enter a URL in an OpenID login box, the OpenID producer will confirm that you've already logged in to the producer site. OpenID is essentially a single sign-on solution. You log in to the producer site once, then you can use your URL to log in to any OpenID consumer site.
Did you even read any of the linked materials? No part of the OpenID system stores your personal details. The only thing OpenID does is allow you to prove that you own a URL. There is no such thing as an 'OpenID profile'--an OpenID producer and consumer just don't exchange that kind of information.
And if you read the specs, I think you will see that OpenID is designed from the ground up with security in mind.
Nothing special, really, just an iPaq via Bluetooth to an SE T68i, then GPRS out to the Internet.
But I have read/. a few times going from Baltimore to New York (or vice-versa) via Amtrak. It is only marginally more difficult to maintain a steady GPRS connection at up to 200 kph than when standing still.
I'm going to go out on a limb here, but, what's so wrong with reverse-engineering games to develop bots?
You call them 'cheaters', I see it as changing the dynamic of the game--it's no longer about how well you play the game, but how well you program your computer to play the game. And what's wrong with that?
So you're playing a multiplayer game and your opponent starts using a bot to get ahead...so why not load up your own bot then?
-Kurt
Re:Auditioning for the Darwin award???
on
Solving a Wiring Mess?
·
· Score: 4, Informative
Couple of notes from an amateur electrician:
"I would suggest buying several different colors to help keep things straight in the next step."
Um, there are color codes for a reason: black (for sure), red (if 220), orange (if 3-phase, then it's the high leg) are all hot white - neutral no insulation or green - ground
"SHUT OFF THE POWER AND INSURE IT WILL NOT BE TURNED BACK ON UNTIL YOU ARE DONE!!!"
And if possible, pull the meter. Seriously. Have the power company pull the meter, do your work with the meter pulled, then have the power company put the meter back in. However, the power company will probably want to see a permit, and that will take a licensed electrician in most cases, so that may not be an option.
Also...if you are terminating aluminum connections, make sure to use anti-oxidant goop on the terminations and torque them only to the recommended specs. Don't have a torque wrench? Call an electrician. Al is nasty if not terminated correctly. In fact, that goes for all connections. If at possible, beg or borrow a torque wrench so that you can terminate connections to the proper specifications. Note that that only applies to main connections, not branch circuits.
Don't believe what you read in the "Space Shuttle Operator's Manual". It's not even an official publication. If you want to _really_ understand the Shuttle, read the Shuttle Crew Operations Manual (SFOC FL-0884). It isn't actually a published document...so it may be hard to find, but believe me, it's an excellent read. No "potential customer" who knew what they were doing would read the "Space Shuttle Operator's Manual".
Hard drives have flown on the Shuttles and the ISS many times before, there's nothing to worry about having a spinning disk onboard. As far as electronic emissions, you've got cosmic rays to worry about, so a little interference from onboard equipment is nothing.
I recall that there was a Pocket PC that had a USB host port - there it is, the Casio E-200. I know it had drivers for USB keyboards, but I think that was the extent of it. You could probably write a driver for a floppy, though. This couldn't be done with a PDA that syncs over USB, though, because those are USB peripherals and not host devices.
I'm one - I can only independently close or blink my left eye. I can, however, blink both eyes simultaneously. I don't know what causes it. I hope this answers your questions.
-Kurt
Misguided versioning?
on
Kernel 2.4.17 Out
·
· Score: 4, Interesting
After several of the last few kernels being released with major bugs, I thought the consensus on LKML was to use -rc versions for bugfixes, and then release a 'final' without making any changes in it. Yet, when I read this changelog, I see that changes were made in the final version. A lot of people will only download a 'final' kernel, because they think that it contains only tested, stable code. That is what the -rc system was to ensure, but releasing a 'final' with changes means that a partially untested kernel is being released to the unsuspecting public. Now, I will admit that there's a very good solution that any user can implement - just don't upgrade. However, these recent quality control problems have given Linux something of a black eye in the public's mind. Therefore, it just seems common sense to not release a kernel with code that hasn't been in for at least one -pre or -rc revision. So, if I were a kernel maintainer, about to release kernel 2.4.18, and I received a 'critical' patch from a project maintainer, I'd make one last -rc release to ensure that the code gets tested before I release it. However, I'm not a kernel maintainer, so take this as you will. I don't mean it as a flame, and I think that Linus and Marcelo have done a wonderful job so far with Linux 2.4.
Not too many people would need it? I disagree. It gives you a centralised structure, with one provider. It was expandable, and could, when it was killed, provide you with 4 phone lines and high-bandwidth net access, over ATM! ATM to the home over fiber! Imagine the possiblities!
I don't want this to sound like an obituary, but ION really was a great idea. Though it never came to my area, it was just like some of the other FTTH services that we saw earlier in the 90's - voice, data, and eventually video all on one line, through one provider. Admittedly, ION had issues, but overall, the service was good, with plenty of bandwidth, and you got everything from one provider. Plus, as I recall, their TOS/AUP was not as bad as most DSL providers - that is, you could run servers, and add routers/home networks.
In short, it was spectacular service with high prices and low demand. So, it died. Oh well.
It may be too hard/too expensive to engineer a system with full redundancy, but what about partial redundancy? For example, suppose that you have 1 (very costly to run) link between two points. So, rather than running a second big pipe, put in a smaller, cheaper pipe that offers partial service, as opposed to no service when the link goes down. There. Partial redundancy. It seems to me that that might be a workable solution.
A well-tuned wireless system with _real_ antennae won't go down whenever it rains or is windy, and the original poster wanted a wireless solution. 802.11b with a directional antenna at each site would probably work fairly well, in fact.
I don't know how the cables go from short to round, could the rounding process have caused a short? Do you know if the capacitors had anything to do with the IDE bus, or could they be unrelated?
Slashdot Mirror
Actually, you're conflating the history of the GM EV1 and the Toyota RAV4 EV. The GM EV1s were indeed rounded up after their leases ended, and most went to the crusher (although a few ended up being sent to university research labs, and one went to the Smithsonian (where it is no longer on display, for reasons unknown)). The Toyota RAV4 EV, on the other hand, was initially only available as a leased vehicle, but in 2002 Toyota sold around 300 RAV4 EVs to purchasers in California, and those vehicles were sold with no strings attached. Many of the leased RAV4 EVs also ended up in private hands after their leases ended.
Wrong. Cingular Blue (the old AWS) was GSM in plenty of markets.
Do some research next time.
"users cannot typically be granted any kind of admin access on a machine without granting them access on the network level"
Not so...I have set up Windows machines several times such that domain users (who do not have Administrator privs on the domain) have local Administrator access on their own machine. It's an ideal solution for more technically aware users, who can be trusted to install their own software.
As to someone infecting machines on the inside, well, that's a matter of network design. You have to plan not only for threats from the outside, but also for threats from the inside.
Finally, "ludicrously inefficient IT department[s]" are the norm rather than the exception. Unfortunate fact of life.
-Kurt
Agreed. This can become a serious problem, and frankly it smacks of egocentrism on the part of IT staff. The "user-presumed-guilty" mentality makes it very difficult for anyone to get anything done.
There isn't even a logical basis for it. If you have Ghost (or whatever else) images for your stock configurations, then if a user screws up their machine, you reimage it and you're done. Better yet, set something to work over the network with PXE, so all you have to do is reboot and tell the machine to boot from the network, and poof, it's reimaged.
It's all politics, really.
-Kurt
Did you even read any of the linked materials? No part of the OpenID system stores your personal details. The only thing OpenID does is allow you to prove that you own a URL. There is no such thing as an 'OpenID profile'--an OpenID producer and consumer just don't exchange that kind of information.
And if you read the specs, I think you will see that OpenID is designed from the ground up with security in mind.
Nothing special, really, just an iPaq via Bluetooth to an SE T68i, then GPRS out to the Internet.
/. a few times going from Baltimore to New York (or vice-versa) via Amtrak. It is only marginally more difficult to maintain a steady GPRS connection at up to 200 kph than when standing still.
But I have read
-Kurt
I'm going to go out on a limb here, but, what's so wrong with reverse-engineering games to develop bots?
You call them 'cheaters', I see it as changing the dynamic of the game--it's no longer about how well you play the game, but how well you program your computer to play the game. And what's wrong with that?
So you're playing a multiplayer game and your opponent starts using a bot to get ahead...so why not load up your own bot then?
-Kurt
Couple of notes from an amateur electrician:
"I would suggest buying several different colors to help keep things straight in the next step."
Um, there are color codes for a reason:
black (for sure), red (if 220), orange (if 3-phase, then it's the high leg) are all hot
white - neutral
no insulation or green - ground
"SHUT OFF THE POWER AND INSURE IT WILL NOT BE TURNED BACK ON UNTIL YOU ARE DONE!!!"
And if possible, pull the meter. Seriously. Have the power company pull the meter, do your work with the meter pulled, then have the power company put the meter back in. However, the power company will probably want to see a permit, and that will take a licensed electrician in most cases, so that may not be an option.
Also...if you are terminating aluminum connections, make sure to use anti-oxidant goop on the terminations and torque them only to the recommended specs. Don't have a torque wrench? Call an electrician. Al is nasty if not terminated correctly. In fact, that goes for all connections. If at possible, beg or borrow a torque wrench so that you can terminate connections to the proper specifications. Note that that only applies to main connections, not branch circuits.
Don't believe what you read in the "Space Shuttle Operator's Manual". It's not even an official publication. If you want to _really_ understand the Shuttle, read the Shuttle Crew Operations Manual (SFOC FL-0884). It isn't actually a published document...so it may be hard to find, but believe me, it's an excellent read. No "potential customer" who knew what they were doing would read the "Space Shuttle Operator's Manual".
Hard drives have flown on the Shuttles and the ISS many times before, there's nothing to worry about having a spinning disk onboard. As far as electronic emissions, you've got cosmic rays to worry about, so a little interference from onboard equipment is nothing.
No, actually this NCP stood for Network Control Protocol, and had nothing to do with Netware's NCP or IPX/SPX.
It's Cray. They use 3M Fluorinert.
I recall that there was a Pocket PC that had a USB host port - there it is, the Casio E-200. I know it had drivers for USB keyboards, but I think that was the extent of it. You could probably write a driver for a floppy, though. This couldn't be done with a PDA that syncs over USB, though, because those are USB peripherals and not host devices.
-Kurt
If I'm not mistaken, you already can point My Documents to an arbitrary share - but I can't remember how at the moment.
-Kurt
-Kurt
After several of the last few kernels being released with major bugs, I thought the consensus on LKML was to use -rc versions for bugfixes, and then release a 'final' without making any changes in it. Yet, when I read this changelog, I see that changes were made in the final version. A lot of people will only download a 'final' kernel, because they think that it contains only tested, stable code. That is what the -rc system was to ensure, but releasing a 'final' with changes means that a partially untested kernel is being released to the unsuspecting public. Now, I will admit that there's a very good solution that any user can implement - just don't upgrade. However, these recent quality control problems have given Linux something of a black eye in the public's mind. Therefore, it just seems common sense to not release a kernel with code that hasn't been in for at least one -pre or -rc revision. So, if I were a kernel maintainer, about to release kernel 2.4.18, and I received a 'critical' patch from a project maintainer, I'd make one last -rc release to ensure that the code gets tested before I release it. However, I'm not a kernel maintainer, so take this as you will. I don't mean it as a flame, and I think that Linus and Marcelo have done a wonderful job so far with Linux 2.4.
Another good point is the built-in integration with the iPod, although you'll have to rip to mp3 for that.
Not too many people would need it? I disagree. It gives you a centralised structure, with one provider. It was expandable, and could, when it was killed, provide you with 4 phone lines and high-bandwidth net access, over ATM! ATM to the home over fiber! Imagine the possiblities!
I don't want this to sound like an obituary, but ION really was a great idea. Though it never came to my area, it was just like some of the other FTTH services that we saw earlier in the 90's - voice, data, and eventually video all on one line, through one provider. Admittedly, ION had issues, but overall, the service was good, with plenty of bandwidth, and you got everything from one provider. Plus, as I recall, their TOS/AUP was not as bad as most DSL providers - that is, you could run servers, and add routers/home networks.
In short, it was spectacular service with high prices and low demand. So, it died. Oh well.
It may be too hard/too expensive to engineer a system with full redundancy, but what about partial redundancy? For example, suppose that you have 1 (very costly to run) link between two points. So, rather than running a second big pipe, put in a smaller, cheaper pipe that offers partial service, as opposed to no service when the link goes down. There. Partial redundancy. It seems to me that that might be a workable solution.
A well-tuned wireless system with _real_ antennae won't go down whenever it rains or is windy, and the original poster wanted a wireless solution. 802.11b with a directional antenna at each site would probably work fairly well, in fact.
I don't know how the cables go from short to round, could the rounding process have caused a short? Do you know if the capacitors had anything to do with the IDE bus, or could they be unrelated?
Your French is a bit off. I think you mean:
n'est pas?
Soon, soon. Right now we're just trying to jet the project off the ground. Eventually, though, we'll release pre-compiled versions in PS and PDF.