Anaconda-devel December 2013

anaconda-devel@lists.stg.fedoraproject.org

12 participants
10 discussions

questions about when and how it is appropriate to translate storage terms
by David Shea 02 Jan '14

02 Jan '14

(copied to anaconda-devel-list) Greetings, i18n list. I have a few questions about how things related to storage should be translated. I have a few situations where I would like to know how a non-English speaker (and in particular a speaker of a language that uses non-Latin characters) would expect something to be displayed, and how they expect something to be input. 1: Partition labels. For display, consider the following screen: http://dshea.fedorapeople.org/storage_i18n/es_format_summary.png Should anything in the type ("Tipo" in this image) column be translated? Things like "partition", "physical volume", "BIOS Boot", "EFI System Partition". Some of these strings also represent names that are written to the partition table for disk labels that support it. Would you expect these strings to be localized or would they all be in English? Would a system with a non-English firmware display something like "EFI System Partition," or would it be a localized string? 2: Partition sizes If you want to create a partition that's 500MB, how would you input that size? How would you expect it to be displayed? Here's a couple of images in Kazakh since it's non Latin and happens to have translations in blivet: http://dshea.fedorapeople.org/storage_i18n/kk_size_input.jpg http://dshea.fedorapeople.org/storage_i18n/kk_size_display.jpg Would you expect sizes to be displayed as the localized МБ, or would you expect "MB"? How would you expect to be able to input the size? Should it be able to accept both localized and English sizes? Related to that, the localized "МБ" and other strings are built by concatenating the translation of "M" for mega- with the translation of "B" for byte. Is that problematic? What would be the correct to handle it? Thank you for your help. David Shea

2 1

Re: Idea for making custom partitioning more accessible
by Máirín Duffy 26 Dec '13

26 Dec '13

Care to elaborate? ~m Sent from my phone, which is not an iphone. -------- Original message -------- From: poma <pomidorabelisima(a)gmail.com> Date:12/23/2013 10:03 PM (GMT-05:00) To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list(a)redhat.com> Subject: Re: Idea for making custom partitioning more accessible On 23.10.2013 03:59, Máirín Duffy wrote: > Hi, > > Some user feedback and usability testing we've done indicates that // > Thoughts? Change users not Acanonda! poma _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list

2 1

Idea for making custom partitioning more accessible
by Máirín Duffy 23 Dec '13

23 Dec '13

Hi, Some user feedback and usability testing we've done indicates that having custom partitioning accessible only by a pop up dialog attached to the 'done' in the storage spoke is confusing - people search for custom partitioning on the first storage spoke screen, don't see it, give up and hit done, then they see it. I think we should consider providing a better pathway to it on the main screen rather than hiding it on the dialog. I think I was overzealous in trying to shield less-technical ("non-Pokemon") users from it in the original mockups and unnecessarily hurt the users wanting to access custom part. We had a discussion about this in IRC today, and after a few iterations (we started with http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… and iterated from there) I put some more work into a set of mockups that might work. The thing is, it's hard to just add a button here or move something there without affecting a lot of other things - in this case, the display of the dialog on exit from storage entirely and the encryption and autopart type options. Okay so here's a little walkthrough: AUTO-PART USER ============== 1) You click on the storage spoke icon and you see this: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… You might opt-into disk encryption, and you leave everything else alone. 2) You click 'Done' in the upper left corner. You go straight to the hub. Yeh. So basically: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… Anything you would have been able to do in the dialog you already did in the main window. Except for choosing auto-part type. If you're not going into custom part, is the default auto-part type good enough? If not, the main screen design will need more thinking. CUSTOM PART USER ================ 1) You click on the storage spoke icon and you see this: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… 2) You click on the radio button that says "I will configure partitioning" and hit Done. Then you'll see this: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… You pick the auto part type you want in the dropdown and hit create to let it do its thing and then tweak accordingly. Or you can start from scratch if you're into that. 3) You click on the 'done' button in the upper left corner of custom part and it does the same as it does now (summary of changes, then back to the hub) RECLAIM DISK SPACE POP-UP ========================= Just a small mod to this one, since encrypt and autopart type are available else where, drop them: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… NO DISK SPACE POP-UP ==================== No changes to this guy: http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Straight-To-Custo… Does this make sense? I know Chris had concerns about having two columns of options on the screen because translations can get lengthy, so I cut the text length substantially and did a vertical stack of options, but I made the radio buttons horizontally aligned (which the HIG actually allows for, who knew.) I also scaled the disk icon down to 96x96, although 64x64 might work better (need to account for icon height of network disks too.) The only sticking point here is that auto-part folks won't get to choose their flavor unless they go into custom. But maybe it's good, people who don't really know the difference won't have to even make the choice. And it's easy enough to go into custom, hit auto part for the flavor you want, and get out? Thoughts? ~m

7 12

Anaconda DNF wishlist wiki page
by Martin Kolman 17 Dec '13

17 Dec '13

During a discussion with Ales Kozumlik a while ago, the idea appeared that it would be good to write a list of features Anaconda would like to use from DNF, mainly based on the (bad) experience with YUM. Therefore, I made this wiki page: https://fedoraproject.org/wiki/Anaconda/DNFWishlist Feel free to add corrections & amendments. :) With best wishes Martin Kolman

1 0

analyzing all /etc/fstab files??
by Gene Czarcinski 11 Dec '13

11 Dec '13

I appear to have been hit by a change in the way anaconda & blivet initialization work. I could install just fine with the Fedora-20-Beta DVD but hit huge problems with Fedora-20-TC5 on real hardware. The systems involved are real hardware and each have multiple installs into different partitions (a mixture of regular partitions, logical volumes and BTRFS subvolumes). Not all of these install can still boot. An example: 1. a system installed on lvm-root1 with /boot on /dev/sda6 2. later, a new ssd was added and /dev/sda6 was used for /boot with the rootfs on a subvol on the new ssd. 3. This left lvm-root1 still existing but with a UUID for /boot which no longer existed on ths hardware. The result: anaconda/blivet barf all over the place with very strange errors. saying it cannot find a UUID. Of course not, it is gone. So what! Not good, not good. If nothing else, this needs to be documented so other folks do not spend a lot of time chasing their tails. Gene

3 4

Anaconda Addon Development Guide almost finished, needs review
by Vratislav Podzimek 10 Dec '13

10 Dec '13

For a few last months I've been line after line putting together the Anaconda Addon Development Guide [1] -- a short and straightforward guide describing how an addon for the Anaconda installer can be implemented, tested, deployed and packaged. I believe it is now almost finished, but it needs review and probably a lot of tweaks based on the feedback, I'll hopefully get, before I'll propose it as a part of the official Fedora project documentation. So comments, suggestions, issue reports or patches [2] are more than welcomed! [1] http://vpodzime.fedorapeople.org/anaconda-addon-development-guide/ [2] https://github.com/vpodzime/anaconda-addon-development-guide -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

1 0

cannot install; anaconda GUI problem on TC5
by Gene Czarcinski 10 Dec '13

10 Dec '13

The is a problem with bugzilla and I get "502 proxy error" trying to create a new report or the info here would be in the report. I have been doing lots of qemu-kvm testing of Fedora 20 but it was time to do some installs on real hardware. This was mainly to be a "clean" install since I have previously installed from the alpha and then continuously updated. I should have done this earlier since this is a bit late in the game to find something like this. The problem: boot the TC5 DVD and attempt to do a regular gui install. Anaconda dies with a X server error. I have the following files: anaconda.log anaconda-tb-4lkAzT program.log storage.log syslog X.log I do not want to attach all of these here and clutter this mailing list. If one specific file would help or the email address for someone I could email these to would be even better. From anaconda.log: 07:50:14,293 ERR anaconda: Problems running the window manager: [Errno 0] SIGCHLD caught when trying to start the X server. Gene

3 3

[Anaconda] something wrong with dmraid disk?
by Kun Huang 09 Dec '13

09 Dec '13

Hi I have a problem when running anaconda in system which has dm-raid device. I used "clearpart --all" but still got the error windows "specified unpartitioned sdc in partition command". And I found a guy have nearly same case as mine: http://bugs.centos.org/view.php?id=3637 When using "dmraid -r -E", I got ERROR message too. So I guess this is a very old problem and is this a dmraid bug?

5 6

console accessibility and anaconda?
by jdashiel＠shellworld.net 06 Dec '13

06 Dec '13

Is it possible to install fedora 20 beta such that it uses the sound card > to speak and finishes up with a console install? I may be interested in > g.u.i. but that will be after I have a console-based installation running > and talking. Since Linus Torvalds has abandoned gnome in favor of xfce, I > figure it may be time to check that environment out too and compare to > what gnome 3.10 has to offer. No accessibility spin for Fedora was > created so one of the things I don't know is what boot parameters to use > to bring the installer up so it can do its work in such a way I have a > reasonable amount of confidence in the work it is and will be doing. Also, if I put a .ks file on a floppy disk and want fedora installed using that file and the floppy is in /dev/fd0, what command line do I enter at the boot prompt for kickstart to find and use that file on /dev/fd0 on my local computer?

1 0

extlinux question
by Gene Czarcinski 30 Nov '13

30 Nov '13

I am not sure when this started happening, but with "recent" Fedora releases for systems with grub2 bootloaders, an additional "rescue" kernel has been provided. This "rescue" kernel is never updated but remains the same as that provided by anaconda. I assume that it is the kernel that was available at install time. I also assume that the purpose of the "rescue" kernel is to provide a backup capability just in case the updating of kernels has managed to create an unbootable system. The question: If this is a good option for grub2 based systems, why isn't a good options to have for systems with extlinux bootloaders too? Just curious. Gene

6 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel December 2013