Public SourceMage Discussion List

["Bearcat M. Sandor" <Sorcerer AT TheDragonsEdge.com>]

David,

This looks awesome! i can't wait to try it out.

Currently, when the Linux spell is cast, any directly dependant spells are
triggered (oprofile, alsa-driver etc.)  When they are, they are compiled
against the current (just dispelled) kernel. So one has to reboot and then
recast them.

Given your work on the linux-new spell, is this problem alleviated?

Thanx,

Bearcat

>
> I'm hoping to get linux-new to a state where it can be integrated into
> linux, soon
>
> Here's some useful info about the spell
>
> Features:
> 1. dependancy checking using make
> 2. viewing patches that only apply to the base kernel you chose
>         so unless you go patch crazy the patches will most-likely apply
> 3. required post patching
>         this is mainly for security fixes and fixing overloaded kernels so
> they actually compile
> 4. having multiple kernels with different patches in different states on
> the same machine...
>         this is done by saving the persistant vars to the kernel tree
> 5. help dialogs explaining what the patches are and what contain
> 6. Options menu
>    1. pulling config files from different locations
>    2. arch selection
>    3. source tree clean options
>
> Some things you might not expect:
> 1. updating
>         linux-new doesn't update with `sorcery upgrade`.  This is because
> I
>     didn't want to stop the update process.  The fact that there is no
> guaranty
>     that a config file will apply to a newer kernel even if it's along the
> same
>     update path is why I chose this approach.
>         in order to update linux-new you have to cast -r -c linux-new, and
>     select an old source tree so that either menuconfig defconfig
> oldconfig
>     whatever runs to create a valid config file.
>         how linux-new updates is this, selecting a LATEST_* anything will
> keep
>     the source tree up-to-date. if you select a latest patch the base
> kernel
>     that the patch depends on will override any latest selection of the
> base
>     kernel, this means if you select the latest 2.6 and ac patches then
> the
>     latest 2.6 kernel updates linux-new won't try to apply the old ac
> patch to
>     the new 2.6 kernel.
>
> 2. no manual kernel version selection
>         I'm going to fight this one, but I don't know if I'm going to
> win...
>     I really don't thing this is needed with the system that is in place,
> now.
>     that's my only argument against it.
>
> Any feed back would be helpful, thanks
>
> - David Brown
> dmlb2000*
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>