Kernel Minimums

J. Greenlees jaqui at telus.net
Tue Dec 7 13:16:19 PST 2004



DHAJOGLO wrote:
> I am gathering from this discussion that a bare minimum is really in the eye of the beholder.  As Ken Moffat suggested it needs to be a bit more specific... do I want to be able to compile?  or will I compile on another machine and just install binaries.
> 
> 
>>But he doesn't want to compile software on the system, just run selected
>>packages.
>>
> 
> 
> I think for my purposes I will look at the minimum to build and install the kernel with a shell.  After that remove various packages to scale back to a bare bones.
> 
> I would prefer a box that I simply place software on... not build it on the running system.
> 
> 
>>Or, built LFS on one root partition, then use that to build just what he wants
>>into another root partition, using the books technique with chroot to test if
>>the minimal system actually runs. This has two advantages.
>>1) He only installs those packages that he wants, rather than trying to figure
>>out what to remove.
>>2) The build environment is a separate system from the target system. Once
>>he's finalised what the final system needs, he can tar it up, put it on CD
>>and install it onto other boxes fairly easily.
>>
>>I agree with Matt that the "From Powerup to Bash" Howto will be of great
>>assistance, but LFS is probably the best way to get there.
>>
> 
> 
> I have not yet had a chance to look at from powerup to bash so I look forward to that doc... thanks for the input.
> 

I seem to remember seeing somewhere it can be gotten down to somewhere 
in the area of 5 megs to run as a webserver.
just the binaries, no headers or build tools.
and probsbly only html with the server, no cgi. ( perl )






More information about the lfs-support mailing list