Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote in
news:c53t65$jrp$1@news.tudelft.nl:
<<snip>>
> In "adaptec.s" you'll see:
> bzImage copy this to /mnt/boot/vmlinuz
> config " /mnt/boot/config
> System.map.gz " /mnt/boot/System.map.gz
> you may want to decompress the latter, but I'm not sure if that is
> needed.

Wow! I was actually going to try something _that crazy_! It
actually works -Thank you! I bet if I tried that on Debian, dpkg
would blow a gasket ;-)
It was not neccessary to expand System.map.gz. I had renamed
all files that were initially in /boot before I copied the files
from /adaptec.s. Amazing.

>
> Now finally run "lilo -r /mnt" (assuming you use lilo and its config
> points to "/boot/vmlinuz"), or whatver you have to do to get grub
> working ON that "just copied" vmlinuz file.
>
> And, of course, after you booted up, you probably want to make your
> own scsi kernel, with just the drivers you really need "built-in"
> and not ALL Adaptec ones, like this one is.
> So make sure that you install the kernel-sources package too, and
> use the just copied "config" as a start TO make your own...

Hmm... After I got the system to boot, and played around a bit,
I copied linux 2.4.25 source (.bz2 I think) to /usr/src, and made the
kernel the same way I did for the Debian install (but of course without the
Debian tools), being careful to include
my scsi controllers' kernel support. The new kernel booted (was found by
GRUB since I used the same names for everything), but it panicked again-
this time after trying to load something about "../modules(?)" (sorry for
slim info). But I disallowed the modular function of the kernel at compile
time! I am sure that all the options I selected were "built-in".
There must be a little *modules daemon* hanging around demanding his
modules?!?
(BTW, the kernel source I used was not "Debianized"- it came from
kernel.org). Hmm... maybe I'll try copying /boot from the Debian partition
to /boot on Slack :P
Confused again, but many Thanks for the great info!