On Tue, 24 Apr 2001, Mike Sensney wrote:
> >Okay. I got the basic-level kernel compiled. Here's what we have:
> >
> >-rw-r--r-- 1 wolfstar root 470k Apr 23 16:14 kernel.standard
> >-rw-r--r-- 1 wolfstar root 404k Apr 23 16:15 kernel.upx
> >
> >Before we get too excited, I'm stating for the record that there is next
> >to NOTHING in this kernel. What's been pulled:
> >
> >This is strictly for a eth-to-eth router. I plan on doing more with it in
> >the near future, and looking to see what I can put back in. This does have
> >IPChains and IPTables support; both are modularized.
> >
> >Thoughts? Questions?
>
> Would it possible to create a "base" .config then create a series of patch
> files to modify the .config file? Would this be manageable or would it be a
> can of worms best not visited?
It's easily possible, yes. The only problem I see is that there may be
issues where it's best left to the person building the kernel to go in and
verify by hand. For example, if you've got a system with two SCSI CD-ROM
drives, and you want to use both for data in a thin-server mode of
operation, then you want the SCSI CD-ROM to be modular. The alternative
is, if you've got only one, your best bet may be compiled in. Things like
that get tough to handle.
> I was thinking of a script, call it LRPkernel that first copies a base
> .config to /usr/src/linux, then applies the patches listed on the command
> line. It would look something like:
> LRPkernel IDE IPSEC PPORT <etc.>
> Then compile the kernel as usual.
Ouch. That is a LOT of grunt work to get the various different configs
done. It MIGHT be easier if the parameters offered on the command line did
something like the following. (I'd like to note for the record that I
almost was able to come up with the script commands here, but not quite.
I'm getting there!)
If $OPT = IDE, then 'cat .config | grep CONFIG_IDE' and somehow (sed?) set
CONFIG_IDE=y(or m, as the case may be).
It'd be a lot easier - and smaller - than patching the .config file from
dozens of separate .config files. This IS doable, but it's just a wee bit
beyond me, for the moment. I've already set up a script to build the
kernel after I've configured it, copy the new kernel to the installed
modules directory along with UPX, compress the kernel, remove UPX, tar up
everything, and copy it to my Sourceforge directory on localdisk. What
you're suggesting would work excellently at the beginning of this script,
assuming I can figure out how to do it.
> I'm not familiar enough with the diff and patch programs to know what
> happens if different patches end up contradicting each other...
Usually, in the case of an "Expected condition not found", the patch
fails. That's another reason why patching would be tough to implement,
whereas kernel parameters being edited by a build script wouldn't be, or
at least not AS tough.
--
George Metz
Commercial Routing Engineer
[EMAIL PROTECTED]
"We know what deterrence was with 'mutually assured destruction' during
the Cold War. But what is deterrence in information warfare?" -- Brigadier
General Douglas Richardson, USAF, Commander - Space Warfare Center
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
