Anaconda-devel July 2004

anaconda-devel@lists.fedoraproject.org

31 participants
35 discussions

stage2.img
by Michael Anckaert 06 Jul '04

06 Jul '04

Hello, I'm modifying the anaconda installer. I've been fairly successfull in this but I have to extract and modify the contents of the stage2.img file everytime I rebuild the installer. I want to know if I can modify the sources that are used by the buildinstaller script so I won't have to modify the file by hand. Can anyone tell me where those sources are? -- Met vriendelijke groeten, Kind regards, Michael Anckaert michael.anckaert(a)pi.be

1 0

New feature in Anaconda
by Hamed Malek 06 Jul '04

06 Jul '04

Hi All, I'm a new subscriber to the list, so please forgive me if I'm asking an old question. As you know Yast (Suse Setup Tool) has a nice tool which let users to resize their existing partition in the middle of setup process. On the other hand Redhat has written a similar partition manager 'parted' as a separate program that perform these things in command line. Now, I'd like to know why anaconda developers has not ported this 'parted' program to anaconda? It doesn't seem to be difficult. Is there any technical or legal issues? Hamed

1 0

Anaconda on Alpha
by Mike Barnes 03 Jul '04

03 Jul '04

Hi folks - I'm in the middle of a somewhere ambitious project to get Fedora Core 2 up and running on Alpha systems. I'm a bit of a masochist when it comes to picking hobbies, I think. Anyway ... I've got 95% of the system rebuilt, and my development system is running a pretty close facsimile of FC2. My next trick is to get a bootable install CD set. I've got a tree, the right bits are in the right places, and the buildinstall process is working fine. "anaconda --test etc..." seems to be doing the right thing. Looks like an FC2 install, anyway. The glitch is coming during the initial boot. There's something screwy with the initrd setup, it seems. mk-images.alpha seems sane (I've updated it slightly based on the other architecture scripts, given that it probably hasn't been touched since RH 7.2). It's creating images, at any rate. Basically, when the installer launches, the kernel fires up, starts /sbin/loader, pops up the first stage of the install process and asks about language selections. It doesn't get much further, since all the module insertions are failing and saying that the modules can't be found. No SCSI controller module = dead end on my system. I've been over the generated modules.cgz (with a little help from "strings"), and all the modules I've specified seem to have made it into the image. I've updated hwdata since my SCSI controller module name changed between 2.4 and 2.6, and once I got to that point the console messages claim it's _trying_ to insert the qlogicisp module - it just can't find it. Any suggestions as to where to start prodding at this are welcomed. I'm starting to suspect that I've modularised some part of the kernel that I should have built in, but I'm not sure what it might be. Of course, that may be the wrong track entirely. Something architecture-specific in the module loader mechanism? I don't know. Thanks, folks.

2 1

anaconda-help
by Patrick Devine 02 Jul '04

02 Jul '04

Has anyone managed to get anaconda-help to build behind a firewall? I always get this lovely error message: xmlto --skip-validation -o C html -m onlinehelp.xsl help-screens-C.xml Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl" compilation error: file /tmp/xmlto-xsl.GerB3E line 4 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl cp: cannot stat `*.htm*': No such file or directory make[1]: *** [C-html] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-help-9.1/help' make: *** [subdirs] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.37092 (%build) It seems really stupid to make your build reliant on pulling style sheets from a network server. --Patrick.

3 5

(no subject)
by Thomas Bellos 02 Jul '04

02 Jul '04

I have followed the instructions about building a customized anaconda installer, found at http://rau.homedns.org/twiki/bin/view/Anaconda/AnacondaDocumentationProject and I ended up with an install cd which displayed no text in the screen, just the images. Just when I was quitting the install and the machine prepared to reboot, I saw some errors regarding pango, which I patched before running buildinstall, according to the above sites instructions. I believe the problem with the text not appearing was due to pango. Additionally, I have trouble locating the following package requirements of the buildinstall script : convertdb1 python2 Xconfigurator (found for older redhat version not fedora) fonts-ISO8859-9 Xft (found for older redhat version not fedora) XFree86-KOI8-R XFree86-KOI8-R-75dpi-fonts. which I did not install at all. Are these packages necessary for rebuilding anaconda? If so, are they available at any site you know?

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel July 2004