On 11/17/06, Paul Nasrat <pnasrat@xxxxxxxxxx> wrote:
On Fri, 2006-11-17 at 08:47 +0100, Jeroen Janssen wrote: > During installation Anaconda complains no kernel was found. After > taking a more detailed look at it, I realised that there is no linux > kernel package named "kernel" in MontaVista Linux, so that ofcourse > explains why it isn't working. What is the kernel package called - what does it provides (rpm -qp --provides kernel-whatever.i686.rpm)
The kernel package is called 'lsp-generic_x86-pc_target' and provides '2.6.10_mvl401-1.1.1.0502020' (yes, I know it is a 'very old' kernel).
It's fairly easy to add an updates.img with yuminstall.py adapted to that tree. Although as I think about it we could encapsulate information like this in metadata to enable flexible package naming policies. > This made me wonder if Anaconda is being used to install non > RedHat/Fedora (RPM) based distributions (i.e. is it possible to > install OpenSuSe or Mandriva with Anaconda?). Anaconda is being used elsewhere, but it'll generally require modifying to your environment.
Ok, that is what I expected, but it is good to have a confirmation on this.
It's quite possible we should look at how the backed works for this, maybe we should supply a generic yum backend with no hooks to anything, or one that pulls the hooks from external metadata. This ties in with some things we want to do for the future anyway. Basically break the postInstall stuff to be modular and pluggable for distros. In essence you can do it at the moment by changing anaconda and either rebuilding or using an updates.img, but making it easier is of interest to us.
Ok, thanks for the information. Are there any concrete plans for these kind of changes (FC7 context?) that I possibly could help with (brainstorming/coding/testing/etc)? For now, I'll be 'refreshing' my python knowledge and see what I can do with an updates image. Best regards, Jeroen Janssen
