Sample run of buildinstall:
(buildinstall --pkgorder /path/to/pkgorder.txt --comp
dist-7.3 --version 7.3 /path/to/mydistro/i386)
buildinstall successfully completes, creating the new
images. (hdstg1.img, netstg1.img, stage2.img). I have
also run genhdlist (genhdlist /path/to/mydistro/i386)
to recreate the hdlist files)
but, when i run anaconda (with test, text & kickstart
options), i get the following error lines --
(errors omitted, errors probably not related to the above steps)
Run genhdlist after buildinstall (if making DVD)/splitdistro (if making CDs)
genhdlist --withnumbers /mydistro/i386 (for DVD)
genhdlist --withnumbers /mydistro/i386-disc[123] (for CDs)
Error Scenario #1:
> Running this command:
> /usr/lib/anaconda-runtime/pkgorder /root/mydistro/i386 i386 | tee /root/mydistro/i386/pkgorder.txt
>
> I obtain this error message:
> Traceback (most recent call last):
> File "/usr/lib/anaconda-runtime/pkgorder", line 10, in ?
> import whiteout
> ImportError: No module named whiteout
>
> Somebody has an idea ?
Yes, make sure that you have installed the anaconda from the distribution that you are rebuilding. IIRC, I saw this when I was trying to rebuild RHEL3 beta2 when I wasn't on a RHEL3 beta2 machine.
Error Scenario #2:
I have run my customized buildinstall script and tried running it.
I get the message that my distro CD was not found in any of my CD-Rom
drives. I checked and re-checked but both .discinfo and .buildstamp (within
stage2.img) are present.
Any other ideas?
The message you're talking about comes from an invalid .discinfo file.
I recall you're working with RH9, so your .discinfo file (on *each* CD) must
follow the seven line format below:
The most important one is the "Product name". It must match everywhere, because
Anaconda uses this information to verify the CD. Generally, using the --release
option to buildinstall will do the trick. Even if you'll have only one CD, run
splitdistro also for sanity, make sure to use the same --release string. In
your case, you also fudged with the 'RedHat' directory, so you need to fix
BaseDir, RPMDir and PixmapDir. You need to do this on _ALL_ CDs, if you have
more than one CD.
Error Scenario #3:
1065471360.097770
mydistro.ca
i386
1,2,3
mydistro/base
mydistro/RPMS
mydistro/pixmaps
I am trying to follow your next hint and try to splitdistro it. I would like
to make one CD (and yes I'm making a RH9 based distro). I got the
splitdistro script to run but it splits the distro over 2 discs and then
stops with an error (see below):
Splitting tree...
Creating disc1...
Creating disc2...
648.0
91.8131446838
1.2
10.0
544.986855316
first to move to disc2 is ooo-dictionaries-1.0.3-0.ximian.6.5.noarch.rpm
Creating disc3...
first to move to disc3 is
Traceback (most recent call last):
File "/usr/lib/anaconda-runtime/splitdistro", line 244, in ?
print "first to move to disc3 is", disc3pkgs[0]
IndexError: list index out of range
My questions:
1. How can I keep splitdistro from separating my distro over more than one
discs and
2. What do I need to do to get splitdistro finishing properly without
errors?
---
I assume you're making only one CD. In that case, you don't need "1,2,3" in the
disc list. Just "1" will do. There seems to be one package "ooo-dictionaries"
spilling into disc2, I'd recommmend checking the archives to burn more than
650MB on your CD _iff_ you have a 700MB CD. This can help you pack everything
on one disc, and splitdistro should instead barf on disc2 instead of disc3.
And yes, splitdistro (in 9.0.4) somewhat unfortunately assumes that there is
content spanning more than one disc. It however, does the right thing for the
first CD so the errors you get are safe to ignore. Once it's done, goto the
i386-disc1 directory and verify that you have a good .discinfo. Then run
mkisofs and you should be good to go.
Making driver disks (rhdiskmod.html):
>I have built driver disks for previous versions of RedHat to support
>> installation with disk controllers or network adapters not supported
>> with the drivers on CD. I am attempting to do the same with Fedora, but
>> it seems that the behavior of the installer has been changed a bit.
>> Instead of searching for the driver under:
There are two things... you can either a) use old, version 0 driver
disks or b) move forward to version 1 (recommended). With Fedora Core
1, the kernel on the install CDs and for pxeboot is the i586 kernel so
that systems that require ACPI can boot with 'acpi=on' and get it while
the floppy still has the i386 BOOT kernel (for space reasons).
A version 1 driver disk looks very similar to a version 0 except that
instead of having rhdd-6.1 on the disk, you use rhdd instead. Then, in
your modules.cgz, the layout is something like
2.4.22-1.2115.nptlBOOT/
i386/
mymodule.o
2.4.22-1.2115.nptl/
i586/
mymodule.o
i686/
mymodule.o
Which then lets you use the same driver disk for multiple architectures
as well and the installer will figure out the right one to use as
needed.
My attempt at buildinstall:
mkdir /mydistro/i386
dump CD's 1, 2, and 3 into /mydistro/i386
cd /usr/lib/anaconda-runtime
./genhdlist --withnumbers /mydistro/i386/