Thunderbolt is Intel's not Apple. Fireware is an IEEE standard. Only minidisplay port is an Apple "proprietary" port.
No, Lightpeak is Intel, Thunderbolt is Apple.
Intel developed Lightpeak, Apple simply purchased the technology and named it Thunderbolt, hence Apple owns the trademark on that one.
You're half right that Intel developed it, you're completely wrong that it's not Apple proprietary. Intel can sell Lightpeak to other companies without Apple's permission, but not Thunderbolt as Thunderbolt belongs to Apple.
Also, just because Firewire is an IEEE standard does not mean it is not proprietary. Being non-proprietary was never a requirement for IEEE standards. If you want to use IEEE1394, you need to pay... Apple.
Waiting for the inevitable mod-down by Apple fanboys who dont like the truth.
Or, if you have transferred the ROM contents to a PC-readable file, a PC running an emulator.
Which has pretty much proved my point for me. PC is the only platform that survives.
BTW, they aren't making SNES's any more, there are so many around simply because they are so bulletproof... You want to make the same bet with an XBox 360.
This is to say nothing of their hard drive connector which locks out 3rd party HDD's. Newer Macbooks use a custom connector, even though it's based on SATA, the connector makes it incompatible with other SATA drives.
Remember that even though they base them on open or accessible standards that they do not own, they can change the shape and pin configuration AND make that proprietary (I.E. how Coke owns their bottle shape). The three ports I menioned above are proprietary to Apple.
That being said, I highly doubt that these things will be tamper proof in the slightest (manufacturers will simply pick the cheapest possible way to comply with the law). Black boxes will be easily hacked so it's a bit of moot point for people who are bad drivers and dont want the proof hanging around (however for good drivers, it does help clear them of fault in an accident).
Because everyone would have the knowledge and skills to do it?
Because no-one would offer such services to these people.
Do you think the average street racer knows how to flash an ECU and change the boost on their turbo? Hell no, they pay someone who does.
That is something I don't get. why don't car manufacturers give us mroe data than a stupid warning light?
Because the average driver can barely remember to indicate, let alone decipher complex instructions like "Change the oil now, dipstick".
Unfortunately car designers have to consider the stupidest users when designing things. Also, the sensors cant always tell whats going on, I.E. fluid pressure could be falling because a cap is loose or because there is a hole in the line somewhere. You'll need to do some diagnostics on your own to do this, unfortunately most people dont know how to check their oil, let alone how to see if there is a leak somewhere.
The car companies have the data right fucking there,
You want access to the data, that's great, I can suggest getting an ODBII device to read the codes. Many car manufacturers will output error codes over ODB, I've got a $15 bluetooth ODB connector and Torque (on Android), with my Honda they're easy enough to figure out (Google is your friend, codes on my Honda were quickly found).
But diagnosing car problems still requires some knowledge on the matter.
With Event Data recorders, you don't have to prevent hacking, or erasure. You just have to be able to detect that it occurred.
There in lies the problem, it's entirely possible to prevent that from being logged.
Seeing as you have physical access to the hardware it would not be difficult at all. At worst it would be a wholesale replacement of the part with a pre-modified version. But it's far more likely that you'll just have to re-flash the firmware.
Not that I'd advocate this, but I have to face the reality it will happen.
The lawyers can data mine these incidents, 5mph over here, unsignaled lane change there, a lane drift on a totally empty road, and put you in the light of a careless driver, and claim that an attentive and defensive driver might have avoided the accident.
This is why the law is very specific about fault (at least in my country). The road code is a 400 page document, if you printed it out you could use it for self defence.
Even if you were in violation of one of the more minor road rules, you can still be ruled to be not at fault. I.E. if you were changing lanes at a traffic light (illegal where I live) and someone runs a red and T-Bones you, there was nothing you could do to avoid that accident. Also whilst the events leading up to an accident are taken into account there is a limit of what can be used (I.E. if someone overtakes you and immediately brakes, forcing you to rear-end him, you will be considered not at fault because the other driver acted in an unsafe manner to put you in that position. However an unsignaled lane change 2 minutes previous would not matter as it did not contribute to the event).
BTW, an unsignaled lane change is the sign of a careless driver, it really should be muscle memory and you shouldn't have to think about it. Failing to do so every now and then is forgivable, but consistently forgetting is the sign of a bad driver. Drifting out of your lane unforgivable, regardless of how full or empty the road is. Anyone who has a history of forgetting to indicate or have trouble staying in their lane is bad driver.
The Event Data Recorder could be logically or physically separate from the Engine Control Unit that you're talking about with that kind of aftermarket support.
And I'm sure it will be separated (but still connected as it needs to get data from the ECU, things like the CAN bus already facilitate this), I was merely using the ECU as an example of how after-market programming has already taken root in the automotive sector.
In the worst case scenario, a EDR (back box) will need to be hardwired, but chances are they'll use off the shelf components so like the ECU, it'll just need to be re-flashed with an aftermarket ROM.
Nothing wrong with a last minute request if it was unavoidable. However, if you had time to report it before, you should have done that. If you know it's not urgent, don't pretend it is, because we can tell, and we will remember your lies.
This, with a good manager they will make you feel appreciated for doing last minute requests. They'll also protect you from people who keep making unreasonable requests. I've had beer, whiskey, chocolate and even flowers bought to my desk by appreciative users, you know what, I like helping these people even if I'm a little bit put out by it because they appreciate what I do/did for them. OTOH you've got the idiots who think they're entitled to my time, day or night... they wonder why I have "an attitude problem". Fortunately I'm in a position where I'm protected from people like that.
I dont mind staying a little late or getting up a little earlier to help someone, as long as they understand this is not the norm.
I could go on, but rest assured, you'll want your own job back.
I agree with everything you've said.
But this is where ITIL rocks. L3 support and Sysadmins dont have to deal with whiny end users, by the time they reach us most of the mundane testing and diagnostics have been done by L1 and 2 support. Also, people tend to be less condescending when they're speaking to an "engineer". Of course this is for the few places who follow ITIL.
But where ITIL sucks is the paperwork. Sigh, this isn't even my final form.
There already is an after market for re-programming ECU's.
I doubt these boxes will be tamper proof in the slightest, car manufactures have a long history of picking the cheapest possible way to comply with legal requirements and as always, if you have physical access to a system it's already compromised.
Actually I wouldn't mind having a black box in the car recording everything... IF I have access to the data.
Here's the argument, access vs control. I'm all for black boxes in cars too (I've already installed a dash cam in my car) but I would also require access to the data.
That being said, I highly doubt that these things will be tamper proof in the slightest (manufacturers will simply pick the cheapest possible way to comply with the law). Black boxes will be easily hacked so it's a bit of moot point for people who are bad drivers and dont want the proof hanging around (however for good drivers, it does help clear them of fault in an accident).
I've contemplated wiring up cameras and building a small server to continuously record front and rear views, so if there's an accident or something and there's questions about what happened I can pull up the video and say "Here, watch what happened."
Most cars already have these sensors available through an ODBII interface, you can get bluetooth ODB connectors off Ebay for $15 and a free application called Torque on Android can read it (IIRC, for full logging you need the full application) so if you want a black box it can be set up with a cheap Android tablet and a dash cam. You could probably even use the Android device as a dash cam (although I haven't seen a mobile device with decent enough video quality to replace my 1080p 30 FPS camera). I've got mine hooked up to my phone, great for diagnosing problems and improving my driving style.
However dash cam and logging devices are double edged swords. Along with proving you're not at fault, they can also prove you did something wrong and many people in my experience dont know when they're doing something wrong.
For me, personally, my biggest concern is the inability to play games, not systems, I've purchased 10, 15, 20 years down the road. So my old 2014 Xbox One fried. Whatever, I still have all the discs I purchased.
What happens when that hardware stops working? 20 years on. How much does a working SNES go for? What other hardware can play SNES games?
And SNES's were bullet proof. No Red Ring of Death issues there (previous to the Xbox 360, saying you had a "red ring" was a good thing).
The only platform that currently supports 20 year old games is the PC. So if having your 20year old games work is an issue to you, game on a PC. Personally I have floppy disks of ancient PC games that still work. My earliest CD ROM game is from 1995.
As much as I enjoy bashing Microsoft, they have redeemed themselves a little by listening to their customers.
You're right, just not in the way you think.
Microsoft has listened to their customers, the publishers who want the console to be in the hands of people. They want people to buy the XBone because it has these capabilities pre-installed (they aren't removed, simply deactivated), a console that doesn't sell is useless to them. One with inbuilt DRM that can be activated at any time is their wet dream.
Microsoft doesn't give two shits about consumers. The XBone will be a loss leader like the Xbox 360. They intend to make their money with licensing fees to game publishers.
For one thing, the retraction will never make as much news as the initial announcement. For another, there is enormous risk that, whatever they say, people will suspect that these schemes still exist (even if they are, for the time being, disabled) and avoid the system out of fear that they will be implemented later.
Frog... Boiling...
Wait until people become financially and emotionally invested in the XBone and then spring it on them. The system is already in place, it just needs to be activated. Because people are too emotionally attached to their favourite console and dont understand the fallacy of sunk costs they'll keep spending money on it.
You have to admire Microsoft for this in a diabolical kind of way.
1. Generate huge amounts of publicity with a bad idea(TM).
2. Claim to revoke bad idea(TM) and generate even more publicity.
3. People buy product.
4. Bring back bad idea(TM), muhahahahahahahaha, fools.
5. Fail to make a profit for years as the product is sold as a loss leader.
It's almost Bond level of villainry. Bravo Microsoft.
1.42 metres per second is 5.11 kph / 3.18 mph, or Force One on the Beaufort scale, which Wikipedia tells me means "Smoke drift indicates wind direction. Leaves and wind vanes are stationary."
Slashdot Mirror
http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4806:15tnmo.2.3
Guess again.
Serial Number 85314959
Word Mark THUNDERBOLT
Owner (APPLICANT) Apple Inc.
And here we go. Modded overrated because fanboys wanted it hidden.
This means they paid Apple to use these proprietary components,
Try again.
Thunderbolt is Intel's not Apple. Fireware is an IEEE standard. Only minidisplay port is an Apple "proprietary" port.
No, Lightpeak is Intel, Thunderbolt is Apple.
Intel developed Lightpeak, Apple simply purchased the technology and named it Thunderbolt, hence Apple owns the trademark on that one.
You're half right that Intel developed it, you're completely wrong that it's not Apple proprietary. Intel can sell Lightpeak to other companies without Apple's permission, but not Thunderbolt as Thunderbolt belongs to Apple.
Also, just because Firewire is an IEEE standard does not mean it is not proprietary. Being non-proprietary was never a requirement for IEEE standards. If you want to use IEEE1394, you need to pay... Apple.
Waiting for the inevitable mod-down by Apple fanboys who dont like the truth.
Care to name them?
Thunderbolt, Firewire, mini display port.
This is to say nothing of their hard drive connector which locks out 3rd party HDD's. Newer Macbooks use a custom connector, even though it's based on SATA, the connector makes it incompatible with other SATA drives.
Remember that even though they base them on open or accessible standards that they do not own, they can change the shape and pin configuration AND make that proprietary (I.E. how Coke owns their bottle shape). The three ports I menioned above are proprietary to Apple.
That being said, I highly doubt that these things will be tamper proof in the slightest (manufacturers will simply pick the cheapest possible way to comply with the law). Black boxes will be easily hacked so it's a bit of moot point for people who are bad drivers and dont want the proof hanging around (however for good drivers, it does help clear them of fault in an accident).
Because everyone would have the knowledge and skills to do it?
Because no-one would offer such services to these people.
Do you think the average street racer knows how to flash an ECU and change the boost on their turbo? Hell no, they pay someone who does.
Because the average driver can barely remember to indicate, let alone decipher complex instructions like "Change the oil now, dipstick".
Unfortunately car designers have to consider the stupidest users when designing things. Also, the sensors cant always tell whats going on, I.E. fluid pressure could be falling because a cap is loose or because there is a hole in the line somewhere. You'll need to do some diagnostics on your own to do this, unfortunately most people dont know how to check their oil, let alone how to see if there is a leak somewhere.
You want access to the data, that's great, I can suggest getting an ODBII device to read the codes. Many car manufacturers will output error codes over ODB, I've got a $15 bluetooth ODB connector and Torque (on Android), with my Honda they're easy enough to figure out (Google is your friend, codes on my Honda were quickly found).
But diagnosing car problems still requires some knowledge on the matter.
With Event Data recorders, you don't have to prevent hacking, or erasure. You just have to be able to detect that it occurred.
There in lies the problem, it's entirely possible to prevent that from being logged.
Seeing as you have physical access to the hardware it would not be difficult at all. At worst it would be a wholesale replacement of the part with a pre-modified version. But it's far more likely that you'll just have to re-flash the firmware.
Not that I'd advocate this, but I have to face the reality it will happen.
The lawyers can data mine these incidents, 5mph over here, unsignaled lane change there, a lane drift on a totally empty road, and put you in the light of a careless driver, and claim that an attentive and defensive driver might have avoided the accident.
This is why the law is very specific about fault (at least in my country). The road code is a 400 page document, if you printed it out you could use it for self defence.
Even if you were in violation of one of the more minor road rules, you can still be ruled to be not at fault. I.E. if you were changing lanes at a traffic light (illegal where I live) and someone runs a red and T-Bones you, there was nothing you could do to avoid that accident. Also whilst the events leading up to an accident are taken into account there is a limit of what can be used (I.E. if someone overtakes you and immediately brakes, forcing you to rear-end him, you will be considered not at fault because the other driver acted in an unsafe manner to put you in that position. However an unsignaled lane change 2 minutes previous would not matter as it did not contribute to the event).
BTW, an unsignaled lane change is the sign of a careless driver, it really should be muscle memory and you shouldn't have to think about it. Failing to do so every now and then is forgivable, but consistently forgetting is the sign of a bad driver. Drifting out of your lane unforgivable, regardless of how full or empty the road is. Anyone who has a history of forgetting to indicate or have trouble staying in their lane is bad driver.
The Event Data Recorder could be logically or physically separate from the Engine Control Unit that you're talking about with that kind of aftermarket support.
And I'm sure it will be separated (but still connected as it needs to get data from the ECU, things like the CAN bus already facilitate this), I was merely using the ECU as an example of how after-market programming has already taken root in the automotive sector.
In the worst case scenario, a EDR (back box) will need to be hardwired, but chances are they'll use off the shelf components so like the ECU, it'll just need to be re-flashed with an aftermarket ROM.
"5. You make unreasonable last-minute requests."
Nothing wrong with a last minute request if it was unavoidable. However, if you had time to report it before, you should have done that. If you know it's not urgent, don't pretend it is, because we can tell, and we will remember your lies.
This, with a good manager they will make you feel appreciated for doing last minute requests. They'll also protect you from people who keep making unreasonable requests. I've had beer, whiskey, chocolate and even flowers bought to my desk by appreciative users, you know what, I like helping these people even if I'm a little bit put out by it because they appreciate what I do/did for them. OTOH you've got the idiots who think they're entitled to my time, day or night... they wonder why I have "an attitude problem". Fortunately I'm in a position where I'm protected from people like that.
I dont mind staying a little late or getting up a little earlier to help someone, as long as they understand this is not the norm.
If a Manager is abusing their position of power then they need to be removed. That's it. There's no petty revenge or "blowback" to consider.
See how far you get with that one.
What's good for the goose is good for the gander.
I could go on, but rest assured, you'll want your own job back.
I agree with everything you've said.
But this is where ITIL rocks. L3 support and Sysadmins dont have to deal with whiny end users, by the time they reach us most of the mundane testing and diagnostics have been done by L1 and 2 support. Also, people tend to be less condescending when they're speaking to an "engineer". Of course this is for the few places who follow ITIL.
But where ITIL sucks is the paperwork. Sigh, this isn't even my final form.
True sysadmin logic! Do as I say, not as I do.
Do not forget this, for we sysadmins are subtle and quick to anger.
There already is an after market for re-programming ECU's.
I doubt these boxes will be tamper proof in the slightest, car manufactures have a long history of picking the cheapest possible way to comply with legal requirements and as always, if you have physical access to a system it's already compromised.
Actually I wouldn't mind having a black box in the car recording everything... IF I have access to the data.
Here's the argument, access vs control. I'm all for black boxes in cars too (I've already installed a dash cam in my car) but I would also require access to the data.
That being said, I highly doubt that these things will be tamper proof in the slightest (manufacturers will simply pick the cheapest possible way to comply with the law). Black boxes will be easily hacked so it's a bit of moot point for people who are bad drivers and dont want the proof hanging around (however for good drivers, it does help clear them of fault in an accident).
I've contemplated wiring up cameras and building a small server to continuously record front and rear views, so if there's an accident or something and there's questions about what happened I can pull up the video and say "Here, watch what happened."
Most cars already have these sensors available through an ODBII interface, you can get bluetooth ODB connectors off Ebay for $15 and a free application called Torque on Android can read it (IIRC, for full logging you need the full application) so if you want a black box it can be set up with a cheap Android tablet and a dash cam. You could probably even use the Android device as a dash cam (although I haven't seen a mobile device with decent enough video quality to replace my 1080p 30 FPS camera). I've got mine hooked up to my phone, great for diagnosing problems and improving my driving style.
However dash cam and logging devices are double edged swords. Along with proving you're not at fault, they can also prove you did something wrong and many people in my experience dont know when they're doing something wrong.
Koresh and the Branch Davidians were hardly terrorists. The FBI shot first.
The idiots shooting up schools are just that, idiots. They're not doing it to terrorize for some political or religious end.
I'll give you McVeigh and Kaczynski.
Why are we limiting this to the US? Chechyan rebels, the IR fucking A?
You've got terrorist organisations in all colours and religions. Saying only Arabs are terrorist is naive to the extreme.
BTW, a lot of mass shootings accompany extremist ideologies. Norway's Anders Brevik for example. So you're wrong with that one too.
For me, personally, my biggest concern is the inability to play games, not systems, I've purchased 10, 15, 20 years down the road. So my old 2014 Xbox One fried. Whatever, I still have all the discs I purchased.
What happens when that hardware stops working? 20 years on. How much does a working SNES go for? What other hardware can play SNES games?
And SNES's were bullet proof. No Red Ring of Death issues there (previous to the Xbox 360, saying you had a "red ring" was a good thing).
The only platform that currently supports 20 year old games is the PC. So if having your 20year old games work is an issue to you, game on a PC. Personally I have floppy disks of ancient PC games that still work. My earliest CD ROM game is from 1995.
So up to a short time ago people did this for free? But now they are worth 100K a pop?
Actually it's a $100,000 program, not $100,000 a bug. With the volume of bugs in Windows they will probably be broke in a week offering $5 a pop.
As much as I enjoy bashing Microsoft, they have redeemed themselves a little by listening to their customers.
You're right, just not in the way you think.
Microsoft has listened to their customers, the publishers who want the console to be in the hands of people. They want people to buy the XBone because it has these capabilities pre-installed (they aren't removed, simply deactivated), a console that doesn't sell is useless to them. One with inbuilt DRM that can be activated at any time is their wet dream.
Microsoft doesn't give two shits about consumers. The XBone will be a loss leader like the Xbox 360. They intend to make their money with licensing fees to game publishers.
Microsoft has made their fortune assuming their users are stupid.
The real problem is, Microsoft is not wrong in that assumption.
Its own, not it's [SICK] own.
Ahem, it's [sic].
"sic" is Latin for "thus". If you're going to be a grammar Nazi, at least be accurate in your own post.
For one thing, the retraction will never make as much news as the initial announcement. For another, there is enormous risk that, whatever they say, people will suspect that these schemes still exist (even if they are, for the time being, disabled) and avoid the system out of fear that they will be implemented later.
Frog... Boiling...
Wait until people become financially and emotionally invested in the XBone and then spring it on them. The system is already in place, it just needs to be activated. Because people are too emotionally attached to their favourite console and dont understand the fallacy of sunk costs they'll keep spending money on it.
You have to admire Microsoft for this in a diabolical kind of way.
1. Generate huge amounts of publicity with a bad idea(TM).
2. Claim to revoke bad idea(TM) and generate even more publicity.
3. People buy product.
4. Bring back bad idea(TM), muhahahahahahahaha, fools.
5. Fail to make a profit for years as the product is sold as a loss leader.
It's almost Bond level of villainry. Bravo Microsoft.
1.42 metres per second is 5.11 kph / 3.18 mph, or Force One on the Beaufort scale, which Wikipedia tells me means "Smoke drift indicates wind direction. Leaves and wind vanes are stationary."
Wind can move at that speed.
Look, I'm not going to believe it's a cat like robot until it can lay around for 18 hours of the day and lick it's own arse.