Bug 84458 - Extra text in bootnet screen asking which interface to use
Extra text in bootnet screen asking which interface to use
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
:
: 84465 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-17 13:46 EST by Glen A. Foster
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-05-25 10:56:39 EDT
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 Glen A. Foster 2003-02-17 13:46:18 EST
Description of problem: Beta-5 install of Phoebe/Gingin, using a floppy with 
boot.img and netdrv.img... On the screen entitled "Networking device" where it 
asks which interface I want to use for the network (NFS) install, below the 
line where newt prints the "Back" button and to the right of the dialog box 
that contains it all is the text string (in white letters):

"2147483630 reading"

... doesn't look quite right and is hard to ignore.

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

How reproducible: don't know

Steps to Reproduce:
1. boot up with boot floppy
2. select NFS install on system with >1 interface present
3. insert network-driver floppy
4. watch on the screen entitled "Networking Device"
Comment 1 Jeremy Katz 2003-02-17 15:30:38 EST
Did you also get something about "requested language is not available"?
Comment 2 Glen A. Foster 2003-02-17 15:36:29 EST
Not that I recall, although I was doing 2 things at once during this install.  
It's entirely possible that message cropped up somewhere and I missed it.
Comment 3 Jeremy Katz 2003-02-17 16:16:01 EST
That's the case where I've seen it, but in any case, the message is from the
gzlib code and is likely due to its signal handling being silly (see message on
tty4 about use of signal(SIG_CHLD, SIG_IGN) and then wait()) which has since
been fixed
Comment 4 Jeremy Katz 2003-02-20 17:06:28 EST
*** Bug 84465 has been marked as a duplicate of this bug. ***
Comment 5 Brent Fox 2003-05-25 10:56:39 EDT
I'm going through Bugzilla closing some bugs that have been marked as Modified
for some period of time.  I believe that most of these issues have been fixed,
so I'm resolving these bugs as Rawhide.  If the bug you are seeing still exists,
please reopen this report and mark it as Reopened.

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