May 2006 - Anaconda-devel - Fedora mailing-lists

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

Digging into bug 191381
by Philip Prindeville 13 May '06

13 May '06

Well, I looked at this a bit and came up with the following path (attached). It's straightforward enough. I was wondering about a few things that I saw along the way. First, unmountCD() seems to be particular to the CD installation method, but it's present in all of the methods... it seems to me that it really should be an internally used (private) helper function leveraged by other less-media-specific methods. Which is partly the case: filesDone() is more generic, and indeed duplicates some of the functionality of unmountCD(). So how about we make filesDone() call unmountCD() in the CD method, and remove all other references to unmountCD() in the other classes and in the base class? I'm seeing a couple of other issues... I'll post more about then in another message, but basically I'm using: # X Window System configuration information xconfig --driver "radeon" --videoram 32768 --resolution 1400x1050 --depth 24 --startxonboot --defaultdesktop gnome # System monitor monitor --noprobe --monitor "LCD Panel 1400x1050" in the ks.cfg, but the resulting anaconda-ks.cfg tells me: monitor --hsync ... xconfig --driver "radeon" --videoram 32768 --resolution "800x600" ... I'll try again in graphical mode, because certain things don't seem to have taken (like the keyboard type and system language, etc). -Philip

1 0

handleKernelModule patch
by andre.maidl＠freedows.com 13 May '06

13 May '06

Date: Tue, 9 May 2006 15:27:56 -0300 From: Andre Murbach Maidl <andre.maidl(a)freedows.com> To: anaconda-devel-list(a)redhat.com Subject: handleKernelModule patch Message-ID: <20060509182756.GA4292(a)han-solo.freesoftware> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi folks, We are trying to create a Fedora Core 5 customized distro. But, when we added a package called kernel-module-ntfs anaconda broke because it couldn't solve the dependencies. I looked for it and found that it was happening because the function handleKernelModule was missing. This function was in depsolve.py, in early versions, but this file was removed from the anaconda-11.1.0.4. At some point in yuminstall.py we have some functions taken from depsolve.py, but handleKernelModule wasn't there. I fix the problem adding the function in yuminstall.py with the other functions from depsolve.py. I hope I have helped. Best regards Andre --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="anaconda-11.1.0.4-kernel-module.patch" --- anaconda-11.1.0.4/yuminstall.py.orig 2006-04-27 16:50:34.000000000 -0300 +++ anaconda-11.1.0.4/yuminstall.py 2006-04-27 16:51:36.000000000 -0300 @@ -498,6 +498,37 @@ rpm.addMacro(key, val) #From yum depsolve.py + def handleKernelModule(self, txmbr): + """Figure out what special magic needs to be done to install/upgrade + this kernel module.""" + + def getKernelReqs(hdr): + kernels = ["kernel-%s" % a for a in rpmUtils.arch.arches.keys()] + reqs = [] + names = hdr[rpm.RPMTAG_REQUIRENAME] + flags = hdr[rpm.RPMTAG_REQUIREFLAGS] + ver = hdr[rpm.RPMTAG_REQUIREVERSION] + if names is not None: + reqs = zip(names, flags, ver) + return filter(lambda r: r[0] in kernels, reqs) + + kernelReqs = getKernelReqs(txmbr.po.returnLocalHeader()) + instPkgs = self.rpmdb.returnTupleByKeyword(name=txmbr.po.name) + for pkg in instPkgs: + hdr = self.rpmdb.returnHeaderByTuple(pkg)[0] + instKernelReqs = getKernelReqs(hdr) + + for r in kernelReqs: + if r in instKernelReqs: + # we know that an incoming kernel module requires the + # same kernel as an already installed module of the + # same name. "Upgrade" this module instead of install + po = packages.YumInstalledPackage(hdr) + self.tsInfo.addErase(po) + self.log(4, 'Removing kernel module %s upgraded to %s' % + (po, txmbr.po)) + break + def populateTs(self, test=0, keepold=1): """take transactionData class and populate transaction set""" --ZGiS0Q5IWpPtfppv--

3 2

Bugs filed...
by Philip Prindeville 11 May '06

11 May '06

Ok, filed a couple more bugs. One suggesting that if "network --device ..." has been specified, then this state should be applied in the %post state. That is, if the target state of the machine is that eth0 is up on boot with DHCP, then this should be the state that %post sees. (The rationale being that if the various partitions are up and mounted when %post runs, why shouldn't the network also be primed at that time???) Second one suggesting that the CDrom be left mounted until after %post has run. In fact, there's really no reason to unmount it before the shutdown/reboot happens (same rationale).

1 1

Dependency issues rebuilding anaconda...
by Philip Prindeville 11 May '06

11 May '06

I tried to build anaconda on an updated machine (I run yum nightly), but got saw that it depended on libsepol-devel (amongst other things). So I tried to fetch them but found out that libsepol-devel is not compatible with the current version of libsepol (1.12.6-1)! You have to back up to libsepol-1.12.4.1! [root@localhost SPECS]# yum install pump-devel elfutils-devel beecrypt-devel libXxf86misc-devel libsepol-devel libsepol Loading "installonlyn" plugin Setting up Install Process Setting up repositories core [1/3] updates [2/3] extras [3/3] Reading repository metadata in from local files Excluding Packages in global exclude list Finished Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package libsepol-devel.i386 0:1.12.4-1.fc5 set to be updated ---> Package beecrypt-devel.i386 0:4.1.2-9.2.1 set to be updated ---> Package pump-devel.i386 0:0.8.24-1.2.2 set to be updated ---> Package elfutils-devel.i386 0:0.119-1.2.1 set to be updated ---> Package libXxf86misc-devel.i386 0:1.0.0-2.2 set to be updated --> Running transaction check --> Processing Dependency: libsepol = 1.12.4 for package: libsepol-devel --> Finished Dependency Resolution Error: Missing Dependency: libsepol = 1.12.4 is needed by package libsepol-devel [root@localhost SPECS]# Does this need to be fixed? Is there an easy (and harmless) way to override that dependence? -Philip

1 1

Why does the Wiki have so many immutable Anaconda pages?
by Steven Augart 11 May '06

11 May '06

Why does the Anaconda part of the Fedora wiki (http://fedoraproject.org/wiki/AnacondaCustomization) have so many immutable pages? I wouldn't mind adding useful information that I've learned in the course of my work, but I don't see an appropriate way to do so. I also wouldn't mind correcting spelling errors and formatting errors. I apologize for my ignorant question here; I'm sure the answer to this is obvious to those of you who've been involved with Fedora for longer; most of my Linux work at the distribution level has been with Debian and SuSE. I'm willing to put up a more accessible Wiki for those of us working on these issues of Anaconda customization, but only if it wouldn't act as a schismatic force in the Fedora community, especially since I'm a newcomer to that community. Steven -- Steven Augart Mazu Networks Cambridge, Massachusetts, USA

2 2

Ideas for some changes...
by Philip Prindeville 11 May '06

11 May '06

Well, I figured out that one of my issues was that the --isUtc option to timezone had been replaced with --utc (which I've not yet found documented) and that it wasn't backward compatible (even though things like the "yes" argument to "zerombr" are non-fatal warnings). Hmmm. Anyway, was wondering about a few other things... For instance, on "network", can you specify this command multiple times, as in: network --bootproto=dhcp --device=eth0 --onboot=on network --bootproto=dhcp --device=ath0 --onboot=off for a laptop with both wired and wireless interfaces? And what about adding: network --bootproto=dhcp --device=eth0 --mtu=1400 Why? Well, when I worked at Cisco we had some users that worked over VPN where the overhead for IPSEC/GRE tunneling reduce the maximum UDP data size (for TFTP, etc) to 1400 bytes. A proper client should specify that it wanted the MaxMTU option from DHCP and then set the interface appropriately, but not all do (PIXE comes to mind). And then there are static IP addresses, of course... Being able to netboot a PC and image it without having to drive 200 miles to come into the nearest corporate office would have been cool. Another thing I was thinking about was being able to perform simple edits of the contents of /etc/sysconfig files. I've written the following script to give an example of this. It has drawbacks, like not supporting subdirectories, but that's easily fixed... The way I use it right now is: %post ... /inst-helper/sysconfig.pl -b.orig 'init/GRAPHICAL=no' 'network/+NETWORKING_IPv6=no' cat >> /etc/modprobe.conf <<__EOF__ # turn off IPv6 alias net-pf-10 off alias ipv6 off __EOF__ Does this seem like it (the functionality of the sysconfig.pl script) would be a useful extension to the parameter section of the Kickstart config file (i.e. make it a built-in command "sysconfig" just like "xconfig" or "timezone")? Thanks, -Philip

3 8

Whither = and whence?
by Philip Prindeville 11 May '06

11 May '06

BTW, am I the only person confused by the parameter syntax, i.e. that some arguments take an '=' and some don't? part / --fstype ext3 --size=1024 firewall --enabled --trust=eth0 --http --ssh network --device eth0 --bootproto dhcp bootloader --location=mbr When do you need '=' and when don't you? Or how about, we get rid of them altogether? -Philip

2 2

Question about Rehat Driver Update Media Format
by McArthor 10 May '06

10 May '06

Hi all, I made a RH driver update floppy image which contains aaa.ko. Installation insmod aaa.ko normally. But after installation, the OS still uses its embedded bbb.ko. So, I aims to add a script to the image, which can automatically configure the installed OS to use my own aaa.ko, just like Suse image's update.pre/update.post. Does RH driver update floppy image contain any script that can run in installation? And when does this script run? Is there any documentation IN DETAIL about the format of RH driver update floppy image? Many thanks! ============== Thx & Rgds McArthor Lee --哈韩Q版小香水 --http://freemail5.eyou.com/sys_sig.php?url=aHR0cDovL2V5b3VhZnAuYWxseWVzLmNvbS9tYWluL2FkZmNsaWNrP2RiPWV5b3VhZnAmYmlkPTk1LDgxLDMmY2lkPTczLDksMSZzaWQ9MTY4JmFkdmlkPTQmY2FtaWQ9NCZzaG93PWlnbm9yZSZ1cmw9aHR0cDovL2FkZmFybS5tZWRpYXBsZXguY29tL2FkL2NrLzQwODAtMjI5MDMtOTQ5OS0wP2FpZD1leW91O3RleHQ7MTAzJm1wcm89aHR0cDovL2hlYWx0aGJlYXV0eS5zZWFyY2guZWJheS5jb20uY24vUV9XMFFRY2F0cmVmWkM2UVFjYXRyZWZaQzZRUWZjY2xaMVFRZmNsWjRRUWZsb2NaMVFRZnJvbVpSMTBRUWZzb29aMVFRZnNvcFoxUVFnYTEwMjQ0WjEwNDI1UVFzYWNhdFo0NzU4OVFRc2FyZ25aUTJkMVFRc2FzY3NaMVFRc2FzbGNaMFFRc2F0aXRsZVpRMjhRNTFRUXNicmZ0b2daMVFRc29mb2N1c1picw== --http://sms.eyou.com --无忧二二族、足球大富翁...尽在亿邮短信

1 0

Why stage2.img and minstg2.img?
by Steven Augart 10 May '06

10 May '06

Why does Anaconda use both stage2.img and keep as a backup minstg2.img? I assume this was done for historical reasons or that it supports some situation that I haven't come across myself. I was wondering how much I need to worry about what goes into minstg2.img on my boot CD, or whether I might just throw it away and get another 26 MB. Thanks, --Steven -- Steven Augart Mazu Networks Cambridge, Massachusetts, USA

2 2

Re: FC 5 Costumization
by Mallasch, Paul 10 May '06

10 May '06

On Friday 05 May 2006 11:17, VnPenguin wrote: >> On 5/5/06, Fabricio Lopes de Souza <linux fabricio gmail com> wrote: >> > Hi all , >> > >> > Anyone can tell me the minimall packages to build a customized FC5 ?? >> >> Define your "minimal" ? Minimal without X ? Minimal with X ? Minimal >> with X and devel ? > > Going with the perhaps poor assumption that the OP meant without X, how would > you get a CD to build with anything less than all the RPMs mentioned > in /usr/lib/anaconda-runtime/upd-instroot? I have been trying to build a min. > CD using variations on Dan Carpenter's scripts. No joy unless I include > almost all the RPMs in /usr/lib/anaconda-runtime/upd-instroot. I'm experiencing the same results, I have a directory containing a minimal set of RPMs, including those RPMs needed to support all of Dan's great scripts & Anaconda (e.g. libX*, etc.) I don't want X and other things so I exclude those RPMs in the mkisofs with -x "libX*" along with some other RPMs I don't want in my distro. Dan's scripts work great and I've managed to debug any error messages and I get a ISO out the other side, BUT... when I go to install that ISO on a machine it fails with RPM dependency errors on some of those RPMs I excluded. I verified my minimal set of RPMs and resolved dependencies prior to creating my directory of RPMs for my ISO, but I'm stuck. It seems like I may have to generate a new comps.xml with my minimal list, but I'm not sure. Any other guidance Dan or others? ThX --Paul

1 0

installing anaconda
by amin saberian 09 May '06

09 May '06

Hello. I want build a new distro. I want customize anaconda installer for my distro, but i cant compail and install it. How can i compail an install anaconda tarbal on fedora core 4 or redhat enterprice 4. Regards. --------------------------------- Yahoo! Mail goes everywhere you do. Get it on your phone.

2 1

anaconda bug: loader2/cdinstall.c's use of probeDevices
by Steven Augart 09 May '06

09 May '06

Thanks to some debugging statements, I've tracked down the source of the /sbin/loader crash I was experiencing that was hurting Mazu's installation process. The bug is in loader2/cdinstall.c's use of Kudzu's probeDevices: devices = probeDevices(CLASS_CDROM, BUS_UNSPEC, 0); if (!devices) { logMessage(ERROR, "No CDROM devices found!"); return 1; } Unfortunately, Kudzu does not return a null pointer in this case. Here is the official documentation (out of /usr/include/kudzu/kudzu.h) for what is actually returned: /* Probe for devices of the specified class, on the specified bus, * with the specified class. Returns a NULL-terminated array of * device (or subclass) pointers */ struct device ** probeDevices (enum deviceClass probeClass, enum deviceBus probeBus, int probeFlags ); A NULL-terminated array of zero elements is not a NULL pointer. So, first of all, if someone can tell me how I can go about submitting a patch for the bug in cdinstall.c, I would appreciate knowing what to do. Second of all, it appears that Kudzu 1.2.24.3, (as distributed in the FC 5 RPM kudzu-devel-1.2.34.3-1), is not detecting the CD drive on the IBM BladeCenter I've been testing on. This is an IBM Machine Type 8677, model # 2XX. (8677-2XX), manufactured in April of 2003. I'll write directly to Bill Notting, the current Kudzu maintainer, and see if I can help make that probing work in Kudzu. Thanks to Dan Carpenter for his helpful reply when I wrote to this list initially about debugging /sbin/loader. Steven -- Steven Augart Mazu Networks Cambridge, Massachusetts, USA

3 6

Re: anaconda bug: loader2/cdinstall.c's use of probeDevices
by Bill Nottingham 09 May '06

09 May '06

Steven Augart (saugart(a)mazunetworks.com) said: > When you have a chance to look at the USB devices list dump I sent you, > please let me know if I can provide more helpful information. For > Mazu's internal purposes (of getting an installer to work on the blade > center), I can probably add some kludges that will detect the CD ROM and > will use mknod() to create the appropriate block device in /tmp so that > we can read the ks.cfg file off of the CD. However, I'd certainly > prefer to make the changes be more generally useful to other users of > libkudzu. I'm sorry if I wasn't clear... if you're getting to the second stage at *all*, with the installer CD in the USB cd-rom, then the detection is working - there's nothing to fix. Bill

1 0

Locating %post scripts, files...
by Philip Prindeville 09 May '06

09 May '06

On other quick question that I didn't find documented... Obvious the more stuff you put into isolinux.img the less RAM you have left over for other stuff, so this is best left with the fewest additional files... That said, is it "normal" and "proper" (etc) for a %post script to make references to stuff in /mnt/source/? For instance, let's say I have a mini-tar overlay of files I want to explode into the new root that's being built (since everything is prefixed in the tarchive by ./inst-helper/ anyway)... is: %post --nochroot (cd /mnt/sysimage ; gunzip -c | tar xf -) < /mnt/source/overlay-root.tgz %post chvt 3 # for debugging... set -x /inst-helper/mkprt --all ... is that a good practice? Or is there a better way to do this? And does the output of all of the %pre (well, that might be tricky) and %post scripts get captured/logged somewhere? Both on a vty and later into a saved log file? Thanks, -Philip

2 3

RE: Default for ks=cdrom
by Shawn Starr 09 May '06

09 May '06

Sure, you can put it into the initrd, if you do this you'll need to change the isolinux.cfg as ks=file:/ks.cfg (being / of initrd). You can also put it into CD-ROM image before you make the .iso. In this case you'd use ks=cdrom:/ks.cfg or some other location you like on the CD. Shawn. -----Original Message----- From: Philip Prindeville [mailto:philipp_subx@redfish-solutions.com] Sent: Tuesday, May 09, 2006 5:20 PM To: Shawn Starr Cc: anaconda-devel-list(a)redhat.com Subject: Re: Default for ks=cdrom So it needs to go in "/" in initrd.img? Is that what I'm understanding? -Philip Shawn Starr wrote: > The kickstart file is only found once the initrd is first loaded via isolinux, so this is after the isolinux stuff has over to the initrd, by passing the ks=cdrom option the loader will check the CD/DVD once its mounted inside Linux for ks.cfg in /. > > Files found in isolinux are not visible to Linux as they are a different CD layer. > > -----Original Message----- > From: Philip Prindeville [mailto:philipp_subx@redfish-solutions.com] > Sent: Tuesday, May 09, 2006 4:39 PM > To: Shawn Starr > Cc: anaconda-devel-list(a)redhat.com > Subject: Re: Default for ks=cdrom > > > Ok, I've only been working on writing Kickstart images for a couple of > days now, > so... what is / mapped to? The isolinux.img filesystem? Is that where > you're > saying the ks.cfg needs to be? > > Repacking the isolinux.img is (for me, anyway) a fair amount of work > that's best > avoided... I'd just as soon have the default location for the file be > /mnt/source/ks.cfg > or /mnt/source/isolinux/ks.cfg ... > > Am I alone in this? > > -Philip > > Shawn Starr wrote: > >> I thought it tries the toplevel '/' by default. >> >> -----Original Message----- >> From: anaconda-devel-list-bounces(a)redhat.com >> [mailto:anaconda-devel-list-bounces@redhat.com]On Behalf Of Philip >> Prindeville >> Sent: Tuesday, May 09, 2006 4:03 PM >> To: anaconda-devel-list(a)redhat.com >> Subject: Default for ks=cdrom >> >> >> Forgot to ask... When one specifies "ks=cdrom" with no path, >> where does Anaconda end up looking? In the CD's root, or in >> isolinux? Or what? >> >> Should this be more explicitly documented? >> >> -Philip >> >> _______________________________________________ >> Anaconda-devel-list mailing list >> Anaconda-devel-list(a)redhat.com >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list >> >> > >

1 0

RE: Default for ks=cdrom
by Shawn Starr 09 May '06

09 May '06

The kickstart file is only found once the initrd is first loaded via isolinux, so this is after the isolinux stuff has over to the initrd, by passing the ks=cdrom option the loader will check the CD/DVD once its mounted inside Linux for ks.cfg in /. Files found in isolinux are not visible to Linux as they are a different CD layer. -----Original Message----- From: Philip Prindeville [mailto:philipp_subx@redfish-solutions.com] Sent: Tuesday, May 09, 2006 4:39 PM To: Shawn Starr Cc: anaconda-devel-list(a)redhat.com Subject: Re: Default for ks=cdrom Ok, I've only been working on writing Kickstart images for a couple of days now, so... what is / mapped to? The isolinux.img filesystem? Is that where you're saying the ks.cfg needs to be? Repacking the isolinux.img is (for me, anyway) a fair amount of work that's best avoided... I'd just as soon have the default location for the file be /mnt/source/ks.cfg or /mnt/source/isolinux/ks.cfg ... Am I alone in this? -Philip Shawn Starr wrote: > I thought it tries the toplevel '/' by default. > > -----Original Message----- > From: anaconda-devel-list-bounces(a)redhat.com > [mailto:anaconda-devel-list-bounces@redhat.com]On Behalf Of Philip > Prindeville > Sent: Tuesday, May 09, 2006 4:03 PM > To: anaconda-devel-list(a)redhat.com > Subject: Default for ks=cdrom > > > Forgot to ask... When one specifies "ks=cdrom" with no path, > where does Anaconda end up looking? In the CD's root, or in > isolinux? Or what? > > Should this be more explicitly documented? > > -Philip > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/anaconda-devel-list >

2 1

RE: Default for ks=cdrom
by Shawn Starr 09 May '06

09 May '06

I thought it tries the toplevel '/' by default. -----Original Message----- From: anaconda-devel-list-bounces(a)redhat.com [mailto:anaconda-devel-list-bounces@redhat.com]On Behalf Of Philip Prindeville Sent: Tuesday, May 09, 2006 4:03 PM To: anaconda-devel-list(a)redhat.com Subject: Default for ks=cdrom Forgot to ask... When one specifies "ks=cdrom" with no path, where does Anaconda end up looking? In the CD's root, or in isolinux? Or what? Should this be more explicitly documented? -Philip _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list

2 1

Default for ks=cdrom
by Philip Prindeville 09 May '06

09 May '06

Forgot to ask... When one specifies "ks=cdrom" with no path, where does Anaconda end up looking? In the CD's root, or in isolinux? Or what? Should this be more explicitly documented? -Philip

1 0

Where is the error ? FC5 Customization
by Fabricio Lopes de Souza 09 May '06

09 May '06

I followed this steps : 1-copy all files from all cds to /fedora_dev/fc5/i386/ 2- # createrepo -g Fedora/base/comps.xml . 3- #pkgorder /fedora_dev/fc5/i386/ i386 /fedora_dev/fc5/i386/Fedora/RPMS/ | tee pkgfile 4- #/usr/lib/anaconda-runtime/buildinstall --comp 5 --pkgorder pkgfile --version 4 --product "Fedora Core" --release "Fedora Core 5" --prodpath Fedora --discs "Fedora Core 5" /fedora_dev/fc5/i386/ 5- # mkisofs -R -J -T -no-emul-boot -boot-load-size 4 -boot-info-table \ -V "Fedora Core 5" \ -A "Fedora Core 5" \ -b isolinux/isolinux.bin \ -c isolinux/boot.cat \ -o FC5-i386-disc1.iso \ i386 and booted in QEMU with : # qemu -boot d -cdrom fc/FC5-i386-disc1.iso hdc.img and the system boots and tell me to choose a intall method , then i choose LOCAL CD-ROM , but "No Fedora core cd Found" !!!!! what is wrong ???? thanks ... []'s

1 0

FC5 buildinstall changes
by Alan Milligan 06 May '06

06 May '06

Hi, I'm now porting our FC3/4 build environment to anaconda-11.0.5-1 - please do advise if I should be using fedora-development trunk instead. I have a very sophisticated Zope-based application to manage all of this, and thus am rather meticulous about reliably and repeatably being able to create custom installers. A fundamental tenet of the build process is working backwards from a bunch of objects that dynamically create a comps.xml and thus the requisites such would indicate. I have a range of anomalies that I'd like explained, or at least contemplated - please excuse me if I've missed something in the release notes ;) 1. Regardless of shipping these, it appears that all anaconda-runtime requires dependencies need to be slipped into the RPMS for the second buildinstall parse. I expect this is a general-enough rule to consider fundamental and I could derive these from whatever version's requires dependencies suggest? Any idea's for what one could/should do to figure/separate a curses install instead of the full-X that the requires dependencies suggests? 2. I get some buildinstall errors about /usr/share/X11/fonts/* needs to be present - I can fix this by including xorg-x11-fonts-* - what's the recommended minimal set of such? 3. The pango-querymodules step requires libXdmcp - this and I suspect a whole range of other dependencies is not in the requires tags. I also get GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0) - which is rather strange, indicating that root should not invoke it ... 4. I seem to have lost bogl and ash from FC5 - should I be worried?? 5. /usr/share/hwdata/videoaliases/* for trimpciids is missing - this seems to require xorg-x11-drv-* - what would be a/the recommended set of video drivers to include?? 6. buildinstall now invokes pkgorder which seems to completely ignore the possibility of defining groups within the comps.xml. There are a whole bunch of hard-coded addGroups() calls which obviously barfs when a large number of these are not present in my comps.xml - if I don't want X Windows, or mysql - surely I should be accomodated. What am I missing here?? 7. When unpacking my kernel (kernel-2.6.15-1.2054_FC5.root.i686.rpm), I have warnings that a worryingly large number of modules "not found in kernel rpm": 3c501 3c503 3c505 3c507 3c515 82596 AM53C974 abyss aic94xx airport arlan at1700 bcm5700 bmac cs89x0 ctc dpt_i2o eepro eepro100 eexpress es3210 eth16i ewrk3 fcal fmv18x hid hp hp-plus i82365 ibmtr ibmveth ibmvscsic ide-cd ipr iseries_veth lance lcs lne390 mace mambonet md mousedev myri_sbus ncr53c8xx ne ne3210 netiucv ni5010 ni65 pcmcia pluto qeth qla2x00 qla6322 qlogicisp qlogicpti siimage sk98lin sktr spidernet sunbmac sunlance sunqe sym53c8xx_2 tcic tcmscsim tmspci tulip_old veth viodasd wavelan xenblk xennet yenta_socket Some of these (ide-cd, mousedev, yenta_socket) seem quite critical to proceedings... 8. Unless I include fedora-logos (or it's equivalent), the anaconda-runtime/splashtolss.sh script cannot be found. Is this in the correct package?? 9. Lastly, I do a bit of an integrity check on files I expect to see present if there is to be any hope at all of booting the CD. I'm now not finding: /usr/src/redhat/BUILD/i386/isolinux/snake.msg /usr/src/redhat/BUILD/i386/BastionLinuxLite/base/hdlist /usr/src/redhat/BUILD/i386/BastionLinuxLite/base/hdlist2 /usr/src/redhat/BUILD/i386/BastionLinuxLite/base/hdstg2.img /usr/src/redhat/BUILD/i386/BastionLinuxLite/base/netstg2.img I do instead see base/minstg2.img - does this file deprecate these others? I'd like to hear opinions about all of this in the hopes of avoiding large production runs of anaconda-installer coffee mug coasters ;) Alan

2 1

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