Anaconda-devel April 2008

anaconda-devel@lists.stg.fedoraproject.org

26 participants
28 discussions

loader/stage2 interaction
by Chris Lumens 14 May '08

14 May '08

I think everyone's familiar with the mess that is prompting for the method in loader and fetching the stage2 image. It's too late to do anything for F9 besides patch the bugs, but it's time to start thinking about what to do for F10. So, let's start thinking about it. The way I see it, the loader currently does the following things regarding setting up the method: - Support the following installation sources: http/ftp, dvd/cd, nfs, nfsiso, hdiso. It'd also be nice to support regular hd installs. - If stage2= is given, use that as the stage2 image. - If there's a CD in the drive and there's a stage2 image on it, use that. stage2= overrides this. - Support configuration from UI, cmdline, and kickstart. - Configure and bring up the network if required for a method. - DVD/CD should prompt for media check. - Each method implies certain locations for updates.img, product.img, etc. that are checked for automatically. Those are the current features, best I can see. Are there any of these features we want to do away with? Does anything no longer make sense? Now for the more controversial stuff. Here's what I would like to see happen in this area for F10. All these things are open for discussion, so jump right in. - There shouldn't be any differences between booting off the network and booting off media. - loader should be moving to just doing what is required to fetch and mount the stage2 image. This can perhaps include inferring an installation repo based on the location of the stage2 image, but the Problem: If the user booted off a CD and we don't have any method configuration screen, the implied updates.img and product.img checks will never work. - We shouldn't be checking if the inferred repo is valid in any way, perhaps except that we can at least mount it (if the method requires that). This requires making the repo editor in stage2 more useful. It also separates the loader from the payload it's installing more. In particular, any remaining .discinfo checks ought to die. - We shouldn't leave the repo mounted at the end of loader. Problem: RHupdates/ will no longer work. Problem: This means both loader and stage2 will have to have some code for mounting installation sources. This probably isn't such a big problem because stage2 will already require it for error handling. - Part of the last one... we should copy the stage2 image out of its initial location. My reasoning for this is still that it makes error handling easier when the repo has trouble. This requires making the repo editor more useful too. Problem: This increases the memory requirements, which no one likes. Your thoughts? Once we at least have some concept of what should be going on, I can get started on working on a code design - hopefully one that removes a lot more than it adds. - Chris

13 62

Checking for ram to early...
by Joel Andres Granados 12 May '08

12 May '08

Hey people :) Anaconda exits if the system has less than 64 Mb of ram. This is logical because if the system has less, its just not possible to install. But I think we are not giving the power user the opportunity to circumvent this situation. see (368311). What I suggest is to make the check after the running of the post script. If the user was intelligent enough to add some temporary swap, anaconda should install successfully. patch attached, comments appreciated. -- Joel Andres Granados Red Hat / Brno, Czech Republic

3 3

[PATCH, RFC] stop neutering DRI
by Bill Nottingham 12 May '08

12 May '08

The attached patch makes anaconda stop neutering DRI/DRM (at least it should.) It does it by including the DRI userspace modules (from mesa) and the kernel DRM drivers. Why do this? To be more like the 'normal' installed system. Heck, if DRI's going to fail, the system's just going to blow up on the first boot anyway. Furthermore, there are cards/chips that do 2D accel via the 3D pipeline. Plus, if we want to actually disable it in anaconda, we should do it explicitly, not by accident as a consequence of some files not being there. Caveats: - listing the kernel drivers explicitly is a hack - this doesn't pull libGL onto the second stage. Assuming nothing dlopens() it, that shouldn't be a problem Bill

5 9

[PATCH] make scripts/buildinstall take multiple repos
by Will Woods 12 May '08

12 May '08

This patch makes buildinstall accept multiple repo arguments. This is useful when, say, you have a couple of packages that haven't hit rawhide yet, but you want to test them in the installer. ./buildinstall ... http://rawhide... /home/wwoods/myrepo or make testiso REPO="http://rawhide... /home/wwoods/myrepo" -w (sorry if this message shows up a couple of times.. still figuring out how to use git-format-patch and git-send-email) --- scripts/buildinstall | 22 +++++++++++++++++++++- 1 files changed, 21 insertions(+), 1 deletions(-) diff --git a/scripts/buildinstall b/scripts/buildinstall index a5001a9..4c71e16 100755 --- a/scripts/buildinstall +++ b/scripts/buildinstall @@ -69,7 +69,11 @@ while [ $# -gt 0 ]; do ;; *) - REPO=$1 + if [ -z "$REPO" ]; then + REPO=$1 + else + EXTRA_REPOS="$EXTRA_REPOS $1" + fi shift ;; esac @@ -123,6 +127,22 @@ baseurl=$REPO enabled=1 EOF +n=1 +for r in $EXTRA_REPOS; do + if [[ $r =~ ^/ ]]; then + r="file://$r" + fi + cat >> $yumconf <<EOF + +[anaconda-extrarepo-$n] +name=anaconda extra repo $n +baseurl=$r +enabled=1 +EOF + let n++ +done + + BUILDINSTDIR=`mktemp -d ${TMPDIR:-/tmp}/buildinstall.tree.XXXXXX` TREEDIR=`mktemp -d ${TMPDIR:-/tmp}/treedir.XXXXXX` -- 1.5.4.5

2 3

updated repo editor
by Chris Lumens 30 Apr '08

30 Apr '08

As previously mentioned, doing all this repo stuff in stage2 means we require a fancier repo editor. Attached is a tarball with a glade file and python script to run it. Key differences from the one in F9: - supports all the methods we already have - got rid of the baseurl/mirrorlist set of input boxes, replaced with a single input field and a mirrorlist checkbox - uses the FileSelectorButton for picking the directory on a hard drive containing ISO images (at least, it does for now - hopefully I can keep this when actually hooking it all up) I hate the magic changing config UI but I think this one is pretty decent. It doesn't change sizes or anything annoying. Thanks to Martin for convincing me that was the way to go. Comments? - Chris

1 0

anaconda branched for Fedora 9
by Jeremy Katz 29 Apr '08

29 Apr '08

There's a new branch in git, f9-branch, to track any final changes needed to anaconda for Fedora 9. Which means that master is now open to things which involve string changes, big changes, etc. If you commit a fix to f9-branch, please be sure to also cherry-pick it over to master unless the fix is just a quick hack and there's a plan for fixing things right on master. Jeremy

1 0

want to know the sequence of anaconda files.
by Amrish Purohit 29 Apr '08

29 Apr '08

hi all, i have recently joined this list. currently i am working on project of virtual appliance. the root partition of linux installation is enctypted with dm-crypt. now i want to customize this installation in such a way that fresh installation from cd happens on encrypted root. i have download the source of anaconda. i think kickstart file configuration will not help me. i have to make changes in source of the anaconda. i want to know the flow of anaconda installtion and which file of function calls which function or file. this may help me towards my solution. can any have any suggestion to my problem?? amrish purohit ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

[PATCH] fix testiso Makefile target - boot.iso, not netinst.iso
by Will Woods 24 Apr '08

24 Apr '08

As the subject suggests - this patch fixes 'make testiso' to actually produce an iso. -w

2 1

[PATCH] Handle the DVD having a disknumber of ALL. (443291)
by Jesse Keating 24 Apr '08

24 Apr '08

--- image.py | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/image.py b/image.py index 021a0e6..5fece23 100644 --- a/image.py +++ b/image.py @@ -111,6 +111,8 @@ def findIsoImages(path, messageWindow): def getDiscNums(line): # get the disc numbers for this disc nums = line.split(",") + if nums == ['ALL']: # Treat "ALL" DVD as disc 1 + return [1] discNums = [] for num in nums: discNums.append(int(num)) -- 1.5.4.5

7 17

Problem installing RHEL4UP6 X86
by Vijay Asokan 22 Apr '08

22 Apr '08

Hello, I have a problem installing RHEL UP6 on X86_64 platform using vnc install method. Anaconda installer starts the VNC server, and provides the IPaddress to connect. Once connected via a vnc client, I see a black screen. I get the following error on the console: The VNC server is now running. Please connect to 172.30.131.245:1 to begin the install... //usr/bin/mini-wm: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory The problem doesn't seem to occur with the RHEL5 X86_64 release. I found a similar problem being fixed in the RH5 release ( http://rhn.redhat.com/errata/RHBA-2007-0644.html) Any help will be greatly appreciated. Thanks, Vijay

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 2008