kernel presentation at ILUG on Sat.

[admin at kclinux.net]

I don't see why not.  I've heard you can get linux to boot off of a USB 32MB
(or higher) memory stick.  (Something I plan on trying as soon as I can find
some information.  I got Windows 98 to work *don't ask* but haven't been
able to get Linux to boot.)  With this technology coming out, I have a
feeling floppies will be obsolete in the not-so-far future.

-----Original Message-----
From: owner-kclug at marauder.illiana.net
[mailto:owner-kclug at marauder.illiana.net] On Behalf Of James Sissel
Sent: Monday, May 05, 2003 12:20 PM
To: kclug at kclug.org
Subject: RE: kernel presentation at ILUG on Sat.

Or maybe a better question is do we really need to compress the kernel
anymore?  With 80G hard drives the norm today do we really need to save
space?

-----Original Message-----
From: James Colannino [mailto:email2jamez at covad.net]
Sent: Monday, May 05, 2003 11:56 AM
To: kclug at kclug.org
Subject: Re: kernel presentation at ILUG on Sat.

> It depends on what make target you specified when you built your 
> kernel. I always use "make dep && make clean bzImage modules 
> modules_install". This creates a bzip2'd kernel. IIRC, the grub/lilo 
> boot loader does the uncompressing so if you use bzip2, you need a 
> boot loader that supports it. 

Oh ok.  That clears up a lot.  I was under the impression that it was 
the kernel itself that was doing the uncompressing.  So how exactly is 
the kernel itself (uncompressed) constructed?  I assume many different C 
programs are being mashed together into one giant binary, or is the 
image comprised of many binary files which are simply read into memory 
consecutively to form one large runtime monolithic kernel?

James


This transmission (and any information attached to it) may be confidential
and is intended solely for the use of the individual or entity to which it
is addressed. If you are not the intended recipient or the person
responsible for delivering the transmission to the intended recipient, be
advised that you have received this transmission in error and that any use,
dissemination, forwarding, printing, or copying of this information is
strictly prohibited. If you have received this transmission in error, please
immediately notify LabOne at the following email address:
securityincidentreporting at labone.com