Anaconda-devel November 2011

anaconda-devel@lists.stg.fedoraproject.org

25 participants
38 discussions

Simple patch for text mode (resolves #737452)
by Vratislav Podzimek 03 Jan '12

03 Jan '12

If we go in a backward direction through the noninteractive step network in text mode we want it to pass through to the previous step. -- Vratislav Podzimek

2 3

[LORAX 0/6] Add livemedia-creator to lorax
by Brian C. Lane 21 Dec '11

21 Dec '11

From: "Brian C. Lane" <bcl(a)redhat.com> The wait is over. I think this stuff is now in good enough shape for others to start using it and providing feedback. The README.livemedia-creator file attempts to document things, or failing that, read the source :) I plan on adding this as a sub-package in the lorax.spec, I haven't done that yet because I wanted to get this out there with enough time for some feedback before vacation next week. The idea behind this is to integrate all live media creation (isos, disk images, ami images, appliances, etc.) into lorax and anaconda. In its current state it will create bootable iso's which can be installed if you set LIVE_BLOCK=/dev/loop1 before running liveinst. See the README for more info and for future plans. Brian C. Lane (6): Changes needed for livecd creation Add execWith utils from anaconda Allow a None to be passed as size to create_runtime Add livemedia-creator Add config files for live media Add livemedia-creator README and example ks README.livemedia-creator | 170 ++++++++ docs/fedora-livemedia.ks | 388 +++++++++++++++++++ share/config_files/live/x86/boot.msg | 5 + share/config_files/live/x86/grub.conf | 8 + share/config_files/live/x86/isolinux.cfg | 98 +++++ src/pylorax/executils.py | 379 ++++++++++++++++++ src/pylorax/imgutils.py | 64 +++ src/pylorax/treebuilder.py | 14 +- src/sbin/livemedia-creator | 623 ++++++++++++++++++++++++++++++ 9 files changed, 1747 insertions(+), 2 deletions(-) create mode 100644 README.livemedia-creator create mode 100644 docs/fedora-livemedia.ks create mode 100644 share/config_files/live/x86/boot.msg create mode 100644 share/config_files/live/x86/grub.conf create mode 100644 share/config_files/live/x86/isolinux.cfg create mode 100644 src/pylorax/executils.py create mode 100755 src/sbin/livemedia-creator -- 1.7.6.4

4 12

Proposal to move install classes info to repository
by Martin Sivak 06 Dec '11

06 Dec '11

Hi guys, I have written a summary of my discussion with dcantrell and dmach from release engineering. https://fedoraproject.org/wiki/Anaconda/Features/InstallClassesInRepo Might be worth a thought. -- Martin Sivák msivak(a)redhat.com Red Hat Czech Anaconda team / Brno, CZ

4 12

Anaconda UI rewrite + AutoQA
by Kamil Paral 02 Dec '11

02 Dec '11

On our last QA meeting Adam Williamson notified us that there would be an Anaconda hackfest at the next FUDCon and we should raise our concerns (if we had some) regarding AutoQA and the UI re-write. Well, I don't know much about anaconda testing inside AutoQA, I just know we execute some anaconda tests, that's all. But I decided to kick off the discussion and CC relevant people. >From what I know, we have two kind of anaconda tests inside AutoQA: 1. older rats_install test written by Will Woods and executed James Laska in the past 2. newer anaconda_storage, anaconda_checkbot and compose_tree written by Chris Lumens and James Laska I am not sure which of those tests provide important feedback to the anaconda team and whether they are being used at all. Can relevant people provide more details about it? Anaconda team, do you have some specific questions about AutoQA integration and the UI re-write? Will you want to change your tests inside AutoQA in response the new UI and need to have some information from us? I'll happy to answer them if I can. Also, if the test authors have some comments or recommendation about the new UI architecture in order to allow simple automated testing, please post them here. Thanks, Kamil

3 7

[rhel6-branch 1/4] Add curl to the install image (#625697)
by Martin Gracik 29 Nov '11

29 Nov '11

--- scripts/upd-instroot | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/scripts/upd-instroot b/scripts/upd-instroot index a318374..99dc580 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -160,7 +160,7 @@ PACKAGES="GConf2 NetworkManager NetworkManager-gnome ORBit2 acl anaconda biosdevname bitmap-fangsongti-fonts btrfs-progs bzip2 bzip2-libs ca-certificates cairo cjkuni-uming-fonts comps-extras coreutils cpio cracklib cracklib-dicts cracklib-python - cryptsetup-luks cyrus-sasl-lib db4 dbus dbus-python dbus-x11 dejavu-sans-fonts + cryptsetup-luks curl cyrus-sasl-lib db4 dbus dbus-python dbus-x11 dejavu-sans-fonts dejavu-sans-mono-fonts device-mapper device-mapper-libs device-mapper-multipath device-mapper-multipath-libs dhclient dmraid dmraid-libs @@ -542,6 +542,7 @@ usr/bin/Xvnc usr/bin/chattr* usr/bin/chvt usr/bin/clear +usr/bin/curl usr/bin/dbus-launch usr/bin/dbus-launch usr/bin/du -- 1.7.5.4

2 4

[PATCH] Update ppc SMS bios after installation
by Mark Hamzy 29 Nov '11

29 Nov '11

Here is a proposed patch that updates a PowerPC's BIOS to boot from the newly installed hard disk rather than back to the installer. The BIOS maintains a list of bootable targets which can be queried with the nvram utility. This list can be modified so that the installation harddrive will show up first. This code will read the list, figure out what drive contains the PReP partition, prepends that drive to the list, and then updates BIOS. For example the list could be the DVD, hard drive, and ethernet. [anaconda root@(none) /]# nvram --print-config=boot-device /vdevice/v-scsi@30000005/disk@8100000000000000 /vdevice/v-scsi@30000002/disk@8100000000000000 /vdevice/l-lan@30000003:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 After running this function, the list will be as follows: [anaconda root@(none) /]# nvram --print-config=boot-device /vdevice/v-scsi@30000002/disk@8100000000000000 /vdevice/v-scsi@30000005/disk@8100000000000000 /vdevice/l-lan@30000003:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 --- pyanaconda/bootloader.py | 58 ++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 58 insertions(+), 0 deletions(-) diff --git a/pyanaconda/bootloader.py b/pyanaconda/bootloader.py index 1150335..84466cd 100644 --- a/pyanaconda/bootloader.py +++ b/pyanaconda/bootloader.py @@ -1877,6 +1877,64 @@ class IPSeriesYaboot(Yaboot): config.write("nonvram\n") # only on pSeries? config.write("fstype=raw\n") + # + # installation + # + + def install(self, install_root=""): + self.updatePowerPCBootList() + + super(IPSeriesYaboot, self).install(install_root=install_root) + + def updatePowerPCBootList(self): + + log.debug ("updatePowerPCBootList: self.stage1_device.path = %s" % self.stage1_device.path) + + buf = iutil.execWithCapture("nvram", + ["--print-config=boot-device"], + stderr="/dev/hvc1", + root="/") + + if len(buf) == 0: + log.error ("FAIL: nvram --print-config=boot-device") + + return + + boot_list = buf.strip ().split () + + log.debug ("updatePowerPCBootList: boot_list = %s" % boot_list) + + buf = iutil.execWithCapture("ofpathname", + [self.stage1_device.path], + stderr="/dev/hvc1", + root="/") + + if len(buf) > 0: + boot_disk = buf.strip () + log.debug ("updatePowerPCBootList: boot_disk = %s" % boot_disk) + + else: + log.error ("FAIL: ofpathname %s" % self.stage1_device.path) + + return + + # Place the disk containing the PReP partition first. + # Remove all other occurances of it. + boot_list = [boot_disk] + filter (lambda x: x != boot_disk, boot_list) + + log.debug ("updatePowerPCBootList: updated boot_list = %s" % boot_list) + + update_value = "boot-device=%s" % (" ".join (boot_list),) + + rc = iutil.execWithRedirect("nvram", ["--update-config", update_value], + stdout="/dev/hvc1", stderr="/dev/hvc1", + root="/") + if rc: + log.error ("FAIL: nvram --update-config %s" % update_value) + + else: + log.info ("Updated PPC boot list with the command: nvram --update-config %s" % update_value) + class MacYaboot(Yaboot): prog = "mkofboot" -- 1.7.7

1 0

Return of NoLoader
by Will Woods 29 Nov '11

29 Nov '11

Courtesans and gentlefops! May I direct your attention to: https://fedoraproject.org/wiki/Anaconda/Features/NoLoader In particular, please note the Scope section, which might also be titled the Big Damn List Of Stuff To Do. The short summary is: Yes, we're really trying to remove loader this time, for real. And it's gonna take some work. So I'm looking for advice and assistance in the following areas: == Boot Option Priorities == Some of these things (ks=, lang=, ip=) are obviously important; some of them are obviously less important (nousb, noprobe), and some of them I'm just not sure if anyone uses them (gdb=, syslog=, wepkey=). If you (or someone you know) depends on any of these things, please give us some information on how and why you use them, so we can make sure things work as expected - and get your help with testing! == Porting to Dracut == Some of these things will probably end up in upstream dracut (e.g. network stuff can go in the 40network module), but a lot of things will end up in our own special dracut module (80anaconda). I'll need some assistance getting all that done for F17, so if you've got some bash skill and want to help with dracut development, this is a perfect place to help make a difference in the quality and stability of the next release! Let me know if you can help, so I have some idea how many people may be involved (and set goals/deadlines appropriately). == General Sanity Checking == Does this plan look sound to everyone? Can we all agree that dropping the stage1 interactive stuff is sane (remember, we'll still have a text-mode installer in the anaconda runtime - just no more dialogs in initrd.img)? Is there anything missing, any improvements you could suggest? Once we've got a finished plan of attack, I might take this to devel-list just to be sure they're all aware (and see if we can solicit further info/assistance). Thanks, -w

6 15

Bringing up the network and errors
by Mark Hamzy 24 Nov '11

24 Nov '11

If I boot with "linux askmethod" and the network fails to come up, anaconda does not bring up the manual network configuration dialog. However, if I boot with "linux vnc", the dialog will come up after the failure. Does this sound like a bug to you all? It seems like in readNetConfig(), LOADER_FLAGS_ASKNETWORK is not set. So, after wait_for_iface_activation() fails, it returns out. -- Mark You must be the change you wish to see in the world. -- Mahatma Gandhi Never let the future disturb you. You will meet it, if you have to, with the same weapons of reason which today arm you against the present. -- Marcus Aurelius

2 1

ksdevice=link does not seem to work
by Dusty Mabe 23 Nov '11

23 Nov '11

Hi Guys, When I attempt a network install and specify ksdevice=link on a machine with multiple nics I end up getting an interactive install. The behavior seems very similar to bugzilla report 549751 https://bugzilla.redhat.com/show_bug.cgi?id=549751 . Is this a known problem? I am using the anaconda in CentOS 6. anaconda-13.21.82-1.el6.centos.1.x86_64.rpm Thanks for any help! Dusty Mabe

2 1

Grubby improvements for use in autotest
by Cleber Rosa 22 Nov '11

22 Nov '11

We have been trying to use Grubby as the booloader entries manager for autotest. We have found along the way that we could use some extra features, and here are a couple of them. Expect more to follow. Sending early hoping to get feedback. Series summary: [PATCH 1/5] Makefile: do not link against glib-2.0 [PATCH 2/5] GRUB: Fix detection by increasing offset when comparing [PATCH 3/5] test.sh: add feature for testing the output of a grubby [PATCH 4/5] Add new '--default-index' feature. [PATCH 5/5] Add new '--default-title' feature.

1 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 November 2011