On Wednesday 19 December 2001 4:34, James A Sutherland wrote:
> Initramfs will do this, it seems. Alternatively, you might have to copy
> some files into a tarball - oh, the stress! Oh, wait - you just compiled
> 100+Mb of C source to make that kernel and the modules. Somehow, making a
> tarball out of the modules doesn't seem too stressful to me.
Do it for 15 production systems, each with varying hardware.
Now do it again for kernel revision 2. Now again for rev 3. Now
again for rev 1 of 2.4.17...
OR
List the names of the modules for boot ONCE in the systems 'grub.conf'
file, and just create a 'current' symlink each time you install
a new kernel and modules. A simple user land util can parge depmod to
give you to right order...no bloat needed.
FYI I only ned create a 'vmlinuz' for new kernel install as it is.
If I could do the same for modules, I wouldn't have a 1.3MB
'catch all' bzImage.
> OK, make the conf file a shell script which copies the modules into a
> tarball or initrd image.
Oh that's nice, clean, and standardized! Again do it for 15 machines...
Many of you people spouting about 'kernel design' really need to get
a clue about putting these things into real world practise, across
mutiple machines, that must stay running...
-- The time is now 22:54 (Totalitarian) - http://www.ccops.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:28 EST