Anaconda-devel May 2013

anaconda-devel@lists.stg.fedoraproject.org

21 participants
16 discussions

Proposal of minor LiveDVD F19 network/hostname configuration UX improvement (PATCH included)
by Radek Vykydal 31 May '13

31 May '13

Original request with links to user inputs is in https://bugzilla.redhat.com/show_bug.cgi?id=963059 Proposed change aims to - offer hostname setting in installer also in cases where network has been setup in Live environment automatically using default dhcp, and make it more prominent also for other cases - give hint to use live desktop environment for network configuration - in a way workable for F19 F18 behaviour: - only in case where there is no network connection we display pre-hub (standalone) network spoke requesting (incorrectly) network configuration, allowing the configuration using the spoke (although preferred/recommended way is to use DE), and containing hostname entry: http://rvykydal.fedorapeople.org/live18standalone.png - network spoke (NETWORK CONFIGURATION) is not displayed on summary hub/screen (want DE tools to be used for network configuration): http://rvykydal.fedorapeople.org/live18hub.png current F19 behaviour: - pre-hub (standalone) network spoke is never displayed (we don't require network connection for Live DVD install) - network spoke (NETWORK CONFIGURATION) is not displayed as in F18 proposed behaviour: - pre-hub (standalone) network spoke containing - hint to use DE tools to configure network optionally - entry allowing to setup hostname is always displayed - network spoke (NETWORK CONFIGURATION) is not displayed as in F18 see http://rvykydal.fedorapeople.org/live_network_hostname.webm The patch is attached. Do you see it as an improvement acceptable for F19? (It could use some wording/layout polishing.) Radek

4 7

anaconda 'text' and 'vnc' mode and more than one network card inquiry
by Reartes Guillermo 31 May '13

31 May '13

Hi, I noticed that when one has more than one ethernet card, when 'text' or 'vnc' boot parameters are specified, vnc is avaiable on all ethernet cards (but only one at a time). That is ok and it is not a problem in any way, it just works. However, anaconda shows: "Please manually connect yout vnc clicent to xxx.xxx.xxx.xxx:x to begin the install" But since one can actually use other ip/nic to connect, should it be better to show one line per valid ip to connect to anaconda's vnc? (stating to use only one at a time). In my example, the ip shown is the one from the second nic (eth1), not the expected first nic (eth0). So there is no guarantee tha the first nic (eth0) is always the one shown. Can the explanatory text be changed to reflect the fact that one can connnect via vnc to another (not shown) ip/nic? Or at least documented, since one can easyly switch to VT2 and issue an 'ip addr show' and try to connect via vnc to each nic. Thanks in advance.

2 1

Custom Partitioning Change Request (Always confirm each DELETE action using the keyboard)
by Reartes Guillermo 29 May '13

29 May '13

Hi, Currently, when using the keyboard, one simple DEL key deletes a mount point entry, at least a newly created one. Sometimes (for other reasons) the focus of the field i am editing is lost and i end up having all mount points deleted because i was deleting text and suddenly all is deleted. Most of the time i don't know why i lost focus, but by the time i realize, i had deleted all entries (or most of them). And since i am testing somewhat complex disk layout it is annoying to have to re-do all again after pressing the wrong keyboard key. Proposal: DEL ---> Confirmation dialog. (Y/N) SHIFT-DEL --> No Confirmation dialog. Assume Y. Thanks in advance.

1 0

Use anaconda in command line?
by Kun Huang 28 May '13

28 May '13

Hi developers: Is there any document to talk about using anaconda in command line? Such as: anaconda --kickstart=xx.ks --cmdline --target=/dev/sda I'm trying it in my environment, but it takes long time to response and fails.

5 7

New Python Maintainer - Self Introduction
by Bohuslav Kabrda 28 May '13

28 May '13

Hi guys, as a new Fedora and RHEL Python maintainer, I'd like to introduce myself and start communicating with you. I took Python over from Dave Malcolm a month ago and I figured it'd be good to start talking to devs of important Python projects that Fedora/RHEL rely on. I'd like to keep the communication channel between me and you open, so if you ever need a Python patch or there's something that I can do for you (in my power :)), feel free to reach out to me. My most important long-term goal is to migrate Fedora to use Python 3 as a default. I already prepared rpm-python3 bindings for the packaging team and although YUM will never work with Python 3, I'm relying on DNF, which will work with Python 3 for sure, as I was told. So my question for anaconda devs is: What would it take to migrate anaconda to Python 3? Are there already any plans to do so (and timeframe)? What could I do to help with that? Thank you all, Slavek. -- Regards, Bohuslav "Slavek" Kabrda.

2 2

Of freezes &c
by Adam Williamson 27 May '13

27 May '13

So now we're past Beta, I see this kind of thing popping up again: https://bugzilla.redhat.com/show_bug.cgi?id=959677#c35 "Nice! If anybody wants a patch for this to be included in the final release, please propose this as a final blocker." Please don't abuse the project-wide blocker process in this way. The blocker process is for tracking bugs that must be fixed before the release. It is not a todo list or a private freeze exception list. The official freeze date for F19 Final is 2013-06-18, it is listed as "Final Change Deadline" at http://fedorapeople.org/groups/schedule/f-19/f-19-devel-tasks.html . So far as the Fedora project is concerned, there is no freeze until that time. If the anaconda team wants to apply a private freeze to anaconda changes for the entire post-Beta period it is your right to do so, however, you should either come up with your own mechanism for tracking exceptions to your private freeze or at least work with other teams to decide how existing mechanisms can sensibly be applied to your private freeze, not simply decide to start using the project-wide release blocker tracking mechanism as a private freeze break list. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Welcome Screen issue with default language (sometimes it is not English)
by Reartes Guillermo 27 May '13

27 May '13

Hi, With F19b-TC2, i noticed that sometimes the default language in the Welcome Screen is not English but Portuguese.Also it is not cantered in the selected language. Cheers.

4 6

Guided partitioning is fundamentally broken for Btrfs default use
by Chris Murphy 12 May '13

12 May '13

Originally I was thinking the installer's assertion that Btrfs is not resizable just needed a verbiage change to "Resize unsupported" https://bugzilla.redhat.com/show_bug.cgi?id=962143 But there's a consequence that makes this a show stopper for Btrfs becoming the eventual default file system. Actual behavior: 1. F18, use Guided Partitioning, partition scheme set to Btrfs, on a blank drive. 2. F19, use Guided Partitioning = can't, there isn't enough space and the installer won't resize Btrfs volumes. Expected behavior: Either Guided partitioning should enable the shrinking of the Btrfs file system to make room for a new 500MB ext4 /boot. OR it needs to support /boot on Btrfs subvolumes. OR it needs to support reusing an existing /boot. Currently none of these are supported in Guided partitioning. Work around: Use Manual partitioning, and place /boot on btrfs as a subvolume. This also triggers this grubby bug https://bugzilla.redhat.com/show_bug.cgi?id=864198. Chris Murphy

1 0

anaconda text mode does not start VNC with 512mb ram
by Reartes Guillermo 12 May '13

12 May '13

Hi, I have F18 (installed via text/vnc method) and i tried to install F19b TC3 i386. anaconda refuses to launch vnc for F19: "Not asking for VNC because current memory (500184) < MIN_GUI_RAM (524288)" Is it intended or should i file a bug-report for this? The netbook has a 512mb ram stick, and since F18 could be installed via vnc, i expected the same for F19. Now i am shot of 24mb ram approx. Cheers.

2 4

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel May 2013