On Thu, 9 May 2002, Ashwin Mansinghka wrote:
> Hi Robert,
>
> On Thu, 9 May 2002, Robert wrote:
>
> > Hey again Ashwin...
>
> --- Snip
> >
> > #!I hope the above generally covers what I might be coming
> > #!across. Is there a simple way to do this downgrade to i386
> > #!(kernel compilation and glibc
> > #!support) ?
> >
> > Like I said, in the kernel parameters, the processor-specific sections
> > have various processor types setup for kernel optimizations. You should
> > be able to simply go with lowest-common denominator (ie: i386 support
> > only) and recompile it. It should then revert to a kernel that will run
> > on any basic Intel platform. However, it's not the kernel that's truly
> > a problem here, as I can see. More than likely, you'll run into many HW
> > compatibility issues (especially that vid card one) as you hop from
> > machine to machine. Deal with that one first, as suggested, and I'm
> > pretty sure the rest will follow.
> >
>
> I was wondering if I can just use the RPMS with simple "rpm" commands and
> pass some command line flags and recomplie a kernel make a image (the
> basic i386) and install and configure lilo and fix the hard disk on a
> machine (with 386 chip) lying with the sysadmin stores do the basic test
> here that lose face at the customer premises.
>
> I am looking for the rpm way as in case of goof ups I can atleast use the
> rpm again and restore whatever I had. I already have too much in my
> hardisk to loose. Moreover I do not have much time too.
>
> Looking forward to some suggestions again.
>
> Thanks for the clarity provided.
Here's a possible procedure which others can object to if they see
something that won't do what you want:
Get kernel-2.4.9-31.i386.rpm from, for example,
ftp://updates.redhat.com/7.2/en/os/i386/ and install with
rpm -ivh kernel-2.4.9-31.i386.rpm
If you really do use lilo, modify /etc/lilo.conf to add the new kernel
as a boot choice, using the other choices as a model for the lines you
add. If there are initrd... lines for the kernels in lilo.conf, you
should use the mkinitrd command to make another initrd*.img file in /boot.
To make the new kernel default, the new, unique label you give it should
be in the default=... line. Then run lilo, and you'll be ready to boot.
You won't have to recompile anything, and the old kernel will still be
available to boot from if you want. But maybe you use grub, not lilo.
If you use grub, modify /boot/grub/grub.conf to add the new kernel as
a boot choice, using the other choices as a model for the lines you add.
Put the set of lines for the new kernel before the other choices in order
to make the new kernel be the default. You still will be able to choose
one of the others if necessary. If there are initrd ... lines for the
kernels shown in grub.conf, you should use the mkinitrd command to make
another initrd*.img file in /boot. You should then be able to boot your
machine to test that everything works with the new kernel.
The Redhat kernel binaries are intended to be generic; so you can
expect it to work on the other machines you use. And the old kernels will
still be available -- you won't have to use rpm again to get them back.
Since the mkinitrd command uses /etc/modules.conf, which refers to
equipment on your machine, the first time you boot on another machine some
things may not work. But maybe you won't need them anyway (like
ethernet), and if you do, you can change modules.conf and run mkinitrd
again.
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
