Quote:
Yeah. I'd love to hit that option accidentally.
Clearly it could be designed so that accidental keypresses can't cause it to happen.
Quote:
t's only ever going to be called once per drive and the rest of the time it'll be taking up memory which could be put to better use.
If it didn't take up *that* much memory, the convenience would be worth it. Assuming that one already had Hijack installed, then there's no need for any special kernels, the instructions would be simplified, it would be reliable and universal. Heck, if it could create the necessary folders, you might even be able to add a second slave disk drive in the field without needing a serial connection or even a PC at all. For someone doing a big upgrade that involved swapping a lot of disks back and forth, it might save them a lot of time and effort.
I agree that if the code is huge, then it belongs in a special kernel.