Anaconda-devel January 2006

anaconda-devel@lists.fedoraproject.org

36 participants
31 discussions

Changing the default theme
by Manilal K M 06 Feb '06

06 Feb '06

Hello everybody, I don't know whether this query is an offtopic. However I need information regarding it. I have custom compiled the FC-4 and installed it sucessfully with the great help from anaconda-devel-list. Now I need to change the default theme clearlooks to "Simple". I edited the patch associated with redhat-artwork (redhat-artwork-0.121-clearlooks.patch) and the file "redhat-artwork-0.122/gtkrc1-skel" and changed them to "Simple". However I noticed NO change in the theme. After Logging in I still get the default Blucurve icons and Clearlooks theme. Kindly advice. regards Manilal

3 4

Anaconda and tty2
by Ajith Vargese Thampi 02 Feb '06

02 Feb '06

Hi, When i build my custom anaconda-10.2.0.5. I dont get the tty2 while i get the tty3/4 and others. What could be the issue with tty2 not loading? Has it anything to do with busybox.anaconda being problematic? or is it anything to do with bash being problematic? Also, i get really untidy text. Could this be because of the locales? how do i make sure the locales are present properly? Also, i have xorg running successfully and then the next instant it crashes with an IO error 104 in mini-wm. Are gnome packages ever necessary for anaconda to run in graphics mode? Please do hoping for some tips from the masters. Thanks Aristo

2 4

[PATCH] clean up some dialogs
by Bill Nottingham 31 Jan '06

31 Jan '06

Change some dialogs to error dialogs, with proper icons, and replace 'OK' with 'Reboot' (oooh, HIGgy). Also marks with FIXME those that reference 'Press 'OK'', as we don't want to change strings now. Noticed the following different versions of the text in anaconda: Press 'OK' Press OK Press the OK button Press <Enter> Press <return> and some of the 'reboot now' dialogs already have a custom button of 'Exit' as opposed to 'Reboot' (didn't change those.) Passes pychecker. It occurs to me that perhaps we need intf.warningWindow and intf.errorWindow. Bill

1 0

Kickstart configurations
by John Summerfied 29 Jan '06

29 Jan '06

I'm not actually on the ks list, and I don't expect a long debate, and this is probably of interest to a few here, so enough of my rationalisations: see here: http://www.linuxpr.com/releases/8413.html Now, if this could be refined and incorporated into Anaconda so one could boot the standard ISO and create an install image on USB .... The install image could be an ISO or a script to make an ISO. -- Cheers John -- spambait 1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list

1 0

[PATCH] create drive (disk) dev nodes under /dev
by Patrick Mansfield 27 Jan '06

27 Jan '06

Running with iSCSI install patches, in stage2 device nodes are currently created under /tmp (like /tmp/sda) rather than /dev. But in the enablefilesystems / turnOnFilesystems, we call scanForRaid and that ends up deleting all drives /tmp nodes, so when we later try to open /tmp/sda, the install fails. This patch more sensibly creates device nodes under /dev like we'd do in stage1, rather than the default /tmp, and avoids the problem. diff -uprN -X /home/patman/dontdiff anaconda-10.91.4/partedUtils.py use-dev-anaconda-10.91.4/partedUtils.py --- anaconda-10.91.4/partedUtils.py 2005-12-11 15:35:33.000000000 -0800 +++ use-dev-anaconda-10.91.4/partedUtils.py 2006-01-25 15:24:05.000000000 -0800 @@ -891,7 +891,7 @@ class DiskSet: for drive in self.driveList(): if drive in DiskSet.skippedDisks and not initAll: continue - deviceFile = isys.makeDevInode(drive) + deviceFile = isys.makeDevInode(drive, '/dev/' + drive) if isys.driveIsRemovable(drive) and not flags.expert: DiskSet.skippedDisks.append(drive) continue

2 1

loader and module options
by Alain TAUCH 27 Jan '06

27 Jan '06

Hi all, I'm looking for some advices regarding a pxe installation. I need to force the speed/duplex of my NIC to get my installation working, but for this, I have to pass options to my driver module. And I precisely don't how to achieve this :/ To precise where the problem occurs: I can get the kernel and initrd via tftp, but I'm stuck when trying to get the kickstart file via nfs because of my NIC's speed/duplex. Using a /etc/modules.conf in the initrd did not work, so I tried to tweak the module-info file and set my options as the default ones: I used the format in the comment of the module-info file stating: # The version 0 module-info format is ('|' denotes the left margin): # |<module-name> # | <module-type> [<module-alias>] # | "<description-string>" # | <argument> "<argument-description-string>" ["<match-regex>" ["<default>"]] # |# <comment> but It did not work out, so I looked at the moduleinfo.c code, and precisely the part parsing the argument line: <snip> nextModule->args = realloc(nextModule->args, sizeof(*nextModule->args) * (nextModule->numArgs + 1)); chptr = start; while (!isspace(*chptr) && *chptr) chptr++; if (*chptr) { oldch = *chptr; *chptr = '\0'; nextModule->args[nextModule->numArgs].arg = strdup(start); start = chptr + 1; while (*start && isspace(*start)) start++; if (*start == '"') { start++; chptr = strchr(start, '"'); if (chptr) { *chptr = '\0'; nextModule->args[nextModule->numArgs].description = strdup(start); nextModule->numArgs++; } } } </snip> reading this I had the impression that the only thing that was parsed was: <argument> "<argument-description-string>" and that if you tried to put: <argument> "<argument-description-string>" "<match-regex>" "<default>" you would get: in .arg: <argument> in .description: <argument-description-string>" "<match-regex>" "<default> so I tried to directly set the default values in the <argument> part (who knows) but without success either :( any ideas ? -- Alain

2 2

Splittree Overflowing
by abayomi onibudo 21 Jan '06

21 Jan '06

Hi all, dont know if anyone got to see the posting below yesterday, thought may be it did not come through. i am creating a custom 1 disk distro using the attached comps.xml which i modified. I am pretty much trying to reduce the RPMS to a bare minimal that will fit on 1 CD using Gnome so i removed all kde related packages including kdelibs and related KDE packages as well other language support from the comps.xml I have also ran the following install package dependency test on the set of RPMS i am using... rpm --test --dbpath /tmp/testdb -Uvh /home/fc3/i386/mydistro/RPMS/* .rpm and all dependencies appear resolved ok. Also, i started building the distro ok with a succesfull completion of running buildinstall, however when i run splittree as below i get the following. -----------------splittree----- [root@eshin fc3]# splittree.py --arch=i386 --total-discs=1 --bin-discs=1 --src-discs=1 --release-string="Wazobia Linux 1" --pkgorderfile=/home/fc3/pkgfile --distdir=/home/fc3/i386 --srcdir=/usr/src/redhat/SRPMS --productpath=Wazobia First package on disc1: fedora-logos-1.1.34-1.1.noarch.rpm Last package on disc1 : mutt-1.4.1-10.i386.rpm i386-disc1 size: 599M Overflowing redhat-artwork-0.117-1.src.rpm on disc1 Overflowing anaconda-10.1.0.2-1.src.rpm on disc1 Overflowing libgnome-2.8.0-2.src.rpm on disc1 Overflowing system-config-packages-1.2.20-1.src.rpm on disc1 Overflowing fedora-logos-1.1.34-1.1.src.rpm on disc1 Overflowing rhgb-0.14.1-1.src.rpm on disc1 Overflowing fedora-logos-1.1.29-1.src.rpm on disc1 Overflowing kudzu-1.1.95-1.src.rpm on disc1 Overflowing mkinitrd-4.1.18-2.src.rpm on disc1 Overflowing comps-1.20060115-0.20060115.src.rpm on disc1 Overflowing comps-1-0.20060115.src.rpm on disc1 Overflowing comps-%{compsversion}-0.20060115.src.rpm on disc1 i386-disc1 size: 669M ------------------------------------------------------------------------end of splittree output i then proceed to mkiso which runs ok using the mkisofs command as below, and then implantisomd5 on the iso image which seems to boot ok i.e. running anaconda untill when it about to start installing packages then it aborts abnormally. I suspect the problem is from above but i cant seem to figure whether i dont have enough space left on the CD i.e. the Overfloowing but would have thougt 669MB was good enough. Can anyone please point me in the right dorection or let me know if i am doing something wrong or if they know a solution to the problem? ---mkisofs--command.... mkisofs -R -J -T -v -no-emul-boot -boot-load-size 4 -boot-info-table V "MyDistro Demo" -b isolinux/isolinux.bin -c isolinux/boot.cat -x "lost+found" -o MydistroDemo-i386-disc.iso disc ---end of mkisofs----commands Thanks Abayomi

1 0

Howto update the Anaconda install for an FC4 installation
by Terry Barnaby 20 Jan '06

20 Jan '06

Hi, Is there some information somewhere on how to update the anaconder installer for FC4 ? I have an FC4 tree on a server and am tring to install FC4 on another system using NFS. There appears to be a bug in the stock FC4 anaconda installer "Error informing kernel about modification to partition ..." and so I am tring to update the Anaconda installer to see if that fixes my problem. I assume I can install the updated anaconda and anaconda-runtime RPM's on the server and execute some commands to generate the new stage 2 images in Fedora/base ? Cheers Terry

3 3

Custom 1 Disc distro
by abayomi onibudo 19 Jan '06

19 Jan '06

Hi all, i am creating a custom 1 disk distro using the attached comps.xml which i modified. I am pretty much trying to reduce the RPMS to a bare minimal that will fit on 1 CD using Gnome so i removed all kde related packages including kdelibs and related KDE packages as well other language support from the comps.xml I have also ran the following install package dependency test on the set of RPMS i am using... rpm --test --dbpath /tmp/testdb -Uvh /home/fc3/i386/mydistro/RPMS/* .rpm and all dependencies appear resolved ok. Also, i started building the distro ok with a succesfull completion of running buildinstall, however when i run splittree as below i get the following. -----------------splittree----- [root@eshin fc3]# splittree.py --arch=i386 --total-discs=1 --bin-discs=1 --src-discs=1 --release-string="Wazobia Linux 1" --pkgorderfile=/home/fc3/pkgfile --distdir=/home/fc3/i386 --srcdir=/usr/src/redhat/SRPMS --productpath=Wazobia First package on disc1: fedora-logos-1.1.34-1.1.noarch.rpm Last package on disc1 : mutt-1.4.1-10.i386.rpm i386-disc1 size: 599M Overflowing redhat-artwork-0.117-1.src.rpm on disc1 Overflowing anaconda-10.1.0.2-1.src.rpm on disc1 Overflowing libgnome-2.8.0-2.src.rpm on disc1 Overflowing system-config-packages-1.2.20-1.src.rpm on disc1 Overflowing wazobia-logos-1.1.29-1.src.rpm on disc1 Overflowing fedora-logos-1.1.34-1.1.src.rpm on disc1 Overflowing rhgb-0.14.1-1.src.rpm on disc1 Overflowing fedora-logos-1.1.29-1.src.rpm on disc1 Overflowing kudzu-1.1.95-1.src.rpm on disc1 Overflowing wazobia-release-3-8.src.rpm on disc1 Overflowing wazobia-release-1-8.src.rpm on disc1 Overflowing mkinitrd-4.1.18-2.src.rpm on disc1 Overflowing comps-1.20060115-0.20060115.src.rpm on disc1 Overflowing comps-1-0.20060115.src.rpm on disc1 Overflowing comps-%{compsversion}-0.20060115.src.rpm on disc1 i386-disc1 size: 669M ------------------------------------------------------------------------end of splittree output i then proceed to mkiso which runs ok using the mkisofs command as below, and then implantisomd5 on the iso image which seems to boot ok i.e. running anaconda untill when it about to start installing packages then it aborts abnormally. I suspect the problem is from above but i cant seem to figure whether i dont have enough space left on the CD i.e. the Overfloowing but would have thougt 669MB was good enough. Can anyone please point me in the right dorection or let me know if i am doing something wrong or if they know a solution to the problem? ---mkisofs--command.... mkisofs -R -J -T -v -no-emul-boot -boot-load-size 4 -boot-info-table V "MyDistro Demo" -b isolinux/isolinux.bin -c isolinux/boot.cat -x "lost+found" -o MydistroDemo-i386-disc.iso disc ---end of mkisofs----commands Thanks Abayomi

1 0

I want to customize loader of anaconda...
by Alexandre Pedroso 19 Jan '06

19 Jan '06

Hi, I'm a newbie and i don't speeky english very well. but I go to try explain me, OK? In the reality, I only wanted to use loader of anaconda and to make it call my shell installer. My shell installer is ready and i don't need help with it. I need only make a loader customized based in anaconda. Somebody could help me? Thanks

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel January 2006