Well, things went OK I guess..... but still a couple of doubts.
The compile produced a bzImage instead of a vmlinux. Should there be a size difference of close to 50%. Would I assume that bzImage is compressed and vmLinux is not. bzImage is about 1.7M and and vmlinux is about 3.1M.
But where there's a big difference is in the moudels. For instance,the compile produced a lower quantity of modules, which could be because the .config for Slackware specifies more modules. I tried not to change the "stock" configuration much, modifying just a little bit more than I needed for the serial part.
But the big difference seems to be in the size of the module files. Here's an example:
/lib/modules/2.6.13/kernel/drivers/acpi ( an area that I didn't touch )
Quote:
module compiled size Slack size
ac.ko-------------96.2K---------5K
asus_acpi.ko-----151.9K--------18K
battery.ko-------119.7K--------10K
button.ko--------104.0K---------7K
ibm_acpi.ko------170.0K--------20K
toshiba_acpi.ko--104.10K--------7K
container.ko----- -- ----------YES ( didn't note the size)
fan.ko----------- -- ----------YES ( didn't exist in the compile)
processor.ko ---- -- ----------YES
thermal.ko------- -- ----------YES
video.ko--------- -- ----------YES
|
From container on there were no modules in the compile.
Perhaps I should do it all over, now that I've got the hang of it, unless you can tell me that this isn't all that strange. I hadn't made any efforts to remove pieces that I thought I wouldn't be using, which I do this time around. Maybe I can use my present .config as a reference as well.
The other thing. The whole modules tarball weighs about 150M and I only have 65M left on the host CPU. I wanted to see if I could just copy the new modules.
Dave