it flashed the kernel no problem. when it said "format hard drive" I hit CTRL-C, no effect, so then I typed N and hit return, and it proceeded to format the hard drive. ARRRGHHH!
sigh.
Full Version: Install Bug In Cortez's Updater.sh
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Android
so, I'm setting up dual booting, but didn't get it quite right, and needed to put the sharp kernel back. I used cortez's updater.sh, put the zImage.bin onto the memory card with it, and kicked it off*
it flashed the kernel no problem. when it said "format hard drive" I hit CTRL-C, no effect, so then I typed N and hit return, and it proceeded to format the hard drive. ARRRGHHH!
sigh.
it flashed the kernel no problem. when it said "format hard drive" I hit CTRL-C, no effect, so then I typed N and hit return, and it proceeded to format the hard drive. ARRRGHHH!
sigh.
damn, it didn't just format it, it repartitioned the hard drive too!
Ouch. I hope you have backups and/or nothing important on your hard drive.
QUOTE(Capn_Fish @ Apr 10 2008, 09:12 PM) 
Ouch. I hope you have backups and/or nothing important on your hard drive.
fortunately, nothing too important as I'd flattened it when installing cortez's android.
it's kind of funny, really, as I'd installed cacko with katastrphos kernel + new modules + kat's WM sound driver and got it just right. then I'd partitioned the microdrive, formatted it, copied on all the debian files, added the new kernel, copied over kat's sharp kernel, put a few scripts in place, and then installed the yonggun kernel, and so was on the very last stage to have dual booting ready. booted the new yonggun kernel but it wouldn't mount the hard drive 'cos I'd forgotten to put journalling on, so I had to restore sharp kernel to boot cacko to turn on journalling. So, I was at the very very last step when I wiped out the entire debian install
QUOTE(speculatrix @ Apr 10 2008, 11:07 PM)
QUOTE(Capn_Fish @ Apr 10 2008, 09:12 PM)
Ouch. I hope you have backups and/or nothing important on your hard drive.
fortunately, nothing too important as I'd flattened it when installing cortez's android.
it's kind of funny, really, as I'd installed cacko with katastrphos kernel + new modules + kat's WM sound driver and got it just right. then I'd partitioned the microdrive, formatted it, copied on all the debian files, added the new kernel, copied over kat's sharp kernel, put a few scripts in place, and then installed the yonggun kernel, and so was on the very last stage to have dual booting ready. booted the new yonggun kernel but it wouldn't mount the hard drive 'cos I'd forgotten to put journalling on, so I had to restore sharp kernel to boot cacko to turn on journalling. So, I was at the very very last step when I wiped out the entire debian install
The installer asks whether or not you would like to format the internal drive. Only 'y', 'n' and the Enter key are accepted as input. The Enter key accepts the default, in the case of disk formatting this is (unfortunately for you) 'y'. I guess pressing Ctrl+C contains the Enter-keycode? Or did you press Enter after the Ctrl+C? Anyhow, you haven't convince me that this is a bug
. I could of course set the default to 'n', just to prevent any more harm.
QUOTE(cortez @ Apr 11 2008, 08:07 AM)
The installer asks whether or not you would like to format the internal drive. Only 'y', 'n' and the Enter key are accepted as input. The Enter key accepts the default, in the case of disk formatting this is (unfortunately for you) 'y'. I guess pressing Ctrl+C contains the Enter-keycode? Or did you press Enter after the Ctrl+C? Anyhow, you haven't convince me that this is a bug . I could of course set the default to 'n', just to prevent any more harm.
. I could of course set the default to 'n', just to prevent any more harm.er, I think any program feature which will let a user completely destroy the contents of the computer as the default action is a bug, not a feature.
I would change it so that you have to type, literally, YES to get it to wipe the microdrive. It's not as if someone can't reboot and re-run the tool if they later decide they did want to wipe everything!
anyway, that's only my humble opinion.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.