On Sat, 15 Jun 1996, Craig Sanders wrote: (clipped own stuff) > > (I'm thinking of the equiv. of "lilo (options) || echo Warning! blah > > blah") > > > > and/or could LILO be run in "verbose" mode? > > > > I suggest this because it would have saved me a lot of time.. > > > > In other words: (please idiot proof this for my benefit :) ) > > Before I switched to using the kernel package scripts I had my own > 'makelinux' and 'addlilo' scripts which performed a similar function. > > addlilo added an appropriate entry to the end of /etc/lilo.conf and then > ran: > > lilo -t && lilo > > i.e. 'lilo -t' tests the lilo config. if it's OK then lilo is run. > > maybe something like this (but expanded to provide useful warning/error > information) should be done in the debian kernel package script? > > Craig
After using "perforate" I wasn't sure so went to copy the kernel image around to unperforate it and was going to run lilo again. But, I accidentally deleted the kernel image. So I ran dpkg -i (the kernel image) and it finished without incident -- Lilo gave an error, but no being verbose, only said "OldLinux not found" and I assumed (<- the problem) that the found images were used, rebooted, then spent several hours trying to get a clean boot into the system so I could run lilo again. lilo -t && lilo wouldn't have helped (me anyway) I think -- if LILO fails it won't install an MBR anyway (as far as I know). It might give a more verbose error message, tho. [EMAIL PROTECTED] "The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language."
