All,

I just "googled" for "benchmark performance linux kernel i386 versus
i686" and found nothing of any import. I am just wondering if anyone has
bothered doing this. It would be nice to know what the tradeoff is
between performance and convenience of not needing to know the CPU
architecture. Using multi-CD distros I would also choose the closest
matching kernel, but for my Ubuntu installs I haven't bothered.

Martin


  

Martin Visser, CISSP
Network and Security Consultant 
Consulting & Integration
Technology Solutions Group - HP Services

410 Concord Road
Rhodes NSW  2138
Australia 

Mobile: +61-411-254-513
Fax: +61-2-9022-1800     
E-mail: martin.visserAThp.com

This email (including any attachments) is intended only for the use of
the individual or entity named above and may contain information that is
confidential, proprietary or privileged. If you are not the intended
recipient, please notify HP immediately by return email and then delete
the email, destroy any printed copy and do not disclose or use the
information in it.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Matthew Palmer
Sent: Monday, 19 December 2005 11:57 AM
To: [email protected]
Subject: [SLUG] Re: pentium M series

On Mon, Dec 19, 2005 at 10:14:15AM +1100, ashley maher wrote:
> On Sat, 2005-12-17 at 12:54 +1100, Jeff Waugh wrote:
> > <quote who="ashley maher">
> > 
> > > TO my surprise Ubuntu chose to install the 386 series kernel.
> > 
> > Can't fit a lot of kernels on the CD, as well as a complete desktop.

> > :-)
> 
> is this an example of gnome bloat???

More kernel bloat.  Debian woody had most of the 4th CD taken up with
various kernels.  You can have a *lot* of variations in your kernel
config, it seems...

- Matt
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to