Anaconda-devel May 2006

anaconda-devel@lists.fedoraproject.org

40 participants
57 discussions

Prompting for customization
by Philip Prindeville 28 May '06

28 May '06

I was wondering what would be involved in adding steps to a build DVD where additional per-user customization is done. Since the company does a poor job of tracking which PC's (and their associated MAC addresses) are given out to which users (new hires especially), it's hard to discover (via LDAP queries, for instance) what user name owns a PC, what resources should be preconfigured on it (such as SMB share volumes, etc). So I was thinking of adding a step where a pop-up (or series of pop-ups) prompts the user for things like: * his AD domain; * his AD username (different from his UNIX name); * his AD password; * his desired MS networking shares; * his Wifi SSIDs and associated Radius information etc, etc. Is there an easy way to do this? Are there any examples out there of someone doing this? Would it be something that could be easily added into Anaconda via script-extensions? -Philip

5 10

Simplifying ks.cfg files
by Philip Prindeville 25 May '06

25 May '06

Here's a random musing... (I have a lot of these.) Rather than using --ondrive= and --drive= for the clearpart and part commands in the ks.cfg file, why not have a single global command like "usedrive sda" or whatever? That way, you don't have to worry about making an incomplete edit or having an inconsistent configuration that sets the MBR on one drive, but formats partitions on another, etc. etc. -Philip

1 0

Buildstamps do not match
by Matt Paine 25 May '06

25 May '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.py calls 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. Thankyou Matt.

1 0

Anaconda error
by Fabricio Lopes de Souza 24 May '06

24 May '06

Hi , Im getting some error in package selection : [error] Traceback (most recent call last): File "/usr/bin/anaconda", line 1218, in ? intf.run(id, dispatch) File "/usr/lib/anaconda/text.py", line 512, in run rc = apply(win, (self.screen, ) + args) File "/usr/lib/anaconda/textw/grpselect_text.py", line 148, in __call__ self.__deselectPackage(grp, pkg) File "/usr/lib/anaconda/textw/grpselect_text.py", line 52, in __deselectPackage except mdErrors.PackageSackError: NameError: global name 'mdErrors' is not defined [/error] i have the anacdump.txt file , if is needed to debug , tell me and i atach to email ! and another question , im editing the fedora 5 instalation . but i only edit the comps.xml and do a createrepo . Am i missing anything ? [sorry bad english ;]

2 1

are driver disks broken in FC5?
by Dan Carpenter 24 May '06

24 May '06

Has anyone got a driver disk to work in FC5? I created a driver disk, it detected and loaded fine for the install but after the install it wasn't in /lib/modules/`uname -r`/updates/. I looked through the source. The code to copy drivers to /lib/modules/`uname -r`/updates/ is in copyExtraModules which is only used by doPostInstall in packages.py. As far as I can tell from looking at the source this code is never called. If you do a `grep packages . -R | grep import` you can see which parts of packages.py are used and it's not there. Of course, if anyone had successfully created a driver disk for FC5 then I must be doing something wrong. :) regards, dan carpenter

2 1

Anaconda Font Selection Problem
by Ali Majdzadeh 22 May '06

22 May '06

Hi Everybody I have added Persian fonts to stage2.img. How can I configure anaconda to use these newly installed fonts? (I want to view Persian texts without any problem.) Regards Ali

1 0

Anaconda Version In Redhat Enterprise Linux 4
by Ali Majdzadeh 22 May '06

22 May '06

Hi EveryBody I have compiled anaconda-10.2.1.5. Is there anyway to use this version instead of RHEL 4's anaconda? What version of anaconda is used in RHEL 4? Best Regards Ali

3 2

firewall icmp
by Alexandre CONRAD 19 May '06

19 May '06

Hello, how can I setup the kickstart to enable firewall and allow ICMP (pings, traceroutes) from outside without having to do any post configuration ? Thank you. Regards, -- Alexandre CONRAD - TLV Research & Development tel : +33 1 30 80 55 05 fax : +33 1 30 80 55 06 6, rue de la plaine 78860 - SAINT NOM LA BRETECHE FRANCE

2 1

Remounting CD/DVD when running %post?
by Philip Prindeville 17 May '06

17 May '06

Ok, going back and looking at: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=129091 this patch works pretty well for me, except... one small point. Just before PostInstall() gets run, I'm wondering if we shouldn't unmount /mnt/source and remount it as /mnt/sysimage/mnt/source... then create a link as: ln -s /mnt/sysimage/mnt/source /mnt/ so that both chroot'd and non-chroot'd %post scripts can see /mnt/source correctly? Does that seem reasonable? I'm not a Python guru (Perl is my preferred perversion), so if anyone has a patch for me to try out, I'd be happy to oblige them. Thanks, -Philip

1 0

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

17 May '06

> > Hi David > Thanks for your clarifying. > I am going to test the issue using Fedoras Core 5. > > Ragards > Ali > > > On 5/15/06, David Cantrell <dcantrell(a)redhat.com> wrote: > > > > Ah, sorry about that. Rawhide is technically called Fedora Development > > (I guess). It's the active development tree for the next release of > > Fedora Core. Trees are updated daily. More info: > > > > I would point you at a URL on fedoraproject.org, but I can't find > > anything in that wiki at the moment. > > > > But understand that rawhide is not a release, it's just an ongoing tree > > that changes daily. If you want to jump in to that world, be sure to > > get on fedora-test-list and/or fedora-devel-list. > > > > > > Ali Majdzadeh wrote: > > > Hi David > > > Sorry, but I do not know the meaning of rawhide. Would please explain > > it > > > more? > > > > > > Regards > > > Ali > > > > > > On 5/15/06, David Cantrell <dcantrell(a)redhat.com> wrote: > > > > > > > >It depends on what your goal is. It's going to be unpleasant to work > > on > > > >rawhide anaconda on RHEL4, so if you want to do that, you should > > > >consider using rawhide. > > > > > > > >You can check out the RHEL4 branch of anaconda from CVS as > > well. It's > > > >named 'rhel4-branch'. > > > > > > > >Ali Majdzadeh wrote: > > > >> 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 > > > >> > > > > > > > > >-- > > > >David Cantrell > > > >Red Hat / Westford, MA > > > > > > > > -- > > David Cantrell > > Red Hat / Westford, MA > > > >

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