Anaconda-devel May 2005

anaconda-devel@lists.stg.fedoraproject.org

25 participants
30 discussions

Removing Fedora Name
by Sohail Riaz 29 May '05

29 May '05

Hi i created my desired customize linux but cant remove Fedora name appearing in different places like in Checking of the media "Welcome to Fedora Core", and "Running anaconda, the Fedora Core System installer". Please help me out in removing Fedora Name Thanks in advance

2 1

Fix dual disk macs so we don't corrupt disk1/part1
by Paul Nasrat 25 May '05

25 May '05

OF is clever, we don't need to be on first disk: Tested working on G4. Paul

1 0

158696 patch
by Chris Lumens 25 May '05

25 May '05

I believe what's going on with this bug is that the VG editor is using the sizes of the preexisting PVs (because they have not been deleted yet) instead of the new PV request. Crazy or not? - Chris Index: iw/lvm_dialog_gui.py =================================================================== RCS file: /usr/local/CVS/anaconda/iw/lvm_dialog_gui.py,v retrieving revision 1.46 diff -u -r1.46 lvm_dialog_gui.py --- iw/lvm_dialog_gui.py 12 Mar 2005 03:01:54 -0000 1.46 +++ iw/lvm_dialog_gui.py 25 May 2005 17:53:10 -0000 @@ -308,13 +308,18 @@ sw.set_policy(gtk.POLICY_NEVER, gtk.POLICY_AUTOMATIC) sw.set_shadow_type(gtk.SHADOW_IN) - for uid, size, used in alllvmparts: + for part in alllvmparts: + uid = part[0] request = partitions.getRequestByID(uid) + if request.type != REQUEST_RAID: partname = "%s" % (request.device,) else: partname = "md%d" % (request.raidminor,) + size = request.getActualSize (partitions, self.diskset) + used = part[2] + # clip size to current PE pesize = int(self.peCombo.get_active_value()) size = lvm.clampPVSize(size, pesize) @@ -338,7 +343,11 @@ """ row = 0 - for uid, size, used in alllvmparts: + for part in alllvmparts: + uid = part[0] + request = partitions.getRequestByID(uid) + size = request.getActualSize(partitions, self.diskset) + # clip size to current PE pesize = int(self.peCombo.get_active_value()) size = lvm.clampPVSize(size, pesize)

2 1

anaconda branched for fc4
by Jeremy Katz 25 May '05

25 May '05

anaconda has been branched for the Fedora Core 4 freeze. Branch is fc4-branch. All sorts of craziness is likely to commence on HEAD before long :-) Jeremy

2 2

ask a question about buildinstall,thanks a lot in advance;-)
by 王秀文 25 May '05

25 May '05

everyone, Hello. I have updated the kernel-related rpm packages including kernel,kernel-BOOT,kernel-smp and so on.That is that we use our own kernel rpm packages. I have not customized anaconda.Do i need to run "buildinstall" command?I just use the *.img files included in FC1 distribution. By the way,What "buildinstall" command do?What files "buildinstall" command create? I try to run it,then it created files below. images/bootdisk.img images/drvblock.img images/drvnet.img images/pcmciadd.img images/pexboot/vmlinuz images/README Fedora/base/hdstg2.img Fedora/base/netstg2.img Fedora/base/stag2.img If I have missed some files buildinstall should create,please let me know. Thanks a lot lot lot! mosquite

1 0

patch for manual partition growing
by Chris Lumens 23 May '05

23 May '05

We'd noticed that when manually partitioning the disk, some amount of space was left free at the end of the disk after growing partitions. In particular, the amount of free space was equal to the contents of the "Size (MB)" field on the Edit Partition screen. This first started appearing after an autopart.py fix for dual booting on Mac OS X. It being late on a Friday and partitioning code being hard enough to stare at even normally, here's the patch for everyone else to review before we commit. I'm wondering if this rebreaks the Mac OS X case or not. We don't think so, but I'd like some confirmation. - Chris Index: autopart.py =================================================================== RCS file: /usr/local/CVS/anaconda/autopart.py,v retrieving revision 1.166 diff -u -r1.166 autopart.py --- autopart.py 6 May 2005 19:42:52 -0000 1.166 +++ autopart.py 20 May 2005 21:28:07 -0000 @@ -621,12 +621,12 @@ del free[key] continue freeSize[key] = 0 - largestFree[key] = 0 + largestFree[key] = (0, 0) for part in free[key]: sz = partedUtils.getPartSize(part) freeSize[key] += sz - if sz > largestFree[key]: - largestFree[key] = sz + if sz > largestFree[key][0]: + largestFree[key] = (sz, part.geom.start) return (free, freeSize, largestFree) @@ -789,8 +789,8 @@ maxsect = long(maxFSSize) imposedMax = 1 - maxfree = largestFree[drive] - if maxsect > largestFree[drive]: + (maxfree, freestart) = largestFree[drive] + if maxsect > maxfree + freestart: maxsect = long(maxfree) imposedMax = 1

2 1

Error after Anaconda Customization
by Sohail Riaz 23 May '05

23 May '05

I customize the anaconda installer that it only install my set of packages. But it failed during the RPM TRANSACTION STEP. What will be the problem; following steps i've been taken 1) edit the comps.xml 2) did'nt create comps.rpm, if i want how i do it 3) buildinstall failed , therefore i use to edit stage2.img Regards,

1 0

anaconda_header.png
by fonteneau 20 May '05

20 May '05

Hi, I'm working with FC3 and anaconda to create my own distribution. I'm triing for long time to modify the anaconda_header.png image to have my own during the installation. I've change the anaconda RPM sources and also fedora-logos RPM sources to put my own anaconda_header.png. I've regenerate the RPM for anaconda and fedora-logo, installed them on the devel distribution and in the buildtree architecture. The when running buildinstall and making the iso cdrom, I've always the original anaconda_header.png during the installation. Do I made something wrong ? shure ;o) Thanks for help Vincent

2 1

lvm volume goup pe size limitation
by David Maciejak 19 May '05

19 May '05

Hi, Included a patch to modify /usr/lib/anaconda/fsset.py to assign by default pesize to 32Mo as it is mentioned in new version of vgcreate man extract below. "To limit kernel memory usage, there is a limit of 65536 physical extents (PE) per logical volume, so the PE size determines the maximum logical volume size. The default PE size of 32MB limits a single logi- cal volume to 2TB (see the -s option to change that limit). There is also (as of Linux 2.4) a kernel limitation of 2TB per block device." Without this patch max volume group is 65536*4Mo (hardcoded in anaconda) which is about 256Go. Since RHEL 3.0 update 1, we can set pesize option on volgroup from ks but default value to 32Mo should be great. Could you apply this patch on current? Thanks David Maciejak

2 1

PATCH - software raid for ppc on installation
by Dustin Kirkland 19 May '05

19 May '05

Anaconda people- The attached patch enables the setup of software RAID on IBM PowerPC installations. The functionality was overwhelmingly already present, however a few things had to be enabled for this platform, and a few additional sanity checks seemed a good idea... The following changes were necessary and are represented in the attached patch: 1) The prepbootFileSystem must have the PARTITION_BOOT flag and ppc must be listed in the raidBootArches 2) All PReP partitions must be the first partition on their disc--not 'at least one of them', if you want to be able to automatically failover to boot off of another disc. This involved a little rearranging of tricky little hack in autopart.py. Somebody please sanity-check my change here...it does what I want it to do, but I certainly don't want to boondoggle someone else (ie another platform). I think this should be contained only to PPC, but have a look and see what you think. 3) Additionally, if you choose to RAID your /boot partition, the only level that makes sense (to me anyway) is RAID1. So I added a check in the anaconda gui that ensures this. Note that this will affect all platforms, but this seems sensible to me. I don't know of any bootloaders that are able to read anything other than a mirrored RAID filesystem. Correct me here? ... 4) Additionally, this functionality also depends on a separate patch I've submitted to the yaboot-devel list. That patch will handle the writing of yaboot to each and every PReP partition, as well as adding the functionality needed for the bootloader to read filesystems marked as "Linux RAID". Questions? Comments? Dustin

3 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel May 2005