Exactly. If it still has data on it, it wasn't refurbished. Any proper refurb will "factory" low-level format the drive. This clears all the accumulated run-time stats, zeros the entire platter, rewrites all the tracking information, and rewrites the stored firmware. (ie. it takes vendor specific, proprietary tools.)
A drive that still has data on it is a "working pull".
Depending on the drive, degausing it will very likely destroy it, by erasing the factory formated tracking information and firmware. (the same is true of an LTO tape... "bulk erasure" will destroy the tracking information.)
The read/write heads on a hard drive create a *very* powerful magnetic field. It's just over a very, very tiny area. See Also: The MythBusters episode where they try to erase a credit card mag-stripe.
lol. A screw driver hammered into the side of the column is a dead giveaway. I had the switch housing (clamshell crimped together, really crappy) come apart in my old ford tempo. A few hours with a bag a zip ties...
It was even easier with even older cars that had the switch on the dash. Reach under the dash, one yank, and Bob's your uncle! *whistles innocently*
You won't believe it until you see it with your own eyes -- in person. (you're doing exactly what the ignition switch does, just without the key... turn the ignition on, pulse the starter.)
On the cars I know, that's a lot more work than you might think. Audi/VW/etc. put the ECU where it isn't easy to reach. (unlike Datsun bolting them to the floor under the driver seat.) Once you do get to it, they're often filled with epoxy -- "weather proofing". Honda, on the other hand, easy to get to, easy to chip -- but I think that's intentional to make the cars favorable to hobby/tinkerers.
(Heh, our LeMons "race" car -- honda civic -- has two ECUs. One seriously hacked up for racing, and it's original OBD-II ecu for when it gets inspected.:-))
Well, COULD do... back in the 80's. Starting a car by touching the right two wires in the igition harness ended around 1989 with the last of the carbureted cars. (I'm told that was a Subaru Justy.) A carbureted car could be started that way. Cars with electronic ignitions have more wires. And modern ones have anti-theft devices.
OnStar is a GM brand. I'm told the Toyota/Lexus Enform/Safety-Connect system is run by OnStar. (on verizon's network.)
If you're going to boost a car thusly equiped, you'd be wise to remove or disable the thing FIRST. When manufacturers get wise and link the module into the anti-theft logic -- meaning the car won't work without it -- simply disable the radio/antenna. Not being able to start your car because it cannot see T-Mobile's network (for example) would never be accepted by customers.
Actually, Windows doesn't provide an undelete either. What you may be thinking of (the recycling bin) is an artifact of Explorer. (and to some extent, system restore.) While there are tools to look for deleted files and attempt to restore them, they are not "builtin", but understand how files are deleted and allocated and can "reverse" the process. Technically, the exact same sort of tool can be created for most linux filesystems -- in fact, I've done it for ext2. The reason such tools don't exist is because of the nature of UNIX(tm) -- once the blocks are free, they can be used by another file immediately, and often are.
No it isn't. Or do you think "resistant" is the word to describe a filesystem that can corrupt files that haven't been touched since the OS was installed simply from the power being pulled?
So, that'd be "don't do it the UNIX(tm) way" and "don't do it the Microsoft Exchange way". In other words... "Don't run a mail server on windows." I agree with this.
The problem here is that the base installation of windows will put a few hundred smallish files (i.e 0-2 blocks) in a directory -- inf files, fonts, log files, cursors, etc. Once running, IE will do the same thing with it's cache (cookie files.) Registry files and event logs will grow without bounds (unless you set one) -- and the registry will never shrink without direct user action (i.e. using a 3rd party tool.)
because even Windows hasn't had such issues in over a goddamn decade
BULL FUCKING SHIT! I have machines all over the office with subtly screwed NTFS's due to power failures. I've had to completely rebuild 3 machines over the last year due to power failures resulting in corrupt and unbootable systems. I've had to repair the same g** d*** VM three times in the last month due to power glitches. I G** D**** HATE!!!!! WINDOWS. For a "journaled filesystem", Microsoft has failed in every way.
In contrast, the dozens of linux systems (all using xfs) have been kicked about hundreds of times over the last few years. I've not had to touch a single. f'ing. one. Bare hardware, VM, makes no difference. I can pull the FC storage link mid-write and the linux images will be just fine -- sure the vm crashes, but plug it back in and it'll boot up fine.
If they have physical possession of your stuff, there is nothing you can do that cannot be disabled, removed, turned off, reset, or bypassed. All you can do is make it hard, expensive, and/or time consuming.
Thinkpad? The TPM can be erased/cleared/bypassed/etc. You have to completely disassemble the laptop to get to the chip. With the right hardware and software (which can be had on the darker parts of the interweb for ~$30), it's easy to defeat -- in fact, you can read and decrypt your password. As for the ATA spec for securing the drive, unless you've taken the explicit steps to disable it, there's a manufacturer password to unlock the drive.
Actually, they're all pretty bad about that. My favorite is the delivery note with nothing at all marked on it. At least that driver was smart enough to stick them in the door frame instead of hanging on the doorknob or relying on that sticky to hold it to a dirty door in the wind.
At the apartment, many times, but UPS and Fedex would just go straight to the office and unload everything. If you're lucky, you got a note as per above. But most of the time, if you weren't looking at the tracking info, you'd get a call from the office staff to "get your crap out of the closet." (they were much less irate about it when educated about the UPS/Fedex way of delivery.)
Of course, they were also just as likely to leave stuff stacked outside your door... where neighborhood child could walk off with it, dogs could pee on it, etc. They do that today at my townhouse... boxes sitting out in my driveway in the rain. (now that I think about it, they do that at the office too... crap stacked in the hallway when you get back from lunch.) I've had the landscapers bring me jiffy mailers they found blown in the ditch. And Fedex has left legal documents propped against my front door -- things that require my verified signature (i.e. SHOW ID and sign PAPER, not that damned electronic pad that has the resolution of a fat crayon.)
Exactly! Maybe Verizon has a different relationship with Cisco, but every time I've ever had Cisco replace defective parts, they've always required the bad parts be sent back. In a few cases, the courier takes the defective stuff with him.
Answer: by bringing in the people who designed the SAN and database. (i.e. the people who know what the bits on disk are supposed to be.)
Somehow I seriously doubt any Oracle-proper (not MySQL) database is using InnoDB as it's storage backend. And it more doubtful Microsoft would use mysql for anything at all.
The point stands... if *your* InooDB files get damaged in any way, there are no tools to fix it. The InnoDB devs have openly stated they don't care. (innodb-tools google code project is ~90% useless junk. It has very little understanding of the on-disk format, and what it does know is outdated and incomplete. And it doesn't repair anything; it attempts to dump the table data.)
They have a transformer in them because they are d***ed cheap. A solid state (electronic) regulator is much more efficient, smaller, and lighter, but requires some engineering and a few pennies more to build.
All of them have some sort of power regualtor (transformer, transistors, etc.) that will generate heat in the process. You cannot put 120V (AC or DC) right into an LED. (not for long...)
In a normal flight, the LEM doesn't come back to Earth. In this case, it was a lifeboat for the return to Earth. It was cut loose prior to reentry. The CM came back pretty much as normal from that point.
The LEM fell out of orbit -- uncontrolled re-entry. It did not survive intact. However, the SNAP-27 in one of it's payload modules most likely did, as it was designed to do so. The thing is, no one was paying close attention to the LEM as it de-orbited -- not that anyone could have spotted/followed the SNAP-27 in that mess.
Slashdot Mirror
Exactly. If it still has data on it, it wasn't refurbished. Any proper refurb will "factory" low-level format the drive. This clears all the accumulated run-time stats, zeros the entire platter, rewrites all the tracking information, and rewrites the stored firmware. (ie. it takes vendor specific, proprietary tools.)
A drive that still has data on it is a "working pull".
Depending on the drive, degausing it will very likely destroy it, by erasing the factory formated tracking information and firmware. (the same is true of an LTO tape... "bulk erasure" will destroy the tracking information.)
The read/write heads on a hard drive create a *very* powerful magnetic field. It's just over a very, very tiny area. See Also: The MythBusters episode where they try to erase a credit card mag-stripe.
Mildly radioactive, but still *highly* toxic. (and as others have said, far more valuable and rare.)
lol. A screw driver hammered into the side of the column is a dead giveaway. I had the switch housing (clamshell crimped together, really crappy) come apart in my old ford tempo. A few hours with a bag a zip ties...
It was even easier with even older cars that had the switch on the dash. Reach under the dash, one yank, and Bob's your uncle! *whistles innocently*
Heh. The key there... a cellphone is a tracking device. Granted, tower triangulation isn't going to tell what seat you're in.
You won't believe it until you see it with your own eyes -- in person. (you're doing exactly what the ignition switch does, just without the key... turn the ignition on, pulse the starter.)
On the cars I know, that's a lot more work than you might think. Audi/VW/etc. put the ECU where it isn't easy to reach. (unlike Datsun bolting them to the floor under the driver seat.) Once you do get to it, they're often filled with epoxy -- "weather proofing". Honda, on the other hand, easy to get to, easy to chip -- but I think that's intentional to make the cars favorable to hobby/tinkerers.
(Heh, our LeMons "race" car -- honda civic -- has two ECUs. One seriously hacked up for racing, and it's original OBD-II ecu for when it gets inspected. :-))
Well, COULD do... back in the 80's. Starting a car by touching the right two wires in the igition harness ended around 1989 with the last of the carbureted cars. (I'm told that was a Subaru Justy.) A carbureted car could be started that way. Cars with electronic ignitions have more wires. And modern ones have anti-theft devices.
OnStar is a GM brand. I'm told the Toyota/Lexus Enform/Safety-Connect system is run by OnStar. (on verizon's network.)
If you're going to boost a car thusly equiped, you'd be wise to remove or disable the thing FIRST. When manufacturers get wise and link the module into the anti-theft logic -- meaning the car won't work without it -- simply disable the radio/antenna. Not being able to start your car because it cannot see T-Mobile's network (for example) would never be accepted by customers.
Actually, Windows doesn't provide an undelete either. What you may be thinking of (the recycling bin) is an artifact of Explorer. (and to some extent, system restore.) While there are tools to look for deleted files and attempt to restore them, they are not "builtin", but understand how files are deleted and allocated and can "reverse" the process. Technically, the exact same sort of tool can be created for most linux filesystems -- in fact, I've done it for ext2. The reason such tools don't exist is because of the nature of UNIX(tm) -- once the blocks are free, they can be used by another file immediately, and often are.
RIGHT. Said like a marketing exec for InnoDB. I guess you've never heard of bugs, hardware faults, cosmic rays, etc.
No it isn't. Or do you think "resistant" is the word to describe a filesystem that can corrupt files that haven't been touched since the OS was installed simply from the power being pulled?
So, that'd be "don't do it the UNIX(tm) way" and "don't do it the Microsoft Exchange way". In other words... "Don't run a mail server on windows." I agree with this.
The problem here is that the base installation of windows will put a few hundred smallish files (i.e 0-2 blocks) in a directory -- inf files, fonts, log files, cursors, etc. Once running, IE will do the same thing with it's cache (cookie files.) Registry files and event logs will grow without bounds (unless you set one) -- and the registry will never shrink without direct user action (i.e. using a 3rd party tool.)
Please come visit my office to see just how much of a pain in the ass the "stable" NTFS can be.
BULL FUCKING SHIT! I have machines all over the office with subtly screwed NTFS's due to power failures. I've had to completely rebuild 3 machines over the last year due to power failures resulting in corrupt and unbootable systems. I've had to repair the same g** d*** VM three times in the last month due to power glitches. I G** D**** HATE!!!!! WINDOWS. For a "journaled filesystem", Microsoft has failed in every way.
In contrast, the dozens of linux systems (all using xfs) have been kicked about hundreds of times over the last few years. I've not had to touch a single. f'ing. one. Bare hardware, VM, makes no difference. I can pull the FC storage link mid-write and the linux images will be just fine -- sure the vm crashes, but plug it back in and it'll boot up fine.
If they have physical possession of your stuff, there is nothing you can do that cannot be disabled, removed, turned off, reset, or bypassed. All you can do is make it hard, expensive, and/or time consuming.
Thinkpad? The TPM can be erased/cleared/bypassed/etc. You have to completely disassemble the laptop to get to the chip. With the right hardware and software (which can be had on the darker parts of the interweb for ~$30), it's easy to defeat -- in fact, you can read and decrypt your password. As for the ATA spec for securing the drive, unless you've taken the explicit steps to disable it, there's a manufacturer password to unlock the drive.
Actually, they're all pretty bad about that. My favorite is the delivery note with nothing at all marked on it. At least that driver was smart enough to stick them in the door frame instead of hanging on the doorknob or relying on that sticky to hold it to a dirty door in the wind.
At the apartment, many times, but UPS and Fedex would just go straight to the office and unload everything. If you're lucky, you got a note as per above. But most of the time, if you weren't looking at the tracking info, you'd get a call from the office staff to "get your crap out of the closet." (they were much less irate about it when educated about the UPS/Fedex way of delivery.)
Of course, they were also just as likely to leave stuff stacked outside your door... where neighborhood child could walk off with it, dogs could pee on it, etc. They do that today at my townhouse... boxes sitting out in my driveway in the rain. (now that I think about it, they do that at the office too... crap stacked in the hallway when you get back from lunch.) I've had the landscapers bring me jiffy mailers they found blown in the ditch. And Fedex has left legal documents propped against my front door -- things that require my verified signature (i.e. SHOW ID and sign PAPER, not that damned electronic pad that has the resolution of a fat crayon.)
Exactly! Maybe Verizon has a different relationship with Cisco, but every time I've ever had Cisco replace defective parts, they've always required the bad parts be sent back. In a few cases, the courier takes the defective stuff with him.
Answer: by bringing in the people who designed the SAN and database. (i.e. the people who know what the bits on disk are supposed to be.)
Somehow I seriously doubt any Oracle-proper (not MySQL) database is using InnoDB as it's storage backend. And it more doubtful Microsoft would use mysql for anything at all.
The point stands... if *your* InooDB files get damaged in any way, there are no tools to fix it. The InnoDB devs have openly stated they don't care. (innodb-tools google code project is ~90% useless junk. It has very little understanding of the on-disk format, and what it does know is outdated and incomplete. And it doesn't repair anything; it attempts to dump the table data.)
Tell that to InnoDB. And there are no (usable) tools for repairing or recovering any data. I've been there too. many. times.
(in fact, had the exact same problem with a Derby DB earlier this week. They don't even pretend to have any recovery tools.)
Which is cheaper... 100 LEDs or a tiny 10:1 transformer? Answer: the transformer. That's why they do it.
(Even the CREE ultra-high output LEDs only sink 3V. That'd be 40. And they are not even remotely cheap.)
They have a transformer in them because they are d***ed cheap. A solid state (electronic) regulator is much more efficient, smaller, and lighter, but requires some engineering and a few pennies more to build.
All of them have some sort of power regualtor (transformer, transistors, etc.) that will generate heat in the process. You cannot put 120V (AC or DC) right into an LED. (not for long...)
In a normal flight, the LEM doesn't come back to Earth. In this case, it was a lifeboat for the return to Earth. It was cut loose prior to reentry. The CM came back pretty much as normal from that point.
The LEM fell out of orbit -- uncontrolled re-entry. It did not survive intact. However, the SNAP-27 in one of it's payload modules most likely did, as it was designed to do so. The thing is, no one was paying close attention to the LEM as it de-orbited -- not that anyone could have spotted/followed the SNAP-27 in that mess.
Indeed, since their own HD channels are only 6Mb/s.