|
For everyone's enjoyment and since I haven't been to an NLUG meeting
in about 10 years, I thought I would dig into my personal NLUG
archive and randomly forward a message to the list from back in our
first year. That was 1997. Telalink hosted the NLUG list. We met at
Vanderbilt. Slackware or Red Hat were the distributions of choice
among the LUG. Here is a message about compiling
a kernel with 96MB of RAM (back when that was a lot).
Gibson -------- Original Message --------
If you compiled the kernel you can replace it with the copy in the source tree. You can also replace it with the uncompressed version. Your running kernel is likely /vmlinuz. The other versions are in /usr/src/linux/arch/i386/boot/zImage and /usr/src/linux/arch/i386/boot/compressed/vmlinux Replace the kernel then redo lilo. If you need to boot the machine, you can use the slackware boot disk. You can use the mount image to boot and mount your root partition: mount root=/dev/hda1 (or your root partition) Before you waste your time copying the compressed kernel, you should do a diff and make sure they are different. Finally there are several things you can do without reinstalling. If you are sure that you have not messed up your filesystem beyond repair, then should be able to replace your kernel with the slackware boot kernel, or a new kernel that you compile. --Adam. > -----Original Message----- > From: Dagmar d'Surreal [SMTP:[email protected]] > Sent: Tuesday, November 25, 1997 1:53 PM > To: diana > Cc: [email protected] > Subject: Re: [NLUG] Slackware 3.3 crc error > > On Mon, 24 Nov 1997, diana wrote: > > > Hey, guys, > > > > Loaded clean Slackware 3.3 install from cd, restarted, got error ... > > > > LILO Loading Linux > > Uncompressing Linux > > > > crc error > > > > -- System halted > > > > Running on Intel 166 MMX, VXPro chipset motherboard, 98 megs RAM, 1.2 gig > > hard drive. > > > > What does this mean? How can I correct it? > > 1. Umm... I'm fairly sure that's a typo. No one makes motherboards > that run 98 Mb of RAM. 96Mb would be fairly unlikely as well, but at > least it would be possible. In any case, it's just a nitpick and > unrelated to the actual problem. > > 2. It means the kernel on the disk is corrupted (or nonexistant). You > will need to reinstall or boot from a bootdisk, mount the root > filesystem and check to make sure LILO is trying to boot the proper > partition. For newbies, it's probably simpler to just reinstall. > > ---------------------------------------------------------------------- > ---- > Dagmar the Surreal <[email protected]> Freelance Internet > Guru > Finger for PGP key "...preserving bandwidth by killing Windows > boxes." > > > > ================================================================= > To unsubscribe, send mail to <[email protected]> > with "unsubscribe" in the body of the message. ================================================================= To unsubscribe, send mail to <[email protected]> with "unsubscribe" in the body of the message. -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. |
