Bug 29994 - instimage directory missing. kickstart / NFS-install fails
Summary: instimage directory missing. kickstart / NFS-install fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkkickstart
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-28 10:53 UTC by Juergen Weiss
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-02-28 12:05:36 UTC
Embargoed:

Attachments (Terms of Use)

Description Juergen Weiss 2001-02-28 10:53:23 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [de] (X11; U; Linux 2.2.17-14smp i686)


on fisher-i386-disc2.iso the /RedHat/instimage NFS installer tree is
missing, also it is indicated in the README file. So kickstart and
NFS-Installations fails.

Reproducible: Always
Steps to Reproduce:
1.copy Redhat dirs from disc 1 and disc 2 to target directory
2. try an nfs install with bootnet.img
3.
	

Actual Results:  Installation fails

Expected Results:  Installation should complete without errors

md5checksum are ok
Comment 1 Matt Wilson 2001-02-28 11:02:05 UTC 
the README file is out of date.  The installation should complete properly if
you just copy disc1 and disc2 into the same directory.
Comment 2 Juergen Weiss 2001-02-28 12:04:11 UTC 
I'm not quit sure that this is a proper solution. There are no *.py files neither in disc1 nor in disc2
I mount the iso-image with
                                              mount -o loop fisher-i386-discx.iso /mnt/RedHat-CDx      x=1,2
                                              cd /mnt/RedHat-CDx
                                              find . -name "*.py" -print
No files where found
Comment 3 Matt Wilson 2001-02-28 14:43:31 UTC 
you don't understand the new implementation.  The nfs installer uses the
loopback ext2 filesystem in RedHat/base/stage2.img.
Note You need to log in before you can comment on or make changes to this bug.