I rather like this idea. Might be a pipe dream, but would be nice.
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Tue, 24 Apr 2001, Mike Sensney wrote:
> At 09:34 PM 04/23/2001 -0400, George Metz 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:
> >
> >Loopback/Network block device support
> >IDE and SCSI support
> >Hot-pluggable device support
> >Watchdog timer support
> >Token-Ring support
> >TOS-Routing
> >A few other random goodies.
> >
> >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?
>
> 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.
>
> I'm not familiar enough with the diff and patch programs to know what
> happens
> if different patches end up contradicting each other...
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
