Anaconda-devel October 2012

anaconda-devel@lists.stg.fedoraproject.org

26 participants
21 discussions

Ability to install to loopmounted filesystem - mentor wanted
by Tirtha Chatterjee 02 Dec '12

02 Dec '12

Hello. I am trying to implement something like Wubi on Fedora. For this, I first need to make it possible to install to loopmounted filesystems through anaconda. I don't think a lot of modification to the existing source code is required. I tried going through the source code, but it seemed quite big to manage without some guidance. I would be extremely happy if someone guided me on this. Hoping for an affirmative reply :-) -- Regards Tirtha Chatterjee KDE developer http://wyuka.co.cc/

2 3

Re: Reclaim disk space dialog not too much intuitive..
by Staci Page 30 Oct '12

30 Oct '12

I just read yer reply, srry if u sent it a bit ago but it landed in my junkbox. I was into your ad for real I think we may hit it off. I am wondering if you have met up with anyone on Craigslist b4? I have, however have had a few crappy meets unfortunately. I have been using here for about 4 months to deter the weirdos and its worked so far. Well if u want to look at my pictures on there and let me know if I am yer what you are looking for we'll go from there. Its quicker if u just text or call me after u are verified so I wont miss yer email and idk how much longer I'm going to be at my computer.

1 0

Reclaim disk space dialog not too much intuitive..
by Martin Banas 30 Oct '12

30 Oct '12

Hello, I've been looking at reclaim space dialog in new anaconda recently.. In my opinion it's too much complicated, and not transparent to user. I think it could be more intuitive so that everybody knows what it does. I saw ubuntu installer recently and I really liked the way they deal with partitions. I'm not a designer and I never worked in inkscape, but I tried to did some draft how it could look like. Please note that the trash bin is downloaded somewhere from internet and is under creative common license... I would like to hear your opinions about the picture I attached. Regards, Martin

3 2

Blocker bug list
by Adam Williamson 30 Oct '12

30 Oct '12

I seem to have been sending this to several people on IRC lately, so I thought I'd just post it here to be sure all the anaconda team knows about it. You should know about this page: http://qa.fedoraproject.org/blockerbugs/current At any time that URL will give you a list of the proposed and accepted blocker and NTH bugs for the next pending pre-release. It is refreshed every half an hour. If you want to know what absolutely needs to be worked on with the highest priority for Fedora - check that page. Accepted blockers come first, then proposed blockers (except ones that are obviously batty), accepted NTH, proposed NTH. The page should always be comprehensive and accurate, you can rely on it. It's a nice simple one stop resource :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Anaconda is giving birth to Blivet
by David Lehman 29 Oct '12

29 Oct '12

The anaconda package is going to be rearranged somewhat for F19. The package is going to be split into three pieces. The main anaconda package will contain only the pyanaconda python module, while the install-time bits and their dependencies will be split out into a sub-package. This will enable other projects that use the pyanaconda module to install it without having to also install all of the installer's runtime dependencies. Finally, the current anaconda storage module will be split out into a new package: blivet. Blivet will be a python module providing system storage configuration functionality. It is expected to require anaconda -- at least initially. To be clear, blivet is a library -- not an application. The main functionality offered by blivet includes: - detection of existing system storage layout - model a set of storage configuration changes in memory before committing them to disk - create/destroy, resize, activate/deactivate devices and filesystems The split will occur early in the F19 development cycle. More information will come as things develop.

3 2

testing F18 on ARM highbank
by David A. Marlin 29 Oct '12

29 Oct '12

We are trying to get an install tree for F18 and test it on a Calxeda Highbank server. I am basing my work on the F17 install we did. What I've done so far: - created an install tree for F18 armhfp lorax -p Fedora -v 18 -r 18 \ --variant="Fedora" \ --source="http://intranet.ges.redhat.com/es/Fedora/fedora-secondary/development/18/ar…" \ --source="http://dmarlin.fedorapeople.org/yum/f18/armhfp/os/Packages/" \ /es/scratch/dmarlin/F18/lorax-trees/armv7hl-tree The second source repository includes a newer test kernel package. - set up the local repos and tftp server - created a kickstart (attached) I used the previous F17 kickstart file as a base and changed the repo paths for F18. Everything else is the same. - tried a PXE-boot, kickstart install. This started as before (F17) but quickly failed. We had always used cmdline mode, but this time if dropped out due to unanswered questions. I switched to 'text' mode to try an work through these. The first thing I hit was: Install hub 1) [x] Timezone settings 2) [ ] Install Destination (US/Eastern timezone) (Error checking storage 3) [x] Set root password configuration) (Password is set.) Please make your choice from above ['q' to quit | 'c' to continue]: 2 I selected the only drive on the system, and to use all space. I'm not sure why this was undefined, as all the partitioning is specified in the kickstart file, and worked in F17. After this, it started installing but encountered an error and produced a backtrace (attached). AttributeError: 'YumPayload' object has no attribute 'storage' I'm not sure where to go from there. Any suggestions or improving the kickstart (to permit cmdline mode to work) or to work around this error are appreciated. Thank you, d.marlin

5 7

LVM enabled by default in F18
by Ric Wheeler 25 Oct '12

25 Oct '12

I would like to request that we keep LVM enabled by default for F18. In Fedora 19, we are going to move firmly onto the btrfs bandwagon with btrfs as default which will not require LVM. Changing the default in F18 for ext4 users just creates a one release pool of ext4 on raw partition systems right before we shift again to btrfs. Not to mention lack of Fedora specific documentation on how to admin these raw partitions, dependent projects like the update rollback based on LVM (or btrfs), etc. Sorry for not noticing this earlier in the release cycle! Ric

2 1

Review of Fedora 18 Release Criteria (Second Attempt)
by Tim Flink 24 Oct '12

24 Oct '12

While the last conversation around the F18 release criteria did yeild some interesting information, it wasn't quite what I had in mind so let's try this again :) With all of the criteria changes we've had for F18, we'd like to get some feedback on the current criteria to make sure that we're not either overreaching or missing some important functionality. We're interested in feedback on the criteria themselves instead of the blocker or criteria review process. I've listed the new and revised criteria for F18 at the end of this email but input on the old criteria would also be appreciated. - http://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria - http://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria - http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria Tim ============================================================ New/Changed Alpha Release Criteria ============================================================ The installer must be able to install each of the release blocking desktops, as well as the minimal package set, with each supported installation method The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data The installer must allow the user to select which of the disks connected to the system will be affected by the installation process. Disks not selected as installation targets must not be affected by the installation process in any way ============================================================ New/Changed Beta Release Criteria ============================================================ The installer must be able to complete an installation using automatic partitioning to a validly-formatted disk with sufficient empty space, using the empty space and installing a bootloader but leaving the pre-existing partitions and data untouched === This is still under review - waiting for input === The installer's custom partitioning mode must be capable of the following: * Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types * Creating encrypted partitions * Rejecting obviously invalid operations without crashing For each one of the release-blocking package sets ('minimal', and the package sets for each one of the release-blocking desktops), it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed, using any officially recommended upgrade mechanisms. The upgraded system must meet all release criteria. ============================================================ New/Changed Final Release Criteria ============================================================ For each one of the release-blocking package sets ('minimal', and the package sets for each one of the release-blocking desktops), it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed, using all officially recommended upgrade mechanisms. The upgraded system must meet all release criteria.

1 0

anaconda couldn't recognize the image file format of PNG!!
by 赵小强 22 Oct '12

22 Oct '12

Hi,there: I download some source packages from centos 6.2 and rebuild them. The I use them build a install DVD iso image. it can boot up, but I encouter a fatal error: unable to read anaconda_header.png: Couldn't recognize the image file format for file "/usr/share/anaconda/pixmaps/anaconda.png". The anaconda_header.png is actually there and it can be opened by gthumb. The detail error message shows it may be the problem of gtk2. But I changed nothing of gtk2's SPEC file and the it build successfully. Version of information: gtk2-2.18.9-6.el6.x86_64.rpm anaconda-13.21.149-1.el6.x86_64.rpm. Any ideas? Thx in advance :-)

2 3

F18 RC2 btrfs options
by Chris Murphy 20 Oct '12

20 Oct '12

I'm finding the current options and UI for the btrfs options to be non-discoverable, i.e. I don't know what they do. 1. Each option has a red (-0Gb) after it. 2. Redundancy (mirror) is presumably "-d raid1", unclear why it's checkable with one disk. 3. Optimized performance (stripe) is presumably "-d raid0", unclear why it's checkable with one disk. 4. The Technology pop-up menu is unclear which option it applies to, I'm guessing just mirroring and striping. A thin black line separating would make this more clear. Or drop the option entirely (honestly in a GUI I don't see the advantage of LVM or MD over btrfs integrated RAID, compared to the cluttering of the UI that results from providing the choice.) 5. Error detection (parity). Is this the metadata profile? If so, I think it being unchecked by default is confusing, because there isn't a -m none option. I'd even suggest the UI could be eliminated by making some reasonable choices for the user based on the first two options: Single disk, use metadata default of duplicated on that single disk. Multiple disk where -d raid0 or raid1, use -m raid1 because it's safer. Multiple disk where -d raid10, use -m raid10 6. Compression lacks an LZO option, and defaults to ZLIB. Chris Murphy

4 18

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel October 2012