Anaconda-devel August 2013

anaconda-devel@lists.stg.fedoraproject.org

13 participants
11 discussions

Start a nNew thread

boot options of anaconda
by MaShimiao 04 Sep '13

04 Sep '13

Hi all, I want to know all boot options supported by anaconda. How can I get them with a specified version? Thanks.

2 1

PV part specification
by Gene Czarcinski 03 Sep '13

03 Sep '13

In kickstart, is there a way of specifying an LVM PV partition in a manner which does not involve specifying a specific device such as sdb1? I tried using the PV's UUID but anaconda "does not like" LVM UUIDs.

3 5

Anaconda problem with Fedora 18/19
by Vehmaa, Jari (NSN - FI/Espoo) 21 Aug '13

21 Aug '13

Hello folks, This is my first posting to this list. I have an own Fedora(16,17,18,19) spin. My customers have reported that F18, F19 based kick start installation fails soon with "black screen" or "no video" and then it just hangs. I got information that usually adding "xdriver=vesa nomodeset" will help to black screen problems. After adding basic video parameters, then installation goes a little bit further, but then it crashes with message: Error accessing file for config file:///tmp/anaconda-yum.conf. Please see the picture from http://forums.fedoraforum.org/showthread.php?t=291451. The file tmp/anaconda-yum.conf exists and the content looks like reasonable: 8<-----8<-----8<-----8<-----8<-----8<----- [main] cachedir=/tmp/yum.cache keepcache=0 logfile=/tmp/yum.log metadata_expire=never pluginpath=/usr/lib/yum-plugins,/tmp/updates/yum-plugins pluginconfpath=/etc/yum/pluginconf.d,/tmp/updates/pluginconf.d plugins=1 reposdir=/etc/yum.repos.d,/etc/anaconda.repos.d,/tmp/updates/anaconda.repos.d,/tmp/product/anaconda.repos.d 8<-----8<-----8<-----8<-----8<-----8<----- I can install my F18 spin successfully to Dell Optiplex GX620 Desktop and Dell PowerEdge 540 hw. Usually dvd based installation fails with HP Proliant servers. My older F16 and F17 spins have worked fine with all HP hw. I would be very grateful for any help. Br, Jari

1 0

Pls have a review of my media
by Kun Huang 20 Aug '13

20 Aug '13

Hi, all Now I have some work with anaconda on different media (usb/iso), and also have some questions, please have a review. My target: have a directory contains kinds of data could be used to generate a bootable iso (by mkisofs) and be copied to usb drive as boot-install usb. And I have one test case could work: /images/install.img # stage2 contains anaconda codes /isolinux/... # use for booting in iso case /syslinux/... # use for booting in usb case /os/xxx.iso # a directory contains an ISO image /repo/*.rpm # my own repo node.ks # kickstart which uses /repo/*.rpm as additional repo for packages /Packages/*.rpm # this directory and repodata/ below is standard repo in Centos6.4 /repodata/ .discinfo # these two are used in iso case .treeinfo this case works for my cases: in iso case, it boots by isolinux, and install @core in /Packages; and in usb case, it boots by syslinux and install @core packages from /os/*.iso. Now my problem is that the /os/xxx.iso and /Packages&/repodata are duplicated actually. I tried use /os/xx.iso and repo=cdrom:/os but failed with un-catched exception "nonetype has no attribute 'format' " Now before further testing on repo=cdrom:/os I have several questions: (my anaconda version is 13.21.195 ) 1. will anaconda find *.iso under /os in my ISO image by repo=cdrom:/os? 2. are there more better or more common solutions for my target? Thanks for any reply

1 0

questions about anaconda
by MaShimiao 19 Aug '13

19 Aug '13

hi all, When I use the newest anaconda, I find it is different from the former versions. The interface has huge changes. So, I have several questions about anaconda, could you help me? 1. Does the newest anaconda still support upgrading a system? 2. Does the newest anaconda still support rescuing a system? 3. Kickstart is part of anaconda or just have function which supports kickstart? Thank you very much.

2 2

Where and how to deal with EULA?
by Vratislav Podzimek 16 Aug '13

16 Aug '13

With the transition from the Firstboot to the Initial Setup we have lost the EULA acceptance screen and we should bring it back. However, I think that the approach like "We have replaced your data with our great system. Oh, and by the way, do you agree with our EULA? Yes, please proceed." is not the right one. I believe we should make users see and accept the EULA before they click on the "Begin installation" button. Or, in case that would be too disruptive and enforcing, at least to the system installation phase (on the second hub). Of course, if the 'firstboot --reconfig' appears in the kickstart, the same screen would appear in the Initial Setup (for OEM installations). As for the UX side -- I'd go with a simple text view showing the license with an "I agree" checkbox below it. Once that gets checked, the spoke would be completed and the installation (first boot) might continue. Any suggestions or ideas? -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

4 5

Getting Started as a Translator on Transifex
by Dimitris Glezos 15 Aug '13

15 Aug '13

Hi Anaconda, Welcome, glad to have you on here! I'm Dimitris, founder of Transifex. Hopefully by now you have found the project you are looking for and joined a language team. As a translator, you will be spending most of your time in the translation editor. It's the place where you can see all the text (strings) that need to be translated, submit translations, and collaborate with others. Take a look at our [Introduction to the Web Editor](http://support.transifex.com/customer/portal/articles/972120-introd… to get acquainted with the basics. Should you run into any questions about using Transifex, check out our support portal. Enjoy!

1 0

GRUB as the ISO boot loader for POWER arch
by Paulo Flabiano Smorigo/Brazil/IBM 13 Aug '13

13 Aug '13

Hi all, Currently, yaboot is the ISO boot loader in fedora and the Fedora on POWER team is making an effort in order to replace it by GRUB2 in the F20 release cycle. I'm sending a lorax patch so you guys can comment on it. I'm planning to create a feature page for that too. This patch only change the lorax template for ppc and should not affect other archs, like x86. -- Paulo Flabiano Smorigo Software Engineer Linux Technology Center - IBM Systems & Technology Group --- share/config_files/ppc/bootinfo.txt | 9 ++++---- share/config_files/ppc/grub.cfg.in | 34 ++++++++++++++++++++++++++++ share/ppc.tmpl | 44 ++++++++++++------------------------- 3 files changed, 53 insertions(+), 34 deletions(-) create mode 100644 share/config_files/ppc/grub.cfg.in diff --git a/share/config_files/ppc/bootinfo.txt b/share/config_files/ppc/bootinfo.txt index ac766d4..6eac6c4 100644 --- a/share/config_files/ppc/bootinfo.txt +++ b/share/config_files/ppc/bootinfo.txt @@ -1,7 +1,8 @@ -<chrp-boot> <description>Linux</description> -<os-name>Linux</os-name> -<boot-script>boot &device;:\ppc\chrp\yaboot</boot-script> -<icon size=64,64 color-space=3,3,2> +<chrp-boot> +<description>grub 2.00</description> +<os-name>grub 2.00</os-name> +<boot-script>boot &device;:\boot\grub\powerpc-ieee1275\core.elf</boot-script> +<icon size=64,64 color-space=3,3,2> <bitmap> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF diff --git a/share/config_files/ppc/grub.cfg.in b/share/config_files/ppc/grub.cfg.in new file mode 100644 index 0000000..f125ac2 --- /dev/null +++ b/share/config_files/ppc/grub.cfg.in @@ -0,0 +1,34 @@ +set default=0 +set timeout=5 + +echo -e "\nWelcome to the @PRODUCT@ @VERSION@ installer!\n\n" + +for BITS in 32 64; do + if [ -d "/ppc/ppc${BITS}" ]; then + menuentry "Install @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os { + linux /ppc/ppc${2}/vmlinuz @ROOT@ ro + initrd /ppc/ppc${2}/initrd.img + } + + menuentry "Test this media & install @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os { + linux /ppc/ppc${2}/vmlinuz @ROOT@ rd.live.check ro + initrd /ppc/ppc${2}/initrd.img + } + + menuentry "Rescue a @PRODUCT@ system (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os { + linux /ppc/ppc${2}/vmlinuz @ROOT@ rescue ro + initrd /ppc/ppc${2}/initrd.img + } + fi +done + +submenu 'Other options...' { + menuentry 'Reboot' { + reboot + } + + menuentry 'Exit to Open Firmware' { + exit + } +} + diff --git a/share/ppc.tmpl b/share/ppc.tmpl index bbef5fa..dfd3257 100644 --- a/share/ppc.tmpl +++ b/share/ppc.tmpl @@ -2,6 +2,7 @@ <% configdir="tmp/config_files/ppc" BOOTDIR="ppc" +GRUBDIR="boot/grub" LIVEDIR="LiveOS" MACDIR=BOOTDIR+"/mac" NETBOOTDIR="images/netboot" @@ -9,7 +10,6 @@ NETBOOTDIR="images/netboot" WRAPPER="usr/sbin/wrapper" WRAPPER_DATA="usr/"+libdir+"/kernel-wrapper" -bitsizes = set() prepboot = "" ## NOTE: yaboot freaks out and stops parsing its config if it sees a '\', @@ -37,13 +37,18 @@ mkdir ${BOOTDIR} ## boot stuff for normal (CHRP/PREP) PPC systems install ${configdir}/bootinfo.txt ${BOOTDIR} install boot/efika.forth ${BOOTDIR} -mkdir ${BOOTDIR}/chrp -install usr/lib/yaboot/yaboot ${BOOTDIR}/chrp -runcmd ${inroot}/usr/lib/yaboot/addnote ${outroot}/${BOOTDIR}/chrp/yaboot -## special boot dir for PowerMacs -mkdir ${MACDIR} -install usr/lib/yaboot/yaboot ${MACDIR} -install ${configdir}/ofboot.b ${MACDIR} + +mkdir ${GRUBDIR}/powerpc-ieee1275 +runcmd grub2-mkimage -O powerpc-ieee1275 -d /usr/lib/grub/powerpc-ieee1275 -p '()/boot/grub' \ +-o ${outroot}/${GRUBDIR}/powerpc-ieee1275/core.elf iso9660 ext2 ofnet net tftp http +install /usr/lib/grub/powerpc-ieee1275/*.mod ${GRUBDIR}/powerpc-ieee1275 +install /usr/lib/grub/powerpc-ieee1275/*.lst ${GRUBDIR}/powerpc-ieee1275 + + +install ${configdir}/grub.cfg.in ${GRUBDIR}/grub.cfg +replace @PRODUCT@ '${product.name}' ${GRUBDIR}/grub.cfg +replace @VERSION@ ${product.version} ${GRUBDIR}/grub.cfg +replace @ROOT@ "${rootarg}" ${GRUBDIR}/grub.cfg ## copy mapping and magic files needed for isos install ${configdir}/mapping ${BOOTDIR} @@ -59,7 +64,6 @@ install ${configdir}/magic ${BOOTDIR} ## separate dirs/images for each arch KERNELDIR=BOOTDIR+"/ppc%s" % bits NETIMG=NETBOOTDIR+"/ppc%s.img" % bits - bitsizes.add(bits) %> ## install kernel mkdir ${KERNELDIR} ${NETBOOTDIR} @@ -71,13 +75,6 @@ install ${configdir}/magic ${BOOTDIR} installupgradeinitrd images-${kernel.arch} ${kernel.upgrade.path} ${KERNELDIR}/upgrade.img %endif - ## install arch-specific bootloader config - install ${configdir}/yaboot.conf.in ${KERNELDIR}/yaboot.conf - replace @BITS@ ${bits} ${KERNELDIR}/yaboot.conf - replace @PRODUCT@ '${product.name}' ${KERNELDIR}/yaboot.conf - replace @VERSION@ ${product.version} ${KERNELDIR}/yaboot.conf - replace @ROOT@ "${rootarg}" ${KERNELDIR}/yaboot.conf - ## kernel-wrapper magic that makes the netboot combined ppc{32,64}.img runcmd ${inroot}/${WRAPPER} -p of \ -D ${inroot}/${WRAPPER_DATA} \ @@ -92,19 +89,6 @@ install ${configdir}/magic ${BOOTDIR} %endif %endfor -## choose correct yaboot.conf -mkdir etc -%if len(bitsizes) == 2: - ## both kernels means hybrid - use the magic hybrid config - install ${configdir}/yaboot.conf.3264 etc/yaboot.conf - replace @PRODUCT@ ${product.name} etc/yaboot.conf - replace @VERSION@ ${product.version} etc/yaboot.conf - replace @ROOT@ "${rootarg}" etc/yaboot.conf -%else: - ## single arch - use the arch-specific yaboot.conf from above - copy ${KERNELDIR}/yaboot.conf etc/yaboot.conf -%endif - ## make boot.iso runcmd mkisofs -o ${outroot}/images/boot.iso -chrp-boot -U \ ${prepboot} -part -hfs -T -r -l -J \ @@ -113,8 +97,8 @@ runcmd mkisofs -o ${outroot}/images/boot.iso -chrp-boot -U \ -hfs-volid ${product.version} -hfs-bless ${outroot}/${MACDIR} \ -map ${inroot}/${configdir}/mapping \ -no-desktop -allow-multidot -graft-points \ - etc=${outroot}/etc \ ${BOOTDIR}=${outroot}/${BOOTDIR} \ + ${GRUBDIR}=${outroot}/${GRUBDIR} \ ${NETBOOTDIR}=${outroot}/${NETBOOTDIR} \ ${LIVEDIR}=${outroot}/${LIVEDIR} -- 1.8.1.4

1 0

different ID_FS_TYPE in 'same' usb drives
by Kun Huang 09 Aug '13

09 Aug '13

Hi all: I have two 'same' usb drives (the 'same' means same model from same brand). And I use each one for running anaconda, but have different results. One is everything ok, but another must failed at the step: The installation source given by device %s " "could not be found. Please check your " "parameters and try again." I have looked a lot of codes, and finally find that the ID_FS_TYPE of those usb drives are different. The unexpected case is here: DeviceTree.addUdevDevice: info: {'ID_VENDOR_ID': '0781', 'ID_PART_TABLE_TYPE': 'dos', 'ID_USB_INTERFACE_NUM': '00', 'ID_REVISION': '1.26', 'LVM_SBIN_PATH': '/usr/sbin', 'ID_VENDOR_ENC': 'SanDisk\\x20', 'ID_PATH': 'pci-0000:00:1d.7-usb-0:5.1:1.0-scsi-0:0:0:0', 'ID_MODEL_ID': '5567', 'ANACBIN': '/usr/sbin', 'ID_VENDOR': 'SanDisk', 'ID_FS_LABEL_ENC': 'Ubuntu-Server\\x2012.04.2\\x20LTS\\x20i386', 'ID_SERIAL': 'SanDisk_Cruzer_Blade_4C532000000613115504-0:0', 'DEVTYPE': 'disk', 'MINOR': '16', 'MPATH_SBIN_PATH': '/usr/sbin', 'ID_FS_TYPE': 'iso9660','DEVLINKS': '/dev/block/8:16 /dev/disk/by-id/usb-SanDisk_ Cruzer_Blade_4C532000000613115504-0:0 /dev/disk/by-path/pci-0000:00: 1d.7-usb-0:5.1:1.0-scsi-0:0:0:0 /dev/disk/by-label/Ubuntu- Server\\x2012.04.2\\x20LTS\\x20i386 /dev/disk/by-id/edd-int13_dev80', 'SUBSYSTEM': 'block', 'ID_MODEL': 'Cruzer_Blade', 'ID_SERIAL_SHORT': '4C532000000613115504', 'ID_USB_INTERFACES': ':080650:', 'ID_INSTANCE': '0:0', 'sysfs_path': '/devices/pci0000:00/0000:00: 1d.7/usb1/1-5/1-5.1/1-5.1:1.0/host2/target2:0:0/2:0:0:0/block/sdb', 'ID_FS_LABEL': 'Ubuntu-Server_12.04.2_LTS_i386', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'ID_BUS': 'usb', 'name': 'sdb', 'symlinks': ['/dev/block/8:16', '/dev/disk/by-id/usb-SanDisk_Cruzer_Blade_4C532000000613115504-0:0', '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:5.1:1.0-scsi-0:0:0:0', '/dev/disk/by-label/Ubuntu-Server\\x2012.04.2\\x20LTS\\x20i386', '/dev/disk/by-id/edd-int13_dev80'], 'MAJOR': '8', 'ID_EDD': 'int13_dev80', 'DEVPATH': '/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/ host2/target2:0:0/2:0:0:0/block/sdb', 'UDEV_LOG': '3', 'DEVNAME': 'sdb', 'ID_MODEL_ENC': 'Cruzer\\x20Blade\\x20\\x20\\x20\\x20', 'ID_USB_DRIVER': 'usb-storage'} ; name: sdb ; In this case, that usb's device instance in anaconda is Iso9660FS, which 'self.format.type' is iso9660. And then here<https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/d…>return False. And in devicetree.devices only didn't contain my usb drive (because devicetress.devices are all partitionable devices in codes, my usb drive in usb case have been looked as False) Ok, all of reasons are from ID_FS_TYPE. This value is from a C lib, and I have no experience on C programming. Could I get some hints?

1 0

what is storage.protectedDevices?
by Kun Huang 05 Aug '13

05 Aug '13

Hi, all https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/_… this is an old version anaconda, but I just need know the meaning of this line. In my case, I used 'repo=hd:......' so anaconda.protected here valuate as true in L93, so when run to L97( my case is not livecd, and "not storage.protectedDevices"), the program looks me as upgrade case, so it checks anaconda.id.getUpgrade(). My case is installing a system from usb. Kickstart files, and repo are all from usb device. But how storage.protectedDevices means here? Thanks Gareth

2 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 August 2013