public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Rick Warner <rick@microway.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: zImage on 2.6?
Date: Tue, 3 May 2005 18:23:28 -0400	[thread overview]
Message-ID: <20050503222328.GE12199@animx.eu.org> (raw)
In-Reply-To: <200505031742.40554.rick@microway.com>

Rick Warner wrote:
> On Tuesday 03 May 2005 12:40 pm, Wakko Warner wrote:
> > Please keep me CCd

> As others have mentioned, bzImage seems to be a requirement now for x86.  
> However, zImage will not do any better for you.  I recall doing testing of 
> zImage vs bzImage a long time back, and the bzImage kernels were slightly 
> smaller than the zImage ones anyway.  I think you're going to be out of luck 
> trying to get your kernel that small.  A single floppy boot/root disk isn't 
> really possible with 2.6 kernels anymore.  Have you looked into pxe booting 
> instead?  I work at a cluster company and we do tons of pxe/network booting 
> stuff.

Not all machines are PXE capable.  The boot will be generally CDrom or USB
stick.  I wanted to continue to support our machines that are not capable of
booting from either of these (which all of these are not PXE capable)

I might beable to pull this off, I don't know yet.  If it wasn't for all the
modules I have placed in the initrd, I could.  (I could remove one of the
modules and it would fit just fine but I might actually need that module)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-05-03 22:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03  1:29 zImage on 2.6? Wakko Warner
2005-05-03  2:35 ` Randy.Dunlap
2005-05-03 10:45   ` Wakko Warner
2005-05-03 14:26     ` Randy.Dunlap
2005-05-03 16:33       ` Wakko Warner
2005-05-03 16:59         ` Randy.Dunlap
2005-05-03 22:19           ` Wakko Warner
2005-05-03 22:27             ` segin
2005-05-03 22:31               ` Wakko Warner
2005-05-03 23:15                 ` segin
2005-05-04  0:28                 ` shogunx
2005-05-04  1:29                   ` Wakko Warner
2005-07-12  4:55                   ` H. Peter Anvin
2005-05-03 22:37             ` Randy.Dunlap
2005-05-03 23:05               ` Wakko Warner
2005-05-03 23:16                 ` Randy.Dunlap
2005-07-12  4:54           ` H. Peter Anvin
2005-05-03 18:28     ` Krzysztof Halasa
2005-07-12  4:58       ` H. Peter Anvin
2005-05-03 16:06 ` Rick Warner
2005-05-03 16:40   ` Wakko Warner
2005-05-03 18:01     ` Lennart Sorensen
2005-05-03 18:44     ` Brian Gerst
2005-05-03 22:20       ` Wakko Warner
2005-05-03 21:42     ` Rick Warner
2005-05-03 22:23       ` Wakko Warner [this message]
2005-07-12  5:00         ` H. Peter Anvin
2005-05-04 13:50 ` Wakko Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050503222328.GE12199@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick@microway.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox