Juanito


Group: Members
Posts: 1601
Joined: Sep. 2005 |
 |
Posted: Mar. 25 2008,07:21 |
 |
I made a dumb mistake the other day - I added a task to bootlocal.sh with no definate end that was not backgrounded and thus the boot sequence could not complete.
As far as I could tell, the only way to get out of the situation was by using <ctrl-alt-del> which shut down the machine.
All that needed doing to fix the problem was to comment out one line in bootlocal.sh, but...
1. On a frugal-hd-lilo install, I cannot enter "base norestore" at the prompt (because there isn't one) so I was stuck in the loop. 2. After a floppy "fromusb" boot I edited bootlocal.sh in backup.tar.gz using emelFM, but this caused the file to be unreadable on the next frugal-hd-lilo boot 3. After another floppy "fromusb" boot I moved backup.tar.gz, effectively creating a "norestore" situation on the next frugal-hd-lilo boot, but then after manually unpacking and copying a bunch of files from backup.tar.gz I of course missed some...
Apart from not making dumb mistakes in the first place, there has to be a better/smarter/easier way to fix this kind of error - any suggestions for next time would be gratefully received 
[NB: frugal-hd-lilo boot = 5mins, floppy "fromusb" boot = 10mins on this machine]
|