Manoj Srivastava wrote:
> The new warning reads:
> ==
> As a reminder, in order to configure lilo, you need to
> add an 'initrd=/initrd.img' to the image=/vmlinuz
> stanza of your /etc/lilo.conf
> ==
>>"Bill" == Bill Moseley <[EMAIL PROTECTED]> writes:
Bill> I think those are clear, now that the parts are making more
Bill> sense to me. It might be helpful to show the lilo line in the
Bill> first message box,
Well, the first message is spit out before we have determined
what boot
>>"Stan" == Stan Kaufman <[EMAIL PROTECTED]> writes:
Stan> This was good; it pointed out which RTFM was germane. A note
Stan> that the new 2.4.x kernel images use initrd whereas the 2.2.x
Stan> kernels didn't would help those of us who don't follow kernel
Stan> development realize that there's
"Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
>>> "Stan" == Stan Kaufman <[EMAIL PROTECTED]> writes:
Manoj> Any suggestions for improved wording? This is what is
Manoj> there now:
>> ==
>>
Manoj Srivastava wrote:
> Any suggestions for improved wording? This is what is there now:
> ==
> You are attempting to install an initrd kernel image (version $version)
> This will not work unless you have configured your
At 12:21 AM 02/28/02 -0600, Manoj Srivastava wrote:
> Any suggestions for improved wording? This is what is there now:
>==
>You are attempting to install an initrd kernel image (version $version)
>This will not work unless yo
>>"Stan" == Stan Kaufman <[EMAIL PROTECTED]> writes:
Stan> Should be enough; the package maintainer's scripts clearly said
Stan> "Don't go any further until you've fixed your bootloader". It
Stan> would have been more helpful if there had been more explicit
Stan> info about how to do so, but t
"Bill Moseley" <[EMAIL PROTECTED]> writes:
> At 12:04 PM 02/27/02 -0800, Stan Kaufman wrote:
> >I just installed 2.4.17 on a new woody box, which involved an
> >upgrade from the 2.2.14 potato system my floppy install disks
> >created. The kernel-image package provided clear notice during
> >install
At 12:04 PM 02/27/02 -0800, Stan Kaufman wrote:
>I just installed 2.4.17 on a new woody box, which involved an upgrade from the
>2.2.14 potato system my floppy install disks created. The kernel-image package
>provided clear notice during installation that the bootloader needs to be
>altered
>in or
#include
Bill Moseley wrote on Wed Feb 27, 2002 um 06:41:05AM:
> So, I'd like to avoid the kernel panic this time with the
> kernel-image-2.4.17-k7 package. What steps do I need to take to make sure
> I will end up with a bootable image? Someone mentioned that moving to the
> more modular 2.4 k
On Wed, 27 Feb 2002, Stan Kaufman wrote:
> Faheem Mitha wrote:
>
> > On 27 Feb 2002, Bill Moseley wrote:
> >
> > > So, I'd like to avoid the kernel panic this time with the
> > > kernel-image-2.4.17-k7 package. What steps do I need to take to make sure
> > > I will end up with a bootable image?
Faheem Mitha wrote:
> On 27 Feb 2002, Bill Moseley wrote:
>
> > So, I'd like to avoid the kernel panic this time with the
> > kernel-image-2.4.17-k7 package. What steps do I need to take to make sure
> > I will end up with a bootable image? Someone mentioned that moving to the
> > more modular 2
On 27 Feb 2002, Bill Moseley wrote:
> I had started the process of building a kernel yesterday before being so
> rudely interrupted by sleep.
>
> I'm currently running 2.2.20 but upgrading to 2.4.17. I had tried once
> before to use a kernel-image, but ended up with a kernel-panic that I never
I had started the process of building a kernel yesterday before being so
rudely interrupted by sleep.
I'm currently running 2.2.20 but upgrading to 2.4.17. I had tried once
before to use a kernel-image, but ended up with a kernel-panic that I never
followed up on. This system was installed Woody
14 matches
Mail list logo
