Red Hat Bugzilla – Bug 37286
7.0 boot floppy incompatible with 2.2.19-7.0.1 kernel
Last modified: 2007-04-18 12:32:48 EDT
Not really anaconda but there is no catagory for "install floppy".
When you upgrade a kickstart server to the 2.2.19-7.0.1 kernel, kickstart
floppies no longer work. This is due to a compatibility between the v2/3
NFS in 2.2.19-7.0.1 and the "mount" command on the boot floppy.
It can be worked around by forcing the rpc.mountd on the server into v2
only mode however this is less than desirable if your kickstart servers is
a general purpose NFS server.
Are you saying the default nfs behavior of a system with the 2.2.19 kernel is
different than from how it would act with the kernel shipped in 7.0?
Michael do you know of anything different with NFS in this context?
That's exactly what I am saying. :-) The 2.2.19-7.0.1 kernel and
nfs-utils-0.3.1-7 default to v2 and v3 NFS. The 2.2.16-22 kernel (and related
nfs-utils) was v2 only. This difference is not normally a problem *except* for
the "mount" command shipped on the RH 7.0 boot/install diskette. It would seem
that it cannot handle the responses from the new rpc.mountd in the new
Do you see this problem with Red Hat Linux 7.1?
It would seem that the "lang" and "keyboard" parameters of the kickstart .cfg
file have changed as I get prompted for them on the 7.1 install floppy when I
didn't on the 7.0 install floppy.
However I think the answer you are looking for is yes, the 7.1 boot floppy can
mount from an NFS server running the 2.2.19-7.0.1 kernel and updated nfs-utils
without having to force the rpc.mountd on the server into v2 mode.
I am thinking that knowing this gives you an idea of what needs to be done to
the 7.0 boot floppy to make it work with NFS v3 no?
No, the parameters for land and keyboard did not change between 7.0 and 7.1. I
can't spend time tweaking the 7.0 boot disks at this point. Resolving as
'Current Release' since the 7.1 boot disks work ok.