Bug 65456 - New install to run Xwindows
New install to run Xwindows
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-05-24 10:35 EDT by Chad Schonrock
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:48:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Comment (70.13 KB, text/plain)
2002-05-24 10:36 EDT, Chad Schonrock
no flags Details

  None (edit)
Description Chad Schonrock 2002-05-24 10:35:44 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
IBM Netfinity 5000 8659-4ry

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Additional info:
Comment 1 Chad Schonrock 2002-05-24 10:36:25 EDT
Created attachment 915052 [details]

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 2 Jeremy Katz 2002-05-24 13:39:27 EDT
Is this on an upgrade of an install that was done to a loopback mounted fs?
Comment 3 Chad Schonrock 2002-05-24 13:55:11 EDT
Comment 4 Jeremy Katz 2002-05-30 17:24:26 EDT
Is this reproducible?  If so, could you download the disk image at
http://people.redhat.com/~katzj/anaconda-loop.img and copy it to a floppy.  Then
boot the installer with 'linux updates'.  Once it crashes, you should be able to
go to tty2 and look at the contents of the file /tmp/fsspace and put them here
so that I have a better idea of what's going on?
Comment 5 Michael Fulbright 2002-07-15 12:55:56 EDT
Closing due to inactivty, please reopen if you have additional information to add.
Comment 6 Red Hat Bugzilla 2006-02-21 13:48:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.