Anaconda-devel April 2007

anaconda-devel@lists.stg.fedoraproject.org

24 participants
34 discussions

Creation of Fedora CD install
by Joel Andres Granados 07 May '07

07 May '07

Hi List: Was poking at pungi to creat CD images and found out that it spits out a traceback that has something to do with a missing directory. On further investigation I found out that the error was located in the splittree.py file. The directory for the first CD is created but the necessary directories for the subsequent CD (2,3,4....) are not created. For my system the error was corrected with the addition of a line to the splittree.py file. Diff: --- splittree.py-11.2.0.55 2007-04-24 17:49:16.000000000 +0200 +++ splittree.py-11.2.0.55-JG 2007-04-24 17:52:52.000000000 +0200 @@ -228,6 +227,7 @@ pass else: + os.makedirs("%s-disc%d/%s" % (self.dist_dir, i, self.product_path)) self.linkFiles(self.dist_dir, "%s-disc%d" %(self.dist_dir, i), self.common_files) self.createDiscInfo(i) AFAIK this line was erased to take away the RPMS directory. But in erasing the whole line the "self.product_path" directory was also erased. I tested the change and everything seems in place. Regards.

2 2

[patch] Several patches to process Dogtail testcases in Anaconda
by Alexander Todorov 02 May '07

02 May '07

What's in the tar.gz: * anaconda.process_and_launch_dogtail_script.diff The biggest patch of all. This adds a --dogtail option to the command line options for anaconda. Checks all possible conditions specifying a dogtail script: kickstart, boot cmd line, anaconda cmd line option. Downloads the script, fork and execute it before anaconda.intf.run(). * gui.py.always_load_a11y.diff Removed checking for dogtail. Always loads accessibility. How to properly check if dogtail is required? import gui happens prior to parsing kickstart data. I would like to have os.environ["GTK_MODULES"] = "gail:atk-bridge" outside gui.py. Can anybody help me to clean this up? * installdata.py.save_dogtail_kickstart.diff Added code that writes the dogtail option to the /root/anaconda-ks.cfg after install is complete. * scripts.upd-instroot.dogtail_files.diff Added code to extract the missing files into stage2.img. Works fine, already sent to anaconda-devel-list. These patches are against anaconda-11.1.2.36. * pykickstart.data.add_dogtail.diff * pykickstart.parser.add_dogtail_command.diff Added dogtail command support for kickstart. You can now add dogtail <url> in the ks file. These 2 are posted to Red Hat Bugzilla. Until they make it to upstream they have to be added to the scripts/upd-instroot pykickstart rpm version is 0.43-1.el5 Please review these patches. Greeting, Alexander

2 3

No handler could be found...
by xxxxxx xxxxx 27 Apr '07

27 Apr '07

Hi, I made a custom Linux distro, with anaconda, createrepo, etc etc. However, my distro installer constantly gives "No handlers could be found for logger "yum.YumBase". I REALLY want to get rid of it. I know it does no harm, but it looks very ugly... How can I fix this? Thanks!

1 0

How does anaconda probe the scsi hard disk, smp, hugememory while installing linux
by Rakesh L 24 Apr '07

24 Apr '07

Hi, I am regular linux user. I am having a problem in finding how does anaconda probe the underlying scsi hard disk, cpu with smp, hugememory, dual port network device of a computer while installing linux. please reply if anybody knows the answer. Thanks for all your valuable replies. -- Rakesh

1 0

PATCH: Anaconda & Kadischi installer, graphical mode
by Jasper Hartline 24 Apr '07

24 Apr '07

Here is a patch against anaconda-11.2.0.54-2 which I've created which allows Anaconda to be run in it's graphical mode, while inside a LiveCD, when doing LiveCD to HDD installs. Since we pass an http:// or ftp:// URL to Anaconda, it's traditional setting was to use TUI mode. I've tested this and it seems to work OK. The only other solution I could think of, whether the patch is accepted or not is to actually check for the presence of a "/.livecd" file in the root of the environment we are running in, this would eliminate having to check flags.rootpath, and give finer grained control. Not knowing the route Anaconda is going to take in light of Pilgrim, and since we don't use the already existant flags.livecd, I've provided both patches. If niether patch is accepted, or a better method cannot be put in place to allow Anaconda to run in GUI mode when run within the LiveCD environment, namely Kadischi's I can always just provide the patch in the Kadischi package, and document it for those wanting to build or have LiveCDs that will install to disk in GUI mode.. when using http:// or ftp:// URL repository strings. Attached are anaconda-live-file-GUI.patch for checking the presence of "/.livecd" file and anaconda-live-rootpath-GUI.patch for simply checking flags.rootpath. Thanks. J. Hartline

2 2

Fedora Core 7 test 3 network install via proxy server
by Makoto Sakurai 23 Apr '07

23 Apr '07

Dear all; I am using the Fedora Core test 3 i386 on Intel Duo 2 Core on the spec of Intel Core 2 Duo E6600 Gigabyte GA-965P-DS4 Rev3 Gigabyte GV-NX76G512P-RH Princeton PDD2/667-1GX2 (4GB memory) I/O DATA DVR-H42LEB HGST HDT725032VLA360 Scythe Goriki plug-in(450W power) ANTEC SOLO AINEX CVT-04 Owltech D353(B)/BOX The installation of Fedora Core 6 i386 from DVD and Windows Vista Business (dual boot) was successful. However, I need the latest version of Fedora for the following reasons: 1: The Xen 3.0 of Fedora 6 is unstable and kernel-xen crashes and reboots. 2: I will install the Fedora Core in a computer lecture so that I have better use the nerwork installation, which I did at home. The problem is, when I tried to network install via HTTP and set server redhat.download.fedoraproject.org and directory pub/fedora/linux/core/test/6.92/Prime/i386/os/, the following error is shown before starting the copying rpm files: Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated. Cannot open/read reoind,xnk fuke fir reoisutiry:anaconda-base-200703261959.i386 The rescure disk was clean, so that it is not the problem of my CD-ROM. I also tried to change screen ALT+F2 and in the command line, "export http_proxy=cache.ks.prv:8080", but in vain. Do you have any idea? My only hope is to copy the whole files of pub/fedora/linux/core/test/6.92/Prime/i386/os to a local network (HTTP or FTP inside ks.prv) and then do the network installation. But is there any other way to network install using proxy server in Fedora Core? I heard SUSE can do it. I will appreciate it if you would give me some comment on this. Yours Sincerely, Makoto Sakurai

1 0

Not so small list of issues on F7 t3
by Felipe Contreras 23 Apr '07

23 Apr '07

Hi everyone, I just installed F7 t3 and I wrote down all the issues and some comments regarding anaconda. == On the LiveCD == * Can't close livecdinst without rebooting It asks if it's OK even if it's experimental, I choose to exit, then I get: Reboot, Cancel. I don't want to reboot, so I Cancel, and I get back to the original screen. Clicking the X in the window manager thing doesn't work either. == In general == * Sometimes the GRUB dialog appear, sometimes not * The netinstall with ftp doesn't work, with http is fine == From USB key (diskboot.img) == * Anaconda asks twice to ignore the USB key device (/dev/sdb) * It appears anyway as the main device to install to * If I uncheck it from the list, it's still the main device * Even if I uncheck it, and select another device as main, the GRUB dialog still marks it as the device to install to, and the dropdown box is disabled * If I go back, GRUB is installed on /dev/sdb anyway, and now the screen with the devices has nothing on the dropdown for the main device, and clicking next crashes anaconda: (snipped) /iw/autopart_type.py, line 73, in getNext /gui.py, line 1034, in nextClicked TypeError: iter must be a GtkTreeIter That's about it. Also it should be great to be able to just run the GRUB part, because GRUB is now installed on my USB key instead of my internal hd =/ Best regards. -- Felipe Contreras

2 2

[Fwd: command for accessible install]
by Alexander Todorov 23 Apr '07

23 Apr '07

Hello, this question looks interesting. I guess anaconda does not support accessible installs at the moment. What are the pros and cons of that? Is there much work to be done except adding some device drivers (e.g. for braille display devices)? This can benefit disabled users and may be done if it requires not too many changes. What is your opinion here? Greetings, Alexander. -------- Original Message -------- Subject: command for accessible suse install Date: Thu, 19 Apr 2007 20:26:50 -0400 From: Cody Hurst <churst35(a)verizon.net> To: gnome-accessibility-list(a)gnome.org Hello al, I am looking for the appropriate boot command to use at a suse install to initialize my braillenote 32's braille display via the serial port for accessible installation. Any one have this comand or know where I can find it? Cody _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list(a)gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list

2 1

Error when compiling anaconda 11.1.1.3
by Olivier D 21 Apr '07

21 Apr '07

Hello, I'm trying to compile anaconda 11.1.1.3 : rpmbuild -ba anaconda.spec I'm getting the following errors about wireless.h : cc -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DUSESELINUX=1 -I/usr/include/python2.4 -I.. -DHAVE_NFS -I/usr/include/glib- 2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libdhcp -I/usr/include/dhcp4client -I/usr/include/dhcp6client -fPIC -o wireless.lo wireless.c In file included from wireless.c:29: /usr/include/linux/wireless.h:636: error: expected specifier-qualifier-list before '__s32' /usr/include/linux/wireless.h:648: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token /usr/include/linux/wireless.h:663: error: expected specifier-qualifier-list before '__s32' /usr/include/linux/wireless.h:674: error: expected specifier-qualifier-list before '__u8' /usr/include/linux/wireless.h:690: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:703: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:730: error: expected specifier-qualifier-list before '__u8' /usr/include/linux/wireless.h:792: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:806: error: expected specifier-qualifier-list before '__u16' /usr/include/linux/wireless.h:820: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:828: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:837: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:849: error: expected specifier-qualifier-list before '__u16' /usr/include/linux/wireless.h:872: error: 'IFNAMSIZ' undeclared here (not in a function) /usr/include/linux/wireless.h:887: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:931: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:1032: error: expected specifier-qualifier-list before '__u32' /usr/include/linux/wireless.h:1050: error: expected specifier-qualifier-list before '__u16' cc1: warnings being treated as errors wireless.c: In function 'get_wreq': wireless.c:34: warning: value computed is not used wireless.c:35: error: 'struct iwreq' has no member named 'ifr_name' wireless.c:35: error: 'struct iwreq' has no member named 'ifr_name' wireless.c:35: error: 'struct iwreq' has no member named 'ifr_name' wireless.c:35: error: 'struct iwreq' has no member named 'ifr_name' wireless.c: In function 'set_essid': wireless.c:81: error: 'struct iw_point' has no member named 'flags' wireless.c:82: error: 'struct iw_point' has no member named 'pointer' wireless.c:83: error: 'struct iw_point' has no member named 'length' wireless.c:85: error: 'struct iw_point' has no member named 'flags' wireless.c:86: error: 'struct iw_point' has no member named 'pointer' wireless.c:87: error: 'struct iw_point' has no member named 'length' wireless.c: In function 'get_essid': wireless.c:108: error: 'struct iw_point' has no member named 'pointer' wireless.c:109: error: 'struct iw_point' has no member named 'length' wireless.c:110: error: 'struct iw_point' has no member named 'flags' wireless.c:120: error: 'struct iw_point' has no member named 'pointer' wireless.c: In function 'set_wep_key': wireless.c:193: error: 'union iwreq_data' has no member named 'data' wireless.c:194: error: 'union iwreq_data' has no member named 'data' wireless.c:195: error: 'union iwreq_data' has no member named 'data' wireless.c:198: error: 'union iwreq_data' has no member named 'data' wireless.c:199: error: 'union iwreq_data' has no member named 'data' wireless.c:200: error: 'union iwreq_data' has no member named 'data' wireless.c: In function 'set_managed': wireless.c:221: error: 'union iwreq_data' has no member named 'mode' make[1]: *** [wireless.lo] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.1.3/isys' make: *** [subdirs] Error 1 error: Bad exit status from /var/tmp/rpm- tmp.41753 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.41753 (%build) infos about /usr/include/linux/wireless.h : /* * This file define a set of standard wireless extensions * * Version : 20 17.2.06 * * Authors : Jean Tourrilhes - HPL - <jt(a)hpl.hp.com> * Copyright (c) 1997-2006 Jean Tourrilhes, All Rights Reserved. */ Any idea ? Olivier

1 0

Re: anaconda-11.2.0.47 performance ...
by Alan Milligan 20 Apr '07

20 Apr '07

John Summerfield wrote: > Alan Milligan wrote: > >> Just an FYI, but I've just built and deployed essentially an FC6 + >> Updates + loads of Zope and Plone using the latest devel anaconda and >> friends. >> >> The performance was glacial across both an AMD x86 desktop (admittedly >> with only 256MB RAM - the rest was purloined by my x86_64 build server), >> and my Sony laptop with 740MB RAM. >> >> The installer is a DVD with circa 1.1 GB image and 900 packages, the >> upgrade involved circa 750 of these. >> >> The act of resolving dependencies for install took around 15 minutes, an >> hour to install the 750 packages, and the best part of 15 minutes to >> cleanup - total time circa 1.5 hours for a simple upgrade. >> >> rpm-4.4.2-32 >> yum-3.1.6-1.BAL6 >> >> I do hate to project the outcome of a 4GB DVD installer ... >> >> Thoughts anyone?? >> > > Just to test something.... > > Create an archive on disk and do an http install to match the one you've > done. One hopes you're using kickstart, and if not, that you will:-) > Strangely, I was experiencing real problems setting up the NIC to do http installs. But these don't need an archive disk/iso image they're expecting a file layout as per the iso. However, I'm serving these up with Zope which isn't necessarily the quickest thing on the planet, and sticking Squid in front of it isn't going to do much for one-off requests... > The time taken for that is useful, but not the point. Analyse the > webserver logs and use the information there to create a file for > mkisofs so you can specify the file order. > > I don't quite understand why I should do this. I already have a perfectly good pkgorder.txt and know what the file order will be ... > Create a new dvd image, and install from that. > > Report on the difference, I've long been curious about this, but never > enough to do some kind of benchmark. > > I'd be interested to know the time for each of the three; wristwatch > measurement is fine. > > > I actually think that yum's causing quite a few of these problems whilst we await a higher performance version to land. I'm still surprised at the length of time taken to unpack the RPM packages - I can't imagine why there'd be major changes in the RPM libraries/Python bindings that could cause this. I'm a couple of days away from doing any more testing unfortunately. While I can't retest these upgrades, I will post some qemu install results - hopefully I can get the kemu accelerator working as it's even more glacial than the above ;) Alan

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel April 2007