Hi Gary,
Just returned to town today, so I am a bit late reading your message.
Thanks for the information, and as a result I had a closer look at the
information I reported about NFS AutoInstall.
I had copied the CD-ROMs to the NFS server the same as your steps. I looked
at the Automated Install diskette's contents and compared them to one I
created following your steps with the result that they were identical in all
the areas which mattered. Also, installing with the manually created disk or
with the Auto generated one produced the same results.
Your comments that the install worked OK for you made me repeat my earlier
testing and pay close attention to what tty3 was really reporting. It does
in fact install packages from CD 2's RPM2 directory, not as I had indicated
earlier.
What got me going with some false assumptions was that after the manual
install 'rpm -qa' reported 187 packages installed. And after the Automated
install, 'rpm -qa' reported only 174 packages installed. This result was
identical to the testing I had done for installing from CDs where the auto
install did not install packages from the second CD. As a result, a bad
assumption on my part.
Today I tried to determine why the difference in the number of installed
packages, 187 verses 174. To make a long story short, it appears that not
all the selected packages are placed in the 'default packages' list in the
auto_inst.cfg file.
The manual install's 187 packages matched the Individual Package Flat File
listing in the graphic installer, yellow check marks and Must have. The auto
install's 174 did not, the missing packages had a yellow check mark.
My auto_inst.cfg file's 'default_packages' section only lists 28 packages.
>From this I assume that the installer creates an install list which is
comprised of 1) Must have packages, 2) packages identified in the
'default_packages' list, 3) any dependancy packages that are need by 1 and 2
and, 4) packages required by other elements in the auto_inst.cfg file such as
'X'. Somehow, 13 packages have gone missing between the installs.
The only way that I can ensure that all 187 packages are installed when using
the Automated install is to replace the 'default_packages' list with the
output of: rpm -qa --queryformat "'"%{NAME}"',\n" and deleteing the trailing
comma from the last package listed.
Thanks again for catching my error.
regards
Dave
On Friday 27 April 2001 19:42, you wrote:
> Hi Dave,
>
> I noticed your mentioning that you could not install from a second
> cdrom over NFS. I thought I would tell you that the documentation
> is incorrect. It is working fine for me. This is what I did:
>
>
> #mkdir /install/mdk8.0
> #cd /install/mdk8.0
>
> Insert cdrom 1
>
> cp -rp /mnt/cdrom/* .
>
> Insert cdrom 2
>
> cp -rp /mnt/cdrom/* .
>
>
> As for creating an auto install floppy the problem is that the kernel
> is too big so the disk fills up.
>
>
> 1) Create an network boot floppy.
>
> 2) Install a machine via nfs the way I like it.
>
> 3) Edit the syslinux.cfg file on the floppy and delete the
> lines:
>
> display boot.msg
> F1 help.msg
> F2 boot.msg
>
>
> 4) Delete the files: help.msg and boot.msg.
>
> 5) Copy the file /root/auto_inst.cfg.pl to the floppy as
> the auto_inst.cfg.
>
> 6) Edit the syslinux.cfg file on the floppy and change every line
> that starts with:
>
> append .....
>
> append kickstart=floppy automatic=method:nfs,server:$SERVER
> ,directory:/install/mdk8.0/,network:dhcp, .......
>
> or if you want to do define a static IP address you can change it to
>
> append kickstart=floppy automatic=method:nfs,server:$SERVER
> ,directory:/install/mdk8.0/,network:static,ip:137.79.95.211,netmask:255.255
>.255.0,gateway:137.79.95.1,dns:137.78.160.9, .......
>
>
>
> Hope it helps.
>
>
> - Gary Brack
