Bug 81147 - ctc network not configured automatically
ctc network not configured automatically
Product: Red Hat Raw Hide
Classification: Retired
Component: anaconda (Show other bugs)
s390 Linux
medium Severity medium
: ---
: ---
Assigned To: Brock Organ
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-01-06 00:13 EST by Chris Ricker
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-06 15:23:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2003-01-06 00:13:46 EST
I'm messing with installations into hercules. For hercules, I have the following
contents in /etc/hercules/hercules.prm:

root=/dev/ram0 ro ip=off DASD=120
chandev=ctc0,0x600,0x601 CHANDEV=ctc0,0x600,0x601
DNS= SEARCHDNS=example.com:test.example.com

When I start a 7.2 install under hercules, all these parameters get read
automatically -- the ctc is properly configured, the host name is set, etc.

When I start a rawhide install under hercules, none of these parameters get set.
I have to configure a ctc network connection manually, etc.
Comment 1 Brock Organ 2003-01-06 14:54:45 EST
I have been able to install to hercules using the current 7.2 s390 (31-bit)
install trees:


Try using this instead of rawhide ... :)
Comment 2 Chris Ricker 2003-01-06 15:03:14 EST
Yeah, I can do that (and it works). It seems like rawhide is broken / regressed
though, since the installer in 7.2 reads the ctc settings automatically, but the
installer in rawhide doesn't unless I manually specify them

It might just be a quirk of hercules though -- I don't have access to real s/390
to see what happens there
Comment 3 Brock Organ 2003-01-06 15:23:09 EST
glad to hear it is working for you ... remember, rawhide == unsupported (and if
it breaks, you get to keep the pieces ... :) )

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