Anaconda-devel May 2006

anaconda-devel@lists.fedoraproject.org

40 participants
57 discussions

Re: Regarding "Confirm Install" box not showing up
by C.C. Chakkaradeep 16 May '06

16 May '06

Hi Steven and all, > ----- Original Message ----- > From: "Steven Augart" <saugart(a)mazunetworks.com> > To: "C.C. Chakkaradeep" <chakkaradeepcc(a)linuxmail.org> > Subject: Re: Regarding "Confirm Install" box not showing up > Date: Mon, 15 May 2006 08:57:00 -0400 > > > > Which version of Anaconda are you running? > Should I assume that you're installing Fedora Core 5? FC 4? Red > Hat 9? Something else? > am using Fedora Core 3 and anaconda version is 10.1 . I have these rpms installed, anaconda-help-10.1.0-1 anaconda-runtime-10.1.0.2-1 busybox-anaconda-1.00.rc1-5 anaconda-10.1.0.2-1 I have successfully customized the RPMs and Installation, except this "Confirm Install" dialog not popping up. > Are you using the stock Anaconda provided with your linux distro on > the installation disk? (I assume so.) Yeah, these rpms are direct from the FC3 CDs. > > I hope we can be helpful. > Thank you. Regards, C.C.Chakkaradeep -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze

1 0

PATCH: Detecting grub failure
by Ragnar Kjørstad 16 May '06

16 May '06

Hi The attached patch adds checking for the exitcode from grub. The old code silently ignored failures from grub, which makes debugging more difficult. --- python/bootloader.py (revision 47239) +++ python/bootloader.py (working copy) @@ -1,4 +1,5 @@ import os +import sys from iutil import getArch, getDiskPart, execWithRedirect, devify import isys import raid @@ -274,13 +275,16 @@ for cmd in cmds: os.write(p[1], cmd + '\n') os.close(p[1]) - execWithRedirect(grubbin, + status = execWithRedirect(grubbin, [ "grub", "--batch", "--no-floppy", "--device-map=/boot/grub/device.map" ], stdin = p[0], stdout = "/dev/tty5", stderr = "/dev/tty5", root = instRoot) os.close(p[0]) + if status: + log("Grub failed with exitcode %d" % status) + sys.exit(0) return -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com Scaling the Linux Datacenter

1 1

RE: Detecting network failure
by Lazarev, Roman 15 May '06

15 May '06

Steve, I have automated generation of the bootdisk.img, in a way where it takes params from CGI, builds new ks.cfg based on params, and then stuffs it into initrd (rdstuff). It's the attached to the system through virtual media. The process takes about 1 minute to the server booting floppy, but it's too much time. I was just testing a new piece of equipment that came in and the server has 4 network ifaces and has feeds to 3 subnets. I didn't know which iface was eth0 which eth3 I also didn't know what subnet is associated with which nic. Yes it does sound strange but it does happen. Anyways, I have co-workers that are using my build and sometimes they can't proceed because they can't retrieve the netstg2 image and all that. So it always comes back to me ;) Some time ago I was speaking to an Intel hardware vendor about introducing a check-net type of a thing from their remote management card. Now that the industry is strongly considering SMASH CLP, this would be akin to Sun's "watch-net"... So... I was wondering if there could be a simple thing in anaconda that's basically - ethtool/mii-tool/tcpdump combo - ok, are we on the subnet? Right, can we ping the remote server? [if not, display in English - dude, I'm not sensing the connection, link down ] - right, can we get to it on port (21, 80, else?) [ if not, dude, your connection is live and good, yes I'm on the network, but the server is down ] right, is the image available [ no there's not even a build tree there, pointing to the right directory ? ] , right - build. Instead there's a "reverse DNS lookup 5 second"... Well that's cryptic ;) Thanks, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: Steven Augart [mailto:saugart@mazunetworks.com] Sent: Monday, May 15, 2006 6:40 PM To: Lazarev, Roman Cc: anaconda-devel-list(a)redhat.com Subject: Re: Detecting network failure Lazarev, Roman wrote: > It also is time consuming to regenerate images every time I want to > test another interface. This comment is intriguing. What do you mean by "regenerate images every time I want to test another interface" ? Do you mean that you're testing different kinds of network interfaces, or is there something else going on here? > Is it possible/is there already a stub that tests network connectivity > and says - yes, I'm able to communicate - in plain English language ;) I'm sorry, I don't understand what you mean by "a stub". Are you hacking on Anaconda and adding features to the Python components? My experience with Anaconda guts is almost entirely with the C loader stage. --Steven Augart

2 1

Detecting network failure
by Lazarev, Roman 15 May '06

15 May '06

Hi! I'm messing around with the new build here for RHEL4 and bumping into a problem - a simple one too - problems with network connectivity. Every time it happens I have to wait for anaconda to time out trying to get images from the network. It also is time consuming to regenerate images every time I want to test another interface. Is it possible/is there already a stub that tests network connectivity and says - yes, I'm able to communicate - in plain English language ;) Thanks a bunch!!! Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173

2 1

Failed to loading mousedev module
by Philip Prindeville 15 May '06

15 May '06

Is this code deprecated, or what exactly? From what I can tell, the mouse command has gone away, right? So why does this message always appear, or what can one do to fix it? At the very least, can we fix the syntax on the message? Should I file a bug? Thanks, -Philip

1 0

Re: Problem Testing Anaconda
by Ali Majdzadeh 15 May '06

15 May '06

Hi David Thanks for your attention I am using Redhat Enterprise Linux 4. Do you think I should try Fedora Core 5? Best Regards Ali On 5/15/06, David Cantrell <dcantrell(a)redhat.com> wrote: > > Ali Majdzadeh wrote: > > Hi Again Steven > > I downloaded the CVS version of Anaconda, but the compilation fails with > the > > following errors: > > > > ... > > make[2]: Leaving directory `/opt/Tools/anaconda/isys/gzlib' > > cc -c -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -Wall -Werror > > -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 > > -D_LARGEFILE64_SOURCE=1 -DUSESELINUX=1 -I/usr/include/python2.3 -I.. > > -DHAVE_NFS -fPIC -o isys.lo isys.c > > In file included from net.h:5, > > from isys.c:55: > > /usr/include/linux/ethtool.h:18: error: syntax error before "u16" > > /usr/include/linux/ethtool.h:20: error: syntax error before "port" > > /usr/include/linux/ethtool.h:21: error: syntax error before > "phy_address" > > /usr/include/linux/ethtool.h:22: error: syntax error before > "transceiver" > > /usr/include/linux/ethtool.h:23: error: syntax error before "autoneg" > > /usr/include/linux/ethtool.h:27: error: syntax error before '}' token > > /usr/include/linux/ethtool.h:50: error: syntax error before "u8" > > /usr/include/linux/ethtool.h:64: error: syntax error before "u8" > > /usr/include/linux/ethtool.h:73: error: syntax error before "u8" > > make[1]: *** [isys.lo] Error 1 > > make[1]: Leaving directory `/opt/Tools/anaconda/isys' > > make: *** [subdirs] Error 1 > > > > Any ideas? > > Check the modest BuildRequires line in anaconda.spec and make sure you > have all the development things installed. > > -- > David Cantrell > Red Hat / Westford, MA >

2 3

Re: Problem Testing Anaconda
by Ali Majdzadeh 15 May '06

15 May '06

> > Hi Steven > I use anaconda-10.2.1.5 but unfortunately I can not remember where I have > downloaded it. > > Regards > Ali > > > On 5/15/06, Steven Augart <saugart(a)mazunetworks.com> wrote: > > > > On Mon, 2006-05-15 at 19:37 +0430, Ali Majdzadeh wrote: > > > there is no version-release string in the output message it > > > generates. > > > > Dear Ali, > > > > Did you download Anaconda from CVS? Or did you download a particular > > numeric version? Where did the sources come from? If you don't know > > for sure what version you have, that's OK, just please say how you got > > the sources and where from. > > > > --Steven > > > > > > >

1 1

Re: Problem Testing Anaconda
by Ali Majdzadeh 15 May '06

15 May '06

Hi Jasper Thanks for your attention I checked the directory where I installed Anaconda. Actually, there is no log out there, and as you probably have noticed, there is no version-release string in the output message it generates. Any ideas? Regards Ali On 5/15/06, Jasper O'neal Hartline <jasperhartline(a)adelphia.net> wrote: > > I won't be able to help you probably, but I think Anaconda should print > it's version-release string > somewhere in the logs or right there during or before some of the very > first messages are printed > and operations take place. I don't know why, just sounds good. > > J. Hartline > > > Ali Majdzadeh wrote: > > > Hi All > > I have compiled and installed Anaconda. > > I used the following commad to test it: > > > > ./anaconda --method cdrom:///media/cdrom --rootpath //opt/install/ > > > > I got the following error: > > > > * Display mode = g > > * Method = cdrom:///media/cdrom > > Probing for video card: ATI Radeon Mobility 9200 > > Probing for monitor type: Unknown monitor > > Probing for mouse type: Skipped mouse probe. > > Starting graphical installation... > > Exception starting GUI installer: splashScreenShow() takes exactly 1 > > argument (0 given) > > * Exception starting GUI installer: splashScreenShow() takes exactly 1 > > argument (0 given) > > GUI installer startup failed, falling back to text mode. > > * GUI installer startup failed, falling back to text mode. > > Traceback (most recent call last): > > File "./anaconda", line 1049, in ? > > methodobj = CdromInstallMethod(method[8:], rootPath, intf) > > TypeError: __init__() takes exactly 5 arguments (4 given) > > > > Can anyone help me? > >

2 1

Problem Testing Anaconda
by Ali Majdzadeh 15 May '06

15 May '06

Hi All I have compiled and installed Anaconda. I used the following commad to test it: ./anaconda --method cdrom:///media/cdrom --rootpath //opt/install/ I got the following error: * Display mode = g * Method = cdrom:///media/cdrom Probing for video card: ATI Radeon Mobility 9200 Probing for monitor type: Unknown monitor Probing for mouse type: Skipped mouse probe. Starting graphical installation... Exception starting GUI installer: splashScreenShow() takes exactly 1 argument (0 given) * Exception starting GUI installer: splashScreenShow() takes exactly 1 argument (0 given) GUI installer startup failed, falling back to text mode. * GUI installer startup failed, falling back to text mode. Traceback (most recent call last): File "./anaconda", line 1049, in ? methodobj = CdromInstallMethod(method[8:], rootPath, intf) TypeError: __init__() takes exactly 5 arguments (4 given) Can anyone help me? Best Regards Ali

1 0

Regarding "Confirm Install" box not showing up
by C.C. Chakkaradeep 15 May '06

15 May '06

Hi all, I am using kickstart installation. Here, i have done my own partitioning,language selection and keyboard selection, timzone and skipped these steps for the user. The user is presented only with the root password screen.Even the packages are customized and selected in the kickstart itself. Everything is working fine, except that my user wants a confiorm message as how we get in normal installtions which shows "You need 2 cds to continue" and asks for "Continue" or "Reboot". I have attached my kickstart file with this mail.. How to bring this screen up via kickstart? Thanks in advance... Regards, C.C.Chakkaradeep -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze

2 1

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 2006