Anaconda-devel July 2006

anaconda-devel@lists.stg.fedoraproject.org

19 participants
15 discussions

Splittree - problem..
by Krishnan N 01 Aug '06

01 Aug '06

Hi I'm trying to remaster disc-1 of FC5.. in the process i keep getting the following error that i'm unable to get past... The Process im trying to follow is on the link : http://wings.buffalo.edu/computing/ublinux/HOWTO-createdistro.php Just wondering if anyone here has come across the same... [root@aadisankara ublinux]# /usr/lib/anaconda-runtime/splittree.py --arch=i386 --total-discs=5 --bin-discs=5 --src-discs=0 --release-string="Fedora 5" --pkgorderfile=/home/ublinux/pkgorder.txt --distdir=/home/ublinux/i386 --srcdir=/home/ublinux/i386/SRPMS --productpath Fedora /home/ublinux/i386 Traceback (most recent call last): File "/usr/lib/anaconda-runtime/splittree.py", line 455, in ? logfile = timber.main() File "/usr/lib/anaconda-runtime/splittree.py", line 379, in main self.createSplitDirs() File "/usr/lib/anaconda-runtime/splittree.py", line 233, in createSplitDirs self.createDiscInfo(i) File "/usr/lib/anaconda-runtime/splittree.py", line 158, in createDiscInfo discinfo_file = open("%s-disc%d/.discinfo" % (self.dist_dir, discnumber), 'w') IOError: [Errno 2] No such file or directory: '/home/ublinux/i386-disc1/.discinfo' Will appreciate ur inputs to help me get past the same.. regards krishnan.

3 2

[patch] add --nogr to buildinstall
by Paul B Schroeder 31 Jul '06

31 Jul '06

This adds a --nogr flag to buildinstall so that you don't need to modify anaconda and update NEEDGR in upd-instroot.. Also moves some of graphics related echos inside the ifs for NEEDGR.. No sense in saying you're doing something you're not.. ;) Also fixes annoying -maxdepth flag warning I was seeing with find in the mk-images.* sources.. Tested and seems to work fine for x86.. Applies cleanly against 11.0.5.. I can update it to apply cleanly to the current CVS tree if desired.. Cheers....Paul... -- --- Paul B Schroeder <pschroeder "at" uplogix "dot" com> Senior Software Engineer Uplogix, Inc. (http://www.uplogix.com/)

2 2

build a linux install CD
by Nguyễn Lương Hoàng 28 Jul '06

28 Jul '06

Hi everyone i must wonder how the fadora core installation CD is built? what is the structure of initrd to invoke anaconda to select drivers and partitioning.... can you tell me how to build a linux install CD? thanks --------------------------------- World Cup nay đã có trên trang chủ ưa thích của bạn - hãy ghé qua www.yahoo.com.vn

2 1

RE: Anaconda Installer.
by Krishnan N 27 Jul '06

27 Jul '06

hi Will be great if someone can point me to some simple & easy to understand articles / turorials on how the anaconda Installer works & how it can be customized regards/ krish.

2 1

Install Issue with Remastered FC5 disc-1.
by Krishnan N 24 Jul '06

24 Jul '06

Hi I'm in the process of figuring out " how to remaster FC5 "...... To start with, my task was to Remaster just CD1 of FC5... So, i have stripped the number of RPM's available, on CD1 & remade an image of CD1.... My new CD1 successfully boots & goes thru the installation process...but at the end of it, instead of being prompted to insert disc-2 , i get a message saying " install complete... remove disk & reboot ".... My new CD1 boot well in the command line mode...... But, i'm now trying to figure out, wat is it that tells the anaconda installer to look for disc-2 after disc-1 is installed???? I have attached the script i'm using for ur perusal & comments.. regards linuxnewbie.

1 1

firstboot & disable SElinux
by VnPenguin 23 Jul '06

23 Jul '06

Hi all, I'm working on customized version of FC5. I would like to disable SELinux by default in firstboot. Anyone could tell me how to do this please. Thanks, -- http://vnoss.org Vietnamese Open Source Software Community

1 0

Buildstamps do not match
by Francenildo Pereira Alves 20 Jul '06

20 Jul '06

Hi everyone. Basically I've been back at it, trying to do a buildinstall, and with every progress I make I continue to get the same error when the CD boots - no cd was found that matches your boot media....... I've hacked into the source for anaconda and filled it up with some debug outputs while getting to know my way around a little bit, and I've found out where its going wrong. The buildstamps do not match. I have one buildstamp (/.buildstamp) that is stamped 200605251433.i386 and another one (/mnt/runtime/.buildstamp) that is stamped 200603142328.i386. That causes verifyStamp (found in loader2/method.c) to fail, causeing the message. Now I know the cause, how do I find the solution? I see that buildinstall.pycalls mk-stamp, which puts the current date/time/arch into /tmp/makebootdisk.dir.$$/.buildstamp, which appears to be compiled into the initrd.img on the cdrom (/isolinux/initrd.img). So the question is where is it getting the 200603 build stamp (original fedora 5 build is my guess). And why doesn't the buildinstall process use the same buildstamps for each place. I could hack mk-images to hard code the 200603 stamp, but I would prefer it to stamp it to the correct build date/time. Any information would be fantastic.ThankyouMatt. I am with the same problem, someone could help us. Thanks in advance Francenildo

1 0

Installing Fc5 on dmraid problems
by Sorin Ban 20 Jul '06

20 Jul '06

Hello to everybody. Please help me. I have two SATA drives in a bios fake raid0 on nVIDIA nForce3-250Gb with two partition NTFS for Win XP, one ext3 as Linux root and one for Swap. In FC3 I use a PATA drive with a little /boot partition and everything work OK (run dmraid –ay, mount, chroot; I don't try to make a new initrd). Dmraid -ay creates in /dev/mapper, devices for raid and the four partitions: nvidia_jdabijfd, nvidia_jdabijfd1 … nvidia_jdabijfd4. When I try go to FC5, anaconda fail with message "cannot mount /dev/hdb2 as /" (hdb is the DVD-writer) even if I try to clear install or upgrade. Looking in anaconda.log I observe then fail when it try mount \dev\mapper\nvidia_jdabijfdp2 partition as "/" and pass at mounting the hdb2 partition as "/", fail again because hdb is the DVD-writer. Anaconda find correct the raid device and the partitions, the properties of the partitions are corrects (in Disk druid), but the name of the partition devices create from Anaconda differ of then create from dmraid –ay whit a "p" suffix. The same things are happen in case of Linux rescue DVD mode. What can I do for installing or upgrading FC5? Thanks in advance, Sorin PS. The "p" suffix appears deliberate in Anaconda: anaconda-10.91.16-1 - More consistency in dev naming for dmraid (pjones) booty-0.66-1 - use "mapper/raidnamep0" for partition names instead of "mapper/raidname0"

1 0

can't cleanly exit shell from FC5 rescue CD
by Adam Monsen 19 Jul '06

19 Jul '06

I asked this one on the fedora-list first [1], but no one knew the answer. Thought I'd give you installer expert types a shot. I'm having a problem with the Fedora Core 5 rescue CD: I can't cleanly exit the shell. When I type in 'exit' and hit enter, I see the following: sh-3.1# exit logout ...and nothing happens. Anyone seen this? Any ideas? Here are the exact repro steps for people who like that kind of thing: REPRO STEPS: * boot to Fedora Core 5 rescue CD * type 'linux rescue' at the prompt and hit ENTER * choose language = English * choose keyboard = us * don't start up network interfaces * don't try to find existing installations * at the shell prompt, type 'exit' and hit ENTER EXPECTED RESULT: * system reboots ACTUAL RESULT: * system hangs after 'logout' is printed to the console ADDITIONAL INFO: * No, 'shutdown -r now' doesn't work, either: sh-3.1# shutdown -r now (running in test mode). Greetings. anaconda installer init version 11.0.5 starting mounting /proc filesystem... done creating /dev filesystem... done mounting /dev/pts (unix98 pty) filesystem... done mounting /sys filesystem... done sh-3.1# -- Adam Monsen

1 2

Re: [rhn-users] Kickstart Issue - Custom Bootdisk to Network Install
by Warren_Crigger＠navyfederal.org 14 Jul '06

14 Jul '06

Warren_Crigger(a)navyfederal.org wrote: >>> I do not have the luxury of using DHCP and the normal method of >>> kickstart, so I made a custom boot CD with the isolinux directory and >>> TRANS.TBL file on it from the actual RHEL4AS disk (that's it!). I can >>> boot normally and from there give it testing kickstart boot options >>> which are: >>> >>> linux ks=http://<ip>/profiles/ks.cfg ip=<ip> netmask=<netmask> >>> gateway=<gateway> ksdevice=eth0 >>> >>> It then loads the kernel, starts to grab files off the remote server >>> (see logs below), fires up anaconda, detects the video/mouse/etc, and >>> then says: >>> >>> "you are trying to install on a machine which isn't supported by this >>> release of Red Hat Enterprise Linux ES" >>> >> From a quick search I did... I could only find information relating to >>it being a missing kernel in your repository(there were a few others >>relating to a missing architecture which the Dell PE1650 should be i686). >>https://www.redhat.com/archives/fedora-list/2004-May/msg08527.html >>The link points to older distro's but the reason for the error shouldn't >>be that different... If this is the first box you've tried off the >>repository, might be worth another look to make sure it has all the >>files off all the cd's and permissions are correct for the webserver. >>Hope that helps, >>-Mitch >Thanks for the response + info. I'll check for the 'missing kernel' - I have several kernels in the repository, but none just simply named "kernel.rpm (until now, I copied what kernel I normally use over to that name as well)." >I'll test this out tomorrow as I'm headed home for the day... >You'll notice in the apache logs from the box serving up the media that there are 2 404's for a .img file. It never complains about that during the install - Only later after anaconda does its thing and it loads a few more >files(product, netstg2 images + hdlist and comps.xml). I copied the media per the documentation, until I found that RH was looking for more than what was documented, then copied everything. I can verify ownership is correct, I >did a recursive chown on em all earlier after loading up more stuff off the CDs and actually the permissions are wide open temporarily so my samba user can access them while testing (yea, yea, I know =P). >Thanks! I tried this this morning with no luck. The kernel.rpm being there makes no difference, it still states "you are trying to install on a machine which isn't supported by this release of Red Hat Enterprise Linux ES." The only clue I have is that its looking for "updates.img" from the install source after looking at the apache error logs. I'm at a loss :( I can't find that file on the disks or in my repository, and googling it isn't helping a whole lot, apparently I have to create it but I'm unsure of how to.

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 July 2006