Anaconda-devel June 2006

anaconda-devel@lists.stg.fedoraproject.org

28 participants
30 discussions

new vmlinuz and initrd and old Fedora Install
by Rithick Bala 29 Jun '06

29 Jun '06

I am trying to use the vmlinuz and initrd from FC5 to install FC2. I am using PXE and the reason to go with the newer vmlinuz and initrd is to get all the driver support that I need. However, the install stop with "that directory does not contain a Fedora Core installation tree". Is there an easy way to circumvent?

1 0

Patch for splittree.py to follow symlinks in package size calculation
by Eric Moret 29 Jun '06

29 Jun '06

Hello all, Goal: ---- I am trying to create a 5 discs fedora core 5 - FC5 distribution based on a single DVD image. In order to save disk space I would like to create a unified tree with symlinks to packages rather than the real rpm files. Problem: ------- When I run splittree.py on the tree populated with symlinks here is what I get: $ /usr/lib/anaconda-runtime/splittree.py \ --arch=i386 \ --total-discs=5 \ --bin-discs=5 \ --src-discs=0 \ --srcdir=/usr/local/src/cs-fedora/SRPMS \ --release-string="Fedora Core 5" \ --pkgorderfile=/usr/local/src/cs-fedora/pkgfile.txt \ --distdir=/usr/local/src/cs-fedora/i386 \ --productpath=Fedora First package on disc1: kernel-2.6.17-1.2139_FC5.i686.rpm Last package on disc1 : lucene-javadoc-1.4.3-1jpp_11fc.i386.rpm i386-disc1 size: 133M Files and links to packages in Fedora/RPMS only take up to 133M! The package size calculation does not follow symlinks. So they all fit on the first disc. Obviously not what I want. Solution: -------- Below is a simple patch that follows symlink for calculation of file size. With this patch applied I actually obtain the 5 discs filled up with proper links to packages... and saving quite a bit of disk space. $ /usr/lib/anaconda-runtime/splittree.py \ --arch=i386 \ --total-discs=5 \ --bin-discs=5 \ --src-discs=0 \ --srcdir=/usr/local/src/cs-fedora/SRPMS \ --release-string="Fedora Core 5" \ --pkgorderfile=/usr/local/src/cs-fedora/pkgfile.txt \ --distdir=/usr/local/src/cs-fedora/i386 \ --productpath=Fedora First package on disc1: kernel-2.6.17-1.2139_FC5.i686.rpm Last package on disc1 : evolution-sharp-0.10.2-9.3.i386.rpm i386-disc1 size: 629M First package on disc2: mono-data-1.1.13.7-1.fc5.1.i386.rpm Last package on disc2 : ant-apache-oro-1.6.5-1jpp_7fc.i386.rpm i386-disc2 size: 623M First package on disc3: eclipse-platform-3.1.2-1jpp_15fc.i386.rpm Last package on disc3 : kdeedu-devel-3.5.3-0.1.fc5.i386.rpm i386-disc3 size: 640M First package on disc4: xfsprogs-2.7.3-1.2.1.i386.rpm Last package on disc4 : slrn-pull-0.9.8.1pl1-1.2.1.i386.rpm i386-disc4 size: 621M First package on disc5: thunderbird-1.5.0.4-1.1.fc5.i386.rpm Last package on disc5 : lucene-javadoc-1.4.3-1jpp_11fc.i386.rpm i386-disc5 size: 603M Hope this helps! __ Eric --- splittree.py.orig 2006-06-19 09:46:35.000000000 -0700 +++ splittree.py 2006-06-28 22:35:24.000000000 -0700 @@ -107,13 +107,13 @@ """Gets the size as reported by du -s""" if blocksize: - p = os.popen("du -s --block-size=1 %s" % path, 'r') + p = os.popen("du -sL --block-size=1 %s" % path, 'r') thesize = p.read() p.close() thesize = long(string.split(thesize)[0]) return thesize else: - p = os.popen("du -sh %s" % path, 'r') + p = os.popen("du -shL %s" % path, 'r') thesize = p.read() p.close() thesize = string.split(thesize)[0]

1 0

compilation error
by U M A R 28 Jun '06

28 Jun '06

hi, I know this is not the correct mailing list for talking about debian..Even though if any body aware of this error ........they can send me the reply. while compiling anaconda in testing system of debian..i got the followin error....any body knows where the error is? Support mounting NFS file systems (CONFIG_NFSMOUNT) [Y/n/?] y umount (CONFIG_UMOUNT) [Y/n/?] y Support forced filesystem unmounting (CONFIG_FEATURE_MOUNT_FORCE) [Y/n/?] y * * Common options for mount/umount * Support for loop devices (CONFIG_FEATURE_MOUNT_LOOP) [Y/n/?] y Support for a real /etc/mtab (instead of /proc/mounts) (CONFIG_FEATURE_MTAB_SUPPORT) [N/y/?] n * * Debugging Options * Build BusyBox with Debugging symbols (CONFIG_DEBUG) [N/y/?] n gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -c -o applets/applets.o applets/applets.c gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -c -o applets/busybox.o applets/busybox.c ar -ro applets/applets.a ./applets/applets.o ./applets/busybox.o ar: creating applets/applets.a gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -c -o archival/cpio.o archival/cpio.c gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -c -o archival/gunzip.o archival/gunzip.c gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -c -o archival/gzip.o archival/gzip.c archival/gzip.c:2166: warning: type qualifiers ignored on function return type archival/gzip.c:2166: error: conflicting types for 'build_bl_tree' archival/gzip.c:1643: error: previous declaration of 'build_bl_tree' was here make[2]: *** [archival/gzip.o] Error 1 make[2]: Leaving directory `/root/anaconda/OfficialAnaconda/anaconda-10.0/busybox-1.00-pre10' make[1]: *** [busybox] Error 2 make[1]: Leaving directory `/root/anaconda/OfficialAnaconda/anaconda-10.0' make: *** [build-stamp] Error 2 Best Regards: U M A R --------------------------------- Want to be your own boss? Learn how on Yahoo! Small Business.

2 1

change time zone and jump package select
by Devi 28 Jun '06

28 Jun '06

Hi all 1. Did anyone knows how to change default time zone America/New_York to other time zone on customize anaconda installatation? 2. how to hide/jump/disable Package select page on anaconda installation, because i just create single cd FC5 installation and do not need other package to selected rgs -dv

2 1

optimize the installation of fedora 5
by Claudio Oliveira 28 Jun '06

28 Jun '06

Good Afternoon, It would like to optimize the installation of fedora 5 in way text, in way to install so oque desire, alguem could indicate me one howto? grateful -- Claudio Oliveira Batista Analise de sistemas (31)8827-8532 "A Embalagem Diz: Requer sistema MS Windows ou Superior Então, eu instalei o Linux"

1 0

[patch 0/4] elilo multiboot support
by Aron Griffis 23 Jun '06

23 Jun '06

The following patches give grubby the ability to manipulate multiboot-capable elilo.conf. Fedora's elilo already contains the support, these patches simply teach grubby to take advantage of it. These patches are an enabler for using Xen on ia64 with Fedora. I have tested these changes with both grubby and elilo, using both multiboot and non-multiboot configurations. Regards, Aron

2 8

file conflicts
by Alan Milligan 21 Jun '06

21 Jun '06

Hi, In "preparing translation from installation home" Anaconda install step, my distro currently has the misfortune of throwing a file conflict exception. Is there a process somewhat similar to repoclosure which I can run to identify candidate packages causing this travesty? Alan

2 1

ignoring GPT partitions
by Adam Miller 20 Jun '06

20 Jun '06

Hi, I'm working on a completely automated install of FC4x86_64 on a AMD Opteron 175 box with 16x Western Digital 400GB drives. The OS is being installed on a 20GB partition, and the rest of the 5TB are on a single GPT partition. The GPT partition will house data that I do not want destroyed when installing the OS. Anaconda will warn, however, that this partition is GPT. I wish to ignore this fact in the install, but I don't know how to add in the kickstart to ignore this drive. Any suggestions? Cheers, Adam Miller UWM

3 3

AI - Anaconda Image
by Frozen River 19 Jun '06

19 Jun '06

Hello Folks, Sorry for cross post -- sent the same mail to the kickstart list - anyways made a customization of kickstart/anaconda and I would like to share it with the rest of the anaconda community. It's essentially a way to bypass the rpm installation during a kickstart and instead using file sets images. What differes from other tools such as system imager is that the hardware doesn't need to be the same. Instead as during any kickstart the hardware is detected and the support (kernel etc) is installed as usual. Hence you can e.g. have the same image for a small development server as for the big production server or even snapshot the production server and deploy it on a smaller test machine to investigate bugs. Anyways let me introduce AI i.e. Anaconda Image, please let me first note that it's a work in progress and that the code is far from polished. The code it self can be downloaded from http://frozenriver00.tripod.com/ks-RHAS4.cfg AI – Anaconda Image; A way of rapid kickstart deployment with help of file set images on the same hardware architecture but regardless of hardware. Main ideas are to; By pass the lengthy time it takes for all rpm packages to be installed on a system Be able to do customizations on the system and have them ready at install time without help of cumbersome post kickstart scripts or other scripts fetching additional configurations or packages at a post install Be able to snapshot a system either as a backup or for replication and deploy that snapshot on any hardware as long as the architecture is the same To accomplish this kickstart is preformed on the system as usual with the exception of nearly the entire rpm installation portion of kickstart. Instead just before the rpm installation is to take place a cpio archive is extracted complete with the rpm database and all other files (packages) of the system you want to build (basically you have made compleate backup with help of cpio on a system you want to use as your golden system). After the extraction is complete the necessary rpm packages such as kernel, filesystem support packages and boot loader packages will be installed as normal during a kickstart. The system is by that time ready for use and it has the correct initrd image and kernel along with the support of the filesystem such as e.g. ext3, xfs or what ever you will use. The way to customize kickstart without hacking anaconda it self is to use the special word " %installclass" in the kickstart configuration file. This way the kickstart file is split in two parts and the latter part with you custom python code loaded. This way its relatively easy to overload and extend all functions and procedures present in anaconda. What you do is basically defining a " class CustomKickstart(KickstartBase):" in which you skip nearly all steps in a kickstart and add a few of your own namely: flashpre – preparation to flash mainly getting hw support info (pretty much a copy of existing code) flashinstall – extraction of the cpio archive flashpackage – installation of the packages needed for hardware support (also mostly a copy of anaconda code and butchered) flashpost – post stuff to write hw conf and similar When appending the " %installclass" a new keyword flash can be used in your kickstart config file. It takes the following arguments --server="IP ADDRESS" which is the server from when you will NFS mount your system image --dir=/where/I/have/my/image/ By default it will look for the directory "RedHat/4" in this dir – but if it doesn't find it will traverse up. The main server image it looks for is "default" but you can have it to look for image names based in MAC address, "desktop", "server" and so forth and so on. The comments in the code are covering those scenarios pretty extensively. And I will try to explain it further when I get the code a bit more polished. The code is however fully functional and I have used to build 66 servers with a average build time of nine minutes per server :) – that's fully configured servers with third party applications and ready for immediate use. Best luck the Frozen one... PS: Note however that there are a few anomalies in the RedHat Advance Server Anaconda implementation. The key word " %installclass" is not really supported even if it's fully documented in the code. If you use it strait up and down hence I had to change Kickstart.c in loader2 not just look for pre post and packages in the ksReadCommands function since installclass should also taken into consideration if we do a custom kickstart installation ( i.e. we should stop parsing when we reach installclass) Changed kickstart.py so that it don't remove the tmp /tmp/ks.conf.new after invoking custom kick start (we will get an error since the file will not excist later on in the execution) i.e. "#os.unlink(newKsFile)" in kickstart.py I mean it's probably a good idea to keep the ksclass.py why remove something looks very meaning less to me? One strange thing is that I didn't find why we could not do ip=dhcp – there is definitely something wrong in the parser since (ip= xxxxyyyyssss.eeee,) doesn't work while ip, gateway, netmaskworks.

2 1

conditional auto-partioning of a disk
by Paul Armor 19 Jun '06

19 Jun '06

Hi, we're working on headless installation of a large number of computers. We're trying to install FC4, which I beleive is using anaconda 10.2.1. These systems can be in either of two states: Disk is already partioned, with one partition containing data we want to keep. Disk is "blank", and we want to repartition in a particular way. Several of us have poked around but not been able to put together a method by which we can do this within anaconda purely. I'm wondering if anyone could suggest a means by which we could do this. We've not figured out how to do such if-then logic in the install section, and haven't had success in %pre. How do other do such things? Thanks! Paul Armor

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 June 2006