On Fri, 27 Apr 2001, Mike Sensney wrote:
> >if your
> >target is anything else, you SHOULD go in and configure by hand. (As
> >always, YMMV.)
>
> Yes again. But make a patch file of your changes. Your new patch may
> become the basis of another 'standard' patch if it becomes popular.
Most likely, when I go into edit the kernel by hand for finetuning, it's
to add support in to the kernel directly for a specific piece of hardware
rather than use it as a module. Don't know how overly useful it would be.
> >Erm, I perhaps am missing something here, but I thought that the point of
> >all this was to avoid having to use the 'make *config' step altogether,
> >by building a kernel .config "by script" as it were. Was I misinterpreting
> >this?
>
> Only a small confusion.
> LRPkernel is the tool for applying patches.
> Newpatch is the tool for creating patches.
Gotcha! So basically build a script that will save the default config as
something else, then automatically take the modified .config file, diff it
with the original, and bam you have a patch named whatever you want
based on the command line parameters. Now I follow. (I think.)
Little random update; SuSE was pissing me off fairly badly this past week,
so I made the mistake of nuking it and installing Mandrake 8.0. This
proceeded to trash the partition my mp3s existed on without asking me, as
well as having some other fairly nasty effects. So I burned my system to
the ground, and right now it's sitting there with a zero'd out drive
waiting for an install. I'm HOPING that I can get it back up and running
tonight, but no guarantees.
So for the short term, no more kernel compiles. And yeah, I know 2.4.4 is
out, and I really want it. Fixes the Via chipset bugs.
--
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
