Albert wrote:

[kernel-size]
> Mine (iee1394, usb) is

> 2411873 : kernel-2.6.10-gentoo-r4
> 1272222 : initrd-2.6.10-gentoo-r4

Handmade kernel (no genkernel -> no initrd )

roland@merlin boot $ ls -l *`uname -r`*
-rw-r--r-- 1 root root 1167199 17. Nov 11:20 kernel-2.4.26-gentoo-r10
-rw-r--r-- 1 root root 630697 17. Nov 11:19
System.map-2.4.26-gentoo-r10

here on my laptop

Roland

On 2005-02-18, Johan Lindquist <spam@smilfinken.net> wrote:
>
> By "installing" you refer to configuring lilo or grub, I guess? If
> someone always uses the same name for the images (perhaps renaming the
> current one to foo.old would be a part of the shell script in that
> case), the "installation" part would indeed be the copying.
>


Hmmm, is this really true, I don't think so ?? apart from the
really bad idea of just overwriting the existing kernel, I think
it's necessary to rerun lilo even if the kernel name is the same.

/klacke

--
Claes Wikstrom -- Caps lock is nowhere and
http://www.hyber.org -- everything is under control

Roland Schulte-Osthoff wrote:
>
> Handmade kernel (no genkernel -> no initrd )
>
> roland@merlin boot $ ls -l *`uname -r`*
> -rw-r--r-- 1 root root 1167199 17. Nov 11:20 kernel-2.4.26-gentoo-r10

Handmade kernel here too:

ben@phoenix ben $ ls -l /boot/linux-`uname -r`/bzImage
-rw-r--r-- 1 root root 1256303 Jan 17 16:47
/boot/linux-2.6.10-gentoo-r5/bzImage

Small, and fast to boot (pun intended :P )

--
Ben M.

Claes Wikstrom wrote:
>
> [snip] apart from the really bad idea of just overwriting the
> existing kernel [snip]

Awww, live a little

--
Ben M.

Andy Fraser wrote:
> oldNbald wrote:
>
>> Think I'll relax a bit - stop worrying about having it _perfect_ the
>> first go around - and pick my through.
>
> The beauty of compiling a kernel with only the things you need is it
> only takes 5 - 10 mins (depending on your hardware) to compile so if you
> mess up you're not going to have to wait ages to compile in what you
> missed. :-)

What's more, recompiling a 2.6 kernel will only compile the changes.
Forget to configure cdrom support? Nevermind, it's only a 30s compile *g* .

--
Ben M.

So anyway, it was like, 15:21 CET Feb 18 2005, you know? Oh, and, yeah,
Claes Wikstrom was all like, "Dude,
> On 2005-02-18, Johan Lindquist <spam@smilfinken.net> wrote:

>> By "installing" you refer to configuring lilo or grub, I guess? If
>> someone always uses the same name for the images (perhaps renaming
>> the current one to foo.old would be a part of the shell script in
>> that case), the "installation" part would indeed be the copying.
>
> Hmmm, is this really true, I don't think so ??

I've been using grub so long, I temporarily forgot how lilo works, but
I've already pointed that out once in this thread.

> apart from the really bad idea of just overwriting the existing
> kernel,

Please refer to the parentesised part above. Thanks.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
16:50:31 up 117 days, 5:17, 4 users, load average: 0.18, 0.06, 0.01
Linux 2.6.9 x86_64 GNU/Linux Registered Linux user #261729

Ben Measures wrote:

>> The beauty of compiling a kernel with only the things you need is it
>> only takes 5 - 10 mins (depending on your hardware) to compile so if
>> you mess up you're not going to have to wait ages to compile in what
>> you missed. :-)
>
>
> What's more, recompiling a 2.6 kernel will only compile the changes.
> Forget to configure cdrom support? Nevermind, it's only a 30s compile *g* .

That's if you don't run "make clean" or "make mrproper" right? For some
reason I don't trust the compile process if I don't at least run "make
clean" first (I've been bitten by my own projects) but that's probably
just me. :-)

--
Andy.