Anaconda-devel October 2005

anaconda-devel@lists.fedoraproject.org

27 participants
39 discussions

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

06 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 10 Nov '05

10 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

Current dir/include path of kickstart files?
by Toralf Lund 31 Oct '05

31 Oct '05

I have a kickstart file with the following construct: %packages --resolvedeps %include workstation-pkgs.cfg - i.e. I'm storing package selection in a separate file. The main kickstart and workstation-pkgs.cfg will both be stored on the root of the install medium. I believe this worked fine in the past, but with Enterprise Linux 4WS, I get an error like "workstation-pkgs.cfg: no such file or directory". I change the include line to %include /mnt/source/workstation-pkgs.cfg everything works fine, but it doesn't seem quite right to make such assumptions about the mount point of the install medium. So, where does the kickstart mechanism look for included files? What's the current directory on kickstart execution? Has this changed recently? - Toralf

2 2

iSCSI install: support install-from and/or install-to
by Patrick Mansfield 25 Oct '05

25 Oct '05

Hi - I am looking into adding iSCSI install support to anaconda. Any opinions on supporting install from iSCSI, such as CDROM (sr) or local disk (sd)? This seems useful in some cases, though it is not required to suppport installing to iSCSI disks: a network, local scsi, or ide install method could still be used. Supporting this means we would have to support iSCSI in the stage1 (loader/initrd) portion rather than in stage2 of the installation. -- Patrick Mansfield

2 5

.po files
by Michel MENGIS 22 Oct '05

22 Oct '05

Hi, How do you build .po files for the common language? Do u have a script which is parsing all anaconda .py or do u build it ? I had some modification in anaconda, and I would like to translate all sentences tagged _ Best regards, Michel MENGIS__________________________ POSEIDON Project Manager EPFL - DIT - DIT-SB Ecole Polytechnique Fédérale de Lausanne - EPFL Tel: (+41) 021 693 2266

1 0

Re: Where to start from?
by C.C. Chakkaradeep 21 Oct '05

21 Oct '05

----- Original Message ----- From: "John Summerfied" <debian(a)herakles.homelinux.org> To: Subject: Re: Where to start from? Date: Wed, 19 Oct 2005 07:22:48 +0800 > > C.C. Chakkaradeep wrote: > > Hi all, > > > > i want to modify some of the features of anaconda, like putting > > my own rpms in the installer...modifying the comps.xml and even > > enhancing gui, how doi start?..is there any source code > > documentation for it? > > What have you done to help yourself? I know python and C. I have downloaded the source code, but dont know where to start...how the process goes on?... the /sbin/loader - this is the one which gets executed and the anaconda gui pops up, so where does this get invoked, which python script/c file is responsible for this? thanks in advance, with regards, Chakkaradeep.C.C -- _______________________________________________ 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

RE: I do want to customize my own distribution (was RE: I don'twant to customize my own distribution.....)
by Edwards, Scott (GE Healthcare) 20 Oct '05

20 Oct '05

Yup, that fixed it!! Seems to work fine now!! I should add that to the Anaconda wiki... Thanks to all that helped with suggestions, etc. -Scott -----Original Message----- From: Brian Long [mailto:brilong@cisco.com] Sent: Thursday, October 20, 2005 2:19 PM To: Edwards, Scott (GE Healthcare) Cc: anaconda-devel-list(a)redhat.com Subject: RE: I do want to customize my own distribution (was RE: I don'twant to customize my own distribution.....) On Thu, 2005-10-20 at 15:04 -0500, Edwards, Scott (GE Healthcare) wrote: > After messing around with the SL scripts I have discovered exactly what the problem is. I just don't know what the solution is. > > The problem is the Java rpms. If I include the jre*.rpm and/or the jdk*.rpm the genhdlist always spits out the warning that "ordering not found" for those packages and the installation fails as soon as it gets to the Preparing for RPM installation stage. If I leave those packages out the install completes successfully. > > Does anyone have any ideas as to why the jre rpm wouldn't have an ordering? I am assuming that Sun left something out of them that anaconda needs? Sure. Sun incorrectly names their RPMs they provide for download vs. the built-in N-V-R (name version release). If you run "rpm -qp --qf '% {name}-%{version}-%{release}\n' jre*.rpm", you should rename the RPM to that name. This takes care of genhdlist, etc. /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

1 0

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

20 Oct '05

After messing around with the SL scripts I have discovered exactly what the problem is. I just don't know what the solution is. The problem is the Java rpms. If I include the jre*.rpm and/or the jdk*.rpm the genhdlist always spits out the warning that "ordering not found" for those packages and the installation fails as soon as it gets to the Preparing for RPM installation stage. If I leave those packages out the install completes successfully. Does anyone have any ideas as to why the jre rpm wouldn't have an ordering? I am assuming that Sun left something out of them that anaconda needs? Thanks -Scott -----Original Message----- From: Connie Sieh [mailto:csieh@fnal.gov] Sent: Tuesday, September 27, 2005 9:26 AM To: Edwards, Scott (GE Healthcare) Cc: anaconda-devel-list(a)redhat.com Subject: Re: I do want to customize my own distribution (was RE: I don't want to customize my own distribution.....) Scott, We saw the need to be able to customize RedHat based releases when we designed Scientific Linux. Scientific Linux is a RHEL 3/4 rebuild just as Centos is, but with the ability to customize it. We call these customizations "sites" as different "sites" might want customizations. Items that can be customized include Custom install images used by anaconda Custom version of anaconda(has to be based on RHEL 3/4 version) Added rpms Updated rpms Downgraded rpms including the kernel For more information see http://www.scientificlinux.org/documentation/howto/create.site The describes how to make a site, indicated for 3.0.x, same general instructions for 4.x . ftp://ftp.scientificlinux.org/linux/scientific/ For a example of a customized site ftp://ftp.scientificlinux.org/linux/scientific/303/i386/sites/Fermi/ As you can see from the above url, this is basically a release within a release, with only the changes in the site directory. -Connie Sieh Fermi National Accelerator Laboratory On Mon, 26 Sep 2005, Edwards, Scott (GE Healthcare) wrote: > > > 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 > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/anaconda-devel-list >

4 3

RE: "Cannot allocate memory"
by Aggarwal, VikasX 19 Oct '05

19 Oct '05

I have statically compiled daemon on diskette and related config files are there. I made driver-update disks for crc32c libcrc32c etc. I no more get "cannot allocate memory" Daemon send the login , target gives login response and also target iqN name. Daemon is trying to do the first ioctl(ESTABLISH_SESSION) Now scsi_add_host will fail. Stack trace ---- Sysfs_create_dir Create_dir Class_device_add Scsi_sysfs_add_host Scsi_add_host Iscsi_create_host Iscsi_ioctl_establish_session Sys_ioctl Syscall_call -----Original Message----- From: Jeremy Katz [mailto:katzj@redhat.com] Sent: Wednesday, October 19, 2005 1:48 PM To: Aggarwal, VikasX Cc: anaconda-devel-list(a)redhat.com; Mike Christie Subject: Re: "Cannot allocate memory" On Mon, 2005-10-17 at 15:09 -0700, Aggarwal, VikasX wrote: > I have built an iSCSI driver update disk as I need to read iSCSI disk > during installation. Just adding a driver isn't going to be enough here. There's the daemon and some other pieces which need to be integrated as well before you'll be able to use iSCSI disks at install time. Jeremy

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel October 2005