Folks,
I'd like for RHEL5's Anaconda to be able to not only install my OpenAFS kmod but install the right kmod variant for PAE, xen, etc.
I've been working on the fedorakmod plugin for Yum for a bit during the summer but got stumped on a yum bug. Yesterday, I spent way too much time figuring out the exact bug and making fedorakmod work around it. With the plugin, Yum is now able to install all of the needed kmod packages for a specific kernel module.
So, upstream is here:
https://linuxczar.net/svn/slack/trunk/fedorakmod/
The plugin is also included in CVS head for yum-utils. Testing, feedback, and patches are welome.
What else needs to be done to have this included in Anaconda?
Jack
Jack Neely wrote:
The plugin is also included in CVS head for yum-utils. Testing, feedback, and patches are welome.
What else needs to be done to have this included in Anaconda?
I think that what we really want is to more generically support adding plugins. Right now, we don't do any enabling at all of plugins; while it may (or may not :-) make sense to do the kmod plugin by default, people are over time definitely going to want to enable "their" plugin. With an updates.img or product.img, we make it pretty easy for delivering more code to do specific customizations. Adding a directory in there for yum plugins and seeing the existence of the path and setting the YumConfig so that we look there would make a lot of sense.
Jeremy
On Mon, Jan 29, 2007 at 10:54:02AM -0500, Jeremy Katz wrote:
Jack Neely wrote:
The plugin is also included in CVS head for yum-utils. Testing, feedback, and patches are welome.
What else needs to be done to have this included in Anaconda?
I think that what we really want is to more generically support adding plugins. Right now, we don't do any enabling at all of plugins; while it may (or may not :-) make sense to do the kmod plugin by default, people are over time definitely going to want to enable "their" plugin. With an updates.img or product.img, we make it pretty easy for delivering more code to do specific customizations. Adding a directory in there for yum plugins and seeing the existence of the path and setting the YumConfig so that we look there would make a lot of sense.
What I was hoping you'd say. :-)
Jack
Jeremy
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Mon, Jan 29, 2007 at 10:54:02AM -0500, Jeremy Katz wrote:
I think that what we really want is to more generically support adding plugins. Right now, we don't do any enabling at all of plugins; while it may (or may not :-) make sense to do the kmod plugin by default, people are over time definitely going to want to enable "their" plugin.
Long term, I'd love to see as much as possible of anaconda's upgrade-kludges code moved to yum plugins. I'm still chasing that dream of being able to do live cross-release upgrades cleanly. (I know some things will still require offline, but a lot of logic like "mozilla was installed; we probably want to add firefox" could be done.)
anaconda-devel@lists.stg.fedoraproject.org