Anaconda-devel November 2006

anaconda-devel@lists.stg.fedoraproject.org

20 participants
23 discussions

FC6 firstboot error
by Vnpenguin 28 Nov '06

28 Nov '06

Hi All, I try to install FC6 on VMware. Unfortunately I have a error with firstboot: http://people.vnoss.net/~vnpenguin/fc6-firstboot-err.png Could you tell me how to fix this please, TIA

2 1

anaconda method hd install from fully exploded tree?
by Jeroen Janssen 27 Nov '06

27 Nov '06

Hi, I couldn't find any information on Anaconda being able to install from a fully exploded tree from the harddisk. As far as I can tell the 'harddisk' option expects the ISO files to be available. Is it possible to do an install from a fully exploded tree from the harddisk? Is this something that is considered usefull for other people to have? Best regards, Jeroen Janssen

2 1

testing (Anaconda) changes?
by Jeroen Janssen 27 Nov '06

27 Nov '06

Hello, I've been doing some work with Anaconda to get it to install MontaVista Linux RPMs. I finally have been able to install the RPMs on disk (I'll spare you the details, unless someone is really interested). At this point the installation 'fails' because there are some obvious differences between Fedora Core 6 and MontaVista Linux Professional 4. I would like to 'patch' some of the anaconda files and test the changes in an easy way. I've done the following in the past for testing: * changes rpm and rpm-python were tested locally on my Fedora Core 6 machine, when everything worked ok, I updated the packages in the "installation repo" and generated a new iso file. * changes in rpmUtils and yum were tested locally, and during install with an updates.img using the "updates" kernel option during boot from CD. However, it seems that updates to anaconda itself (kickstart.py, dispatch.py, etc) are not possible from the updates.img (at least from looking at the anaconda script it only allows to update items for "rhpl", "yum", "rpmUtils", "urlgrabber", "pykickstart", "rhpxl", "pirut"). Is there an easy way to test changes to anaconda (without building a new ISO) that I can use? I did some testing with xen in the past, but I haven't found out if/how I can specify my own anaconda to be used. Is it possible to use a custom anaconda for xen installs? I noticed the anaconda --test option, but I can not find documentation on exactly how/what it does (does it create partitions? install RPMs? etc) Best regards, Jeroen Janssen

3 2

arch in yum.rpmUtils and rhpl?
by Jeroen Janssen 27 Nov '06

27 Nov '06

Hello, It seems there is both an rhpl.arch and a yum.rpmUtils.arch containing "the same code". Any idea why this is? Note the latest yum.rpmUtils.arch seems to be more up-to-date? Since it provides some more functions: isMultiLibArch, getBestArchFromList, getArchList, getBaseArch. The rest is identical. Anyway, it seems this file contains a list of supported arches, so I'm guessing this is my best entry for getting support for installing x86_586 MontaVista Linux packages (more on this tomorrow). Best regards, Jeroen Janssen

2 1

install RPMs from 'different' arch?
by Jeroen Janssen 27 Nov '06

27 Nov '06

Hello, I'm trying to install MontaVista Linux 4 Pro RPMs using the FC6 Anaconda installer. The Fedora Core 6 RPMs have the architecture i686 (for the i386 installation). However, the MontaVista Linux RPMs (for the generic x86 target) have an architecture of x86_586. As a result, Anaconda currently 'ignores' all the MontaVista Linux RPMs during install (since the architectures don't match). Is there a way to 'force' Anaconda to also install the packages for the x86_586 architecture? (possibly by 'patching' the yuminstall.py?) Best regards, Jeroen Janssen

3 2

Re: anaconda method hd install from fully exploded tree?
by Kay Williams 27 Nov '06

27 Nov '06

> >Date: Mon, 27 Nov 2006 16:42:42 +0100 >From: "Jeroen Janssen" <jeroen.janssen(a)gmail.com> >Subject: anaconda method hd install from fully exploded tree? >To: anaconda-devel-list(a)redhat.com >Message-ID: > <e34e42440611270742y13e65186o5dc9dd7b7abe7bff(a)mail.gmail.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >Hi, > >I couldn't find any information on Anaconda being able to install from >a fully exploded tree from the harddisk. As far as I can tell the >'harddisk' option expects the ISO files to be available. > >Is it possible to do an install from a fully exploded tree from the harddisk? >Is this something that is considered usefull for other people to have? > Paul Schroeder posted a patch to enable tree-based installation from a harddrive. Here is a link to the posting: https://www.redhat.com/archives/anaconda-devel-list/2006-August/msg00076.ht…. Would be great to see this in the main product. >Best regards, > >Jeroen Janssen >

1 0

Resend: mediacheck and kickstart
by Aleksandar Lazic 23 Nov '06

23 Nov '06

Hi, have nobody any infos to this?! Btw.: will you accept a patch which add this feature? --- Today I have searched why our 'linux mediacheck ks=...' doesn't work and I have found this post from 24 Nov 2003: http://www.redhat.com/archives/anaconda-devel-list/2003-November/msg00135.h… after I have read this post I got the current srpm from centos 4.4 and have looked into both files and have seen that the message in the mail is still true. Do you have plans to change this behaviour with for example 'forcemediacheck' or something similar? Regards Aleks

3 7

/etc/hosts file
by Kashif Ali 22 Nov '06

22 Nov '06

Hi, I have been playing with kickstarts for a while, however i never understood why when you have the line: network --device eth0 --bootproto static --ip 192.168.1.8 --netmask 255.255.255.0 --gateway 192.168.1.254 --nameserver 192.168.1.252 --hostname host.mydomain.com kickstart creates a /etc/hosts file as follows: 127.0.0.1 host.mydomain.com myhost localhost.localdomainlocalhost why doesn't it do it correcty as: 127.0.0.1 localhost.localdomain localhost 192.168.1.8 host.mydomain.com host i know you can create a script in the %post but i was wondering if there was a correct way of generating hosts file in the kickstart that i maybe missing?

4 5

FC6 on ppc remastering
by Torsten 22 Nov '06

22 Nov '06

Hi all, currently I try to remaster FC6 for ppc[64]. And after searching for while I found this message in the mailing list. http://www.redhat.com/archives/anaconda-devel-list/2006-April/msg00039.html I looked into the repack.sh but I guess it can't work for a ppc based system because of the first mkisofs. It looks for some isolinux stuff but this is not valid for ppc. So I guess I need some different parameters (like -prep-boot) and propably some additional tasks. Could anybody help on this? Thanks in advance, Torsten

2 2

installSteps & stepToClass
by Jeroen Janssen 19 Nov '06

19 Nov '06

Hello, I'm trying to understand the installStep construction in dispatch.py and text/gui.py. There are a number of installSteps in dispatch.py that have a function. Am I correct to understand that a step either has a function defined in installSteps or a stepToClass definition (in text.py or gui.py)? Also it seems there is some common stepToClass code in both text.py and gui.py. For instance: gui.py: "language" : ("language_gui", "LanguageWindow"), text.py: "language" : ("language_text", "LanguageWindow"), But there seem to be a lot more gui files (in iw/) then text files (in textw/). Is there some documentation on this? (or should it be 'self documenting'?) Also the 'betaNagScreen' seems to be common (using anaconda.intf.messageWindow) for both text and ui. As far as I (initially) can tell, this is the only common (ui-wise) step. Is there a specific reason for this? Best regards, Jeroen Janssen

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel November 2006