October 2005 - Anaconda-devel - Fedora mailing-lists

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

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

19 Oct '05

I have built an iSCSI driver update disk as I need to read iSCSI disk during installation. But when my daemon tries to do ioctl to driver it gets "Cannot allocate memory" There is not much running. Why the driver's memory allocation will fail during the installation environment.? The reason I am asking it here is because the driver/daemon work fine when machine is already booted up/running. But I need to use that driver during installation phase. I am installing RHEL 4.0 , kernel 2.6.9-22 and my driver is cisco iscsi initiator 4.0.1.11 built for this kernel. Any ideas to troubleshoot this. -vikas

2 1

help: can i load kernel modules crc32c & md5
by Aggarwal, VikasX 19 Oct '05

19 Oct '05

Hi, My driver needs these modules(crc32c & md5) during installation phase itself. Please help . How can i load kernel modules crc32c & md5 while still have'nt kicked off the installation. I did ctrl-alt-f1 and typed #modprobe crc32c && #modprobe md5 My driver is built on driver-update-disk but additionally it needs crypto modules as well. Regards -vikas aggarwal

2 1

Where to start from?
by C.C. Chakkaradeep 19 Oct '05

19 Oct '05

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? i would be very happy if anyone helped me on this.. thanks in advance.. regards, 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

Upgrade from RHL 7.3 to ....
by John Summerfied 19 Oct '05

19 Oct '05

I've looked at the Anaconda list from Jan 05 and don't see the answer there. I may need to upgrade a RHL 7.3 (plus legacy) box to Fedora or a RHEL clone or something. {Can,Should,Might} Anaconda be able to do this? My suspicion is that it can go from 7.3 to EL because it's very like upgrading AS to EL, but I'd like affirmation before I try it. -- Cheers John -- spambait 1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list

2 4

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

18 Oct '05

Can anyone in anaconda mailing list tell, how to load those modules from one of the packages "during preinstall phase of RHEL4.0 U2" ? -vikas -----Original Message----- From: Mike Christie [mailto:michaelc@cs.wisc.edu] Sent: Tuesday, October 18, 2005 2:46 PM To: Aggarwal, VikasX Cc: anaconda-devel-list(a)redhat.com Subject: Re: "Cannot allocate memory" Aggarwal, VikasX wrote: > Mike, > I just checked /proc/kallsyms > Crypto_alloc_tfm && crypto_alloc_tfm2 are listed there along with > other crypto_XYZ. > Seems "during install time" the crypt is available statically . Not > sure why initiator still getting NULL when it called crypto_alloc_tfm. > it is not those, it is the md5 and crc modules that hook in the crypto api that are needed.

1 0

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

18 Oct '05

Mike, I just checked /proc/kallsyms Crypto_alloc_tfm && crypto_alloc_tfm2 are listed there along with other crypto_XYZ. Seems "during install time" the crypt is available statically . Not sure why initiator still getting NULL when it called crypto_alloc_tfm. -vikas -----Original Message----- From: Mike Christie [mailto:michaelc@cs.wisc.edu] Sent: Monday, October 17, 2005 3:51 PM To: Aggarwal, VikasX Cc: anaconda-devel-list(a)redhat.com Subject: Re: "Cannot allocate memory" Aggarwal, VikasX wrote: > I have built an iSCSI driver update disk as I need to read iSCSI disk > during installation. > install to a iscsi disk is really not supported like this, so I am not sure what is available at install time. > But when my daemon tries to do ioctl to driver it gets "Cannot > allocate memory" > Normally during a light load like this is, it is becuase you do not have a crypto module loaded (they return ENOMEM when if it is not loaded). Send me your iscsi.conf file.

1 0

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

18 Oct '05

Only these 2 entries in /etc/iscsi.conf DiscoveryAddress=192.168.0.119:3260 TargetName=iqn.1987-05.com.cisco.00.c9564bfc19bb80c0d168338aa9199d34.tar get_netapp1 Also my target replies with headerdigest=no, datadigest=no as I checked in login-response. DO I still need the crypto modules in installation phase. I can build them and load them through floppy ? Is there a way in anaconda installer to enable the crypto modules? -vikas -----Original Message----- From: Mike Christie [mailto:michaelc@cs.wisc.edu] Sent: Monday, October 17, 2005 3:51 PM To: Aggarwal, VikasX Cc: anaconda-devel-list(a)redhat.com Subject: Re: "Cannot allocate memory" Aggarwal, VikasX wrote: > I have built an iSCSI driver update disk as I need to read iSCSI disk > during installation. > install to a iscsi disk is really not supported like this, so I am not sure what is available at install time. > But when my daemon tries to do ioctl to driver it gets "Cannot > allocate memory" > Normally during a light load like this is, it is becuase you do not have a crypto module loaded (they return ENOMEM when if it is not loaded). Send me your iscsi.conf file.

1 0

FC-devel install
by Florian La Roche 17 Oct '05

17 Oct '05

Current FC-devel tree via kickstart stops at kickstart.py:655 due to missing _(). Maybe the following would fix it: --- kickstart.py +++ kickstart.py @@ -28,6 +28,7 @@ import urlgrabber.grabber as grabber import lvm from pykickstart.parser import * from pykickstart.data import * +from rhpl.translate import _ import logging log = logging.getLogger("anaconda") greetings, Florian La Roche

2 1

RHEL 4 package deps?
by Brian Long 14 Oct '05

14 Oct '05

Hello, My group is working on our RHEL 4-based kickstart profiles. There are 3 RPMs that Anaconda installs even if we put -package in ks.cfg. rpm -e is successful during %post, so I'd like to know how to narrow down why Anaconda thinks it needs those packages. They are xorg-x11-xfs, ttmkfdir, and chkfontpath. Is there a way to enable more verbosity such that Anaconda tells us why they are pulled in (on Alt-F3 or wherever)? /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

4 8

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

14 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

Package ordering problems in RHEL 3
by patrickd＠vmware.com 13 Oct '05

13 Oct '05

Hey guys, I noticed that there's a problem in packages.py/hdrlist.py with package ordering. There seemed to be an API change between RPM 4.2.1 and 4.2.3 which returns the ORDER tag h[1000003] as an empty list instead of a "None" value. At any rate, if you're trying to install on a system which doesn't have ordered packages, this bit of code in packages.py always fails: depcheck = DependencyChecker(id.grpset) if not id.grpset.hdrlist.preordered(): log ("WARNING: not all packages in hdlist had order tag") # have to call ts.check before ts.order() to set up the alIndex ts.check(depcheck.callback) ts.order() else: ts.check(depcheck.callback) which results in a system having the RPMs installed in alphabetical order. This is not good, as you can imagine. Anyway, the problem is sitting in the preordered() method call in hdrlist.py. def preordered(self): preordered = 1 for h in self.pkgs.values(): if h.isSelected() and h[1000003] == None: preordered = 0 return preordered should be: def preordered(self): preordered = 1 for h in self.pkgs.values(): if h.isSelected() and not h[1000003]: preordered = 0 return preordered simple change, but caused me a great deal of frustration. grr. If you want a diff, let me know. --Patrick.

2 1

Re: Anaconda, grub and XFS
by James Pearson 11 Oct '05

11 Oct '05

Eric Sandeen wrote: > Jeremy Katz wrote: > >> Yes, but it's a hack that was added at the explicit request of the XFS >> developers with a "this will fix the problems". And having to >> constantly change it because they don't want to have the same semantics >> as all of the other filesystems which are even pseudo-supported is a >> waste of time. > > > Jeremy, I do apologize for the previous workaround which ... didn't work. > > But I have to take issue with the "semantics" you mentioned. Nothing in > the linux kernel guarantees that the block device address space will be > coherent with the filesystem address space - so what grub is trying to > do here (write through the filesystem, read back via the block device > with fs still mounted) is fundamentally broken. > > ext2 seems less prone to problems, I'm not sure why. But there is no > guarantee or mechanism in the kernel to make what grub is doing > bulletproof. (last I looked there were lots of wishful "syncs" in the > grub code, along with comments that did not inspire confidence!) So, if as Eric says, the previous workaround doesn't work, can we have the remount workaround (that works) instead? Thanks James Pearson

1 0

Anaconda, grub and XFS
by James Pearson 11 Oct '05

11 Oct '05

There has been an on going issue with installing grub on an XFS partition - anaconda will hang at the installing boot loader stage as grub 'spins'. The attached patch for 'booty' works round this problem by remounting the XFS file system that contains /boot as read-only and then as read-write before running the grub install command. This patch replaces the current XFS freeze/thaw work round that fails to work (a lot) more often than not. James Pearson

2 3

Testing Anaconda Changes
by Brian Long 10 Oct '05

10 Oct '05

What is the recommended way to test Anaconda changes when developing a patch for submission? It appears I need to run a RawHide system because anaconda RPM build requires kudzu-devel >= 1.2.0, etc. Is there a better way for me to test my changes besides rebuilding the RPM? I'm currently touching C code in isys and loader2. Any ideas would be appreciated. /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

2 1

Re: Custom CD results in GRUB Error 13 at boot -- please file under ...
by Bryan J. Smith 10 Oct '05

10 Oct '05

what chronically stupid Linux admins can do! "Bryan J. Smith" <b.j.smith(a)ieee.org> wrote: > Or do I really need to go through the full "pkgorder" (for > 1 CD that is only 440MB total?) ... > Another thing, it does appear I am getting some "%post" and > "%pre" "scriptlet" errors in ./root/install.log from some > packages -- including a "%pre" error from "coreutils" (and > it says it's skipping the package). What does that result > from? The lack of running a full "buildinstall"? I've been so focused on package selection and other details that I completely ignored the obvious here. In my complete oblivious state, after deciding to tail the install.log on the next attempt, I realized that it was because all RPMs were installing alphabetically. Doh! Yes, stupid, pkgorder *IS* required! Yes, I should have realized that. Yes, I honestly didn't notice it until the tail was spitting it out before my eyes in real-time -- again, Doh! My apologies for using the list as a brainstorm. Oh well, the fact that it's Internet searchable will teach me to be a little more restrained before exposing my complete ineptitude to the world at times. Lack of sleep ... honest! ;-> -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers)

1 0

Custom CD results in GRUB Error 13 at boot ...
by Bryan J. Smith 10 Oct '05

10 Oct '05

Apologize if this has been covered before, but I've been wrestling with this for 3 days now. I basically have a test system that is a light install of ~1GB that I am trying to make into a single, bootable RHEL3 CD. I basically did a bare install, and then ran "rpm -e" until the system worked as desired. I then did a "rpm -qa" and built my ./RedHat/RPMS/ filelist from that. I have run the "genhdlist --withnumbers" and painstakenly modified my comps.xml to match the RPMs, as well as just tried to use the default comps.xml as well. Everything seems to go fine, no errors during the install in any case -- full or minimal. But at the first boot of the newly installed system, GRUB throws out an Error 13. Upon closer inspection of the system install, it appears not only has no kernel been installed in /boot, but the "coreutils" packages has not been installed. Everything else seems to be installed from an "rpm -qa" listing though. Are there additional RPMS that the ./RedHat/RPMS/ directory needs on the CD that would not be listed in a "rpm -qa" output? Or do I really need to go through the full "pkgorder" (for 1 CD that is only 440MB total?) or "buildinstall" (I haven't updated the packages at all -- just using stock RHEL3U6 RPMS and a stock RHEL3U6 system as the build)? I'm kinda just curious why the kernel and coreutils wouldn't get installed? It does say "installing bootloader" (or similar) at the end. Another thing, it does appear I am getting some "%post" and "%pre" "scriptlet" errors in ./root/install.log from some packages -- including a "%pre" error from "coreutils" (and it says it's skipping the package). What does that result from? The lack of running a full "buildinstall"? A Google search showed some people running into it with bad hardware or other things. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145324 Note, I'm installing from an image on the hard drive, although I've burned to a CD-R and get the sam errors. I'm building the ISO image and installing from it to save time -- using the stock RHEL3U6 CD#1 to boot and passing either "expert" or "askmethod". It can't be a hardware or disk space issue, as the original RHEL3U6 CDs or ISO images do install fine. It's clearly my repackaging that is at fault. Sorry if this is clearly the result of not running "buildinstall" and going through the full procedure. Just let me know that. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers)

1 0

comps.rpm
by Mario Borrego 08 Oct '05

08 Oct '05

Does is necesary make the comps.rpm step in fedora core 4? If the answer is yes, then where is the comps src? Thanks

1 0

Re: Fedora Logos
by abayomi onibudo 07 Oct '05

07 Oct '05

Manilal, thanks for the email, that works great. However, the Shadowman icon still remains on both the Gnome and KDE taskbar when i log onto Gnome or KDE respectively. Do you know the steps for replacing that as well? Also, i will like to completely refrain from using the names fedora in any of my rpms, do you know whats steps are necessary to completely replace the fedora-logos rpms and sources with something like mydistro-logos.rpm which will be used in place of fedora-logos. Thanks Abayomi On 10/6/05, Manilal K M <manilalkm(a)gmail.com> wrote: > > On 10/6/05, abayomi onibudo <aonibudo(a)gmail.com> wrote: > > Manilal, > > > > thanks for the email, that works great. However, the Shadowman icon > still > > remains on both the Gnome and KDE taskbar when i log onto Gnome or KDE > > respectively. Do you know the steps for replacing that as well? > > > > Also, i will like to completely refrain from using the names fedora in > any > > of my rpms, do you know whats steps are necessary to completely replace > the > > fedora-logos rpms and sources with something like mydistro-logos.rpmwhich > > will be used in place of fedora-logos. > For this you have to change the theme. The is configured in the > libgnome package. > Edit the patchfile : > /usr/src/redhat/SOURCES/libgnome-2.7.2-default-icontheme.patch > change the theme Simple again to gnome. recompile the rpm and check it. > This will change the whole icons in the desktop. Otherwise you have to > edit the main-menu icon in redhat-artwork package. > regards > Manilal >

1 0

HTTP 1.1 required?
by Brian Long 07 Oct '05

07 Oct '05

Hello, I have a bunch of Network Appliance filers globally that serve up our kickstart images over NFS. In certain cases, I'd like to enable httpd on these filers and kickstart over HTTP. The httpd on filers only does HTTP 1.0. Would Loader or Anaconda see this as a problem? I already know Yum wouldn't work because it requires HTTP 1.1 byte- ranges. :( Thanks. /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

2 1

[PATCH] fix for broken "nevra already in HeaderList" test
by Matt Wilson 07 Oct '05

07 Oct '05

Patch attached. -- Matt Wilson rpath, Inc. msw(a)rpath.com

1 0

Re: new kickstart work
by Chris Lumens 07 Oct '05

07 Oct '05

Argh, I sent this reply to the wrong one of the billion lists I'm subscribed to. I blame the morning. >> from pykickstart.parser import * >> from pykickstart.data import * >> >> ksdata = KickstartData() >> kshandlers = KickstartHandlers(ksdata) >> ksparser = KickstartParser(ksdata, kshandlers) >> ksparser.readKickstart("ks.cfg") > > Do we care about ksdata and kshandlers after the fact? If you care about the data in the kickstart file, then you do care about ksdata. It will be populated as an effect of the call to readKickstart. I can't think of a good reason off-hand why you would care about kshandlers, though. - Chris

1 0

new kickstart work
by Chris Lumens 06 Oct '05

06 Oct '05

As anyone who's been following Rawhide knows, kickstart has been undergoing a whole lot of work recently. This work has been a complete rewrite of the kickstart file parser and data representation in anaconda due to a couple realizations: (1) anaconda and s-c-kickstart use completely different code bases. The biggest problem here is that s-c-kickstart is falling farther and farther out of sync with anaconda as to what is supported and what's not. (2) There are some long-standing bugs in kickstart that cannot be fixed because the current code is sort of tough to work with. One example of this is post scripts in include files all get executed in the chroot environment, regardless of what you want. (3) We don't have any validation tools right now besides writing a kickstart file and cramming it through anaconda to see if it works or not. (4) Even within anaconda, there are multiple kickstart file parsers. (5) s-c-kickstart doesn't understand all the options that kickstart supports so if you take an existing file and run it through the program, what you get out will have lots of data stripped (if it even reads in the file at all). Okay, enough rationale. My main idea was to create a single new codebase that handles all the reading and writing of kickstart files and to make that code generic enough to where it's not a pain to adapt it to your uses. Therefore, I present the new pykickstart package in Rawhide. It's been in the works within anaconda for a couple weeks now but I have finally broken it out into its own package so you can use it for your own purposes. As always, the documentation is a bit light at the moment but that will be coming soon. The code is pretty well commented so it should be reasonably easy to follow, but here's an outline of the core: - KickstartData is a class containing a variety of attributes that represents the kickstart file. Wherever possible, things are represented in some real type instead of just a string. There are a variety of other Kickstart*Data classes found in data.py. These are meant to be put in the lists in KickstartData. - KickstartParser is the central class. It is essentially a state machine that transitions on seeing the various sections of the kickstart file. Functions are run upon state transitions, and these functions may be overridden in a subclass of KickstartParser if you need specialized behavior. The core function of readKickstart should be generic enough to never need overriding, unless you are doing something really crazy. If it's not flexible enough, this is probably a bug on my part. - KickstartHandlers deal with all the commands found in the command section of your kickstart file. Each command has its own handling function that deals with the legal options for the command and sets values in KickstartData appropriately. Again, you may subclass KickstartHandlers to do whatever you would like. If you want to make your own subclass handlers, it is a good idea to call the superclass handler first to set KickstartData. Then, do whatever you would like. - We are using all sorts of features from OptionParser, which I am not going to go into here. However, one of the nice features is the ability to mark options as deprecated. - KickstartWriter takes a KickstartData object and spits out a file. It similarly has handlers for each command, though I haven't done nearly as much with it as I have with the front end. So real quick: how would you go about using all this stuff? I'm glad you asked. from pykickstart.parser import * from pykickstart.data import * ksdata = KickstartData() kshandlers = KickstartHandlers(ksdata) ksparser = KickstartParser(ksdata, kshandlers) ksparser.readKickstart("ks.cfg") There you have it. You've now got ksdata populated and ready for use. Oh, you might also want to handle the various exceptions that can be thrown. How would you go about extending pykickstart for your own purposes? I'm going to save that for another long email. Or, you can look at kickstart.py in anaconda and see what's going on. It's really not too difficult. I think this is going to result in being able to make a lot of new stuff around kickstart pretty easily. My first goal is getting s-c-kickstart fixed up to use pykickstart (ugh, this is lots of work). My second goal is making a ksvalidator. That should be really simple. Oh, and a warning. This is all still in a lot of flux and before FC5, I might totally rewrite parts of the API. Nothing is stable yet and shouldn't be taken as such. Feel free to experiment with it, but understand I might get a crazy idea and redo something. So, thoughts? - Chris

2 1

Fedora Logos
by abayomi onibudo 06 Oct '05

06 Oct '05

I am creating a new distribution and i have successfully rebuilt Fedora 3 distro as my own distro using a different product name with buildinstall. I also managed to rebuild fedora-logos-1.1.29-1.noarch.rpm with new logos corresponding to my own distro. I have included the new fedora-logos-1.1.29-1.noarch.rpm in my RPMS folder for my distro before creating the iso. When i boot my system to attempt to install my distro the anaconda images reflect those of my distro, however, after installation the fedora-logos still appear as Fedora core 3. Can anyone please let me know what steps to take to get my distro to include my newly designed logos rather than Fedora core 3 logos? Thanks Abayomi

2 3

Rawhide install fills /var
by Orion Poplawski 05 Oct '05

05 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Testing nfs kickstart installs of rawhide. I create a 512MB /var partition. This partition filled up during the install with /var/cache/yum/anaconda/packages being the main culprit. I'm kind of surprised since I didn't think yum copied the packages to the cache dir when installing from a file: url. Perhaps a chroot issue? - - Orion PS - Any idea when will support for multiple repos be available? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDQvY8ORnzrtFC2/sRAt7iAKCKix17OvrkYEGlbtRmiZ8s/iqOPwCgp+Ii R0pXantiBhD92nIH5ZRXUPQ= =FuYr -----END PGP SIGNATURE-----

2 1

Re: Storage driver detection and sata_nv
by Bill Nottingham 04 Oct '05

04 Oct '05

Paul (bdi-emc(a)ntlworld.com) said: > On Tuesday 04 October 2005 02:47, Bill Nottingham wrote: > > > And from the wording of your response, I take it that this mechanism > > > USED to not work well with Anaconda, but Anaconda was later modified to > > > accommodate this mechanism? > > > > The probing library anaconda used, yes. > > That would be kudzu would it ? > > If so, would the support be functioning in kudzu1.1.111 ? You want 1.1.117-1 or later. Bill

1 0

RE: Storage driver detection and sata_nv
by Andrew Chew 04 Oct '05

04 Oct '05

> Andrew Chew (AChew(a)nvidia.com) said: > > Does this mechanism cause anaconda to not detect the device > to load the > > appropriate driver? > > Depends on the release. It *should* work in FC4 or later. I apologize. I'm not up to speed on the exact RedHat release chronology. Where is FC4 in relation to RHEL4 WS? And from the wording of your response, I take it that this mechanism USED to not work well with Anaconda, but Anaconda was later modified to accommodate this mechanism?

2 1

Storage driver detection and sata_nv
by Andrew Chew 04 Oct '05

04 Oct '05

I was wondering how anaconda's storage driver detection works, in particular as it pertains to the sata_nv driver's generic pci_device entries. The sata_nv driver has entries in its pci_device table that wildcards the device id, and filtering specifically for vendor id and class code (0x0101 and 0x0104). This is done in order to accommodate new controllers on old kernels/distros that don't have explicit support for the new controllers and provide enough support so that the OS can at least be installed, after which one can perhaps apply a sata_nv driver patch if so desired. Does this mechanism cause anaconda to not detect the device to load the appropriate driver? Thanks in advance

2 1

Kadischi/chroot patches
by Ignacio Vazquez-Abrams 03 Oct '05

03 Oct '05

Is there any chance of getting the Kadischi patches into Anaconda, either as-is or slightly modified? It looks as though they might be the start of an effort to have a chroot install via Anaconda. -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

3 2

Change set-up language ???
by RiB 03 Oct '05

03 Oct '05

Hi all, Could anyone tell me how to change a language using during Red Hat installation process (English by default) to another character set (Vietnamese for example). I've heard that they can do this through the modification in the Anaconda Project, is it possible ? If so, what are the files I need to modify ? Thanks for all the replies. I'm glad to meet all of you. --------------------------------- Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.

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