Re: Using Anaconda to install MontaVista Linux?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2006-11-17 at 08:47 +0100, Jeroen Janssen wrote:
> Hello,
> 
> I'm looking into installing a "not-RedHat/Fedora" rpm based
> distribution with Anaconda (in this case MontaVista Linux) on a
> generic x86 plaform. I'm not sure if this is the correct list to
> discuss this, but since this is the only Anaconda development list I
> could find, here goes.
> 
> I did an 'experiment' with the FC6 CD 1 by using a netbase
> installation (http) to a repository containing (only) all the
> MontaVista Linux rpm files (so no FC6 rpms were available in this
> repository).
> 
> 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)

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.

> Also, what packages does Anaconda 'expect' to be present in the repository?
> I found (from looking at the Anaconda python sources) the following depedencies:
> * kernel*
> * authconfig
> * chkconfig
> * mkinitrd
> * rhpl
> * system-config-securitylevel-tui
> * grub (or lilo?) on i386

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.

Paul


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux