Hi,
I was wondering if it's possible to compile the latest kernel, then take
the three files (bzImage, config and System.map) and copy them over to
the Slackware 10 CD1, in place of the originals in the kernels/bare.i
directory. Would that cause errors during install or it's something
normal to do...

If that's not how it's done, is there a way to update the default
install kernel on the CD - something like slipstreaming with SP2 a
Windows XP install Cd.

Thanks in advance!

On 2004-12-09, The Chief <chiefster@local.tribe> wrote:
> Hi,
> I was wondering if it's possible to compile the latest kernel, then take
> the three files (bzImage, config and System.map) and copy them over to
> the Slackware 10 CD1, in place of the originals in the kernels/bare.i
> directory. Would that cause errors during install or it's something
> normal to do...
>
> If that's not how it's done, is there a way to update the default
> install kernel on the CD - something like slipstreaming with SP2 a
> Windows XP install Cd.

I don't think you can overwrite a file already on a CD. If you have some HD
space, what you could do is copy the full CD to harddisk, overwrite the old
kernel with the new, blank the original source CD, then burn the full updated
image back to the recently blanked disk. It'd work, but it'll take some space
for temp. storage.

If it messes up because of the difference in names, just manually copy them
over later to /boot. Edit lilo.conf and rerun lilo and you should be all set.

Here's my lilo.conf, which uses a different kernel
name than the default:


# Lilo.conf
# Lilo is responsible for loading the OS from the disk by
# pulling it's kernel into memory
# This file can support many kernels

# -[Global variables]-----------------------------------------------
boot=/dev/hde
prompt
timeout=150
lba32
compact
vga=normal
root=/dev/hde1
read-only
menu-title="GNU/Linux Kernel Selection"


## -[Linux Kernals]----------------------------------------------------
##
## Note: Always refer to the kernels by their full names, not
## the symlinked name, which may get tangled up in an upgrade
## ex: vmlinuz-generic-2.6.9 instead of "vmlinuz"

# A 2.4 series, 2.4.28 kernel
image=/boot/bzImage-2.4.28
label=Kernel-2.4.28

# With an initrd used:
# initrd = /boot/initrd.gz



--
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Thanks for the input, jayjwa.

That's exactly what I meant. I was wondering if I open the the
slack-10.iso file and replace the "original" (2.4.26 i think) kernel and
put the newest (compiled beforehand) bzImage, System.map and config and
also replace the "original" kernel source with the newest one, would
that work? And I mean, if I am to do a clean install, am I gonna be
running the new kernel or the way the installation script is written,
I'll have to edit something else to get it working?

P.S. Sorry for being unclear, I meant to replace the files beforehand in
the ISO file and then burn them to a new CD, not overwrite them.

> I don't think you can overwrite a file already on a CD. If you have some HD
> space, what you could do is copy the full CD to harddisk, overwrite the old
> kernel with the new, blank the original source CD, then burn the full updated
> image back to the recently blanked disk. It'd work, but it'll take some space
> for temp. storage.
>
> If it messes up because of the difference in names, just manually copy them
> over later to /boot. Edit lilo.conf and rerun lilo and you should be all set.
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please do not top-post. Thank you.
- The Management

In alt.os.linux.slackware, The Chief dared to utter,
> I was wondering if I open the the
> slack-10.iso file and replace the "original" (2.4.26 i think) kernel and
> put the newest (compiled beforehand) bzImage, System.map and config and
> also replace the "original" kernel source with the newest one, would
> that work?

In theory yes, but in actuallity no. Linux does not include write
support for the iso9660 filesystem[0]. Your basic principles though are
fairly sound. I had to do something similar yesterday to install
Slackware on a new server we just put together that has a Serial ATA
hard drive[1].

I grabbed the slackware-current/kernels/sata.i directory from a mirror
and copied it into slackware-10.0/kernels/ on my source tree for
Slackware, then modified isolinux/isolinux.cfg an iso per Pat's
instructions in isolinux/README[2]. Burned the disk and everything
worked out just fine.

> And I mean, if I am to do a clean install, am I gonna be
> running the new kernel or the way the installation script is written,
> I'll have to edit something else to get it working?

After package installation the installer asks you what kernel you wish
to use. Simply choose the one you used to boot the installer.

[0] This is why tools like mkisofs are required.
[1] Now that I've actually done this it seems that the advice I gave
for doing it long long ago was sound. Point for me! ;^)
[2] Not exactly, I left out gnome, kde, kdei, x, and xap and the iso
was still bigger than I wanted it, so I left out the e series and cut
the bloat in half. Who uses emacs anyway? :^)[3]
[3] Lookie here! I actually did footnotes and remembered to include all
of them!

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBuxZllKR45I6cfKARAn0SAKCXRSdGGVrMgNj/ar1fbDdgoQgiWACbBudc
2Noctd9RY0DLSPi9pdDL3+A=
=//GS
-----END PGP SIGNATURE-----