Anaconda-devel July 2012

anaconda-devel@lists.fedoraproject.org

30 participants
33 discussions

newui networking todo
by Radek Vykydal 27 Jul '12

27 Jul '12

I put newui networking todo, notes, questions here: https://fedoraproject.org/wiki/Anaconda/Network#Newui_networking_TODO Radek

1 0

[rhel5-branch] Syslinux changed paths from /usr/lib to /usr/share (#843290)
by Martin Gracik 27 Jul '12

27 Jul '12

--- scripts/mk-images | 2 +- scripts/mk-images.x86 | 6 +++--- scripts/upd-instroot | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/scripts/mk-images b/scripts/mk-images index 61dc004..4823ad0 100755 --- a/scripts/mk-images +++ b/scripts/mk-images @@ -886,7 +886,7 @@ done doPostImages # do some clean up before making the cramfs of the second stage -rm -rf $INSTIMGTEMPLATE/usr/lib/anaconda-runtime $INSTIMGTEMPLATE/usr/lib/syslinux $IMGPATH/usr/lib/syslinux +rm -rf $INSTIMGTEMPLATE/usr/lib/anaconda-runtime $INSTIMGTEMPLATE/usr/share/syslinux $IMGPATH/usr/share/syslinux if [ -n "$foundakernel" ]; then # make the second stage diff --git a/scripts/mk-images.x86 b/scripts/mk-images.x86 index 38556f6..d56d782 100644 --- a/scripts/mk-images.x86 +++ b/scripts/mk-images.x86 @@ -1,4 +1,4 @@ -SYSLINUX=$IMGPATH/usr/lib/syslinux/syslinux-nomtools +SYSLINUX=$IMGPATH/usr/share/syslinux/syslinux-nomtools if [ ! -f $SYSLINUX ]; then echo "Warning: nomtools syslinux doesn't exist" @@ -67,12 +67,12 @@ makeBootImages() { --modules "$INITRDMODS" [ $? = 0 ] || exit 1 - if [ -f $IMGPATH/usr/lib/syslinux/isolinux.bin ]; then + if [ -f $IMGPATH/usr/share/syslinux/isolinux.bin ]; then echo "Building isolinux directory" MBD_BOOTTREE=$TOPDESTPATH/isolinux MBD_FSIMAGE=$TOPDESTPATH/images/pxeboot/initrd.img mkdir $MBD_BOOTTREE - cp $IMGPATH/usr/lib/syslinux/isolinux.bin $MBD_BOOTTREE/isolinux.bin + cp $IMGPATH/usr/share/syslinux/isolinux.bin $MBD_BOOTTREE/isolinux.bin prepareBootTree diff --git a/scripts/upd-instroot b/scripts/upd-instroot index d83d375..b18675d 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -775,7 +775,7 @@ usr/$LIBDIR/python?.?/site-packages/cairo/* usr/$LIBDIR/python?.?/site-packages/gtk*/gtk/* usr/$LIBDIR/python?.?/site-packages/gtk*/* usr/$LIBDIR/rpm/rpmpopt -usr/lib/syslinux/* +usr/share/syslinux/* usr/lib/yaboot/* usr/sbin/chroot usr/sbin/ddcprobe -- 1.7.9.5

2 1

First mock up of new text UI
by Jesse Keating 25 Jul '12

25 Jul '12

I spent today thinking through text installs in newui. While I believe that text installs should have minimalistic configuration options, I also believe that the little it has should follow the same sort of idea as the hub/spoke design of newui. Another requirement of text mode is that the same UI work across all text interfaces (real tty, serial, ssh, s390 x3270 shell, etc...), targeting the lowest common platform. For systems like s390x that means no curses, no fancy screen widgets, just dumb text printed on a somewhat narrow screen with no scrolling capability. What I've done is a hacky mock up of how a text install would progress. Some of these config options might go away (like lang/keymap since we have good command line argument options for these). The idea is the same as newui. A hub from which configuration can be done in any order, but also with some items that are required to be completed. Of note, I brought back the root password selection because with text mode you only get @minimal, and thus no firstboot. We don't want people to have to root their machines just to get a password set. This is pretty much the cmdline UI slightly re-designed. You'll find a series of screen shots at http://jkeating.fedorapeople.org/textui/ Walk through them as numbered (yes I'm missing a 2-...). I have no idea yet if we can handle many choice screens like lang and keyboard. Timezone data can be broken down much how tzselect does it. Feedback would be appreciated! -- Jesse Keating Fedora -- Freedom² is a feature!

6 13

mdraid DDF container support
by Jared_Dominguez＠DELL.com 25 Jul '12

25 Jul '12

Greetings, I've been working on a feature to add DDF container support using mdraid to Anaconda. It should be building on the work done to support IMSM containers using mdraid instead of dmraid. I've been hoping to have a patch ready already, but I'm running into some problems related to differences in how metadata for the two container formats is exposed. This is also the first time I've worked on Anaconda so am still familiarizing myself with the codebase. For IMSM, Anaconda has a udev rule that gets a value for MD_DEVICES: ENV{ID_FS_TYPE}=="isw_raid_member", IMPORT{program}="$env{ANACBIN}/mdadm --examine --export $tempnode" Alas, for DDF, the same rule doesn't get a value for MD_DEVICES. One can get this information for DDF by first doing "mdadm -A -e ddf --scan". Subsequently, "mdadm --detail --export /dev/md127" will give MD_DEVICES. However, it seems to me to be a poor practice to assemble any arrays in 70-anaconda.rules. Besides, while testing, Anaconda seems not to like this in there anyway: ENV{ID_FS_TYPE}=="ddf_raid_member", RUN+="$env{ANACBIN}/mdadm -A -e ddf --scan" KERNEL=="md[0-9]*|md_d[0-9]*|md/*", IMPORT{program}="$env{ANACBIN}/mdadm --detail --export $tempnode" It interferes with Anaconda accessing the array with mdadm, causing Anaconda to hang indefinitely. Might anyone with more Anaconda development experience have suggestions for where to try collecting this one piece of information? --Jared -- Jared Dominguez Linux Engineering Dell | Enterprise Product Group

2 2

glade files
by Chris Lumens 25 Jul '12

25 Jul '12

I made a mistake when adding these glade files. I should have given them the default .glade extension instead of .ui like I thought was the standard. xgettext requires that they have a .glade extension to be picked up for translation. So, I'm going to push a patch that moves everything. I hate having to do this because it screws up git history unless you use the --follow option. On the other hand, who ever looks at the git history of a UI file? - Chris

1 0

anaconda disk image partitioning question
by David A. Marlin 25 Jul '12

25 Jul '12

I am using livemedia-creator on F17 to create a disk image. I manually select the partitioning scheme in the kickstart: clearpart --all part /boot --size 255 --fstype ext3 --label=boot part swap --size 511 part / --size 3327 --fstype ext4 --label=rootfs Previously I created several disk images and they all had the partitions in the following order: 1 - /boot 2 - swap 3 - / (root) I created another disk image today, but the partitions are now in the following order: 1 - /boot 2 - / (root) 3 - swap The reason this is significant is that after installing the disk image onto physical media I want to be able to resize the root partition ('/'), and that is only practical if it is the last partition on the image. So my question is, what determines the order of the partitions on a disk image, and is there a way to select, or guarantee a specific order? Thank you, d.marlin

2 2

Release criteria vs. Anaconda
by Petr Schindler 23 Jul '12

23 Jul '12

Hi, I'd like to ask you. Which interfaces you want to stop support? I've read that there won't be text interface. Are there any other changes which we should reflect in release criteria [1][2][3]? [1] https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria [2] https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria [3] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria

2 1

[PATCH anaconda/master] Add support to determine the ARM processor variety and select the correct kernel to install.
by David A. Marlin 20 Jul '12

20 Jul '12

Attached is my latest version of the ARM processor variety patch. It incorporates suggestions made previously, and was made against anaconda/master (but applied to 17.29 for testing). I simplified the hash/lookup by consolidating some machine types, but I understand this may still be unacceptable. I am currently tracking master and carrying these patches locally. I keep the rpms in a local repo for testing. We are working on a method of exposing the platform in userspace, but that is not in place yet. Would it be possible to accept this as an interim solution with the expressed intent that the hash would be removed as soon as an alternative solution is available? If not, would a version of this patch with the hash/lookup stubbed out be acceptable? I would like to get as much of this upstream as possible, to minimize the patch(es) I need to carry locally and simplify keeping up with master. Any suggestions are appreciated. Note: We successfully completed a test kickstart install on an ARM system today using the modified anaconda-17.29. d.marlin

6 12

[PATCH] Re-remove fedora-import-state
by Will Woods 18 Jul '12

18 Jul '12

Commit c8c14c9 deleted these two files, but they got resurrected in some merge somehow. Delete them again, since we don't need them. --- data/systemd/fedora-import-state | 14 -------------- data/systemd/fedora-import-state.service | 13 ------------- 2 files changed, 27 deletions(-) delete mode 100644 data/systemd/fedora-import-state delete mode 100644 data/systemd/fedora-import-state.service diff --git a/data/systemd/fedora-import-state b/data/systemd/fedora-import-state deleted file mode 100644 index a853ab9..0000000 --- a/data/systemd/fedora-import-state +++ /dev/null @@ -1,14 +0,0 @@ -#!/bin/bash -# fedora-import-state: import state files from initramfs (e.g. network config) - -# exit early if root isn't writeable -[ -w / ] || exit 0 - -# copy state into root -cd /run/initramfs/state -cp -a -t / . - -# run restorecon on the copied files -if [ -e /sys/fs/selinux/enforce ]; then - find . | ( cd /; restorecon -i -f -; ) || : -fi diff --git a/data/systemd/fedora-import-state.service b/data/systemd/fedora-import-state.service deleted file mode 100644 index 5294fe1..0000000 --- a/data/systemd/fedora-import-state.service +++ /dev/null @@ -1,13 +0,0 @@ -[Unit] -Description=Import network configuration from initramfs -DefaultDependencies=no -ConditionDirectoryNotEmpty=/run/initramfs/state -Conflicts=shutdown.target -Before=shutdown.target emergency.service emergency.target systemd-tmpfiles-setup.service -After=remount-rootfs.service - -[Service] -ExecStart=/lib/systemd/fedora-import-state -Type=oneshot -TimeoutSec=0 -RemainAfterExit=yes -- 1.7.10.4

1 1

[PATCH] Re-remove fedora-import-state
by Will Woods 18 Jul '12

18 Jul '12

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel July 2012