Anaconda-devel August 2008

anaconda-devel@lists.stg.fedoraproject.org

29 participants
24 discussions

[PATCH] removal of libdhcp
by David Cantrell 21 Dec '08

21 Dec '08

No patch attached because it's quite large. I apologize for the length, but considering this replaces a library and introduces a new struct it meant a new file and changing calls everywhere. http://dcantrel.fedorapeople.org/anaconda/iface/ iface.h - Header file explaining the iface API. iface_t structure replacing pumpNetIntf and networkDeviceConfig, and all of the functions. iface.patch - The changes, it's about 90% complete at this point. *.txt - Explanations and notes. This patch removes anaconda's use of libdhcp, which also means removing libdhcp4client and libdhcp6client. For static network configuration, I am using libnl. To gather current network interface information, I am using libnl. To control IPv6 autoconf, I read/ write /proc since that's all we can do right now. For DHCP and DHCPv6, I run dhclient and dhcp6c, respectively. I'd like everyone to have a look at iface.h and the patch file. It's not complete yet, so I probably know about the obvious things (the FIXMEs and the useless debugging printfs and the incomplete isys.py code and so on). The goal with iface.patch is to get us closer to using NetworkManager in stage 1 and stage 2. I envision the NM changeover to be just as large, but hopefully by then we will have decided to nuke certain parts of loader entirely. Completely eliminating libdhcp and friends will be a nice step. There are some other things that need discussion as well. mkinitrd currently uses libdhcp, for example. This had me thinking we could generate libisys in an anaconda-devel package for things like mkinitrd, but I'm just brainstorming. Maybe I should put the iface code elsewhere? I dunno. At any rate, mkinitrd needs to be not left out. Work in progress, comments welcome. -- David Cantrell <dcantrell(a)redhat.com> Red Hat / Honolulu, HI

8 28

[PATCH] Choose logos package
by Jeroen van Meeuwen 07 Sep '08

07 Sep '08

This is a patch that enables choosing a specific -logos package rather then having dependency resolving pull in a package, and using it to build the installer images which usually show whatever logos used, everywhere. Due to (recent) changes in the master branch, I have not yet been able to test this specific changeset but it's derived from what I did against the Fedora 9 branch to make rebranding work. I hope it shows the point of what I'm trying to do and I'll rebase the patch later if necessary. Consider this not yet ready for checkin if you will ;-) The package sack for an initialized yum object is mostly populated with more then one -logos package. Which of these packages is going to satisfy the "system-logos" dependency is (at this moment at least) at best an educated guess (Provides:, Obsoletes:, Conflicts: and/or a significant NEVRA bump don't seem to help). The patch let's one specify a specific -logos package using --logopkg to the buildinstall script, which then excludes a certain set of other, known -logos packages by means of adding a list to the "exclude=" parameter in the $yumconf used, and let's $LOGOPKG be used whereever possible. This relates to bugz 457378 and 457379 (although the former had been fixed already), which were created when trying to have foobarbaz-logos be the -logos package for the brand FooBarBaz Fedora derivative. I think the alternative route is to do fu to the virtual requires/provides mechanism that we have now with "system-logos", and I'm not sure how we could make the one intended (right) package go in that way. Hope this helps, Kind regards, Jeroen van Meeuwen -kanarip

4 5

Network interface configuration with kickstart
by Andreas Zuber 03 Sep '08

03 Sep '08

Hi We have some problems with the automatic installation if the server we want to install, has more than two interfaces to configure. There is now way how i can be sure that a specific network card gets the right configuration after the installation. This is because there is no way to specify the MAC address for a interface. So there is no relation to the real hardware. am i right that the kickstart command "network" just writes the configuration in /etc/sysconfig/network-scripts/ ? Why not also write the MAC adress to this file during installation? This may solve many problems. This way the Network interfaces are all in the right order and we are all happy :-) -- Andreas Zuber Linux System-Ingenieur Puzzle ITC GmbH www.puzzle.ch Telefon +41 31 370 22 00 Direkt +41 31 370 22 49 Mobile +41 79 766 25 51 Fax +41 31 370 22 01 Puzzle ist Mitglied der Eclipse Foundation: <http://www.puzzle.ch/eclipse/>

3 4

usb drive based installs.
by Jerry Vonau 30 Aug '08

30 Aug '08

Hi All: Here is a quick howto: Grab a usb flash drive, I chose a superstore core micro 2gb cost $11.19 cdn, no endorsement just the closest to my house. Insert the drive in to the usb port, mine became usb0 on the desktop, which is sdb1 in /dev. umount it, umount /dev/sdb1. toggle the bootable flag with fdisk, umount again. grab: http://members.shaw.ca/jvonau/pub/mkusbinstall run my mkusbinstall with: mkusbinstall <path/to/iso> /dev/path This creates a boot-able usb-drive based on the boot-able iso filename that was given. If you used a stock fedora boot.iso as the source, you could now boot the flash drive and do any installs except for harddrive based installs. To preform a "usb drive" based install you would need to use disc1 as the source and then copy over disc2-5 to the /iso on the drive. Patches welcome to enable an auto copy of the rest. With the kickstart file that I use, only about 500 packages are used by on disc1 and disc2, so I get away with the 2gb drive. If your usb size is large enough and have a filesystem to support it, I see no reason that you couldn't use the whole set, or use a dvd as the source. For XS, the plan is for one cd sized install disk so this should be no issue then. Just curious if pungi has to produces an iso that is larger that a cd then this should work anyway. Just can't burn the image to cdrom, just now it's a "dvd.iso" but still loopback mountable right? I'll play around later... Jerry

1 0

Rebuilding fedora installer with newer boot kernel
by Jeremy Sanders 29 Aug '08

29 Aug '08

Hi - Is it relatively easy to rebuild a fedora network install disc (to install over nfs with kickstart) with a newer boot kernel? We have a system which only boots with an updated kernel, so it would be nice to be able to install this system with kickstart. Are there any docs for doing this? This is with Fedora 8. Thanks Jeremy -- Jeremy Sanders <jss(a)ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/

2 1

Reipl support
by Mark Hamzy 28 Aug '08

28 Aug '08

Hello, I am working on a feature for the 390 architecture called reipl. It allows the vm to be rebooted into a specific partition. On scenario where this would be usefull is after the initial install, the vm should boot from the newly installed partition and not from the reader (where it initially booted from). It constists of three peices. 1) A Python module, Reipl.py, which reads and writes the settings from the firmware (among other things). 2) A patch to anaconda main python module. At the end of the installation, it will call Reipl.py with the boot partition. It will then write the success of reipl into a file called /var/run/sigusr. 3) A patch to anaconda's loader to read the file /var/run/sigusr and send the appropriate signal (either shutdown or reboot) to linuxrc process. Open issues: 1) Currently, Reipl.py is hard installed into /usr/sbin. I would like to create an rpm package for Reipl consisting of just that file. Is /usr/sbin a good place for it? 2) /usr/sbin is not in sys.path. I have to append sys.path before importing Reipl. Is this okay? Are there any other issues with this code? (See attached file: anaconda-11.1.2.113.patch) (See attached file: Reipl.py) Mark Common Information Model/Web-Based Enterprise Management at http://www.openpegasus.org/ Take a look at the Linux Omni Printer Driver Framework at http://omniprint.sourceforge.net/

5 15

[PATCH] write yum repos used during install under /etc/yum.repo.d/
by Alexander Todorov 26 Aug '08

26 Aug '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Good afternoon list, I've seen people asking for this feature from time to time. The code below comes from the RHEL5 branch but was commented out. Last time I've tested it with RHEL5 it was breaking. I did some slight modifications to the original code and tested this with F9 and it works for me. As you can see only http(s) and ftp repos are written to config files. - --- ~ yuminstall.py | 19 +++++++++++++++++++ ~ 1 files changed, 19 insertions(+), 0 deletions(-) diff --git a/yuminstall.py b/yuminstall.py index ad7615a..dcff552 100644 - --- a/yuminstall.py +++ b/yuminstall.py @@ -1952,6 +1952,25 @@ reposdir=/etc/anaconda.repos.d,/tmp/updates/anaconda.repos.d,/tmp/product/anacon ~ f.write("-%s\n" % pkg) ~ def writeConfiguration(self): + emptyRepoConf = yum.config.RepoConf() + compulsorySettings = [ 'enabled', 'cost' ] + for repo in self.ayum.repos.listEnabled(): + for url in repo.urls: + if url.startswith('http://') or url.startswith('https://') or url.startswith('ftp://'): + fn = "%s/etc/yum.repos.d/%s.repo" % (self.instPath, repo.id) + f = open(fn , 'w') + f.write('[%s]\n' % (repo.id,)) + for k, v in emptyRepoConf.iteritems(): + repoval = repo.getAttribute(k) + if not (k in compulsorySettings): + if not repoval or (repoval == v): + # continue the k, v loop + continue + val = emptyRepoConf.optionobj(k).tostring(repoval) + f.write("%s=%s\n" % (k,val)) + f.close() + # break out of the urls loop + break ~ return ~ def getRequiredMedia(self): Thanks, Alexander. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFIlvlXhmd3WOiFct4RCl03AKCzpSSu8vPREYlri0miioSKoXTjKwCfVney bCTG52FWgSsDjnhfL4OCbCY= =7RjT -----END PGP SIGNATURE-----

4 11

[PATCH] "Invalid Entry for Partition Size" when "Fill all available space" selected
by Mark Hamzy 26 Aug '08

26 Aug '08

The following is from the IBM bugzilla that I am looking at: I am testing RHEL5.1 GA. When creating the file system, I use "Fill all available space" to use up all the free space. The problem is that when I clear out the value for "Size (MB)" and then click ok, anaconda asks me to provide a value. But this value doesn't make any sense to this option. ┌────────┌────────────────────┤ Add Partition ├────────────────────┐─────────┐ │ │ │ │ │ │ Mount Point:/___________________ │ oint │ │ /dev/sd│ │ ↑ │ │ sda1 │ File System type: Allowable Drives: │ ? │ │ Free │ ext2 ↑ [*] sda ? │ ? │ │ /dev/sd│ ext3 ? [ ] sdb ↓ │ ? │ │ sdb1 │ │ ? │ │ sdb2 │ Size (MB): _______ ( ) Fixed Size: │ ? │ │ Free │ ( ) Fill maximum size of (MB): 1____ │ ? │ │ │ (*) Fill all available space: │ ? │ │ │ │ ? │ │ │ [ ] Force to be a primary partition │ ↓ │ │ │ │ │ │ ┌─│ ┌────┐ ┌────────┐ │ │ │ │ │ │ OK │ │ Cancel │ │ │ │ └─│ └────┘ └────────┘ │ │ │ │ │ │ │ │ │ │ └────────└─────────────────────────────────────────────────────────┘ ────────┘ ┌────────┌────────────────────┤ Add Partition ├────────────────────┐─────────┐ │ │ │ │ │ │ Mount Point:/___________________ │ oint │ │ /dev/sd│ │ ↑ │ │ sda1 │ File System type: Allowable Drives: │ ? │ │ Free │ ext2 ┌┤ Invalid Entry for Partition Size ├─┐da ? │ ? │ │ /dev/sd│ ext3 │ │ b ↓ │ ? │ │ sdb1 │ │ Must specify a value │ │ ? │ │ sdb2 │ Size (MB│ │ : │ ? │ │ Free │ │ ┌────┐ │ : 1____ │ ? │ │ │ │ │ OK │ │ : │ ? │ │ │ │ └────┘ │ │ ? │ │ │ │ │ │ ↓ │ │ │ │ │ │ │ │ ┌─│ └─────────────────────────────────────┘ │ │ │ │ │ │ │ │ └─│ └────┘ └────────┘ │ │ │ │ │ │ │ │ │ │ └────────└─────────────────────────────────────────────────────────┘ ────────┘ I have noticied that this is not a problem in the graphical installation because that entry box keeps getting reset to 1. Rather than attempt that same behavior, I just set that value to 1 if there was an error in the number when "Fill maximum size" and "Fill all available" are selected. (See attached file: 41618.Fedora10.patch) Mark Common Information Model/Web-Based Enterprise Management at http://www.openpegasus.org/ Take a look at the Linux Omni Printer Driver Framework at http://omniprint.sourceforge.net/

2 1

Crash in Anaconda Loader during Network install
by Vinay Y S 26 Aug '08

26 Aug '08

While doing network install of Fedora 7 on a Supermicro server using cobbler-based setup, the Anaconda loader is crashing. It prints the backtrace and dies. How do I make sense of that backtrace? Is there a easier way (like attaching gdb upon start) to debug this issue? Please let me know how to get more information that can help solving this crash. Thanks, -- Vinay Y S

2 1

Regarding RAM Management in FC
by Debasis Mahapatra 22 Aug '08

22 Aug '08

Dear All, Hi! I am back with another querry. First, I want to thank David Hopkins for his useful advice regarding installation of Fedora Core on T7400 Dell Workstation. Now, I have another issue. We have got five Dell T7400 workstations which has come with pre-installed Windows XP Pro. It has 1 TB HDD, 32 GB RAM, 1.5GB NVDIA card, etc. In windows it can (detect) use only 4 GB of RAM which may be the limitation of XP. Now, I have put Fedora Core 8 (32 bit) on this machine (I have tried FC9 but it was showing some signal problem regarding monitor, but I have the required resolution and frequency in the monitor) and everything is working fine. But, the only problem is here also it is taking (using) only 4 GB of RAM. It is a dual boot machine now having Windows Xp and Fedora Core 8. So my question is if there is a way to use all my 32 GB RAM and how. I would be grateful if someone can advice me on this. Thanking you all Debasis -- Debasis Mahapatra Project Scientist CAS, IIT Delhi Hauz Khas New Delhi 110 016

5 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel August 2008