Bob George wrote: > > [...] but as I said, maybe you clipped it, all I hadda do was run sys.com > > to get it to boot. I dont think it is that simple with linux. > > In both cases, it depends on what was wrong. Just "getting it running" > temporarily with sys (DOS), or by redoing LILO (linux) may or may not be a > real fix. In my experience Bob, using sys.com was not temporary. By all accounts the dos kernel is not well protected. Linux is. I do recall some few times when some app trashed the boot, but when that happened, sys was all that was needed. If the crash was due to a hardware problem, or an incorrect cmos setting, the mess could be considerable. But nowadays, leaving the cmos on auto prevents the latter.
With the former, well I usta run whatever I could lay my hands on, but since hard drive prices have dropped so dramatically, I've been able to run more reliable drives, and retire any with hot chips, vibration, or whatever, so I aint seen dos trash a drive since. Even bleeding edge hardware is loafing with dos these days. I even ran across GRUB someplace to replace a blown lilo and got the dos partition running on a drive that wont boot the distro. It rather looks like because the Linux kernel is more protected, when it is blown, it is blown further. To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
