Bug 21602 - Installation fails on HP OmniBook 6000
Installation fails on HP OmniBook 6000
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
7.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-12-01 16:42 EST by Need Real Name
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-27 12:29:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-12-01 16:42:24 EST
I have tried to install LINUX 7.0 on my PC HP OmniBook 6000 (P II with 256 
RAM, but without success. 

The PC hangs up and the following information is received. Since the whole 
installation process hangs I have been forced to write the information 
manually.  
I have tried to use the released patch package "Update-disk-20001009.img", 
but the same thing happens. 

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 "/tmp/update/todo.py", line 1488, in doInstall
   self.fstab.makeFilesystems ()
  File "/tmp/update/fstab.py", line 645, in makeFilesystems
   (self.progressWindow, _("Loopback"),
  File "isys.py", line 78, in ddfile
    os.write(fd,buf)
OSError: [Errno 27] File too large
Comment 1 Michael Fulbright 2000-12-04 12:03:37 EST
Could you please give step by step of instructions on how to reproduce?
Comment 2 Need Real Name 2000-12-04 12:26:16 EST
I think that this TR should be cancelled. I made a misstake when i defined the 
allocated area for the Linux Native and the Swap area.
Today a did the whole installation again and it worked fine.
Sorry for this.


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