Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 18018

Summary: Custom installation error
Product: [Retired] Red Hat Linux Reporter: Mark <markgeorge>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-01 13:12:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark 2000-10-01 13:12:00 UTC
When trying a custom install (it worked ok later with a full install), onto
a dual-boot (win98/Linux) system, after formatting the new filesystem, it
came up with the error message:

Traceback (innermost last):
   File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py",
line 20, in run
      rc = self.todo.doInstall ()
   File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1480, in
doInstall
      if self.method.systemMounted (self.fstab, self.instPath,
self.hdList.selected()):
   File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py", line 46, in
systemMounted
      self.loopbackFIle = mntPoint + fstab.filesystemSpace (mntPoint)[0][0]
+ \
   File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 258, in
filesystemSpace
      space.append ((mntPoint, isys.fsSpaceAvailable(topMount + '/' +
mntPoint)))
   File "/usr/lib/anaconda/isys.py", line 16, in fsSpaceAvailable
      return _isys.devSpacefree (fsSystem)
   SystemError: (2, 'No such file or directory')

I know this problem only happens to me when I manually specify the packages
I want to install, because it worked fine when I told it to install
everything.

Comment 1 Alan Cox 2000-10-01 22:02:11 UTC

*** This bug has been marked as a duplicate of 18032 ***