Re: Etherboot and gpxe

Joyce Yu wrote:
> 
> I think the gPXE rom image is too large.

So fix it.

> I just compiled the e1000 
> driver. Here is the different between gPXE and etherboot:
> 
> gPXE:
> ls -l bin/e1000-0x1079.rom
> -rw-r--r--  1 joyce wheel 71680 Aug  6  2009 bin/e1000-0x1079.rom
> 
> etherboot:
> ls -l bin/e1000-82546gb-copper.zrom
> -rw-r--r--  1 joyce wheel 27136 Aug  6  2009 bin/e1000-82546gb-copper.zrom

> It is about 44k more in gPXE. For x86 system with only 128k option RAM, 
> it is really too much.

It's not really that hard to fix.  You just don't have the skill, so 
you're whining and complaining, as usual.

I could make for you, or show you how to make a much smaller .rom image 
for that particular card, but what motivation do I have?

You need to learn better manners if you want free help.

Rather than just point out problems, admit that you don't have the skill 
to fix the problem and _ask for help_.

Try "I need to generate a much smaller .rom image for an e1000 variant 
using gPXE.  Can anyone help me figure out how I might do this?"

What you do is say "gPXE makes rom images that are too big.  I can't use 
them."

My response is: "So, what do you want me to do about it?  Why should I 
help you?  They work fine for lots of other people, and all you do is 
whine all the time."

You probably won't understand this message, but I figure other people 
might get it, so I'll send it anyway.  Honestly, Joyce, you really don't 
know how annoying your constant whining about stuff you don't like is. 
Try being a little more polite, and maybe people will be more inclined 
to help you.

Marty

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july