Anaconda-devel September 2005

anaconda-devel@lists.stg.fedoraproject.org

37 participants
29 discussions

Changing the default theme
by Manilal K M 05 Feb '06

05 Feb '06

Hello everybody, I don't know whether this query is an offtopic. However I need information regarding it. I have custom compiled the FC-4 and installed it sucessfully with the great help from anaconda-devel-list. Now I need to change the default theme clearlooks to "Simple". I edited the patch associated with redhat-artwork (redhat-artwork-0.121-clearlooks.patch) and the file "redhat-artwork-0.122/gtkrc1-skel" and changed them to "Simple". However I noticed NO change in the theme. After Logging in I still get the default Blucurve icons and Clearlooks theme. Kindly advice. regards Manilal

3 4

[PATCH] FC4 cannot load driver disk image on a disk partition
by Akinobu Mita 22 Nov '05

22 Nov '05

Hello, I tried to load driver disk image on a partition in USB storage device. (/dev/sda1:dd.img) But It failed. Steps to Reproduce: 1. create driver disk image (dd.img) 2. put dd.img on USB storage device partition (/dev/sda1) 3. start FC4 installer with "linux dd" 4. select driver disk source as /dev/sda1 and choose the file "dd.img" Actual results: anaconda went wrong stage. anaconda displays: ---| Insert Driver Disk |--- Insert your driver disk into /dev/sda and press "OK" to continue. Expected results: Successfully load from driver disk image. I think below patch fixes this problem. but it is untested. --- anaconda-10.3.0.7/loader2/driverdisk.c.orig 2005-07-27 18:25:13.000000000 +0900 +++ anaconda-10.3.0.7/loader2/driverdisk.c 2005-07-27 18:25:56.000000000 +0900 @@ -380,6 +380,7 @@ int loadDriverFromMedia(int class, modul break; } stage = DEV_LOAD; + break; } case DEV_INSERT: {

3 5

Re: Apples and snakes
by Alan Milligan 09 Nov '05

09 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Katz wrote: > Unfortunately, this would not be the desired behavior of other people. > So as it stands, we're going to stick to requiring the kickstart config > to be specified. > This typical RH response hightlights the fundamental flaw in Fedora and needs to change if this platform is going to have any relevance as the Linux user community's expectations evolve upward. Community users are clearly indicating that they'd like a generalised installer as we all have many and varied uses for Linux - quite often outside the norm - RH's norm at least. Why can't we consider adding another input parameter to the anaconda-runtime suite to package a default kickstart into an image. Most people won't use this and they will still enjoy the status quo. Those of who would like this feature would love to contribute the code even - if only we could ... Alan P.S. I too very strongly support URLGrabber into anaconda!!! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDMOVPCfroLk4EZpkRAkOFAJ9quXZYyEb3LmVt8je1Kjyf03pmFgCg2BEG g3kc+N4Hp3dqqSLkg6BoUrE= =NfqS -----END PGP SIGNATURE-----

5 11

[PATCH] RHEL 4 U2 nfsmountopts
by Brian Long 13 Oct '05

13 Oct '05

The patch in the following Bugzilla adds nfsmountopts flag to Anaconda. This is parsed by loader and used in the doPwMount function when the NFS client mounts /mnt/source. This is needed to override the kickstart kernel defaults in RHEL 4 of rsize=32768,wsize=32768,udp. If tcp was being used, the large rsize,wsize would not be a problem. With udp, however, large rsize,wsize is causing longer installation times due to retransmissions. Please consider this patch for U2 GA or a future RHEL 4 update. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168384 IT 79818 Thank you. /Brian/ -- Brian Long | | | IT Data Center Systems | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s

3 9

DVD asking for Disc 2
by Alexander Rau 30 Sep '05

30 Sep '05

Hi: I created a DVD of RH ES 3 U 5 using ftp://people.redhat.com/ckloiber/mkdvd-rhel3u2.sh Everything goes well until it starts installing packages and and asks for Disc 2. Once I hit enter it tells me that the disc that's in is not the proper RH ES disc... Any thoughts? Thanks AR

2 1

RHEL 3 U5 Anaconda Rebuild Build Error
by Brian Long 28 Sep '05

28 Sep '05

I'm trying to rebuild and patch anaconda-9.1.5.8 from RHEL 3 U5. While in the isys subdirectory, I get the following error. I'm not a gcc or diet guru. Any ideas how I fix this? cc -ffunction-sections -I/usr/include/python2.2 -I.. -Wall -Os -g -DHAVE_NFS -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Werror -c -o ethtool.o ethtool.c ar rv libisys.a ethtool.o a - ethtool.o cc -ffunction-sections -I/usr/include/python2.2 -I.. -Wall -Os -g -DHAVE_NFS -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Werror -c -o getipaddr.o getipaddr.c ar rv libisys.a getipaddr.o a - getipaddr.o diet cc -c -ffunction-sections -I/usr/include/python2.2 -I.. -Wall -Os -g -DHAVE_NFS -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Werror -DGZLIB=1 -DDIET=1 "-Du_char=unsigned char" -o nfsmount.do nfsmount.c gcc323: cannot specify -o with -c or -S and multiple compilations make[1]: *** [nfsmount.do] Error 1 make[1]: Leaving directory `/auto/linux/sandbox/brilong/ciscolinux/anaconda/RHEL3-AS.update5/SRPM/anaconda/BUILD/anaconda-9.1.5.8/isys' make: *** [subdirs] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.73098 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.73098 (%build) Thanks! /Brian/

2 3

dead code in anaconda
by patrickd＠vmware.com 27 Sep '05

27 Sep '05

Hey guys, I noticed a couple bits of dead code in the anaconda-9.1.5.8 code. In partIntfHelpers.py - sanityCheckMountPoint(): ... if mntpt: passed = 1 if not mntpt: passed = 0 else: if mntpt[0] != '/' or (len(mntpt) > 1 and mntpt[-1:] == '/'): passed = 0 elif mntpt.find(' ') > -1: passed = 0 the "if not mntpt" check will never be hit. This would be better written as: if mntpt: passed = 1 if mntpt[0] != '/' or (len(mntpt) > 1 and mntpt[-1:] == '/'): passed = 0 elif mntpt.find(' ') > -1: passed = 0 Also, there's a bug in this function where if you're "editing" an existing partition in the graphical installer and you decide to reformat something like a swap partition as ext2/ext3, there is no requirement to specify a mount point for it. Not really a huge bug, but it's handled differently than when you normally format something as ext2/ext3. Another bit I saw was: In language.py - __init__(): ... allSupportedLangs = [] langInfoByName = {} langFilter = {} allInstalledFlag = 0 langsInstalled = [] if os.access("/usr/share/anaconda/locale-list", os.R_OK): f = open("/usr/share/anaconda/locale-list") lines = f.readlines() f.close() for line in lines: line = string.strip(line) (lang, map, font, name) = string.split(line, ' ', 3) langInfoByName[name] = (lang, map, font) allSupportedLangs.append(name) if allInstalledFlag or (langFilter and langFilter.has_key(lang)): langsInstalled.append(name) ... The langsInstalled list won't ever have anything added to it since allInstalledFlag is never changed and nothing is ever added to the langFilter hash. -p.

1 0

I do want to customize my own distribution (was RE: I don't want to customize my own distribution.....)
by Edwards, Scott (GE Healthcare) 27 Sep '05

27 Sep '05

Hello, I'm still having the same problem I was having almost a year ago, the famous failure after "Preparing RPM transaction...". I made a custom install for Fedora Core 2 which worked fine. Last year I tried to make a custom install of Fedora Core 3 using the exact same procedure, and it always failed after "Preparing RPM transaction...". I worked on it for a couple of weeks trying different things and never could get it to work. At the time there were some instructions on creating a custom Fedora Core 3 CD and I followed them exactly but it still failed. I had to finally abandon the project. I am trying to create a custom install now with CentOS and I get the same problem as I did with Fedora Core 3. Does anyone have any ideas as to what could have changed between Fedora Core 2 and 3 that would break the procedure? These are the steps I follow (after the CD directory is all prepared): /usr/lib/anaconda-runtime/genhdlist --productpath=CentOS $PWD PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder $PWD i386 CentOS > $TEMP_DIR/pkgfile /usr/lib/anaconda-runtime/genhdlist --withnumbers --fileorder $TEMP_DIR/pkgfile --productpath=CentOS $PWD Is there a step I need to add? I have just tried a Google Search and a search of the Fedora Wiki/Anaconda and I can't find instructions for creating a custom CD now. If someone could point me to those instructions on the Wiki, I will try them. Thanks -Scott -----Original Message----- From: anaconda-devel-list-bounces(a)redhat.com [mailto:anaconda-devel-list-bounces@redhat.com]On Behalf Of Greg Morgan Sent: Wednesday, August 17, 2005 8:55 PM To: anaconda-devel-list(a)redhat.com Subject: Re: I don't want to customize my own distribution..... -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Summerfied wrote: > Dustin kirkland wrote: > >> Hey list- >> >> I think since I joined this list earlier this year, probably 3/4 of >> the traffic has been requests to help customize distributions. >> >> I was wondering if it would make any sense at all to separate "the >> further development of the anaconda toolset" and "the roll your own >> distro starting with Fedora" into different lists? > > > Not a lot I'd think. The volume is not high, those best able to answer > would need to be on both lists to provide a service, and the questions > here show what needs to be covered by anyone who feels an urge to document. > > Speaking of feeling the urge to document, perhaps the list traffic will change as more content is added to the Anaconda wiki, http://fedoraproject.org/wiki/Anaconda. You almost have to have a brief understanding of the anaconda development process at first to roll your own. Hence, the traffic. The only problem is that once critical mass has been attained few leave trails for others....but that's for the Anaconda secrets book. ;-) If you have any brief snippets you'd like to add to the wiki, then please let me know after you have added an account here http://fedoraproject.org/wiki/UserPreferences. Adding content to the wiki may be a better way to shape the traffic on this list than dividing the list. Regards, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDA/iSxyxe5L6mr7IRAsQXAJ4jnGkNx0Mm0BmagzuckLNHHwWo6gCaA7dI Q0jDEnuMLdt2qlbX0H9Nk80= =3wS2 -----END PGP SIGNATURE----- _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list

3 2

adding new kernels to bootloader
by Manas Alekar 27 Sep '05

27 Sep '05

Hi! If I wanted to install 2 kernels, and wanted both to appear in the menu.lst file, how can that be done? Only the kernel which booted the CD seems to get added to the menu.lst by anaconda. Thanks in advance. Regards, Manas ps: need to add a debug patched kernel to a comp sci distro I have been trying to make. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

where is anaconda hidden?
by greg wm 24 Sep '05

24 Sep '05

hi, i'm looking inside boot.img (on CentOS 4.1). when this is burned to a CD and booted, anaconda is invoked (eventually). but from where? it isn't in the initrd.img, or if it is, i can't find it.. why do i care? i want to remotely install without any CDs. i'm trying to find the code that runs when you boot from CD.. if there's a better place to ask this question, please advise. ty, greg

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel September 2005