On Thu, 2 Oct 2003, Alan Yang wrote:
> Hello,
>
> I ran into a situation where I don't know how to break the catch-22 cycle.
> The scenario is like this:
> 0. from a DELL machine with scsi device
> 1. I installed the FreeSwan ipsec that seems like a rebuild of kernel is required
> so that
Alan Yang wrote:
so, I am stuck. what to do? I cannot reboot because it would panic
and if I do mkinitrd trying to make a valid img file that would also
fail due to the loop.o wasn't in the kernel that I booted from.
Boot the standard Red Hat kernel and then run mkinitrd.
jch
_
Hi,
Section 3.3 of the kernel HOWTO (http://www.tldp.org/HOWTO/Kernel-HOWTO/)
might be applicable to this situation.
Venkatesh
>
> I am still bit confused actually. So, I think these have to be done:
> 1. run 'make xconfig' to make sure the loopback support is selected
> as built in(not
I am still bit confused actually. So, I think these have to be done:
1. run 'make xconfig' to make sure the loopback support is selected
as built in(not module)
2. run 'make dep; make bzImage' to rebuild the kernel
3. copy the bzImage just built to /boot and make grub.conf to use
the ne
Alan Yang wrote:
Hello,
I ran into a situation where I don't know how to break the catch-22 cycle.
The scenario is like this:
0. from a DELL machine with scsi device
1. I installed the FreeSwan ipsec that seems like a rebuild of kernel is required
so that when insmod loads ipsec.o there wil
