Red Hat ENTERPRISE LINUX AS 2.1 - Installationsanleitung Seite 47

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 86
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 46
Appendix B.
Sample Parameter Files
The IBM S/390(R) and IBM eServer zSeries(R) architectures use a special parameter file to set up
networking before the installation program (anaconda) can be started. This section describes the
contents of the parameter file.
The parameter file has a limit of 32 total parameters. To accommodate limitations of the parame-
ter files, a new configuration file on a CMS DASD should be used to configure the initial network
setup and the DASD specification. The .parm file should contain the real kernel parameters, such
as root=/dev/ram0 ro ip=off ramdisk_size=40000, and single parameters which are
not assigned to variables, such as vnc. Two new parameters which point the installation program at
the new configuration file need to be added to the .parm file. They are CMSDASD and CMSCONF.
CMSDASD=<cmsdasd_address>
Where <cmsdasd_address> represents the list of the device ID of the CMS DASD device
which contains the configuration file. This is usually the CMS user’s ’A disk. This option is
applicable only for users who have a CMS formatted disk (z/VM) available.
For example: CMSDASD=191
CMSCONFFILE=<configuration_file>
Where <configuration_file> represents the name of the configuration file. This value
must be specified in lower case. It is specified in a Linux style file name format. The CMS file
REDHAT CONF is specified as redhat.conf. This option is applicable only for users who have
a CMS formatted disk (z/VM) available.
For example: CMSCONFFILE=redhat.conf
DASD=<dasd-list>
Where <dasd-list> represents the list of DASD devices to be used by Red Hat Enterprise
Linux.
Although automatic probing for DASDs is done if this parameter is omitted, it is highly recom-
mended to include the DASD= parameter, as the device numbers (and therefore the device names)
can vary when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in
an unusable system.
For example: DASD=0.0.0100,0.0201-0.0.0204
The following parameters are required to set up networking:
SUBCHANNELS=
Provides required device bus IDs for the various network interfaces.
qeth: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>,
<data_device_bus_id>"
lcs: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>"
ctc: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>"
Due to the length of the qeth command line, it has been broken
into two lines.
For example (a sample qeth SUBCHANNEL statement):
SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
Seitenansicht 46
1 2 ... 42 43 44 45 46 47 48 49 50 51 52 ... 85 86

Kommentare zu diesen Handbüchern

Keine Kommentare