Anaconda-devel June 2005

anaconda-devel@lists.stg.fedoraproject.org

15 participants
14 discussions

Installing fc3
by surya 30 Jun '05

30 Jun '05

hi list, I am trying to install fc3 on Intel 3GHz hyperthreaded processor on intel 865GBF but in vain. It terminates saying "installation exited abnormally". Any help appreciated. regards, Surya

2 1

PATCH - software raid for ppc on installation (booty)
by Dustin Kirkland 29 Jun '05

29 Jun '05

This is one additional change that's needed for software raid for ppc on installation. This change is actually in booty, and will allow anaconda/booty to accurately write the yaboot.conf configuration file when the user has created more than one bootable PReP partition. The code used to simply write: boot=/dev/<PReP partition> With this new functionality, a list is created containing any PReP partitions that are flagged for formatting. And that list is written to the boot= line of yaboot.conf. Credit where credit is due... Peter Jones developed this version of the patch. (My original didn't work). I've tested it and it writes boot=<dev list> to yaboot.conf accurately. (Slight munging may be necessary--this patch is against booty as of RHEL4). :-Dustin --- booty-0.44/checkbootloader.py 2005-06-14 15:35:38.000000000 -0400 +++ booty-0.44-raid/checkbootloader.py 2005-06-14 15:35:39.000000000 -0400 @@ -75,8 +75,6 @@ dev = string.split(field, '[')[0] if len(dev) == 0: continue - disk = getDiskPart(dev)[0] - rc.append(disk) return rc @@ -117,6 +115,14 @@ dev = string.replace(dev, "'", "") return dev +def getBootDevList(line): + devs = string.split(line, '=')[1] + rets = [] + for dev in devs: + dev = getBootDevString("=%s" % (dev,)) + rets.append(dev) + return string.join(rets) + def getBootloaderTypeAndBoot(instRoot = "/"): haveGrubConf = 1 haveLiloConf = 1 @@ -177,7 +183,7 @@ lines = f.readlines() for line in lines: if line[0:5] == "boot=": - bootDev = getBootDevString(line) + bootDev = getBootDevList(line) if bootDev: return ("YABOOT", bootDev) --- booty-0.44/bootloaderInfo.py 2004-10-04 12:51:41.000000000 -0400 +++ booty-0.44-raid/bootloaderInfo.py 2005-06-14 15:32:30.000000000 -0400 @@ -1501,12 +1501,21 @@ class ppcBootloaderInfo(bootloaderInfo): + def getPrepBootDevs(self, fs): + import fsset + devs = [] + for entry in fs.entries: + if isinstance(entry.fsystem, fsset.prepbootFileSystem) \ + and entry.format: + devs.append('/dev/%s' % (entry.device.getDevice(),)) + return devs + def writeYaboot(self, instRoot, fsset, bl, langs, kernelList, chainList, defaultDev, justConfigFile): from flags import flags - yabootTarget = '/dev/%s' %(bl.getDevice()) + yabootTarget = string.join(self.getPrepBootDevs(fsset)) bootDev = fsset.getEntryByMountPoint("/boot") if bootDev:

3 5

PATCH:mk-images script error causes buildinstall failure
by Prarit Bhargava 29 Jun '05

29 Jun '05

Noticed that the mk-images script causing a buildinstall failure on the ia64 arch. The attached fixes this issue. (I was unsure of how this list wants patches to be presented -- if the patch format that I used, diff -u, is unacceptable please reply with correct patch instructions and I will resubmit.) The bugzilla for this patch is 162072. P. --- usr/lib/anaconda-runtime/mk-images.orig 2005-06-06 18:38:16.000000000 -0400 +++ usr/lib/anaconda-runtime/mk-images 2005-06-29 17:27:37.945567297 -0400 @@ -762,6 +762,7 @@ mkdir -p $MBD_BOOTTREE # provided by the mk-image.$ARCH file + mkdir -p `dirname $MBD_FILENAME` prepareBootImage left=$(df $MBD_BOOTTREE | tail +2) @@ -774,10 +775,7 @@ cp -f $KERNELROOT/$KERNELDIR/${KERNELNAME}-* $EXTRAKERNELPATH fi - mkdir -p `dirname $MBD_FILENAME` - rm -f $MBD_FILENAME - mv -f $MBD_TMPIMAGE $MBD_FILENAME - rm -rf $MBD_TMPIMAGE $MBD_MNTPOINT $MBD_BOOTTREE + rm -rf $MBD_MNTPOINT $MBD_BOOTTREE if [ -z "$INITRDFILE" ]; then rm -f $MBD_FSIMAGE fi --- usr/lib/anaconda-runtime/mk-images.ia64.orig 2005-06-06 18:38:16.000000000 -0400 +++ usr/lib/anaconda-runtime/mk-images.ia64 2005-06-29 17:27:41.528575066 -0400 @@ -14,9 +14,9 @@ IDEMODULES="ide-mod ide-probe-mod ide-disk ide-cd sgiioc4" prepareBootImage() { - dd if=/dev/zero bs=1k count=$BOOTDISKSIZE of=$MBD_TMPIMAGE 2>/dev/null - mkdosfs -C $MBD_TMPIMAGE $BOOTDISKSIZE >/dev/null - mount -o loop -t vfat $MBD_TMPIMAGE $MBD_BOOTTREE + dd if=/dev/zero bs=1k count=$BOOTDISKSIZE of=$MBD_FILENAME 2>/dev/null + mkdosfs -C $MBD_FILENAME $BOOTDISKSIZE >/dev/null + mount -o loop -t vfat $MBD_FILENAME $MBD_BOOTTREE mkdir -p $MBD_BOOTTREE/EFI/boot cp $MBD_FSIMAGE $MBD_BOOTTREE/EFI/boot/initrd.img

1 0

Problems to run anaconda installer with new kernel RPM
by Fabien PERDRIX 25 Jun '05

25 Jun '05

Hi, I use a redhat 9.0 with a 2.4.20-8 kernel. I have to made automatic installation with this OS. Unfortunately it's apparently impossible to run S-ata drivers over this version of kernel. so I decide to upgrade the kernel RPM to the last version (2.4.31). I made without too much difficulties the new kernel RPM and it seems to work fine. I build the anaconda installer without any errors but when i test the installation i have the following problems : ( with Intel ICH6 chipset and a SATA disk) - the driver for the sata chipset is not automaticly loaded, and i need to load it manually from a driver disk i think the problem is in the file pcitable but i can't find how anaconda build it, and when i look to modules.cgz during the installation, my drivers are here. - then the installation go without problem but when the system reboots, lilo doesn't work ! ( i have just "L" on the black screen and the system is frozen ) does anyone have idea about whats happend ? or have links to ressources to help me ? thanks a lot cordialement, Fabien PERDRIX -- Fabien PERDRIX PhéBus Informatique www.phebux.net <http://www.phebux.net> 36A rue des 20 Toises 38950 Saint Martin le Vinoux FRANCE Tél. : (33) 04 76 75 95 95 Fax : (33) 04 76 56 03 55 mel : f_perdrix(a)phebus.fr <mailto:f_perdrix@phebus.fr> ---------------------------------------------------------------------- Ce mel vous a été envoyé à partir du module messagerie de PheBuX équipé d'un Anti-Spam et d'un WebMail. Solution française innovante, fiable et économique, PheBuX est soutenue par l'ANVAR Visitez <http://www.phebux.net> pour vous faire une idée neuve de Linux !!! _____________________________

2 1

SATA disk modules load sequence for FC4 kickstart
by ha haha 24 Jun '05

24 Jun '05

Hi, Ive got another problem for FC4 kickstart installation. The problem is related to SATA module loading sequence. I have a HP workstation XW4200 machine. two SATA disks are connected to motherboard's SATA ports directly, and be detected to /dev/sda, /dev/sdb by former FC2. two other hard disks are connected through Promise SATA cards and detected as /dev/sdc and /dev/sdd. Now when I tried to upgrade it to FC4, it detects the hard drives in different order. FC4 loads sata_promise module first and then ata_piix module. so that former /dev/sd{c,d} are detected as /dev/sd{a,b}, and vice versa. So now I can not do upgrade to FC4 while preserve orignal data on hard disks. If there is a way for me to specify SATA module loading order during unattended kickstart and post-install? Or I have to recompile a new kernel to static-build ata_piix into kernel, and compile sata_promise as a loadable module? MANY thanks. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Problem with getnotincomps.py
by Martin Muench 23 Jun '05

23 Jun '05

Hi everyone I wan't to make a custom version of Fedora Core 4 (some kind of minimal installation). I edited the comps.xml but I stuck on getnotincomps.py when I call it with getnotincomps.py path/to/fedora i386 Fedora/base I get this error: for pkg in comps.packages[name].dependencies: KeyError: 'kernel' The kernel-* rpms are all there. Can anyone help me ?? Thank you

1 0

Re: Anaconda hack
by Matthew Miller 16 Jun '05

16 Jun '05

On Wed, Jun 15, 2005 at 09:28:59AM +0530, Vishal wrote: > Thanks for the reply > I want to do this for redhat linux 7.3 not fedora. Why??? That's a very, very old distribution (and a very old version of anaconda!) > and yes i am ready for the non quick hard work. > Can anyone please tell me where to start as i am somewhat new to anaconda > development. I really think that starting with checking with the others interested in this on the fedora devel list is the way to go. -- Matthew Miller mattdm(a)mattdm.org <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> Current office temperature: 79 degrees Fahrenheit.

2 2

How to recover for booting Windows CD and Windows partitions?
by Andrew Tsang 15 Jun '05

15 Jun '05

I original have 3 Windows XP (different languages) respectively in partition hda1 (1st partition), hda3, and hda4. Partition hda2 was empty. I then repartitioned hda2 to become 3 consecutive partitions & the previous partition hda3 & hda4 became hda5 and hda6 but there was no change with the actual disk location where the 3 Windows partitions resided. Then I installed Red Hat Linux with /boot in hda2, swap in hda3 & / in hda4. I used Grub to configure for multiple boot during the installation. After installation (without error), I was able to boot Linux and Windows XP of hda1 (the 1st partition). But when I booted the Windows XP of either partition hda5 or hda6, booting failed and the following error message was displayed: "The following file is damaged or missing, unable to boot Windows: <Windows root>\system32\hal.dll ...." I tried to recover from the Windows XP installation CD, but I was unable to boot the CD (booting of the CD works on another PC). When the PC displayed "Hit any key to boot from CD ..", I hit ENTER and it displayed "Setup is inspecting your hardware configuration", then screen blanked and the PC hung. I needed to reset the PC and the same process repeated. Booting of the Linux installation CD is fine. Note that the Windows XP installation CDs booted well before the Linux installation. How can I recover the boot record (or something else) so that I can boot from the Windows Installation CD as well as the 2 Windows XP in partition hda5 & hda6? --Andrew Tsang

1 0

Re: Anaconda hack
by Matthew Miller 14 Jun '05

14 Jun '05

On Wed, Jun 15, 2005 at 01:44:27AM +0530, Vishal wrote: > Thanks for the prompt reply, > Yes i want encrypted file system, hardware kes is not actually needed. > i want that the filesystem which should not be mounted by unauthorized > person. There's some work on this for Fedora Core 5. Check the recent fedora-devel archives. Without some major infrastructure support, I don't think this is going to be a quick hack. If you're interested in the non-quick hard work, though, I'm sure the people working on this would appreciate help. -- Matthew Miller mattdm(a)mattdm.org <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> Current office temperature: 81 degrees Fahrenheit.

1 0

Anaconda hack
by Vishal 14 Jun '05

14 Jun '05

Hi all I want to create a customized redhat distribution for the company. I need to hack anaconda, so that when i install it from a CD the resulting installation is such that it the partition/filesystem should not be mounted in any other pc via mount command. Can anyone guide me to accomplish this. Please help Regards Vishal

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