Anaconda-devel April 2013

anaconda-devel@lists.stg.fedoraproject.org

21 participants
12 discussions

SYSLINUX boot in F19
by A.J. Werkman 11 May '13

11 May '13

Op 25-4-2013 19:44, Adam Williamson schreef: > On Wed, 2013-04-24 at 18:48 +0200, A.J. Werkman wrote: >> This is the link about the SYSLINUX feature: >> https://fedoraproject.org/wiki/Features/SyslinuxOption >> >> It talks about a anaconda hidden option and a kickstart option: >> 1. How do I prepare my system to test this feature? What packages need >> to be installed, config files edited, etc.? >> >> Enable syslinux in kickstart with whatever option is decided upon, or >> via the similar Anaconda hidden option. >> >> >> I can't find how this option is called. > I remember reading the feature too, but I haven't heard of it being > added to anaconda yet. Let me check the git logs... > > ...yeah, nothing in there either. It looks like this just hasn't been > added to anaconda at all yet. You might ask in #anaconda and see what > their knowledge of this feature is. Is/will the SYSLINUX feature be implemented in the upcomming F19? Koos.

6 22

Help with Anaconda changes
by Ravindra Kumar 02 May '13

02 May '13

Hi, I work for VMware and I'm packaging open-vm-tools in Fedora. I'm new to Anaconda. I would like to contribute a change to Anaconda, so that during OS install, open-vm-tools is selected/installed by default on virtual machines hosted on VMware. Could someone please help/guide me with making Anaconda changes for the requirement above? What files/functions should be modified? How to go about it (available mechanisms to perform virtualization check)? We have got two suggestions for this 'virt-what' and 'systemd'. I would really appreciate to see some examples of either approach and what is recommended for Anaconda. I'm looking for quick pointers, so that I can make the changes/test and submit the patch for review as soon as possible. I would also like to know if one change (bugfix) would be sufficient for Fedora and RHEL, or do I need to make two separate Anaconda fixes for Fedora and RHEL. I also got to know about this Red Hat bug https://bugzilla.redhat.com/show_bug.cgi?id=884385 ? If possible, could someone please grant me access to this bug? FWIW, my target is to get these changes done in time for Fedora 19 and RHEL 7. Thanks in advance, Ravindra

4 10

Anaconda usability test report from DevConf
by Filip Kosík 01 May '13

01 May '13

Hi, now, I am doing reports from the usability tests that took place in the Czech Republic. I have made the report on Session 1 from DevConf.cz. There are detected some problems. But it is not finished because I have to make a report on Session 2 (and the internal usability tests) etc. So, something may change. But I want to make my current work available. My current report: http://www.visionplus.cz/anaconda/Test_Report_Session1.pdf Pre-test Survey (users background): http://www.visionplus.cz/anaconda/Pre-Test_Survey_DevConf.tar.gz Feedback (after usability tests): http://www.visionplus.cz/anaconda/FeedBack_DevConf.tar.gz Note: One document refers to another using anonymous id. Filip

2 2

Anaconda failure during PXE kickstart package install sequence: Read-only Filesystem
by Parker, Sean E (N-GROMELSKI & ASSOCIATES, INC.) 30 Apr '13

30 Apr '13

Hello - My PXE install fails about half-way through the installation of the packages with the following: (This is last text on the screen at the point it wants me to Ctrl-Alt-Delete) (First section is remnants from my attempts at printing values at the debug prompt) <error text> Error cmd.Cmd.onecmd(self, line) File "/usr/lib64/python2.6/cmd.py", line 219, in onecmd Return func(arg) File "/usr/lib64/python2.6/pdb.py", line 661, in do_run Raise Restart Pdb.Restart Original Exception was: Traceback (most recent call last): File "/usr/lib/anaconda/yuminstall.py", line 173, in callback Self.instLog.flush() IOError: [Errno 30] Read-only file system Error: pythin callback <bound method AnacondaCallback.callback of <yuminstall.AnacondaCallback instance at 0x7ff07cc7ea28>> failed, aborting! Unlink: /mnt/sysimage/var/lib/rpm/__db.002: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.004: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.003: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.001: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.002: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.004: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.003: Read-only file system Unlink: /mnt/sysimage/var/lib/rpm/__db.001: Read-only file system Install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. <end error text> Our system: Supermicro X8DTU motherboard x86_64, with 300GB SCSI and 30GB SSD. RHEL 6.2. This has installed before on this system on SSD only, and it failed yesterday just on a different package. This is an isolated network (PXE server and this host only) This PXE install did a full drive formatting. I've searched google and found no other info on this specific problem. Any ideas? Any suggestions for action at python debug prompt? (I'm not familiar w/ python, but this seems like a systemic issue rather than py coding error) Thanks Sean Sean Parker Gromellski & Associates Office: 703-367-1020 Cell: 703-615-3729 I've sent you an email as a courtesy so you can open/respond when you have time, I would appreciate the courtesy of a response at all.

2 1

draft patches for syslinux/extlinux support
by Matthew Miller 30 Apr '13

30 Apr '13

These are against the F19 alpha and have been tested on a local virt-install but not widely. First patch adds the bootloader type but does nothing with it; second patch adds an extlinux command line option which activates it. In progress but not yet included, third patch to add an option to the bootloader kickstart directive. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

4 5

Re-using existing partitions for root--Anaconda 19.x
by Clyde E. Kunkel 22 Apr '13

22 Apr '13

In anaconda 19.20 (and older) I have been trying to reuse an existing btrfs partition as / and the reformat box is greyed out. The partitioner refuses to use the partition with error msg "you must create a filesystem on the root device." But with a greyed out reformat box how do we do this? Yes, I can delete and recreate the partition, but shouldn't we be able to reuse as long as we request that the partition be reformatted? TIA -- Regards, OldFart

2 1

Anaconda codebase @ Ohloh
by Martin Kolman 10 Apr '13

10 Apr '13

Looks like they have some quite interesting graphs and statistics about the Anaconda codebase, going all the way back to 1999: http://www.ohloh.net/p/anaconda While some observations seem to be a bit bogus, some recent events - such as newui - are quite nicely visible. :) They also have data on related projects, such as Pykickstart and Lorax: http://www.ohloh.net/p/pykickstart http://www.ohloh.net/p/lorax-fedora

1 0

Making room for the layout indicator
by Máirín Duffy 08 Apr '13

08 Apr '13

Hi, So vpodzime put together an awesome layout indicator for anaconda: http://vpodzime.fedorapeople.org/new_layout_indicator.webm One problem though is with the red preproduction/test text in the upper right, there isn't much space for it. So we talked about making the header taller to accommodate it in IRC this morning. While I think we should the header a bit taller, after experimenting with mockups the layout looks a bit unbalanced if I make the header tall enough to include the layout switcher without any other changes. (For example, the vertical alignment of the screen title and done button on the left hand side looks a bit weird when the right side has the three vertical items.) So this is my proposal to fit the indicator in the header: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Layout-Switching/… This involves three changes: - Changing the font size of the 'development/testing' string to be 8 or 9pt - Increasing the height of the header to be 84 pixels tall (it was 78 pixels tall before) - Swapping out the pixbuf from the current one to this one (which is 84 px tall): http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Layout-Switching/… Does this make sense? ~m

3 4

Kickstart in Fedora 19 TC4
by Dean Hunter 06 Apr '13

06 Apr '13

This is just for your information as I am certain you are working furiously. I did some testing building a Fedora 19 guest VM on a Fedora 18 host machine Here is the kickstart script I used: authconfig --enableshadow --passalgo=sha512 autopart --type=lvm bootloader --boot-drive=vda --location=mbr cdrom clearpart --all --drives=vda --initlabel firstboot --disable ignoredisk --only-use=vda install keyboard --vckeymap=us --xlayouts=us lang en_US.UTF-8 network --bootproto=dhcp --device=eth0 --hostname=fedora19.hunter.org --nameserver=192.168.1.11 --noipv6 --activate reboot rootpw --iscrypted $6$82gtiKgE7AvH./ic $TeDjrPrkQ19ULsPEzxStyqzkfRaGvKn0NpSB4ekV98hJOABaO5uQDzQmlCy8t7RwytXzS3t/yRyGZA.8ez2wf/ text timezone America/Chicago --isUtc user --name=local --gecos="Local Administrator" --password=$6 $82gtiKgE7AvH./ic $Cxa598KQzrJ94M2aYzdV0ifOUcLYqbAh0RNvsmiC2hkdX/Xald.EVVNf/MmD4mTeeojBNPBNcY7XcBfgMoSqq/ --iscrypted xconfig --startxonboot %packages @base-x @core @dial-up @firefox @fonts @gnome-desktop @hardware-support @input-methods @multimedia @printing @standard %end I found a few things you might want to add to your list: 1) I am always prompted for an install destination to confirm the disk layout even though autopart and clearpart are specified that save as in anaconda-ks.cfg after a manual build. 2) The setup agent always runs even though firstboot is disabled and the equivalent information is provided in the keyboard, lang, timezone and user statements. 3) The --nameserver is entered correctly into ifcfg-eth0 but it is not enabled. When I examine the configuration with Network Manager, in the DNS section on the IPV4 screen, I must set automatic to off to enable the name server specified by kickstart. 4) Text mode must be specified with kickstart as the graphic mode fails. Graphic mode works fine without kickstart. Thank you for all your efforts and I hope this is helpful.

1 0

Anaconda F19 TC 1 usability test results from Boston tests
by Máirín Duffy 04 Apr '13

04 Apr '13

Hi folks, We ran a test of 4 experienced system administrators (current RHEL users) in the Westford Red Hat office last week. Attached is my write-up of how the tests went along with a list of all of the issues encountered across users. It's in both markdown and HTML format. The markdown is pretty readable as plain text. ~m

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 April 2013