Professional Documents
Culture Documents
Red Hat Enterprise Linux 6 Installation Guide en US
Red Hat Enterprise Linux 6 Installation Guide en US
Installation Guide
Edited by
Rdiger Landmann
r.landmann@redhat.com
Jack Reed
Petr Boko
pbokoc@redhat.com
Legal No tice
Copyright 2015 Red Hat, Inc. and others.
This document is licensed by Red Hat under the Creative Commons AttributionShareAlike 3.0 Unported License. If you distribute this document, or a modified version
of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If
the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees
not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable
law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora,
the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United
States and other countries.
Linux is the registered trademark of Linus Torvalds in the United States and other
countries.
Java is a registered trademark of Oracle and/or its affiliates.
XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the
United States and/or other countries.
MySQL is a registered trademark of MySQL AB in the United States, the European
Union and other countries.
Node.js is an official trademark of Joyent. Red Hat Software Collections is not
formally related to or endorsed by the official Joyent Node.js open source or
commercial project.
The OpenStack Word Mark and OpenStack Logo are either registered
trademarks/service marks or trademarks/service marks of the OpenStack
Foundation, in the United States and other countries and are used with the
OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
This manual explains how to boot the Red Hat Enterprise Linux 6.6 installation
program (anaconda) and to install Red Hat Enterprise Linux 6.6 on 32-bit and 64-bit
x86 systems, 64-bit Power Systems servers, and IBM System z. It also covers
advanced installation methods such as kickstart installations, PXE installations, and
installations over VNC. Finally, it describes common post-installation tasks and
explains how to troubleshoot installation problems.
T able o f Co nt e nt s
T able o f Co ntents
. .hapt
C
. . . .e.r. 1.
. .O
. .bt
. .aining
. . . . . .Re
. .d. Hat
. . . .Ent
. . .e. r.pr
. .is
. .e. Linux
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
..........
. .hapt
C
. . . .e.r. 2.
. . Making
. . . . . . .Me
. . dia
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
..........
2.1. Making an Installation DVD
17
2.2. Making Minim al Boot Media
18
2.2.1. Minim al USB Boot Media for BIO S-based System s
18
2.2.2. Minim al USB Boot Media for UEFI-based System s
19
. .ar
P
. t. .I.. .x8
. .6.,.AMD6
. . . . .4.,.and
. . . .Int
. .e
. l. 6
. .4.
. . Ins
. . .t.allat
. . . .io
.n
. .and
. . . .Bo
. .o. t.ing
. . . . . . . . . . . . . . . . . . . . . .21
..........
. .hapt
C
. . . .e.r. 3.
. . Planning
. . . . . . . . f. o
. r. .Ins
. . t. allat
. . . . io
. .n. .o.n. t. he
. . .x8
. .6. Ar
..c
. hit
. . .e. c. t.ur
. .e. . . . . . . . . . . . . . . . . . .22
..........
3 .1. Upgrade or Install?
22
3 .2. Is Your Hardware C om patible?
22
3 .3. Hardware Requirem ents
23
3 .4. RAID and O ther Disk Devices
23
3 .4.1. Hardware RAID
3 .4.2. Software RAID
3 .4.3. FireWire and USB Disks
23
24
24
24
24
24
25
26
27
. .hapt
C
. . . .e.r. 4. .. Pr
. .e
. par
. . . ing
. . . .f .o.r.Ins
. . .t.allat
. . . .io. n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
..........
4 .1. P reparing for a Network Installation
28
4 .1.1. P reparing for FTP , HTTP , and HTTP S Installation
4 .1.2. P reparing for an NFS Installation
4 .2. P reparing for a Hard Drive Installation
29
29
31
. .hapt
C
. . . .e.r. 5.
. . Sys
. . . t. e. m
. . Spe
. . . .c.if.ic
. .at
. io
. . ns
. . .Lis
. . t. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
..........
. .hapt
C
. . . .e.r. 6. .. Updat
. . . . . .ing
. . .Dr
. .ive
. . .r.s.Dur
. . . ing
. . . .Ins
. . t. allat
. . . . io
. .n. o
. .n. Int
. . .e.l .and
. . . .AMD
. . . .Sys
. . .t.e.ms
. . . . . . . .36
..........
6 .1. Lim itations of Driver Updates During Installation
6 .2. P reparing for a Driver Update During Installation
6 .2.1. P reparing to Use a Driver Update Im age File
6 .2.1.1. P reparing to use an im age file on local storage
36
37
37
37
38
38
41
42
6 .3.1. Let the Installer Find a Driver Update Disk Autom atically
6 .3.2. Let the Installer P rom pt You for a Driver Update
6 .3.3. Use a Boot O ption to Specify a Driver Update Disk
6 .3.4. Select a P XE Target that Includes a Driver Update
6 .4. Specifying the Location of a Driver Update Im age File or a Driver Update Disk
42
42
43
44
44
. .hapt
C
. . . .e.r. 7.
. . Bo
..o
. .t ing
. . . .t.he
. . Ins
. . .t.alle
. . . r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.7. . . . . . . . .
7.1. Starting the Installation P rogram
7.1.1. Booting the Installation P rogram on x86, AMD64, and Intel 64 System s
7.1.2. The Boot Menu
7.1.3. Additional Boot O ptions
7.1.3.1. Kernel O ptions
47
47
49
50
51
51
52
52
. .hapt
C
. . . .e.r. 8. .. Co
. . .nf
. .igur
. . . ing
. . . .Language
. . . . . . . . .and
. . . Ins
. . . t.allat
. . . .io
. .n. So
. . .ur
. .c.e. . . . . . . . . . . . . . . . . . . . .54
..........
8 .1. The Text Mode Installation P rogram User Interface
54
.1.1. Using the Keyboard to Navigate
8
8 .2. Language Selection
8 .3. Installation Method
8 .3.1. Installing from a DVD
8 .3.2. Installing from a Hard Drive
56
56
57
58
58
60
63
64
65
. .hapt
C
. . . .e.r. 9. .. Ins
. . .t.alling
. . . . . Us
. . ing
. . . .Anac
. . . .o. nda
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.6. . . . . . . . .
9 .1. The Text Mode Installation P rogram User Interface
9 .2. The Graphical Installation P rogram User Interface
9 .2.1. Screenshots During Installation
9 .2.2. A Note About Virtual C onsoles
67
67
68
68
69
70
71
75
75
76
83
84
85
86
86
87
89
91
92
94
95
96
97
99
100
101
102
66
66
103
104
104
108
109
112
114
115
117
T able o f Co nt e nt s
9 .15.3. C reate Software RAID
117
119
122
122
125
127
128
130
133
134
135
138
140
140
140
141
. .hapt
C
. . . .e.r. 10
. . .. T
. .r o
. .uble
. . . .s.ho
. .o.t.ing
. . . Ins
. . .t.allat
. . . .io
.n
. .o. n
. .an
. . Int
. . .e.l.o. r. AMD
. . . . .Sys
. . .t.e.m
. . . . . . . . . . .14
. .3. . . . . . . . .
1 0.1. You Are Unable to Boot Red Hat Enterprise Linux
1 0.1.1. Are You Unable to Boot With Your RAID C ard?
143
143
144
144
145
145
145
1 0.3.1. The "No devices found to install Red Hat Enterprise Linux" Error Message
145
146
153
153
153
154
154
154
154
155
155
156
156
157
1 0.4.8. Apache HTTP Server or Sendm ail Stops Responding During Startup
157
. .ar
P
. t. .II.
. .IBM
. . . Po
. . .we
. . r. Sys
. . . .t e
. .ms
..
. . Ins
. . . t.allat
. . . .io
. .n. and
. . . .Bo
. .o
. t. ing
. . . . . . . . . . . . . . . . . . . . . . . . . .158
...........
. .hapt
C
. . . .e.r. 11.
. . . Planning
. . . . . . . . f. o
. r. .Ins
. . t. allat
. . . . io
. .n. .o.n. Po
. . .we
. .r. Sys
. . . t. e
. ms
. . . Se
. . .r ve
. . .r s
. . . . . . . . . . . . . . .159
...........
1 1.1. Upgrade or Install?
1 1.2. Hardware Requirem ents
159
159
159
160
160
161
161
161
161
162
. .hapt
C
. . . .e.r. 12.
. . . Pr
. . e. par
. . . ing
. . . .f o
. .r .Ins
. . .t allat
. . . . io
. .n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
. .3. . . . . . . . .
1 2.1. P reparing for a Network Installation
163
164
164
166
. .hapt
C
. . . .e.r. 13.
. . . Updat
. . . . . ing
. . . .Dr
. .ive
. . .r s
. .Dur
. . . ing
. . . Ins
. . . t.allat
. . . .io
. .n. o
.n
. .IBM
. . . .Po
. .we
. . r. .Sys
. . .t.e.ms
. . .Se
. .r.ve
. .r.s. . . . . . . . . . .
1 3.1. Lim itations of Driver Updates During Installation
169 16 9
1 3.2. P reparing for a Driver Update During Installation
170
170
170
171
171
174
175
175
175
176
177
1 3.4. Specifying the Location of a Driver Update Im age File or a Driver Update Disk
177
. .hapt
C
. . . .e.r. 14
. . .. Bo
. . .o.t.ing
. . .t.he
. . Ins
. . . t.alle
. . . r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
. .0. . . . . . . . .
1 4.1. The Boot Menu
181
1 4.2. Installing from a Different Source
182
183
. .hapt
C
. . . .e.r. 15.
. . . Co
. . nf
. . igur
. . . . ing
. . . Language
. . . . . . . . . .and
. . . Ins
. . .t.allat
. . . .io
. .n. So
. . ur
..c
.e
. . . . . . . . . . . . . . . . . . . .18
. .4. . . . . . . . .
1 5.1. The Text Mode Installation P rogram User Interface
184
186
186
187
188
188
188
189
192
193
194
. .hapt
C
. . . .e.r. 16
. . .. Ins
. . .t.alling
. . . . . Us
. . ing
. . . .Anac
. . . .o. nda
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
. .5. . . . . . . . .
1 6.1. The Text Mode Installation P rogram User Interface
195
195
196
197
197
197
198
199
200
203
204
205
211
T able o f Co nt e nt s
1 6.8.1.1.3. C onfigure FC oE P aram eters
1 6.9. Setting the Hostnam e
1 6.9.1. Editing Network C onnections
211
212
213
215
215
216
218
220
221
223
224
225
226
227
229
230
230
231
232
235
236
238
240
241
243
245
248
250
251
253
256
257
258
259
. .hapt
C
. . . .e.r. 17.
. . . T. r. o
. uble
....s
. ho
. . .o.t.ing
. . .Ins
. . .t.allat
. . . .io. n
. .o.n. .an
. . IBM
. . . .Po
. .we
. . r. .Sys
. . .t.e.ms
. . .s.e.r.ve
. .r. . . . .26
. .0. . . . . . . . .
1 7.1. You Are Unable to Boot Red Hat Enterprise Linux
260
260
261
261
261
1 7.3.1. The "No devices found to install Red Hat Enterprise Linux" Error Message
261
262
269
269
269
269
270
271
271
271
272
1 7.4.7. Apache HTTP Server or Sendm ail Stops Responding During Startup
272
. .ar
P
. t. .III.
. . IBM
. . . .Sys
. . . t.e. m
. .z. Ar
..c
. hit
. . .e. c. t.ur
. .e. .- .Ins
. . t. allat
. . . . io
. .n. .and
. . . Bo
. . .o.t.ing
. . . . . . . . . . . . . . . . . . .273
...........
. .ar
P
. t. .III.
. . IBM
. . . .Sys
. . . t.e. m
. .z. Ar
..c
. hit
. . .e. c. t.ur
. .e. .- .Ins
. . t. allat
. . . . io
. .n. .and
. . . Bo
. . .o.t.ing
. . . . . . . . . . . . . . . . . . .273
...........
. .hapt
C
. . . .e.r. 18
. . .. Planning
. . . . . . . . .f o
. .r .Ins
. . .t allat
. . . . io
. .n
. .o.n. Sys
. . . .t e
. .m. z
. . . . . . . . . . . . . . . . . . . . . . . . . . . .274
...........
1 8.1. P re-Installation
1 8.2. O verview of the System z Installation P rocedure
274
274
276
277
277
278
278
279
279
279
280
280
280
. .hapt
C
. . . .e.r. 19
. . .. Pr
. .e
. par
. . . ing
. . . .f .o.r.Ins
. . .t.allat
. . . .io. n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
. .1. . . . . . . . .
1 9.1. P reparing for a Network Installation
281
282
282
283
284
286
. .hapt
C
. . . .e.r. 20
. . .. Bo
. . .o.t.ing
. . .(IPL)
. . . . t. he
. . .Ins
. . .t.alle
. . .r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
. .7. . . . . . . . .
20.1. Installing Under z/VM
287
20.1.1. Using the z/VM Reader
288
20.1.2. Using a P repared DASD
20.1.3. Using a P repared FC P -attached SC SI Disk
289
289
290
290
291
291
291
292
292
. .hapt
C
. . . .e.r. 21.
. . . Ins
. . .t.allat
. . . .io
.n
. .Phas
. . . .e
. .1:
. .Co
. . nf
. . igur
. . . .ing
. . . a. .Ne
. .t.wo
. . r. k. .De
. .vic
. . .e. . . . . . . . . . . . . . .29
. .3. . . . . . . . .
21.1. A Note on Term inals
296
. .hapt
C
. . . .e.r. 22.
. . . Ins
. . .t.allat
. . . .io
.n
. .Phas
. . . .e
. .2:
. .Co
. . nf
. . igur
. . . .ing
. . . Language
. . . . . . . . . and
. . . .Ins
. . .t.allat
. . . .io. n
. .So
. . ur
. . c. e. . . . . . . . . . . .
22.1. Non-interactive Line-Mode Installation
298 29 8
22.2. The Text Mode Installation P rogram User Interface
298
300
300
301
302
302
303
303
304
305
306
. .hapt
C
. . . .e.r. 23.
. . . Ins
. . .t.allat
. . . .io
.n
. .Phas
. . . .e
. .3:
. .Ins
. . .t alling
. . . . . .Us
. .ing
. . . Anac
. . . . .o.nda
. . . . . . . . . . . . . . . . . . . . .30
. .7. . . . . . . . .
T able o f Co nt e nt s
. .hapt
C
. . . .e.r. 23.
. . . Ins
. . .t.allat
. . . .io
.n
. .Phas
. . . .e
. .3:
. .Ins
. . .t alling
. . . . . .Us
. .ing
. . . Anac
. . . . .o.nda
. . . . . . . . . . . . . . . . . . . . .30
. .7. . . . . . . . .
23.1. The Non-interactive Line-Mode Text Installation P rogram O utput
23.2. The Text Mode Installation P rogram User Interface
23.3. The Graphical Installation P rogram User Interface
307
307
307
307
308
309
310
313
314
315
3.6.1.2.2. FC P Devices
2
3.7. Setting the Hostnam e
2
23.7.1. Editing Network C onnections
321
322
323
324
325
325
327
329
330
332
333
334
335
336
337
339
340
340
343
344
346
348
349
351
354
357
357
358
360
363
364
365
365
366
366
366
. .hapt
C
. . . .e.r. 24
. . .. T
. .r o
. .uble
. . . .s.ho
. .o.t.ing
. . . Ins
. . .t.allat
. . . .io
.n
. .o. n
. .IBM
. . . Sys
. . . t. e
.m
. . z. . . . . . . . . . . . . . . . . . . .36
. .8. . . . . . . . .
24.1. You Are Unable to Boot Red Hat Enterprise Linux
368
4.1.1. Is Your System Displaying Signal 11 Errors?
2
24.2. Trouble During the Installation
24.2.1. The "No devices found to install Red Hat Enterprise Linux" Error Message
24.2.2. Saving Traceback Messages
368
368
368
369
369
376
376
376
377
377
377
. .hapt
C
. . . .e.r. 25.
. . . Co
. . nf
. . igur
. . . . ing
. . . an
. . .Ins
. . .t.alle
. . .d. Linux
. . . . . .o.n. Sys
. . . t. e
.m
. . z. .Ins
. . t. anc
...e
. . . . . . . . . . . . . . .378
...........
25.1. Adding DASDs
25.1.1. Dynam ically Setting DASDs O nline
25.1.2. P ersistently setting DASDs online
25.1.2.1. DASDs Which Are P art of the Root File System
25.1.3. DASDs Which Are Not P art of the Root File System
25.1.4. P reparing a New DASD with Low-level Form atting
25.1.5. Expanding Existing LVM Volum es to New Storage Devices
25.2. Adding FC P -Attached Logical Units (LUNs)
25.2.1. Dynam ically Activating an FC P LUN
25.2.2. P ersistently Activating FC P LUNs
25.2.2.1. FC P LUNs That Are P art of the Root File System
25.2.2.2. FC P LUNs That Are Not P art of the Root File System
25.3. Adding a Network Device
378
378
379
380
381
382
383
385
385
386
386
388
389
389
390
392
393
395
396
396
397
398
. .hapt
C
. . . .e.r. 26
. . .. Par
. . . ame
. . . .t.e.r. and
. . . .Co
. . nf
. . igur
. . . .at
. .io
.n
. .File
. . . s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.0.0. . . . . . . . .
26.1. Required P aram eters
400
26.2. The z/VM C onfiguration File
26.3. Installation Network P aram eters
401
401
405
406
406
407
408
. .hapt
C
. . . .e.r. 27.
. . . IBM
. . . .Sys
. . .t.e.m
. .z. Re
. . f. e
. r. e
. nc
. . .e.s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.0.9. . . . . . . . .
27.1. IBM System z P ublications
27.2. IBM Redbooks P ublications for System z
409
409
410
. .ar
P
. t. .IV.
. . Advanc
. . . . . . .e.d. .Ins
. . t. allat
. . . . io
. .n. O
. .pt
. .io
. .ns
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.12
..........
. .hapt
C
. . . .e.r. 28
. . .. Bo
. . .o.t.O
. pt
. . io
. . ns
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.13
..........
28.1. C onfiguring the Installation System at the Boot Menu
413
28.1.1. Specifying the Language
413
413
414
414
415
T able o f Co nt e nt s
28.1.5. Specifying the Network Settings
28.1.5.1. C onfiguring a Bonded Interface
28.2. Enabling Rem ote Access to the Installation System
28.2.1. Enabling Rem ote Access with VNC
28.2.2. C onnecting the Installation System to a VNC Listener
28.2.3. Enabling Rem ote Access with ssh
28.2.4. Enabling Rem ote Access with Telnet
415
416
416
417
417
418
418
418
418
419
421
421
422
422
423
423
. .hapt
C
. . . .e.r. 29
. . .. Ins
. . .t.alling
. . . . . Wit
. . . ho
. . .ut
. .Me
. . .dia
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.24
..........
29.1. Retrieving Boot Files
424
29.2. Editing the GRUB C onfiguration
29.3. Booting to Installation
424
425
. .hapt
C
. . . .e.r. 30
. . .. Se
. . .t t. ing
. . . .Up
. . an
. . .Ins
. . .t allat
. . . . io
. .n
. .Se
. .r.ve
. .r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.26
..........
3 0.1. Setting Up the Network Server
3 0.2. Network Boot C onfiguration
3 0.2.1. C onfiguring P XE Boot for BIO S
3 0.2.2. C onfiguring P XE Boot for EFI
3 0.2.3. C onfiguring for P ower System s Servers
3 0.3. Starting the tftp Server
3 0.4. Adding a C ustom Boot Message
3 0.5. P erform ing the Installation
426
426
426
428
430
431
432
432
. .hapt
C
. . . .e.r. 31.
. . . Ins
. . .t.alling
. . . . . T. hr
..o
. .ugh
. . . VNC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.33
..........
3 1.1. VNC Viewer
3 1.2. VNC Modes in Anaconda
433
433
434
434
435
435
436
436
436
. .hapt
C
. . . .e.r. 32.
. . . Kic
. . .ks
. .t.ar
. .t .Ins
. . .t allat
. . . . io
. . ns
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.37
..........
3 2.1. What are Kickstart Installations?
437
3 2.2. How Do You P erform a Kickstart Installation?
3 2.3. C reating the Kickstart File
437
437
438
472
473
475
475
477
478
478
478
478
478
479
479
481
482
482
. .hapt
C
. . . .e.r. 33.
. . . Kic
. . .ks
. .t.ar
. .t .Co
. . nf
. . igur
. . . .at
. .o.r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.9.1. . . . . . . . .
3 3.1. Basic C onfiguration
3 3.2. Installation Method
491
492
493
494
495
496
498
3 3.6. Authentication
3 3.7. Firewall C onfiguration
3 3.7.1. SELinux C onfiguration
499
500
500
501
501
502
503
505
505
505
. .ar
P
. t. .V.
. .Af
. .t.e.r. Ins
. . .t.allat
. . . .io
.n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
. .7. . . . . . . . .
. .hapt
C
. . . .e.r. 34
. . .. Fir
. . .s.t.bo
. .o.t. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
. .8. . . . . . . . .
3 4.1. License Inform ation
3 4.2. C onfiguring the Subscription Service
3 4.2.1. Set Up Software Updates
3 4.2.2. C hoose Service
3 4.2.3. Subscription Managem ent Registration
508
509
509
510
511
516
518
519
3 4.5. Kdum p
520
. .hapt
C
. . . .e.r. 35.
. . . Yo
. . ur
. . .Ne
. . xt
. . St
..e
. .ps
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .523
...........
3 5.1. Updating Your System
523
5.1.1. Driver Update rpm P ackages
3
3 5.2. Finishing an Upgrade
3 5.3. Switching to a Graphical Login
3 5.3.1. Enabling Access to Software Repositories from the C om m and Line
3 5.3.1.1. Enabling Access to Software Repositories Through the Internet
523
525
526
527
527
3 5.3.1.2. Using a Red Hat Enterprise Linux Installation DVD as a Software Repository
528
3 5.4. Installing P ackages With yum
529
. .hapt
C
. . . .e.r. 36
. . .. Bas
. . . ic
. . Sys
. . . .t e
. .m. Re
. . .c.o.ve
. .r.y. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .531
...........
3 6.1. Rescue Mode
531
3 6.1.1. C om m on P roblem s
531
3 6.1.1.1. Unable to Boot into Red Hat Enterprise Linux
10
531
T able o f Co nt e nt s
3 6.1.1.1. Unable to Boot into Red Hat Enterprise Linux
3 6.1.1.2. Hardware/Software P roblem s
531
531
531
531
534
534
534
535
535
536
536
537
. .hapt
C
. . . .e.r. 37.
. . . Upgr
. . . . ading
. . . . . .Yo
. . ur
. . .Cur
. . .r.e.nt
. . Sys
. . . t. e. m
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .539
...........
. .hapt
C
. . . .e.r. 38
. . .. Unr
...e
. .gis
. . t. e. r. ing
. . . f. r. o. m
. . Re
..d
. .Hat
. . . .Subs
. . . .c.r.ipt
. . io
. .n
. .Manage
. . . . . . .me
. . nt
. . .Se
. .r.vic
. .e
.s
...............
3 8.1. System s Registered with Red Hat Subscription Managem ent
540 54 0
3 8.2. System s Registered with RHN C lassic
3 8.3. System s Registered with Satellite
540
541
. .hapt
C
. . . .e.r. 39
. . .. Re
. . .mo
. . ving
. . . . Re
. . .d. Hat
. . . .Ent
. . .e.r.pr
. .is
.e
. .Linux
. . . . . Fr
. .o. m
. .x8
. .6. -bas
. . . .e. d
. .Sys
. . .t.e.ms
. . . . . . . .54
. .2. . . . . . . . .
3 9.1. Red Hat Enterprise Linux is the O nly O perating System on the C om puter
542
3 9.2. Your C om puter Dual-boots Red Hat Enterprise Linux and Another O perating System
543
3 9.2.1. Your C om puter Dual-boots Red Hat Enterprise Linux and a Microsoft Windows
O perating System
543
3 9.2.1.1. Windows 2000, Windows Server 2000, Windows XP , and Windows Server
2003
543
3 9.2.1.2. Windows Vista and Windows Server 2008
546
3 9.2.2. Your com puter dual-boots Red Hat Enterprise Linux and a different Linux
distribution
548
3 9.3. Replacing Red Hat Enterprise Linux with MS-DO S or Legacy Versions of Microsoft
Windows
552
. .hapt
C
. . . .e.r. 4. 0
. . Re
. . .mo
. . ving
. . . . .Re
. .d. Hat
. . . .Ent
. . .e. r.pr
. .is
. .e. Linux
. . . . . f. r.o. m
. .IBM
. . . .Sys
. . .t.e.m
. .z. . . . . . . . . . . .554
...........
4 0.1. Running a Different O perating System on your z/VM Guest or LP AR
554
. .ar
P
. t. .VI.
..T
. .e.c.hnic
. . . .al
. .Appe
. . . . ndic
. . . . e. s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555
...........
. .ppe
A
. . .ndix
. . . . A.
. . An
. . .Int
. . .r o
. .duc
. . .t.io
.n
. .t.o. Dis
. . .k
. .Par
. . .t.it.io
. .ns
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .556
...........
A.1. Hard Disk Basic C oncepts
556
A.1.1. It is Not What You Write, it is How You Write It
556
A.1.2. P artitions: Turning O ne Drive Into Many
558
560
561
561
562
562
563
564
564
565
566
567
567
567
11
. .ppe
A
. . .ndix
. . . . B.
. . iSCSI
. . . . . Dis
. . . ks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
. .9. . . . . . . . .
B.1. iSC SI Disks in anaconda
569
B.2. iSC SI Disks During Start Up
569
. .ppe
A
. . .ndix
. . . . C.
. . Dis
. . . k. .Enc
. . .r.ypt
. . .io. n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571
...........
C .1. What is Block Device Encryption?
C .2. Encrypting Block Devices Using dm -crypt/LUKS6tit
C .2.1. O verview of LUKS
C .2.2. How Will I Access the Encrypted Devices After Installation? (System Startup)
C .2.3. C hoosing a Good P assphrase
571
571
571
572
572
572
573
573
573
573
577
. .ppe
A
. . .ndix
. . . . D.
. . Unde
. . . . .r.s.t.anding
. . . . . . LVM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578
...........
. .ppe
A
. . .ndix
. . . . E.
. . T. he
. . . GRUB
. . . . . Bo
. . .o.t.Lo
. . ade
. . . r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .579
...........
E.1. Boot Loaders and System Architecture
579
E.2. GRUB
579
E.2.1. GRUB and the Boot P rocess on BIO S-based x86 System s
579
E.2.2. GRUB and the Boot P rocess on UEFI-based x86 System s
580
.2.3. Features of GRUB
E
E.3. Installing GRUB
E.4. Troubleshooting GRUB
E.5. GRUB Term inology
E.5.1. Device Nam es
581
581
582
583
583
584
584
585
586
586
588
588
588
590
590
12
591
591
T able o f Co nt e nt s
E.10.2. Useful Websites
591
. .ppe
A
. . .ndix
. . . . F.
. . Bo
..o
. .t .Pr
. .o.c.e. s. s. ,. Init
. . . ,. and
. . . .Shut
. . . . do
. . .wn
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
. .2. . . . . . . . .
F.1. The Boot P rocess
592
F.2. A Detailed Look at the Boot P rocess
592
F.2.1. The Firm ware Interface
592
F.2.1.1. BIO S-based x86 System s
F.2.1.2. UEFI-based x86 System s
F.2.2. The Boot Loader
F.2.2.1. The GRUB boot loader for x86 system s
F.2.2.2. Boot Loaders for O ther Architectures
593
593
593
593
594
594
595
598
598
599
F.4.1. Runlevels
F.4.2. Runlevel Utilities
.5. Shutting Down
F
599
600
600
. .ppe
A
. . .ndix
. . . . G.
. . Alt
. . .e. r.nat
. . .ive
. . .s. t.o. .bus
. . .ybo
. . . x. c
.o
. .mmands
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.0.2. . . . . . . . .
. .ppe
A
. . .ndix
. . . . H.
..O
. .t.he
. .r. T
. .e.c.hnic
. . . .al. .Do
. .c.ume
. . . .nt
. .at
. .io. n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.10
..........
. .ppe
A
. . .ndix
. . . . I.
. .Re
. .vis
. . .io. n
. .His
. . .t.o.r.y. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.12
..........
I.nde
...x
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.21
..........
13
14
15
$ curl -o rhel-server-6.6-x86_64-dvd.iso
'https://access.cdn.redhat.com//content/origin/files/sha
256/85/85a...46c/rhel-server-6.6-x86_64-dvd.iso?
_auth_=141...963' -C -
7. Optionally, you can us e a che cks um utility s uch as sha256sum to ve rify the
inte grity of the image file afte r the download finis he s . All downloads on the
Download Re d Hat Ente rpris e Linux page are provide d with the ir che cks ums for
re fe re nce :
$ sha256sum rhel-server-6.6-x86_64-dvd.iso
85a...46c rhel-server-6.6-x86_64-dvd.iso
Similar tools are available for Micros oft Windows and Mac OS X. You can als o us e
the ins tallation program to ve rify the me dia whe n s tarting the ins tallation; s e e
Se ction 28.6.1, Ve rifying Boot Me dia for de tails .
Afte r you download an ISO image file of the ins tallation DVD from the Re d Hat Cus tome r
Portal, you can:
burn it to a phys ical DVD (re fe r to Se ction 2.1, Making an Ins tallation DVD).
us e it to pre pare minimal boot me dia (re fe r to Se ction 2.2, Making Minimal Boot
Me dia).
place it on a s e rve r to pre pare for ins tallations ove r a ne twork (re fe r to Se ction 4.1,
Pre paring for a Ne twork Ins tallation for x86 archite cture s , Se ction 12.1, Pre paring for
a Ne twork Ins tallation for Powe r Sys te ms s e rve rs or Se ction 19.1, Pre paring for a
Ne twork Ins tallation for IBM Sys te m z ).
place it on a hard drive to pre pare for ins tallation to us e the hard drive as an
ins tallation s ource (re fe r to Se ction 4.2, Pre paring for a Hard Drive Ins tallation for x86
archite cture s , Se ction 12.2, Pre paring for a Hard Drive Ins tallation for Powe r Sys te ms
s e rve rs or Se ction 19.2, Pre paring for a Hard Drive Ins tallation for IBM Sys te m z ).
place it on a pre-boot execution environment (PXE) s e rve r to pre pare for ins tallations
us ing PXE boot (re fe r to Chapte r 30, Setting Up an Installation Server).
16
BIOS-bas e d 32-bit
x86
UEFI-bas e d 32-bit
x86
BIOS-bas e d AMD64
and Inte l 64
rhel-variant-vers
ion-i386-boot.iso
rhel-variant-vers
ionx86_64boot.iso
orrhel-variant-ve
rsion-i386boot.iso
rhel-variant-vers
ionx86_64boot.iso or
rhel-variant-vers
ion-i386-boot.iso
rhel-variant-vers
ion-x86_64boot.iso
rhelserver-versionppc64-boot.iso
Not available
efidisk.img (from
x86_64 DVD ISO
image file )
Not available
UEFI-bas e d AMD64
and Inte l 64
POWER (64-bit only)
Sys te m z
Bo o t CD o r bo o t
DVD
Bo o t USB f lash
drive
Not available
Where variant is t he variant o f Red Hat Ent erprise Linux (f o r example, server
o r workstation) and version is t he lat est versio n number (f o r example, 6.5).
17
Mos t wide ly us e d dis c burning s oftware for Linux, s uch as Brasero and K3b has the builtin ability to burn dis cs from ISO image file s .
The e xact s e rie s of s te ps that produce s a DVD from an ISO image file varie s gre atly from
compute r to compute r, de pe nding on the ope rating s ys te m and dis c burning s oftware
ins talle d. Cons ult your dis c burning s oftware 's docume ntation for de taile d information on
burning DVDs .
Impo rtant
In a fe w cas e s with oddly formatte d or partitione d USB me dia, image writing may fail.
18
19
Whe re DVD.iso is the name of the ISO image file , for e xample RHEL6.6-Serverx86_64-DVD.iso.
5. Trans fe r efidisk.img from the ISO image file to your USB flas h drive :
# dd if=/mnt/dvdiso/images/efidisk.img of=/dev/device_name
For e xample :
# dd if=/mnt/dvdiso/images/efidisk.img of=/dev/sdc
No te
Us e the dd command to write the image file dire ctly to the de vice . Us ing cp
to copy the file or trans fe rring the file us ing a file manage r will make the
de vice unbootable .
6. Unmount the ISO image file :
# umount /mnt/dvdiso
20
21
No te
This is the re comme nde d me thod for upgrading be twe e n major ve rs ions of
Re d Hat Ente rpris e Linux.
In-Place Upgrade
An in-place upgrade is a way of upgrading your s ys te m without re moving the
olde r ve rs ion firs t. The proce dure re quire s ins talling the migration utilitie s
available for your s ys te m and running the m as any othe r s oftware . In Re d Hat
Ente rpris e Linux, the Preupgrade Assist ant as s e s s e s your curre nt s ys te m and
ide ntifie s pote ntial proble ms you might e ncounte r during and/or afte r the
upgrade . It als o pe rforms minor fixe s and modifications to the s ys te m. The Red
Hat Upgrade T o o l utility downloads the package s and pe rforms the actual
upgrade . An in-place upgrade re quire s a lot of trouble s hooting and planning and
s hould only be done if the re is no othe r choice . For more information on the
Preupgrade Assist ant , s e e Chapte r 37, Upgrading Your Current System.
Warning
Ne ve r pe rform an in-place upgrade on a production s ys te m without firs t
te s ting it on a clone d backup copy of the s ys te m.
22
23
RAID, or Re dundant Array of Inde pe nde nt Dis ks , allows a group, or array, of drive s to act
as a s ingle de vice . Configure any RAID functions provide d by the mainboard of your
compute r, or attache d controlle r cards , be fore you be gin the ins tallation proce s s . Each
active RAID array appe ars as one drive within Re d Hat Ente rpris e Linux.
On s ys te ms with more than one hard drive you may configure Re d Hat Ente rpris e Linux to
ope rate s e ve ral of the drive s as a Linux RAID array without re quiring any additional
hardware .
Po st-installatio n Usage
You can conne ct and configure e xte rnal Fire Wire and USB hard dis ks afte r
ins tallation. Mos t s uch de vice s are automatically re cogniz e d and available for us e
once conne cte d.
24
als o calle d msdos) labe l, the dis k mus t be re labe le d. This me ans you can not re us e
e xis ting partitions on a MBR-partitione d dis k, and all data on the dis k will be los t. Make s ure
to back up all data on the drive be fore ins talling Re d Hat Ente rpris e Linux.
A GUID Partition Table is only re quire d on the s ys te m's boot drive - the dis k whe re the
boot loade r is ins talle d. Othe r drive s can be labe le d with a Mas te r Boot Re cord and the ir
partition layout can be re us e d.
The re are s e ve ral ways to ins tall Re d Hat Ente rpris e Linux on an UEFI s ys te m and us e a
drive which has a Mas te r Boot Re cord. You can:
Attach the drive to an e xis ting Linux s ys te m and us e an utility s uch as parted or fdisk
to cre ate a GPT labe l on the drive . For e xample , to cre ate a GPT labe l on dis k /dev/sdc
us ing parted, us e the following command:
# parted /dev/sdc mklabel gpt
Warning
Make s ure you s pe cify the corre ct drive . Re labe ling a dis k will de s troy all data on
it, and parted will not as k you for a confirmation.
Pe rform an automate d Kicks tart ins tallation, and us e the clearpart and zerombr
commands . If your s ys te m us e s UEFI firmware , us ing the s e commands on the boot
drive will re labe l it with a GPT.
During a manual ins tallation in the graphical us e r inte rface , whe n you ge t to the
partitioning s cre e n. Se le ct an option other than cus tom partitioning (for e xample Use
All Space). Make s ure to che ck the Review and modify partitioning layout che ck
box, and click Next.
On the following s cre e n, modify the automatically cre ate d layout s o it s uits your ne e ds .
Afte r you finis h and click Next, Anaco nda will us e your layout and re labe l the drive
automatically.
25
have one or more partitions that may be de le te d, the re by fre e ing up e nough dis k
s pace to ins tall Re d Hat Ente rpris e Linux.
To gain a be tte r s e ns e of how much s pace you re ally ne e d, re fe r to the re comme nde d
partitioning s iz e s dis cus s e d in Se ction 9.15.5, Re comme nde d Partitioning Sche me .
If you are not s ure that you me e t the s e conditions , or if you want to know how to cre ate
fre e dis k s pace for your Re d Hat Ente rpris e Linux ins tallation, re fe r to Appe ndix A, An
Introduction to Disk Partitions.
26
DVD Activity
If you boot from a Re d Hat Ente rpris e Linux ins tallation DVD, the ins tallation program
loads its ne xt s tage from that dis c. This happe ns re gardle s s of which ins tallation
me thod you choos e , unle s s you e je ct the dis c be fore you proce e d. The ins tallation
program s till downloads package data from the s ource you choos e .
[1] Unpartitioned disk space m eans that available disk space on the hard drives you are
installing to has not been divided into sections for data. When you partition a disk, each
partition behaves like a separate disk drive.
27
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
No te
The public dire ctory us e d to acce s s the ins tallation file s ove r FTP, NFS, HTTP, or
HTTPS is mappe d to local s torage on the ne twork s e rve r. For e xample , the local
dire ctory /var/www/inst/rhel6.6 on the ne twork s e rve r can be acce s s e d as
http://network.server.com/inst/rhel6.6.
In the following e xample s , the dire ctory on the ins tallation s taging s e rve r that will
contain the ins tallation file s will be s pe cifie d as /location/of/disk/space. The
dire ctory that will be made publicly available via FTP, NFS, HTTP, or HTTPS will be
s pe cifie d as /publicly_available_directory. For e xample , /location/of/disk/space
may be a dire ctory you cre ate calle d /var/isos. /publicly_available_directory
might be /var/www/html/rhel6.6, for an HTTP ins tall.
28
In the following, you will re quire an ISO image. An ISO image is a file containing an e xact
copy of the conte nt of a DVD. To cre ate an ISO image from a DVD us e the following
command:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the re s ulting
ISO image file , and path_to_image is the path to the location on your s ys te m whe re the
re s ulting ISO image will be s tore d.
To copy the file s from the ins tallation DVD to a Linux ins tance , which acts as an ins tallation
s taging s e rve r, continue with e ithe r Se ction 4.1.1, Pre paring for FTP, HTTP, and HTTPS
Ins tallation or Se ction 4.1.2, Pre paring for an NFS Ins tallation.
Warning
If your Apache we b s e rve r or t f t p FTP s e rve r configuration e nable s SSL s e curity,
make s ure to only e nable the TLSv1 protocol, and dis able SSLv2 and SSLv3. This is
due to the POODLE SSL vulne rability (CVE-2014-3566). Se e
https ://acce s s .re dhat.com/s olutions /1232413 for de tails about s e curing Apache, and
https ://acce s s .re dhat.com/s olutions /1234773 for information about s e curing t f t p.
Extract the file s from the ISO image of the ins tallation DVD and place the m in a dire ctory
that is s hare d ove r FTP, HTTP, or HTTPS.
Ne xt, make s ure that the dire ctory is s hare d via FTP, HTTP, or HTTPS, and ve rify clie nt
acce s s . Te s t to s e e whe the r the dire ctory is acce s s ible from the s e rve r its e lf, and the n
from anothe r machine on the s ame s ubne t to which you will be ins talling.
29
has h dis playe d for this particular image on the Downloads page in the Re d Hat
Cus tome r Portal (re fe r to Chapte r 1, Obtaining Red Hat Enterprise Linux). The two
has he s s hould be ide ntical.
3. Copy the images/ dire ctory from ins ide the ISO image to the s ame dire ctory in
which you s tore d the ISO image file its e lf. Ente r the following commands :
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/images /publicly_available_directory/
umount /mount_point
whe re path_to_image is the path to the ISO image file , name_of_image is the
name of the ISO image file , and mount_point is a mount point on which to mount
the image while you copy file s from the image . For e xample :
mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,ro
cp -pr /mnt/tmp/images /var/isos/
umount /mnt/tmp
The ISO image file and an images/ dire ctory are now pre s e nt, s ide -by-s ide , in the
s ame dire ctory.
4. Ve rify that the images/ dire ctory contains at le as t the install.img file , without
which ins tallation cannot proce e d. Optionally, the images/ dire ctory s hould contain
the product.img file , without which only the package s for a Minimal ins tallation will
be available during the package group s e le ction s tage (re fe r to Se ction 9.17,
Package Group Se le ction).
images/
directo ry
30
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
31
Chapte r 1, Obtaining Red Hat Enterprise Linux). Alte rnative ly, if you have the DVD on
phys ical me dia, you can cre ate an image of it with the following command on a
Linux s ys te m:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the
re s ulting ISO image file , and path_to_image is the path to the location on your
s ys te m whe re the re s ulting ISO image will be s tore d.
2. Trans fe r the ISO image to the hard drive .
The ISO image mus t be locate d on a hard drive that is e ithe r inte rnal to the
compute r on which you will ins tall Re d Hat Ente rpris e Linux, or on a hard drive that
is attache d to that compute r by USB.
3. Us e a SHA256 che cks um program to ve rify that the ISO image that you copie d is
intact. Many SHA256 che cks um programs are available for various ope rating
s ys te ms . On a Linux s ys te m, run:
$ sha256sum name_of_image.iso
whe re name_of_image is the name of the ISO image file . The SHA256 che cks um
program dis plays a s tring of 64 characte rs calle d a hash. Compare this has h to the
has h dis playe d for this particular image on the Downloads page in the Re d Hat
Cus tome r Portal (re fe r to Chapte r 1, Obtaining Red Hat Enterprise Linux). The two
has he s s hould be ide ntical.
4. Copy the images/ dire ctory from ins ide the ISO image to the s ame dire ctory in
which you s tore d the ISO image file its e lf. Ente r the following commands :
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/images /publicly_available_directory/
umount /mount_point
whe re path_to_image is the path to the ISO image file , name_of_image is the
name of the ISO image file , and mount_point is a mount point on which to mount
the image while you copy file s from the image . For e xample :
mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,ro
cp -pr /mnt/tmp/images /var/isos/
umount /mnt/tmp
The ISO image file and an images/ dire ctory are now pre s e nt, s ide -by-s ide , in the
s ame dire ctory.
5. Ve rify that the images/ dire ctory contains at le as t the install.img file , without
which ins tallation cannot proce e d. Optionally, the images/ dire ctory s hould contain
the product.img file , without which only the package s for a Minimal ins tallation will
be available during the package group s e le ction s tage (re fe r to Se ction 9.17,
Package Group Se le ction).
32
images/
directo ry
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
33
34
35
36
C hapt e r 6 . Updat ing Dr ive r s Dur ing Ins t allat io n o n Int e l and AMD Sys t e ms
pe rforming an initial RAM dis k drive r update re fe r to Se ction 6.2.3, Pre paring
an Initial RAM Dis k Update .
Devices wit h an equivalent device available
Be caus e all de vice s of the s ame type are initializ e d toge the r, you cannot update
drive rs for a de vice if the ins tallation program has loade d drive rs for a s imilar
de vice . For e xample , cons ide r a s ys te m that has two diffe re nt ne twork adapte rs ,
one of which has a drive r update available . The ins tallation program will initializ e
both adapte rs at the s ame time , and the re fore , you will not be able to us e this
drive r update . Again, comple te the ins tallation with the drive rs loade d by the
ins tallation program and update to the ne w drive rs afte r ins tallation, or us e an
initial RAM dis k drive r update .
37
Figure 6.1. Co nt ent o f a USB f lash drive ho lding a driver updat e image f ile
Note that if you us e this me thod, the s torage de vice will contain only a s ingle file . This
diffe rs from drive r dis cs on formats s uch as CD and DVD, which contain many file s . The
ISO image file contains all of the file s that would normally be on a drive r dis c.
Re fe r to Se ction 6.3.2, Le t the Ins talle r Prompt You for a Drive r Update and Se ction 6.3.3,
Us e a Boot Option to Spe cify a Drive r Update Dis k to le arn how to s e le ct the drive r
update manually during ins tallation.
For automatic ins tallations , you will ne e d to e xtract the ISO to the root dire ctory of the
s torage de vice rathe r than copy it. Copying the ISO is only e ffe ctive for manual
ins tallations . You mus t als o change the file s ys te m labe l of the de vice to OEMDRV.
The ins tallation program will the n automatically e xamine the e xtracte d ISO for drive r
update s and load any that it de te cts . This be havior is controlle d by the dlabel=on boot
option, which is e nable d by de fault. Re fe r to Se ction 6.3.1, Le t the Ins talle r Find a Drive r
Update Dis k Automatically.
38
C hapt e r 6 . Updat ing Dr ive r s Dur ing Ins t allat io n o n Int e l and AMD Sys t e ms
1. Us e the de s ktop file manage r to locate the ISO image file of the drive r dis c,
s upplie d to you by Re d Hat or your hardware ve ndor.
39
40
C hapt e r 6 . Updat ing Dr ive r s Dur ing Ins t allat io n o n Int e l and AMD Sys t e ms
If you s e e only a s ingle file e nding in .iso, the n you have not cre ate d the dis c corre ctly
and s hould try again. Ens ure that you choos e an option s imilar to burn from image if you
us e a Linux de s ktop othe r than GNOME or if you us e a diffe re nt ope rating s ys te m.
Re fe r to Se ction 6.3.2, Le t the Ins talle r Prompt You for a Drive r Update and Se ction 6.3.3,
Us e a Boot Option to Spe cify a Drive r Update Dis k to le arn how to us e the drive r update
dis c during ins tallation.
41
Re fe r to Se ction 6.3.4, Se le ct a PXE Targe t that Include s a Drive r Update to le arn how to
us e an initial RAM dis k update during ins tallation.
Example 6.1. Preparing an init ial RAM disk updat e f ro m a driver updat e image
f ile
In this e xample , driver_update.iso is a drive r update image file that you downloade d
from the Inte rne t to a dire ctory on your PXE s e rve r. The targe t that you want to PXE
boot from is locate d in /var/lib/tftpboot/pxelinux/rhel6/
At the command line , change to the dire ctory that holds the file and e nte r the following
commands :
$ cp driver_update.iso /tmp/initrd_update/dd.img
$ cd /tmp/initrd_update
$ find . | cpio --quiet -c -o -H newc | gzip -9
>/tmp/initrd_update.img
$ cp /tmp/initrd_update.img /var/lib/tftpboot/pxelinux/rhel6/dd.img
Edit the /var/lib/tftpboot/pxelinux/pxelinux.cfg/default file and include the
following e ntry:
label rhel6-dd
kernel rhel6/vmlinuz
append initrd=rhe6/initrd.img,rhel6/dd.img
6.3.1. Let t he Inst aller Find a Driver Updat e Disk Aut omat ically
Attach a block de vice with the file s ys te m labe l OEMDRV be fore s tarting the ins tallation
proce s s . The ins talle r will automatically e xamine the de vice and load any drive r update s
that it de te cts and will not prompt you during the proce s s . Re fe r to Se ction 6.2.1.1,
Pre paring to us e an image file on local s torage to pre pare a s torage de vice for the
ins talle r to find.
42
C hapt e r 6 . Updat ing Dr ive r s Dur ing Ins t allat io n o n Int e l and AMD Sys t e ms
43
If the ins talle r finds more than one location that could hold a drive r update , it
prompts you to s pe cify the location of the update . Se e Se ction 6.4, Spe cifying the
Location of a Drive r Update Image File or a Drive r Update Dis k.
44
C hapt e r 6 . Updat ing Dr ive r s Dur ing Ins t allat io n o n Int e l and AMD Sys t e ms
If the de vice that you choos e contains no s uitable update me dia, the ins talle r will prompt
you to make anothe r choice .
If you made a drive r update dis k on CD, DVD, or USB flas h drive , the ins talle r now loads
the drive r update . Howe ve r, if the de vice that you s e le cte d is a type of de vice that could
contain more than one partition (whe the r the de vice curre ntly has more than one partition
or not), the ins talle r might prompt you to s e le ct the partition that holds the drive r update .
45
46
To s tart, firs t make s ure that you have all ne ce s s ary re s ource s for the ins tallation. If you
have alre ady re ad through Chapte r 3, Planning for Installation on the x86 Architecture, and
followe d the ins tructions , you s hould be re ady to s tart the ins tallation proce s s . Whe n you
have ve rifie d that you are re ady to be gin, boot the ins tallation program us ing the Re d Hat
Ente rpris e Linux DVD or any boot me dia that you have cre ate d.
No te
Occas ionally, s ome hardware compone nts re quire a driver update during the
ins tallation. A drive r update adds s upport for hardware that is not othe rwis e
s upporte d by the ins tallation program. Re fe r to Chapte r 6, Updating Drivers During
Installation on Intel and AMD Systems for more information.
7.1.1. Boot ing t he Inst allat ion Program on x86, AMD64, and Int el 64
Syst ems
You can boot the ins tallation program us ing any one of the following me dia (de pe nding
upon what your s ys te m can s upport):
Red Hat Enterprise Linux DVD Your machine s upports a bootable DVD drive and you
have the Re d Hat Ente rpris e Linux ins tallation DVD.
Boot CD-ROM Your machine s upports a bootable CD-ROM drive and you want to
pe rform ne twork or hard drive ins tallation.
USB flash drive Your machine s upports booting from a USB de vice .
PXE boot via network Your machine s upports booting from the ne twork. This is an
advance d ins tallation path. Re fe r to Chapte r 30, Setting Up an Installation Server for
additional information on this me thod.
47
Impo rtant
Re d Hat Ente rpris e Linux 6.6 doe s not s upport UEFI for 32-bit x86 s ys te ms .
On 64-bit s ys te ms , boot configurations of UEFI and BIOS diffe r s ignificantly from e ach
othe r. The re fore , the ins talle d s ys te m mus t boot us ing the s ame firmware that was
us e d during ins tallation. You cannot ins tall the ope rating s ys te m on a s ys te m that
us e s BIOS and the n boot this ins tallation on a s ys te m that us e s UEFI.
To s tart the ins tallation program from a Re d Hat Ente rpris e Linux DVD or from minimal
boot me dia, follow this proce dure :
1. Dis conne ct any e xte rnal Fire Wire or USB dis ks that you do not ne e d for ins tallation.
Re fe r to Se ction 3.4.3, Fire Wire and USB Dis ks for more information.
2. Powe r on your compute r s ys te m.
3. Ins e rt the me dia in your compute r.
4. Powe r off your compute r with the boot me dia s till ins ide .
5. Powe r on your compute r s ys te m.
To cre ate a boot CD-ROM or to pre pare your USB flas h drive for booting or ins tallation,
re fe r to Se ction 2.2, Making Minimal Boot Me dia.
Ins e rt the boot me dia and re boot the s ys te m.
You might ne e d to pre s s a s pe cific ke y or combination of ke ys to boot from the me dia. On
mos t compute rs , a me s s age appe ars brie fly on the s cre e n ve ry s oon afte r you turn on
the compute r. Typically, it is worde d s ome thing like Press F10 to select boot device,
although the s pe cific wording and the ke y that you mus t pre s s varie s wide ly from
compute r to compute r. Cons ult the docume ntation for your compute r or mothe rboard, or
s e e k s upport from the hardware manufacture r or ve ndor.
If your compute r doe s not allow you to s e le ct a boot de vice as it s tarts up, you might ne e d
to configure your s ys te m's Basic Input/Output System (BIOS) to boot from the me dia.
To change your BIOS s e ttings on an x86, AMD64, or Inte l 64 s ys te m, watch the
ins tructions provide d on your dis play whe n your compute r firs t boots . A line of te xt
appe ars , te lling you which ke y to pre s s to e nte r the BIOS s e ttings .
Once you have e nte re d your BIOS s e tup program, find the s e ction whe re you can alte r
your boot s e que nce . The de fault is ofte n C, A or A, C (de pe nding on whe the r you boot
from your hard drive [C] or a dis ke tte drive [A]). Change this s e que nce s o that the DVD is
firs t in your boot orde r and that C or A (whiche ve r is your typical boot de fault) is s e cond.
This ins tructs the compute r to firs t look at the DVD drive for bootable me dia; if it doe s not
find bootable me dia on the DVD drive , it the n che cks your hard drive or dis ke tte drive .
Save your change s be fore e xiting the BIOS. For more information, re fe r to the
docume ntation that came with your s ys te m.
Afte r a s hort de lay, the graphical boot s cre e n appe ars , which contains information on a
varie ty of boot options . Ins tallation program automatically be gins if you take no action
within the firs t minute . For a de s cription of the options available on this s cre e n, re fe r to
Se ction 7.1.2, The Boot Me nu.
48
Alte rnative ly, pre s s the Esc ke y to acce s s the boot: prompt, at which you can e nte r
additional boot options as de s cribe d in Se ction 7.1.3, Additional Boot Options .
Impo rtant
Exce s s ive input (e .g. clicking the mous e re pe ate dly) during the boot s e que nce may
caus e the ins talle r to ignore ke yboard input late r in the ins tallation proce s s .
49
No te
Re fe r to Chapte r 28, Boot Options for additional boot options not cove re d in this
s e ction.
To pe rform a te xt mode ins tallation, at the ins tallation boot prompt, type :
linux text
To s pe cify an ins tallation s ource , us e the linux repo= option. For e xample :
50
linux repo=cdrom:device
linux repo=ftp://username:password@URL
linux repo=http://URL
linux repo=hd:device
linux repo=nfs:options:server:/path
linux repo=nfsiso:options:server:/path
In the s e e xample s , cdrom re fe rs to a CD or DVD drive , ftp re fe rs to a location
acce s s ible by FTP, http re fe rs to a location acce s s ible by HTTP, hd re fe rs to an ISO
image file acce s s ible on a hard drive partition, nfs re fe rs to an e xpande d tre e of
ins tallation file s acce s s ible by NFS, and nfsiso re fe rs to an ISO image file acce s s ible
by NFS.
ISO image s have an SHA256 che cks um e mbe dde d in the m. To te s t the che cks um
inte grity of an ISO image , at the ins tallation boot prompt, type :
linux mediacheck
The ins tallation program prompts you to ins e rt a DVD or s e le ct an ISO image to te s t,
and s e le ct OK to pe rform the che cks um ope ration. This che cks um ope ration can be
pe rforme d on any Re d Hat Ente rpris e Linux DVD. It is s trongly re comme nde d to
pe rform this ope ration on any Re d Hat Ente rpris e Linux DVD that was cre ate d from
downloade d ISO image s . This command works with the DVD, hard drive ISO, and NFS
ISO ins tallation me thods .
If you ne e d to pe rform the ins tallation in serial mode, type the following command:
linux console=<device>
For te xt mode ins tallations , us e :
linux text console=<device>
In the above command, <device> s hould be the de vice you are us ing (s uch as ttyS0 or
ttyS1). For e xample , linux text console=ttyS0.
Te xt mode ins tallations us ing a s e rial te rminal work be s t whe n the te rminal s upports
UTF-8. Unde r UNIX and Linux, Ke rmit s upports UTF-8. For Windows , Ke rmit '95 works we ll.
Non-UTF-8 capable te rminals works as long as only Englis h is us e d during the
ins tallation proce s s . An e nhance d s e rial dis play can be us e d by pas s ing the utf8
command as a boot-time option to the ins tallation program. For e xample :
linux console=ttyS0 utf8
51
Options can als o be pas s e d to the ke rne l. For e xample , to apply update s for the anaconda
ins tallation program from a USB s torage de vice e nte r:
linux updates
For te xt mode ins tallations , us e :
linux text updates
This command re s ults in a prompt for the path to the de vice that contains update s for
anaco nda. It is not ne e de d if you are pe rforming a ne twork ins tallation and have alre ady
place d the update s image conte nts in rhupdates/ on the s e rve r.
Afte r e nte ring any options , pre s s Enter to boot us ing thos e options .
If you ne e d to s pe cify boot options to ide ntify your hardware , ple as e write the m down. The
boot options are ne e de d during the boot loade r configuration portion of the ins tallation
(re fe r to Se ction 9.18, x86, AMD64, and Inte l 64 Boot Loade r Configuration for more
information).
For more information on ke rne l options re fe r to Chapte r 28, Boot Options.
Re fe r to Se ction 3.7, Se le cting an Ins tallation Me thod for information about ins talling from
locations othe r than the me dia with which you boote d the s ys te m.
52
1. Ens ure that the ne twork cable is attache d. The link indicator light on the ne twork
s ocke t s hould be lit, e ve n if the compute r is not s witche d on.
2. Switch on the compute r.
3. A me nu s cre e n appe ars . Pre s s the numbe r ke y that corre s ponds to the de s ire d
option.
If your PC doe s not boot from the ne tboot s e rve r, e ns ure that the BIOS is configure d to
boot firs t from the corre ct ne twork inte rface . Some BIOS s ys te ms s pe cify the ne twork
inte rface as a pos s ible boot de vice , but do not s upport the PXE s tandard. Re fe r to your
hardware docume ntation for more information.
53
8.1. T he T ext Mode Inst allat ion Program User Int erface
Impo rtant Graphical installatio n reco mmended
We re comme nd that you ins tall Re d Hat Ente rpris e Linux us ing the graphical
inte rface . If you are ins talling Re d Hat Ente rpris e Linux on a s ys te m that lacks a
graphical dis play, cons ide r pe rforming the ins tallation ove r a VNC conne ction s e e
Chapte r 31, Installing Through VNC. If anaco nda de te cts that you are ins talling in
te xt mode on a s ys te m whe re ins tallation ove r a VNC conne ction might be pos s ible ,
anaco nda as ks you to ve rify your de cis ion to ins tall in te xt mode e ve n though your
options during ins tallation are limite d.
If your s ys te m has a graphical dis play, but graphical ins tallation fails , try booting with
the xdriver=vesa option re fe r to Chapte r 28, Boot Options
Both the loade r and late r anaco nda us e a s cre e n-bas e d inte rface that include s mos t of
the on-s cre e n widgets commonly found on graphical us e r inte rface s . Figure 8.1,
Ins tallation Program Widge ts as s e e n in URL Setup, and Figure 8.2, Ins tallation Program
Widge ts as s e e n in Choose a Language, illus trate widge ts that appe ar on s cre e ns during
the ins tallation proce s s .
No te
Not e ve ry language s upporte d in graphical ins tallation mode is als o s upporte d in
te xt mode . Spe cifically, language s writte n with a characte r s e t othe r than the Latin
or Cyrillic alphabe ts are not available in te xt mode . If you choos e a language writte n
with a characte r s e t that is not s upporte d in te xt mode , the ins tallation program will
pre s e nt you with the Englis h ve rs ions of the s cre e ns .
54
Figure 8.1. Inst allat io n Pro gram Widget s as seen in URL Setup
Figure 8.2. Inst allat io n Pro gram Widget s as seen in Choose a Language
The widge ts include :
Window Windows (us ually re fe rre d to as dialogs in this manual) appe ar on your
s cre e n throughout the ins tallation proce s s . At time s , one window may ove rlay anothe r;
in the s e cas e s , you can only inte ract with the window on top. Whe n you are finis he d in
that window, it dis appe ars , allowing you to continue working in the window unde rne ath.
55
Che ckbox Che ckboxe s allow you to s e le ct or de s e le ct a fe ature . The box dis plays
e ithe r an as te ris k (s e le cte d) or a s pace (uns e le cte d). Whe n the curs or is within a
che ckbox, pre s s Space to s e le ct or de s e le ct a fe ature .
Te xt Input Te xt input line s are re gions whe re you can e nte r information re quire d by
the ins tallation program. Whe n the curs or re s ts on a te xt input line , you may e nte r
and/or e dit information on that line .
Te xt Widge t Te xt widge ts are re gions of the s cre e n for the dis play of te xt. At time s ,
te xt widge ts may als o contain othe r widge ts , s uch as che ckboxe s . If a te xt widge t
contains more information than can be dis playe d in the s pace re s e rve d for it, a s croll
bar appe ars ; if you pos ition the curs or within the te xt widge t, you can the n us e the Up
and Down arrow ke ys to s croll through all the information available . Your curre nt pos ition
is s hown on the s croll bar by a # characte r, which move s up and down the s croll bar as
you s croll.
Scroll Bar Scroll bars appe ar on the s ide or bottom of a window to control which part
of a lis t or docume nt is curre ntly in the window's frame . The s croll bar make s it e as y to
move to any part of a file .
Button Widge t Button widge ts are the primary me thod of inte racting with the
ins tallation program. You progre s s through the windows of the ins tallation program by
navigating the s e buttons , us ing the Tab and Enter ke ys . Buttons can be s e le cte d whe n
the y are highlighte d.
Curs or Although not a widge t, the curs or is us e d to s e le ct (and inte ract with) a
particular widge t. As the curs or is move d from widge t to widge t, it may caus e the
widge t to change color, or the curs or its e lf may only appe ar pos itione d in or ne xt to the
widge t. In Figure 8.1, Ins tallation Program Widge ts as s e e n in URL Setup, the curs or is
pos itione d on the Enable HTTP proxy che ckbox. Figure 8.2, Ins tallation Program
Widge ts as s e e n in Choose a Language, s hows the curs or on the OK button.
Warning
Unle s s a dialog box is waiting for your input, do not pre s s any ke ys during the
ins tallation proce s s (doing s o may re s ult in unpre dictable be havior).
57
No te
To abort the ins tallation proce s s at this time , re boot your machine and the n e je ct
the boot me dia. You can s afe ly cance l the ins tallation at any point be fore the Write
changes to disk s cre e n. Re fe r to Se ction 9.16, Write Change s to Dis k for more
information.
If your DVD drive is not de te cte d, and it is a SCSI DVD, the ins tallation program prompts
you to choos e a SCSI drive r. Choos e the drive r that mos t clos e ly re s e mble s your adapte r.
You may s pe cify options for the drive r if ne ce s s ary; howe ve r, mos t drive rs de te ct your
SCSI adapte r automatically.
If the DVD drive is found and the drive r loade d, the ins talle r will pre s e nt you with the
option to pe rform a me dia che ck on the DVD. This will take s ome time , and you may opt to
s kip ove r this s te p. Howe ve r, if you late r e ncounte r proble ms with the ins talle r, you s hould
re boot and pe rform the me dia che ck be fore calling for s upport. From the me dia che ck
dialog, continue to the ne xt s tage of the ins tallation proce s s (re fe r to Se ction 9.3,
We lcome to Re d Hat Ente rpris e Linux).
58
The Select Partition s cre e n applie s only if you are ins talling from a dis k partition (that
is , you s e le cte d Hard Drive in the Installation Method dialog). This dialog allows you to
name the dis k partition and dire ctory from which you are ins talling Re d Hat Ente rpris e
Linux. If you us e d the repo=hd boot option, you alre ady s pe cifie d a partition.
Figure 8.5. Select ing Part it io n Dialo g f o r Hard Drive Inst allat io n
Se le ct the partition containing the ISO file s from the lis t of available partitions . Inte rnal IDE,
SATA, SCSI, and USB drive de vice name s be gin with /dev/sd. Each individual drive has its
own le tte r, for e xample /dev/sda. Each partition on a drive is numbe re d, for e xample
/dev/sda1.
Als o s pe cify the Directory holding images. Ente r the full dire ctory path from the drive
that contains the ISO image file s . The following table s hows s ome e xample s of how to
e nte r this information:
T able 8.1. Lo cat io n o f ISO images f o r dif f erent part it io n t ypes
Part it io n t ype
Vo lume
Original pat h t o
f iles
Direct o ry t o use
VFAT
D:\
/home
If the ISO image s are in the root (top-le ve l) dire ctory of a partition, e nte r a /. If the ISO
image s are locate d in a s ubdire ctory of a mounte d partition, e nte r the name of the
dire ctory holding the ISO image s within that partition. For e xample , if the partition on which
the ISO image s is normally mounte d as /home/, and the image s are in /home/new/, you
would e nte r /new/.
59
60
61
addre s s .
Anaco nda s upports the IPv4 and IPv6 protocols . Howe ve r, if you configure an inte rface to
us e both IPv4 and IPv6, the IPv4 conne ction mus t s ucce e d or the inte rface will not work,
e ve n if the IPv6 conne ction s ucce e ds .
62
The dialog provide s fie lds for IPv4 and IPv6 addre s s e s and pre fixe s , de pe nding on the
protocols that you chos e to configure manually, toge the r with fie lds for the ne twork
gate way and name s e rve r. Ente r the de tails for your ne twork, the n pre s s OK.
Whe n the ins tallation proce s s comple te s , it will trans fe r the s e s e ttings to your s ys te m.
If you are ins talling via NFS, proce e d to Se ction 8.3.4, Ins talling via NFS.
If you are ins talling via We b or FTP, proce e d to Se ction 8.3.5, Ins talling via FTP, HTTP, or
HTTPS.
63
64
65
9.1. T he T ext Mode Inst allat ion Program User Int erface
Impo rtant Graphical Interface o n the Installed System
Ins talling in te xt mode doe s not pre ve nt you from us ing a graphical inte rface on your
s ys te m once it is ins talle d.
Apart from the graphical ins talle r, anaco nda als o include s a te xt-bas e d ins talle r.
If one of the following s ituations occurs , the ins tallation program us e s te xt mode :
The ins tallation s ys te m fails to ide ntify the dis play hardware on your compute r
You choos e the te xt mode ins tallation from the boot me nu
While te xt mode ins tallations are not e xplicitly docume nte d, thos e us ing the te xt mode
ins tallation program can e as ily follow the GUI ins tallation ins tructions . Howe ve r, be caus e
te xt mode pre s e nts you with a s imple r, more s tre amline d ins tallation proce s s , ce rtain
options that are available in graphical mode are not als o available in te xt mode . The s e
diffe re nce s are note d in the de s cription of the ins tallation proce s s in this guide , and
include :
configuring advance d s torage me thods s uch as LVM, RAID, FCoE, z FCP, and iSCSI.
cus tomiz ing the partition layout
cus tomiz ing the bootloade r layout
s e le cting package s during ins tallation
configuring the ins talle d s ys te m with f irst bo o t
If you choos e to ins tall Re d Hat Ente rpris e Linux in te xt mode , you can s till configure your
s ys te m to us e a graphical inte rface afte r ins tallation. Re fe r to Se ction 35.3, Switching to a
Graphical Login for ins tructions .
To configure options not available in te xt mode , cons ide r us ing a boot option. For e xample ,
the linux ip option can be us e d to configure ne twork s e ttings . Re fe r to Se ction 28.1,
Configuring the Ins tallation Sys te m at the Boot Me nu for ins tructions .
66
clicking on buttons or making othe r s cre e n s e le ctions , whe re X is re place d with any
unde rline d le tte r appe aring within that s cre e n.
No te
If you are us ing an x86, AMD64, or Inte l 64 s ys te m, and you do not wis h to us e the
GUI ins tallation program, the te xt mode ins tallation program is als o available . To
s tart the te xt mode ins tallation program, us e the following command at the boot:
prompt:
linux text
Re fe r to Se ction 7.1.2, The Boot Me nu for a de s cription of the Re d Hat Ente rpris e
Linux boot me nu and to Se ction 8.1, The Te xt Mode Ins tallation Program Us e r
Inte rface for a brie f ove rvie w of te xt mode ins tallation ins tructions .
It is highly re comme nde d that ins talls be pe rforme d us ing the GUI ins tallation
program. The GUI ins tallation program offe rs the full functionality of the Re d Hat
Ente rpris e Linux ins tallation program, including LVM configuration which is not
available during a te xt mode ins tallation.
Us e rs who mus t us e the te xt mode ins tallation program can follow the GUI
ins tallation ins tructions and obtain all ne e de d information.
67
keyst ro kes
co nt ent s
1
2
3
ctrl+alt+f1
ctrl+alt+f2
ctrl+alt+f3
4
5
ctrl+alt+f4
ctrl+alt+f5
68
69
No te
To change your ke yboard layout type afte r you have comple te d the ins tallation, us e
the Keybo ard Co nf igurat io n T o o l.
Type the system-config-keyboard command in a s he ll prompt to launch the
Keybo ard Co nf igurat io n T o o l. If you are not root, it prompts you for the root
pas s word to continue .
70
Se le ct Basic St o rage Devices to ins tall Re d Hat Ente rpris e Linux on the
following s torage de vice s :
hard drive s or s olid-s tate drive s conne cte d dire ctly to the local s ys te m.
Specialized St o rage Devices
Se le ct Specialized St o rage Devices to ins tall Re d Hat Ente rpris e Linux on the
following s torage de vice s :
Storage area networks (SANs )
Direct access storage devices (DASDs )
Firmware RAID de vice s
Multipath de vice s
Us e the Specialized St o rage Devices option to configure Internet Small
Computer System Interface (iSCSI) and FCoE (Fibe r Channe l ove r Ethe rne t)
conne ctions .
If you s e le ct Basic St o rage Devices, anaco nda automatically de te cts the local s torage
attache d to the s ys te m and doe s not re quire furthe r input from you. Proce e d to
Se ction 9.7, Se tting the Hos tname .
No te
Monitoring of LVM and s oftware RAID de vice s by the mdeventd dae mon is not
pe rforme d during ins tallation.
71
72
73
whe n you have s e le cte d the s torage de vice s to make available during ins tallation, click
Next and proce e d to Se ction 9.11, Initializ ing the Hard Dis k
74
75
76
the m as iSCSI targe ts and be able to cre ate an iSCSI session to acce s s the m. Each of
the s e s te ps might re quire a us e rname and pas s word for CHAP (Challe nge Hands hake
Authe ntication Protocol) authe ntication. Additionally, you can configure an iSCSI targe t to
authe nticate the iSCSI initiator on the s ys te m to which the targe t is attache d (reverse
CHAP), both for dis cove ry and for the s e s s ion. Us e d toge the r, CHAP and re ve rs e CHAP are
calle d mutual CHAP or two-way CHAP. Mutual CHAP provide s the gre ate s t le ve l of s e curity
for iSCSI conne ctions , particularly if the us e rname and pas s word are diffe re nt for CHAP
authe ntication and re ve rs e CHAP authe ntication.
Re pe at the iSCSI dis cove ry and iSCSI login s te ps as many time s as ne ce s s ary to add all
re quire d iSCSI s torage . Howe ve r, you cannot change the name of the iSCSI initiator afte r
you atte mpt dis cove ry for the firs t time . To change the iSCSI initiator name , you mus t
re s tart the ins tallation.
Pro cedure 9.1. iSCSI disco very
Us e the iSCSI Discovery Details dialog to provide anaco nda with the information that
it ne e ds to dis cove r the iSCSI targe t.
77
your organiz ation's Inte rne t domain or s ubdomain name , pre s e nte d in re ve rs e
orde r with the top-le ve l domain firs t. For e xample , re pre s e nt the s ubdomain
storage.example.com as com.example.storage
a colon followe d by a s tring that unique ly ide ntifie s this particular iSCSI initiator
within your domain or s ubdomain. For e xample , :diskarrays-sn-a8675309.
A comple te IQN the re fore re s e mble s : iqn.201009.storage.example.com:diskarrays-sn-a8675309, and anaco nda pre populate s the iSCSI Initiator Name fie ld with a name in this format to he lp you
with the s tructure .
For more information on IQNs , re fe r to 3.2.6. iSCSI Names in RFC 3720 - Internet
Small Computer Systems Interface (iSCSI) available from
http://tools .ie tf.org/html/rfc3720#s e ction-3.2.6 and 1. iSCSI Names and Addresses in
RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery
available from http://tools .ie tf.org/html/rfc3721#s e ction-1.
3. Us e the drop-down me nu to s pe cify the type of authe ntication to us e for iSCSI
dis cove ry:
78
79
80
81
82
83
any dis cove re d FCoE VLANs will be automatically cre ate d and FCoE ins tance s will be
cre ate d on the VLAN inte rface s .
Valid Ho stnames
You may give your s ys te m any name provide d that the full hos tname is unique . The
hos tname may include le tte rs , numbe rs and hyphe ns .
84
Mo dem Co nfiguratio n
The ins tallation program doe s not configure mode ms . Configure the s e de vice s afte r
ins tallation with the Net wo rk utility. The s e ttings for your mode m are s pe cific to
your particular Inte rne t Se rvice Provide r (ISP).
No te
To change your ne twork configuration afte r you have comple te d the ins tallation, us e
the Net wo rk Administ rat io n T o o l.
Type the system-config-network command in a s he ll prompt to launch the
Net wo rk Administ rat io n T o o l. If you are not root, it prompts you for the root
pas s word to continue .
The Net wo rk Administ rat io n T o o l is now de pre cate d and will be re place d by
Net wo rkManager during the life time of Re d Hat Ente rpris e Linux 6.
To configure a ne twork conne ction manually, click the button Configure Network. The
Network Connections dialog appe ars that allows you to configure wire d, wire le s s , mobile
broadband, InfiniBand, VPN, DSL, VLAN, and bonde d conne ctions for the s ys te m us ing the
Net wo rkManager tool. A full de s cription of all configurations pos s ible with
Net wo rkManager is be yond the s cope of this guide . This s e ction only de tails the mos t
typical s ce nario of how to configure wire d conne ctions during ins tallation. Configuration of
othe r type s of ne twork is broadly s imilar, although the s pe cific parame te rs that you mus t
configure are ne ce s s arily diffe re nt.
85
9.7.1.2. T he Wired t ab
86
Us e the Wired tab to s pe cify or change the media access control (MAC) addre s s for the
ne twork adapte r, and e ithe r s e t the maximum transmission unit (MTU, in byte s ) that can
pas s through the inte rface .
87
88
89
The IPv4 addre s s , ne tmas k, and gate way addre s s are configure d by the DHCP
s e rvice on the ne twork, but DNS s e rve rs and s e arch domains mus t be configure d
manually.
Manual
IPv4 parame te rs are configure d manually for a s tatic configuration.
Link-Local Only
A link-local addre s s in the 169.254/16 range is as s igne d to the inte rface .
Shared to other computers
The s ys te m is configure d to provide ne twork acce s s to othe r compute rs . The
inte rface is as s igne d an addre s s in the 10.42.x.1/24 range , a DHCP s e rve r and
DNS s e rve r are s tarte d, and the inte rface is conne cte d to the de fault ne twork
conne ction on the s ys te m with network address translation (NAT).
Disabled
IPv4 is dis able d for this conne ction.
If you s e le cte d a me thod that re quire s you to s upply manual parame te rs , e nte r de tails of
the IP addre s s for this inte rface , the ne tmas k, and the gate way in the Addresses fie ld.
Us e the Add and Delete buttons to add or re move addre s s e s . Ente r a comma-s e parate d
lis t of DNS s e rve rs in the DNS servers fie ld, and a comma-s e parate d lis t of domains in
the Search domains fie ld for any domains that you want to include in name s e rve r
lookups .
Optionally, e nte r a name for this ne twork conne ction in the DHCP client ID fie ld. This
name mus t be unique on the s ubne t. Whe n you as s ign a me aningful DHCP clie nt ID to a
conne ction, it is e as y to ide ntify this conne ction whe n trouble s hooting ne twork proble ms .
De s e le ct the Require IPv4 addressing for this connection to complete che ck box
to allow the s ys te m to make this conne ction on an IPv6-e nable d ne twork if IPv4
configuration fails but IPv6 configuration s ucce e ds .
90
91
92
Net wo rkManager doe s not us e RA, but re que s ts information from DHCPv6
dire ctly to cre ate a s tate ful configuration.
Manual
IPv6 parame te rs are configure d manually for a s tatic configuration.
Link-Local Only
A link-local addre s s with the fe 80::/10 pre fix is as s igne d to the inte rface .
If you s e le cte d a me thod that re quire s you to s upply manual parame te rs , e nte r de tails of
the IP addre s s for this inte rface , the ne tmas k, and the gate way in the Addresses fie ld.
Us e the Add and Delete buttons to add or re move addre s s e s . Ente r a comma-s e parate d
lis t of DNS s e rve rs in the DNS servers fie ld, and a comma-s e parate d lis t of domains in
the Search domains fie ld for any domains that you want to include in name s e rve r
lookups .
Optionally, e nte r a name for this ne twork conne ction in the DHCP client ID fie ld. This
name mus t be unique on the s ubne t. Whe n you as s ign a me aningful DHCP clie nt ID to a
conne ction, it is e as y to ide ntify this conne ction whe n trouble s hooting ne twork proble ms .
De s e le ct the Require IPv6 addressing for this connection to complete che ck box
to allow the s ys te m to make this conne ction on an IPv4-e nable d ne twork if IPv6
configuration fails but IPv4 configuration s ucce e ds .
93
94
95
4. Ve rify that the inte rface configuration file contains the line ONBOOT=yes. If the file
doe s not alre ady contain the line , add it now and s ave the file .
5. Exit the vi e ditor.
6. Move the inte rface configuration file back to the /etc/sysconfig/networkscripts/ dire ctory:
mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/
The de vice is now re conne cte d in anaco nda.
7. Pre s s Ctrl+Alt+F6 to re turn to anaco nda.
96
Hat Ente rpris e Linux us e s the time z one s e tting to de te rmine the offs e t be twe e n the local
time and UTC on the s ys te m clock. This be havior is s tandard for s ys te ms that us e UNIX,
Linux, and s imilar ope rating s ys te ms .
Click Next to proce e d.
No te
To change your time z one configuration afte r you have comple te d the ins tallation,
us e the T ime and Dat e Pro pert ies T o o l.
Type the system-config-date command in a s he ll prompt to launch the T ime and
Dat e Pro pert ies T o o l. If you are not root, it prompts you for the root pas s word to
continue .
No te
The root us e r (als o known as the s upe rus e r) has comple te acce s s to the e ntire
s ys te m; for this re as on, logging in as the root us e r is be s t done only to pe rform
s ys te m mainte nance or adminis tration.
97
No te
To be come root, type su - at the s he ll prompt in a te rminal window and the n pre s s
Enter. The n, e nte r the root pas s word and pre s s Enter.
The ins tallation program prompts you to s e t a root pas s word [2] for your s ys te m. . You
cannot proceed to the next stage of the installation process without entering a root
password.
The root pas s word mus t be at le as t s ix characte rs long; the pas s word you type is not
e choe d to the s cre e n. You mus t e nte r the pas s word twice ; if the two pas s words do not
match, the ins tallation program as ks you to e nte r the m again.
You s hould make the root pas s word s ome thing you can re me mbe r, but not s ome thing that
is e as y for s ome one e ls e to gue s s . Your name , your phone numbe r, qwerty, password,
root, 123456, and anteater are all e xample s of bad pas s words . Good pas s words mix
nume rals with uppe r and lowe r cas e le tte rs and do not contain dictionary words :
Aard387vark or 420BMttNT, for e xample . Re me mbe r that the pas s word is cas e -s e ns itive . If
you write down your pas s word, ke e p it in a s e cure place . Howe ve r, it is re comme nde d
that you do not write down this or any pas s word you cre ate .
98
Cho o se yo ur o wn passwo rd
Do not us e one of the e xample pas s words offe re d in this manual. Us ing one of
the s e pas s words could be cons ide re d a s e curity ris k.
To change your root pas s word afte r you have comple te d the ins tallation, run the passwd
command as root. If you forge t the root pas s word, s e e Re s olving Proble ms in Sys te m
Re cove ry Mode s in the Re d Hat Ente rpris e Linux 6 De ployme nt Guide for ins tructions on
how to s e t a ne w one .
99
Move a de vice from one lis t to the othe r by clicking on the de vice , the n clicking e ithe r the
button labe le d with a le ft-pointing arrow to move it to the lis t of data s torage de vice s or
the button labe le d with a right-pointing arrow to move it to the lis t of de vice s available for
ins tallation of the ope rating s ys te m.
The lis t of de vice s available as ins tallation targe ts als o include s a radio button be s ide
e ach de vice . Us e this radio button to s pe cify the de vice that you want to us e as the boot
de vice for the s ys te m.
Whe n you have finis he d ide ntifying de vice s to be us e d for ins tallation, click Next to
continue .
100
101
Impo rtant
The following s e ctions only apply to upgrading Re d Hat Ente rpris e Linux be twe e n
minor ve rs ions , for e xample , upgrading Re d Hat Ente rpris e Linux 6.4 to Re d Hat
Ente rpris e Linux 6.5 or highe r. This approach is not s upporte d for upgrade s be twe e n
major ve rs ions , for e xample , upgrading Re d Hat Ente rpris e Linux 6 to Re d Hat
Ente rpris e Linux 7.
In-place upgrade s be twe e n major ve rs ions of Re d Hat Ente rpris e Linux can be done ,
with ce rtain limitations , us ing the Red Hat Upgrade T o o l and Preupgrade
Assist ant tools . Se e Chapte r 37, Upgrading Your Current System for more
information.
The ins tallation s ys te m automatically de te cts any e xis ting ins tallation of Re d Hat
Ente rpris e Linux. The upgrade proce s s update s the e xis ting s ys te m s oftware with ne w
ve rs ions , but doe s not re move any data from us e rs ' home dire ctorie s . The e xis ting
partition s tructure on your hard drive s doe s not change . Your s ys te m configuration
change s only if a package upgrade de mands it. Mos t package upgrade s do not change
s ys te m configuration, but rathe r ins tall an additional configuration file for you to e xamine
late r.
Note that the ins tallation me dium that you are us ing might not contain all the s oftware
package s that you ne e d to upgrade your compute r.
102
103
Partitioning allows you to divide your hard drive into is olate d s e ctions , whe re e ach s e ction
be have s as its own hard drive . Partitioning is particularly us e ful if you run multiple
ope rating s ys te ms . If you are not s ure how you want your s ys te m to be partitione d, re ad
Appe ndix A, An Introduction to Disk Partitions for more information.
105
Warning
If you s e le ct this option, all data on the s e le cte d hard drive s is re move d by
the ins tallation program. Do not s e le ct this option if you have information
that you want to ke e p on the hard drive s whe re you are ins talling Re d Hat
Ente rpris e Linux.
In particular, do not s e le ct this option whe n you configure a s ys te m to chain
load the Re d Hat Ente rpris e Linux boot loade r from anothe r boot loade r.
106
Se le ct this option to re move only partitions cre ate d by a pre vious Linux
ins tallation. This doe s not re move othe r partitions you may have on your hard
drive s (s uch as VFAT or FAT32 partitions ).
Shrink Current Syst em
Se le ct this option to re s iz e your curre nt data and partitions manually and ins tall a
de fault Re d Hat Ente rpris e Linux layout in the s pace that is fre e d.
Warning
If you s hrink partitions on which othe r ope rating s ys te ms are ins talle d, you
might not be able to us e thos e ope rating s ys te ms . Although this partitioning
option doe s not de s troy data, ope rating s ys te ms typically re quire s ome
fre e s pace in the ir partitions . Be fore you re s iz e a partition that holds an
ope rating s ys te m that you might want to us e again, find out how much
s pace you ne e d to le ave fre e .
Use Free Space
Se le ct this option to re tain your curre nt data and partitions and ins tall Re d Hat
Ente rpris e Linux in the unus e d s pace available on the s torage drive s . Ens ure that
the re is s ufficie nt s pace available on the s torage drive s be fore you s e le ct this
option re fe r to Se ction 3.6, Do You Have Enough Dis k Space ?.
Warning
If your 64-bit x86 s ys te m us e s UEFI ins te ad of BIOS, you will ne e d to
manually cre ate a /boot partition. This partition mus t have an e xt3 file
s ys te m. If you choos e to partition automatically, your s ys te m will not boot.
Creat e Cust o m Layo ut
Se le ct this option to partition s torage de vice s manually and cre ate cus tomiz e d
layouts . Re fe r to Se ction 9.15, Cre ating a Cus tom Layout or Modifying the De fault
Layout
Choos e your pre fe rre d partitioning me thod by clicking the radio button to the le ft of its
de s cription in the dialog box.
Se le ct Encrypt system to e ncrypt all partitions e xce pt the /boot partition. Re fe r to
Appe ndix C, Disk Encryption for information on e ncryption.
To re vie w and make any ne ce s s ary change s to the partitions cre ate d by automatic
partitioning, s e le ct the Review option. Afte r s e le cting Review and clicking Next to move
forward, the partitions cre ate d for you by anaco nda appe ar. You can make modifications
to the s e partitions if the y do not me e t your ne e ds .
107
108
Warning
If your 64-bit x86 s ys te m us e s UEFI ins te ad of BIOS, you will ne e d to manually
cre ate a /boot partition. This partition mus t have an e xt3 file s ys te m. If you choos e
to partition automatically, your s ys te m will not boot.
109
Impo rtant
On s ys te ms us ing UEFI firmware , the boot drive (the dis k whe re the boot loade r will
be ins talle d) mus t contain a s pe cial partition (EFI Sys te m Partition) at le as t 50 MB in
s iz e with a mount point of /boot/efi.
The boot drive mus t als o have a GUID Partition Table (GPT) labe l. If you want to
re us e a dis k with e xis ting partitions and a Mas te r Boot Re cord (MBR) labe l, the dis k
mus t be re labe le d. All existing data on the disk will be lost.
To re labe l a dis k to GPT in the graphical ins talle r, firs t go back to Se ction 9.13, Dis k
Partitioning Se tup, and choos e an automatic partitioning option s uch as Use All
Space. Che ck the Review and modify partitioning layout che ck box, and click
Next. On the ne xt s cre e n, modify the automatically cre ate d layout as ne e de d.
This workaround is always ne ce s s ary whe n re us ing a MBR-labe le d drive . If you
choos e Create a Custom Layout at the s tart of the partitioning proce s s , the dis k
will not be re labe le d and you will not be able to proce e d.
Do no t place
/usr
or
/var
If /usr or /var is partitione d s e parate ly from the re s t of the root volume , the boot
proce s s be come s much more comple x be caus e the s e dire ctorie s contain bootcritical compone nts . In s ome s ituations , s uch as whe n the s e dire ctorie s are place d
on an iSCSI drive or an FCoE location, the s ys te m may e ithe r be unable to boot, or it
may hang with a Device is busy e rror whe n powe ring off or re booting.
This limitation only applie s to /usr or /var; not to dire ctorie s be low the m. For
e xample , a s e parate partition for /var/www will work without is s ue s .
110
Figure 9.40 . Part it io ning o n x86, AMD64, and Int el 64 Syst ems
The partitioning s cre e n contains two pane s . The top pane contains a graphical
re pre s e ntation of the hard drive , logical volume , or RAID de vice s e le cte d in the lowe r
pane .
Above the graphical re pre s e ntation of the de vice , you can re vie w the name of the drive
(s uch as /dev/sda or LogVol00), its s iz e (in MB), and its mode l as de te cte d by the
ins tallation program.
Us ing your mous e , click once to highlight a particular fie ld in the graphical dis play. Double click to e dit an e xis ting partition or to cre ate a partition out of e xis ting fre e s pace .
The lowe r pane contains a lis t of all drive s , logical volume s , and RAID de vice s to be us e d
during ins tallation, as s pe cifie d e arlie r in the ins tallation proce s s re fe r to Se ction 9.10,
As s ign Storage De vice s
De vice s are groupe d by type . Click on the s mall triangle s to the le ft of e ach de vice type
to vie w or hide de vice s of that type .
Anaco nda dis plays s e ve ral de tails for e ach de vice lis te d:
Device
the name of the de vice , logical volume , or partition
Size (MB)
the s iz e of the de vice , logical volume , or partition (in MB)
Mo unt Po int /RAID/Vo lume
the mount point (location within a file s ys te m) on which a partition is to be
mounte d, or the name of the RAID or logical volume group of which it is a part
T ype
111
the type of partition. If the partition is a s tandard partition, this fie ld dis plays the
type of file s ys te m on the partition (for e xample , e xt4). Othe rwis e , it indicate s
that the partition is a physical volume (LVM), or part of a software RAID
Fo rmat
A che ck mark in this column indicate s that the partition will be formatte d during
ins tallation.
Be ne ath the lowe r pane are four buttons : Create, Edit, Delete, and Reset.
Se le ct a de vice or partition by clicking on it in e ithe r the graphical re pre s e ntation in the
uppe r pane of in the lis t in the lowe r pane , the n click one of the four buttons to carry out
the following actions :
Creat e
cre ate a ne w partition, logical volume , or s oftware RAID
Edit
change an e xis ting partition, logical volume , or s oftware RAID. Note that you can
only s hrink partitions with the Resize button, not e nlarge partitions .
Delet e
re move a partition, logical volume , or s oftware RAID
Reset
undo all change s made in this s cre e n
112
113
No te
You mus t de dicate at le as t one partition for this ins tallation, and optionally more . For
more information, re fe r to Appe ndix A, An Introduction to Disk Partitions.
114
Mount Point: Ente r the partition's mount point. For e xample , if this partition s hould be
the root partition, e nte r /; e nte r /boot for the /boot partition, and s o on. You can als o
us e the pull-down me nu to choos e the corre ct mount point for your partition. For a s wap
partition the mount point s hould not be s e t s e tting the file s ys te m type to swap is
s ufficie nt.
File System Type: Us ing the pull-down me nu, s e le ct the appropriate file s ys te m type
for this partition. For more information on file s ys te m type s , re fe r to Se ction 9.15.2.1,
File Sys te m Type s .
Allowable Drives: This fie ld contains a lis t of the hard dis ks ins talle d on your s ys te m.
If a hard dis k's box is highlighte d, the n a de s ire d partition can be cre ate d on that hard
dis k. If the box is not che cke d, the n the partition will never be cre ate d on that hard dis k.
By us ing diffe re nt che ckbox s e ttings , you can have anaco nda place partitions whe re
you ne e d the m, or le t anaco nda de cide whe re partitions s hould go.
Size (MB): Ente r the s iz e (in me gabyte s ) of the partition. Note , this fie ld s tarts with
200 MB; unle s s change d, only a 200 MB partition will be cre ate d.
Additional Size Options: Choos e whe the r to ke e p this partition at a fixe d s iz e , to
allow it to "grow" (fill up the available hard drive s pace ) to a ce rtain point, or to allow it
to grow to fill any re maining hard drive s pace available .
If you choos e Fill all space up to (MB), you mus t give s iz e cons traints in the fie ld
to the right of this option. This allows you to ke e p a ce rtain amount of s pace fre e on
your hard drive for future us e .
Force to be a primary partition: Se le ct whe the r the partition you are cre ating
s hould be one of the firs t four partitions on the hard drive . If uns e le cte d, the partition is
cre ate d as a logical partition. Re fe r to Se ction A.1.3, Partitions Within Partitions An
Ove rvie w of Exte nde d Partitions , for more information.
Encrypt: Choos e whe the r to e ncrypt the partition s o that the data s tore d on it cannot
be acce s s e d without a pas s phras e , e ve n if the s torage de vice is conne cte d to anothe r
s ys te m. Re fe r to Appe ndix C, Disk Encryption for information on e ncryption of s torage
de vice s . If you s e le ct this option, the ins talle r prompts you to provide a pas s phras e
be fore it write s the partition to the dis k.
OK: Se le ct OK once you are s atis fie d with the s e ttings and wis h to cre ate the partition.
Cancel: Se le ct Cancel if you do not want to cre ate the partition.
115
software RAID Cre ating two or more s oftware RAID partitions allows you to cre ate a
RAID de vice . For more information re garding RAID, re fe r to the chapte r RAID (Redundant
Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide.
physical volume (LVM) Cre ating one or more phys ical volume (LVM) partitions
allows you to cre ate an LVM logical volume . LVM can improve pe rformance whe n us ing
phys ical dis ks . For more information re garding LVM, re fe r to the Red Hat Enterprise
Linux Deployment Guide.
File syst ems
ext4 The e xt4 file s ys te m is bas e d on the e xt3 file s ys te m and fe ature s a numbe r
of improve me nts . The s e include s upport for large r file s ys te ms and large r file s , fas te r
and more e fficie nt allocation of dis k s pace , no limit on the numbe r of s ubdire ctorie s
within a dire ctory, fas te r file s ys te m che cking, and more robus t journaling. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt4. The e xt4 file s ys te m is s e le cte d by
de fault and is highly re comme nde d.
ext3 The e xt3 file s ys te m is bas e d on the e xt2 file s ys te m and has one main
advantage journaling. Us ing a journaling file s ys te m re duce s time s pe nt re cove ring a
file s ys te m afte r a cras h as the re is no ne e d to fsck [3] the file s ys te m. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt3.
ext2 An e xt2 file s ys te m s upports s tandard Unix file type s (re gular file s , dire ctorie s ,
s ymbolic links , e tc). It provide s the ability to as s ign long file name s , up to 255
characte rs .
xfs XFS is a highly s calable , high-pe rformance file s ys te m that s upports file s ys te ms
up to 16 e xabyte s (approximate ly 16 million te rabyte s ), file s up to 8 e xabyte s
(approximate ly 8 million te rabyte s ) and dire ctory s tructure s containing te ns of millions
of e ntrie s . XFS s upports me tadata journaling, which facilitate s quicke r cras h re cove ry.
The XFS file s ys te m can als o be de fragme nte d and re s iz e d while mounte d and active .
No te
The maximum s iz e of an XFS partition the ins talle r can cre ate is 100 TB.
vfat The VFAT file s ys te m is a Linux file s ys te m that is compatible with Micros oft
Windows long file name s on the FAT file s ys te m.
Btrfs Btrfs is unde r de ve lopme nt as a file s ys te m capable of addre s s ing and
managing more file s , large r file s , and large r volume s than the e xt2, e xt3, and e xt4 file
s ys te ms . Btrfs is de s igne d to make the file s ys te m tole rant of e rrors , and to facilitate
the de te ction and re pair of e rrors whe n the y occur. It us e s che cks ums to e ns ure the
validity of data and me tadata, and maintains s naps hots of the file s ys te m that can be
us e d for backup or re pair.
Be caus e Btrfs is s till e xpe rime ntal and unde r de ve lopme nt, the ins tallation program
doe s not offe r it by de fault. If you want to cre ate a Btrfs partition on a drive , you mus t
comme nce the ins tallation proce s s with the boot option btrfs. Re fe r to Chapte r 28,
Boot Options for ins tructions .
116
117
118
RAID 1 mirrors the data on one s torage de vice onto one or more othe r
s torage de vice s . Additional de vice s in the array provide incre as ing le ve ls of
re dundancy. RAID 1 re quire s at le as t two RAID partitions .
RAID 4 dis tribute s data acros s multiple s torage de vice s , but us e s one
de vice in the array to s tore parity information that s afe guards the array in
cas e any de vice within the array fails . Be caus e all parity information is s tore d
on the one de vice , acce s s to this de vice cre ate s a bottle ne ck in the
pe rformance of the array. RAID 4 re quire s at le as t thre e RAID partitions .
RAID 5 dis tribute s data and parity information acros s multiple s torage
de vice s . Le ve l 5 RAIDs the re fore offe r the pe rformance advantage s of
dis tributing data acros s multiple de vice s , but do not s hare the pe rformance
bottle ne ck of le ve l 4 RAIDs be caus e the parity information is als o dis tribute d
through the array. RAID 5 re quire s at le as t thre e RAID partitions .
RAID 6 le ve l 6 RAIDs are s imilar to le ve l 5 RAIDs , but ins te ad of s toring only
one s e t of parity data, the y s tore two s e ts . RAID 6 re quire s at le as t four RAID
partitions .
RAID 10 le ve l 10 RAIDs are nested RAIDs or hybrid RAIDs. Le ve l 10 RAIDs
are cons tructe d by dis tributing data ove r mirrore d s e ts of s torage de vice s . For
e xample , a le ve l 10 RAID cons tructe d from four RAID partitions cons is ts of two
pairs of partitions in which one partition mirrors the othe r. Data is the n
dis tribute d acros s both pairs of s torage de vice s , as in a le ve l 0 RAID. RAID 10
re quire s at le as t four RAID partitions .
119
120
121
122
Impo rtant
Re comme ndations in the table be low are e s pe cially important on s ys te ms with
low me mory (1 GB and le s s ). Failure to allocate s ufficie nt s wap s pace on the s e
s ys te ms may caus e is s ue s s uch as ins tability or e ve n re nde r the ins talle d
s ys te m unbootable .
2GB
> 2GB 8GB
> 8GB 64GB
> 64GB
At le as t 4 GB
At the borde r be twe e n e ach range lis te d above (for e xample , a s ys te m with 2GB, 8GB,
or 64GB of s ys te m RAM), dis cre tion can be e xe rcis e d with re gard to chos e n s wap
s pace and hibe rnation s upport. If your s ys te m re s ource s allow for it, incre as ing the
s wap s pace may le ad to be tte r pe rformance .
Note that dis tributing s wap s pace ove r multiple s torage de vice s particularly on
s ys te ms with fas t drive s , controlle rs and inte rface s als o improve s s wap s pace
pe rformance .
No te
Swap s pace s iz e re comme ndations is s ue d for Re d Hat Ente rpris e Linux 6.0, 6.1,
and 6.2 diffe re d from the curre nt re comme ndations , which we re firs t is s ue d with
the re le as e of Re d Hat Ente rpris e Linux 6.3 in June 2012 and did not account for
hibe rnation s pace . Automatic ins tallations of the s e e arlie r ve rs ions of Re d Hat
Ente rpris e Linux 6 s till ge ne rate a s wap s pace in line with the s e s upe rs e de d
re comme ndations . Howe ve r, manually s e le cting a s wap s pace s iz e in line with
the ne we r re comme ndations is s ue d for Re d Hat Ente rpris e Linux 6.3 is advis able
for optimal pe rformance .
123
Warning
Note that normally the /boot partition is cre ate d automatically by the ins talle r.
Howe ve r, if the / (root) partition is large r than 2 TB and (U)EFI is us e d for booting,
you ne e d to cre ate a s e parate /boot partition that is s malle r than 2 TB to boot
the machine s ucce s s fully.
No te
If your hard drive is more than 1024 cylinde rs (and your s ys te m was
manufacture d more than two ye ars ago), you may ne e d to cre ate a /boot/
partition if you want the / (root) partition to us e all of the re maining s pace on your
hard drive .
No te
If you have a RAID card, be aware that s ome BIOS type s do not s upport booting
from the RAID card. In cas e s s uch as the s e , the /boot/ partition mus t be cre ate d
on a partition outs ide of the RAID array, s uch as on a s e parate hard drive .
A root partition (3.0 GB - 5.0 GB) this is whe re "/" (the root dire ctory) is locate d. In
this s e tup, all file s (e xce pt thos e s tore d in /boot) are on the root partition.
A 3.0 GB partition allows you to ins tall a minimal ins tallation, while a 5.0 GB root
partition le ts you pe rform a full ins tallation, choos ing all package groups .
124
Ro o t and
/root
The / (or root) partition is the top of the dire ctory s tructure . The /root dire ctory
(s ome time s pronounce d "s las h-root") is the home dire ctory of the us e r account
for s ys te m adminis tration.
Minimum size
/
/usr
250 MB
250 MB, but avoid placing this on a
s e parate partition
50 MB
384 MB
100 MB
250 MB
/tmp
/var
/home
/boot
125
Cons ide r e ncrypting any partitions that might contain s e ns itive data. Encryption
pre ve nts unauthoriz e d pe ople from acce s s ing the data on the partitions , e ve n if the y
have acce s s to the phys ical s torage de vice . In mos t cas e s , you s hould at le as t e ncrypt
the /home partition.
Each ke rne l ins talle d on your s ys te m re quire s approximate ly 10 MB on the /boot
partition. Unle s s you plan to ins tall a gre at many ke rne ls , the de fault partition s iz e of
250 MB for /boot s hould s uffice .
Warning
The PackageKit update s oftware downloads update d package s to
/var/cache/yum/ by de fault. If you partition the s ys te m manually, and cre ate a
s e parate /var/ partition, be s ure to cre ate the partition large e nough (3.0 GB or
more ) to download package update s .
The /usr dire ctory holds the majority of s oftware conte nt on a Re d Hat Ente rpris e Linux
s ys te m. For an ins tallation of the de fault s e t of s oftware , allocate at le as t 4 GB of
s pace . If you are a s oftware de ve lope r or plan to us e your Re d Hat Ente rpris e Linux
s ys te m to le arn s oftware de ve lopme nt s kills , you may want to at le as t double this
allocation.
Do no t place
/usr
or
/var
If /usr or /var is partitione d s e parate ly from the re s t of the root volume , the
boot proce s s be come s much more comple x be caus e the s e dire ctorie s contain
boot-critical compone nts . In s ome s ituations , s uch as whe n the s e dire ctorie s are
place d on an iSCSI drive or an FCoE location, the s ys te m may e ithe r be unable to
boot, or it may hang with a Device is busy e rror whe n powe ring off or re booting.
This limitation only applie s to /usr or /var; not to dire ctorie s be low the m. For
e xample , a s e parate partition for /var/www will work without is s ue s .
Cons ide r le aving a portion of the s pace in an LVM volume group unallocate d. This
unallocate d s pace give s you fle xibility if your s pace re quire me nts change but you do
not wis h to re move data from othe r partitions to re allocate s torage .
126
a If you s e parate s ubdire ctorie s into partitions , you can re tain conte nt in thos e
s ubdire ctorie s if you de cide to ins tall a ne w ve rs ion of Re d Hat Ente rpris e Linux ove r
your curre nt s ys te m. For ins tance , if you inte nd to run a MySQL databas ge in
/var/lib/mysql, make a s e parate partition for that dire ctory in cas e you ne e d to
re ins tall late r.
UEFI s ys te ms s hould contain a 50-150MB /boot/efi partition with an EFI Sys te m
Partition file s ys te m.
The following table is a pos s ible partition s e tup for a s ys te m with a s ingle , ne w 80 GB
hard dis k and 1 GB of RAM. Note that approximate ly 10 GB of the volume group is
unallocate d to allow for future growth.
Example Usage
This s e tup is not optimal for all us e cas e s .
/boot
swap
LVM phys ical volume
The phys ical volume is as s igne d to the de fault volume group and divide d into the
following logical volume s :
T able 9.5. Example part it io n set up: LVM physical vo lume
Part it io n
/
/var
/home
13 GB e xt4
4 GB e xt4
50 GB e xt4
127
128
Installing in text mo de
If you ins tall Re d Hat Ente rpris e Linux in te xt mode , you cannot make package
s e le ctions . The ins talle r automatically s e le cts package s only from the bas e and core
groups . The s e package s are s ufficie nt to e ns ure that the s ys te m is ope rational at
the e nd of the ins tallation proce s s , re ady to ins tall update s and ne w package s . To
change the package s e le ction, comple te the ins tallation, the n us e the Add/Remo ve
So f t ware application to make de s ire d change s .
129
This option provide s OpenLDAP and Ent erprise Ident it y Management (IPA) to
cre ate an ide ntity and authe ntication s e rve r.
Virt ual Ho st
This option provide s the KVM and Virt ual Machine Manager tools to cre ate a
hos t for virtual machine s .
Deskt o p
This option provide s the OpenOf f ice.o rg productivity s uite , graphical tools s uch
as the GIMP, and multime dia applications .
So f t ware Develo pment Wo rkst at io n
This option provide s the ne ce s s ary tools to compile s oftware on your Re d Hat
Ente rpris e Linux s ys te m.
Minimal
This option provide s only the package s e s s e ntial to run Re d Hat Ente rpris e Linux.
A minimal ins tallation provide s the bas is for a s ingle -purpos e s e rve r or de s ktop
appliance and maximiz e s pe rformance and s e curity on s uch an ins tallation.
Warning
Minimal ins tallation curre ntly doe s not configure the fire wall
(iptables/ip6tables) by de fault be caus e the authconfig and system-configfirewall-base package s are mis s ing from the s e le ction. To work around this
is s ue , you can us e a Kicks tart file to add the s e package s to your s e le ction.
Se e the Re d Hat Cus tome r Portal for de tails about the workaround, and
Chapte r 32, Kickstart Installations for information about Kicks tart file s .
If you do not us e the workaround, the ins tallation will comple te s ucce s s fully,
but no fire wall will be configure d, pre s e nting a s e curity ris k.
If you choos e to acce pt the curre nt package lis t, s kip ahe ad to Se ction 9.19, Ins talling
Package s .
To s e le ct a compone nt, click on the che ckbox be s ide it (re fe r to Figure 9.49, Package
Group Se le ction).
To cus tomiz e your package s e t furthe r, s e le ct the Customize now option on the s cre e n.
Clicking Next take s you to the Package Group Selection s cre e n.
130
The High Availability re pos itory include s package s for high-availability clus te ring
(als o known as failover clustering) us ing the Re d Hat High-availability Se rvice
Manage me nt compone nt.
The Load Balancer re pos itory include s package s for load-balancing clus te ring us ing
Linux Virtual Server (LVS).
The Red Hat Enterprise Linux re pos itory is automatically s e le cte d for you. It
contains the comple te colle ction of s oftware that was re le as e d as Re d Hat Ente rpris e
Linux 6.6, with the various pie ce s of s oftware in the ir ve rs ions that we re curre nt at the
time of re le as e .
The Resilient Storage re pos itory include s package s for s torage clus te ring us ing the
Re d Hat global file system (GFS).
For more information about clus te ring with Re d Hat Ente rpris e Linux 6.6, re fe r to the Red
Hat Enterprise Linux 6.6 High Availability Add-On Overview, available from
https ://acce s s .re dhat.com/s ite /docume ntation/Re d_Hat_Ente rpris e _Linux/.
131
If you change the re pos itory information during a non-ne twork ins tallation, s uch as from a
Re d Hat Ente rpris e Linux DVD, the ins talle r prompts you for ne twork configuration
information.
132
133
134
Installing in text mo de
If you ins tall Re d Hat Ente rpris e Linux in te xt mode , the ins talle r configure s the
bootloade r automatically and you cannot cus tomiz e bootloade r s e ttings during the
ins tallation proce s s .
GRUB (GRand Unifie d Bootloade r), which is ins talle d by de fault, is a ve ry powe rful boot
loade r. GRUB can load a varie ty of fre e ope rating s ys te ms , as we ll as proprie tary
ope rating s ys te ms with chain-loading (the me chanis m for loading uns upporte d ope rating
s ys te ms , s uch as Windows , by loading anothe r boot loade r). Note that the ve rs ion of GRUB
in Re d Hat Ente rpris e Linux 6 is an old and s table ve rs ion now known as "GRUB Le gacy"
s ince ups tre am de ve lopme nt move d to GRUB 2. [4] Re d Hat re mains committe d to
maintaining the ve rs ion of GRUB that we s hip with Re d Hat Ente rpris e Linux 6, jus t as we
do with all package s that we s hip.
135
T he GRUB bo o t menu
The GRUB me nu de faults to be ing hidde n, e xce pt on dual-boot s ys te ms . To s how the
GRUB me nu during s ys te m boot, pre s s and hold the Shift ke y be fore the ke rne l is
loade d. (Any othe r ke y works as we ll but the Shift ke y is the s afe s t to us e .)
Installing GRUB
If you ins tall GRUB, it may ove rwrite your e xis ting boot loade r.
By de fault, the ins tallation program ins talls GRUB in the mas te r boot re cord or MBR, of the
de vice for the root file s ys te m. To de cline ins tallation of a ne w boot loade r, uns e le ct
Install boot loader on /dev/sda.
136
Warning
If you choos e not to ins tall GRUB for any re as on, you will not be able to boot the
s ys te m dire ctly, and you mus t us e anothe r boot me thod (s uch as a comme rcial boot
loade r application). Us e this option only if you are s ure you have anothe r way of
booting the s ys te m!
If you have othe r ope rating s ys te ms alre ady ins talle d, Re d Hat Ente rpris e Linux atte mpts
to automatically de te ct and configure GRUB to boot the m. You may manually configure any
additional ope rating s ys te ms if GRUB doe s not de te ct the m.
To add, re move , or change the de te cte d ope rating s ys te m s e ttings , us e the options
provide d.
Add
Se le ct Add to include an additional ope rating s ys te m in GRUB.
Se le ct the dis k partition which contains the bootable ope rating s ys te m from the
drop-down lis t and give the e ntry a labe l. GRUB dis plays this labe l in its boot
me nu.
Edit
To change an e ntry in the GRUB boot me nu, s e le ct the e ntry and the n s e le ct
Edit.
Delete
To re move an e ntry from the GRUB boot me nu, s e le ct the e ntry and the n s e le ct
Delete.
Se le ct Default be s ide the pre fe rre d boot partition to choos e your de fault bootable OS.
You cannot move forward in the ins tallation unle s s you choos e a de fault boot image .
No te
The Label column lis ts what you mus t e nte r at the boot prompt, in non-graphical
boot loade rs , in orde r to boot the de s ire d ope rating s ys te m.
Once you have loade d the GRUB boot s cre e n, us e the arrow ke ys to choos e a boot
labe l or type e for e dit. You are pre s e nte d with a lis t of ite ms in the configuration file
for the boot labe l you have s e le cte d.
Boot loade r pas s words provide a s e curity me chanis m in an e nvironme nt whe re phys ical
acce s s to your s e rve r is available .
If you are ins talling a boot loade r, you s hould cre ate a pas s word to prote ct your s ys te m.
Without a boot loade r pas s word, us e rs with acce s s to your s ys te m can pas s options to the
ke rne l which can compromis e your s ys te m s e curity. With a boot loade r pas s word in place ,
the pas s word mus t firs t be e nte re d be fore s e le cting any non-s tandard boot options .
Howe ve r, it is s till pos s ible for s ome one with phys ical acce s s to the machine to boot from
a dis ke tte , CD-ROM, DVD, or USB me dia if the BIOS s upports it. Se curity plans which
include boot loade r pas s words s hould als o addre s s alte rnate boot me thods .
137
138
The firs t s e ctor of your boot partition This is re comme nde d if you are alre ady us ing
anothe r boot loade r on your s ys te m. In this cas e , your othe r boot loade r take s control
firs t. You can the n configure that boot loade r to s tart GRUB, which the n boots Re d Hat
Ente rpris e Linux.
No te
If you have a RAID card, be aware that s ome BIOS type s do not s upport booting from
the RAID card. In cas e s s uch as the s e , the boot loade r should not be ins talle d on the
MBR of the RAID array. Rathe r, the boot loade r s hould be ins talle d on the MBR of the
s ame drive as the /boot/ partition was cre ate d.
If your s ys te m only us e s Re d Hat Ente rpris e Linux, you s hould choos e the MBR.
Click the Change Drive Order button if you would like to re arrange the drive orde r or if
your BIOS doe s not re turn the corre ct drive orde r. Changing the drive orde r may be
us e ful if you have multiple SCSI adapte rs , or both SCSI and IDE adapte rs , and you want to
boot from the SCSI de vice .
139
No te
While partitioning your hard drive , ke e p in mind that the BIOS in s ome olde r
s ys te ms cannot acce s s more than the firs t 1024 cylinde rs on a hard drive . If this is
the cas e , le ave e nough room for the /boot Linux partition on the firs t 1024
cylinde rs of your hard drive to boot Linux. The othe r Linux partitions can be afte r
cylinde r 1024.
In parted, 1024 cylinde rs e quals 528MB. For more information, re fe r to:
http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html
Impo rtant
Re d Hat doe s not provide cus tome r s upport for third-party boot loade rs .
140
141
142
10.1. You Are Unable t o Boot Red Hat Ent erprise Linux
10.1.1. Are You Unable t o Boot Wit h Your RAID Card?
If you have pe rforme d an ins tallation and cannot boot your s ys te m prope rly, you may
ne e d to re ins tall and cre ate your partitions diffe re ntly.
Some BIOS type s do not s upport booting from RAID cards . At the e nd of an ins tallation, a
te xt-bas e d s cre e n s howing the boot loade r prompt (for e xample , GRUB: ) and a flas hing
curs or may be all that appe ars . If this is the cas e , you mus t re partition your s ys te m.
Whe the r you choos e automatic or manual partitioning, you mus t ins tall your /boot partition
outs ide of the RAID array, s uch as on a s e parate hard drive . An inte rnal hard drive is
ne ce s s ary to us e for partition cre ation with proble matic RAID cards .
You mus t als o ins tall your pre fe rre d boot loade r (GRUB or LILO) on the MBR of a drive that
is outs ide of the RAID array. This s hould be the s ame drive that hos ts the /boot/
partition.
Once the s e change s have be e n made , you s hould be able to finis h your ins tallation and
boot the s ys te m prope rly.
143
144
No te
The e arlyprintk options for BIOS and UEFI s hould als o be e nable d in the ke rne l's
/boot/config-version file - the CONFIG_EARLY_PRINTK= and
CONFIG_EARLY_PRINTK_EFI= options mus t be s e t to the y value . The y are e nable d
by de fault, but if you dis able d the m, you may ne e d to mount the /boot partition in
re s cue mode and e dit the configuration file to re -e nable the m.
No te
To dis able frame buffe r s upport and allow the ins tallation program to run in te xt
mode , try us ing the nofb boot option. This command may be ne ce s s ary for
acce s s ibility with s ome s cre e n re ading hardware .
145
146
147
148
149
Figure 10 .6. Ent er Red Hat Net wo rk aut hent icat io n det ails
Repo rt uplo ader
Spe cify a URL for uploading a compre s s e d ve rs ion of the cras h re port.
150
151
You can now cus tomiz e the re port by che cking and unche cking the is s ue s that will be
include d. Whe n finis he d, click Apply.
152
Re porting is now comple te . Click Forward to re turn to the re port s e le ction dialog. You can
now make anothe r re port, or click Close to e xit the re porting utility and the n Exit to clos e
the ins tallation proce s s .
153
No te
Whe n de fining a partition's type as s wap, do not as s ign it a mount point. Anaco nda
automatically as s igns the mount point for you.
154
Ope n a s he ll prompt. If you are in your us e r account, be come root by typing the su
command.
Now, type the following to e dit the file with gedit .
gedit /etc/inittab
The file /etc/inittab ope ns . Within the firs t s cre e n, a s e ction of the file which looks like
the following appe ars :
# Default runlevel. The runlevels used are:
#
0 - halt (Do NOT set initdefault to this)
#
1 - Single user mode
#
2 - Multiuser, without NFS (The same as 3, if you do not have
networking)
#
3 - Full multiuser mode
#
4 - unused
#
5 - X11
#
6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:
To change from a cons ole to a graphical login, you s hould change the numbe r in the line
id:3:initdefault: from a 3 to a 5.
Warning
Change only the numbe r of the de fault runle ve l from 3 to 5.
Your change d line s hould look like the following:
id:5:initdefault:
Whe n you are s atis fie d with your change , s ave and e xit the file us ing the Ctrl+Q ke ys . A
window appe ars and as ks if you would like to s ave the change s . Click Save.
The ne xt time you log in afte r re booting your s ys te m, you are pre s e nte d with a graphical
login prompt.
155
156
Ve rify that the dis playe d quantity is the s ame as the known amount of RAM in your
s ys te m. If the y are not e qual, add the following line to the /boot/grub/grub.conf:
mem=xxM
Re place xx with the amount of RAM you have in me gabyte s .
In /boot/grub/grub.conf, the above e xample would look s imilar to the following:
# NOTICE: You have a /boot partition. This means that
# all kernel paths are relative to /boot/
default=0
timeout=30
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux Client (2.6.32.130.el6.i686)
root (hd0,1)
kernel /vmlinuz-(2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5ab207-002689545705 mem=1024M
initrd /initrd-(2.6.32.130.el6.i686.img
Once you re boot, the change s made to grub.conf are re fle cte d on your s ys te m.
Once you have loade d the GRUB boot s cre e n, type e for e dit. You are pre s e nte d with a lis t
of ite ms in the configuration file for the boot labe l you have s e le cte d.
Choos e the line that s tarts with kernel and type e to e dit this boot e ntry.
At the e nd of the kernel line , add
mem=xxM
whe re xx e quals the amount of RAM in your s ys te m.
Pre s s Enter to e xit e dit mode .
Once the boot loade r s cre e n has re turne d, type b to boot the s ys te m.
Re me mbe r to re place xx with the amount of RAM in your s ys te m. Pre s s Enter to boot.
localhost.localdomain
localhost
157
P art II. IBM Power Syst ems Inst allat ion and Boot ing
This part of the Red Hat Enterprise Linux Installation Guide include s information about
ins tallation and bas ic pos t-ins tallation trouble s hooting for IBM Powe r Sys te ms s e rve rs . IBM
Powe r Sys te ms s e rve rs include IBM Powe rLinux s e rve rs and POWER7 and POWER6
Powe r Sys te ms s e rve rs running Linux.
For advance d ins tallation options , re fe r to Part IV, Advance d Ins tallation Options .
158
159
Powe rLinux s e rvice and productivity tools is an optional s e t of tools that include hardware
s e rvice diagnos tic aids , productivity tools , and ins tallation aids for Linux ope rating s ys te ms
on IBM s e rve rs bas e d on POWER7, POWER6, POWER5, and POWER4 te chnology.
Docume ntation for the s e rvice and productivity tools is available in the Linux Information
Ce nte r at http://pic.dhe .ibm.com/infoce nte r/lnxinfo/v3r0m0/inde x.js p?
topic=%2Fliaau%2Fliaauras kickoff.htm
IBM Powe r Sys te ms s e rve rs offe r many options for partitioning, virtual or native de vice s ,
and cons ole s .
If you are us ing a non-partitione d s ys te m, you do not ne e d any pre -ins tallation s e tup. For
s ys te ms us ing the HVSI s e rial cons ole , hook up your cons ole to the T2 s e rial port.
If us ing a partitione d s ys te m the s te ps to cre ate the partition and s tart the ins tallation are
large ly the s ame . You s hould cre ate the partition at the HMC and as s ign s ome CPU and
me mory re s ource s , as we ll as SCSI and Ethe rne t re s ource s , which can be e ithe r virtual or
native . The HMC cre ate partition wiz ard s te ps you through the cre ation.
For more information on cre ating the partition, re fe r to the Partitioning for Linux with an
HMC PDF in the IBM Sys te ms Hardware Information Ce nte r at:
http://pic.dhe .ibm.com/infoce nte r/powe rs ys /v3r1m5/topic/iphbi_p5/iphbibook.pdf
If you are us ing virtual SCSI re s ource s , rathe r than native SCSI, you mus t configure a 'link'
to the virtual SCSI s e rving partition, and the n configure the virtual SCSI s e rving partition
its e lf. You cre ate a 'link' be twe e n the virtual SCSI clie nt and s e rve r s lots us ing the HMC.
You can configure a virtual SCSI s e rve r on e ithe r Virtual I/O Se rve r (VIOS) or IBM i,
de pe nding on which mode l and options you have .
If you are ins talling us ing Inte l iSCSI Re mote Boot, all attache d iSCSI s torage de vice s mus t
be dis able d. Othe rwis e , the ins tallation will s ucce e d but the ins talle d s ys te m will not boot.
For more information on us ing virtual de vice s , s e e the IBM Re dbooks publication
Virtualizing an Infrastructure with System p and Linux at: http://publibb.boulde r.ibm.com/abs tracts /s g247499.html
Once you have your s ys te m configure d, you ne e d to Activate from the HMC or powe r it on.
De pe nding on what type of ins tall you are doing, you may ne e d to configure SMS to
corre ctly boot the s ys te m into the ins tallation program.
160
Po st-installatio n Usage
You can conne ct and configure e xte rnal Fire Wire and USB hard dis ks afte r
ins tallation. Mos t s uch de vice s are automatically re cogniz e d and available for us e
once conne cte d.
161
to work with dis k partitions . If you have not worke d with dis k partitions be fore (or ne e d a
quick re vie w of the bas ic conce pts ), re fe r to Appe ndix A, An Introduction to Disk Partitions
be fore proce e ding.
The dis k s pace us e d by Re d Hat Ente rpris e Linux mus t be s e parate from the dis k s pace
us e d by othe r OSe s you may have ins talle d on your s ys te m.
Be fore you s tart the ins tallation proce s s , you mus t
have e nough unpartitioned [6] dis k s pace for the ins tallation of Re d Hat Ente rpris e
Linux, or
have one or more partitions that may be de le te d, the re by fre e ing up e nough dis k
s pace to ins tall Re d Hat Ente rpris e Linux.
To gain a be tte r s e ns e of how much s pace you re ally ne e d, re fe r to the re comme nde d
partitioning s iz e s dis cus s e d in Se ction 16.17.5, Re comme nde d Partitioning Sche me .
[5] P arts of this section were previously published at IBM's Linux information for IBM systems
resource at http://pic.dhe.ibm .com /infocenter/lnxinfo/v3r0m 0/index.jsp?
topic=% 2Fliaay% 2Ftools_overview.htm
[6] Unpartitioned disk space m eans that available disk space on the hard drives you are
installing to has not been divided into sections for data. When you partition a disk, each
partition behaves like a separate disk drive.
162
No te
Make s ure no ins tallation DVD (or any othe r type of DVD or CD) is in your s ys te m's
CD or DVD drive if you are pe rforming a ne twork-bas e d ins tallation. Having a DVD or
CD in the drive might caus e une xpe cte d e rrors .
Ens ure that you have boot me dia available on CD, DVD, or a USB s torage de vice s uch as
a flas h drive .
The Re d Hat Ente rpris e Linux ins tallation me dium mus t be available for e ithe r a ne twork
ins tallation (via NFS, FTP, HTTP, or HTTPS) or ins tallation via local s torage . Us e the following
s te ps if you are pe rforming an NFS, FTP, HTTP, or HTTPS ins tallation.
The NFS, FTP, HTTP, or HTTPS s e rve r to be us e d for ins tallation ove r the ne twork mus t be
a s e parate , ne twork-acce s s ible s e rve r. It mus t provide the comple te conte nts of the
ins tallation DVD-ROM.
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . Re d Hat re comme nds
that you te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and
be fore re porting any ins tallation-re late d bugs (many of the bugs re porte d are
actually due to imprope rly-burne d DVDs ). To us e this te s t, type the following
command at the yaboot: prompt:
linux mediacheck
163
No te
The public dire ctory us e d to acce s s the ins tallation file s ove r FTP, NFS, HTTP, or
HTTPS is mappe d to local s torage on the ne twork s e rve r. For e xample , the local
dire ctory /var/www/inst/rhel6.6 on the ne twork s e rve r can be acce s s e d as
http://network.server.com/inst/rhel6.6.
In the following e xample s , the dire ctory on the ins tallation s taging s e rve r that will
contain the ins tallation file s will be s pe cifie d as /location/of/disk/space. The
dire ctory that will be made publicly available via FTP, NFS, HTTP, or HTTPS will be
s pe cifie d as /publicly_available_directory. For e xample , /location/of/disk/space
may be a dire ctory you cre ate calle d /var/isos. /publicly_available_directory
might be /var/www/html/rhel6.6, for an HTTP ins tall.
In the following, you will re quire an ISO image. An ISO image is a file containing an e xact
copy of the conte nt of a DVD. To cre ate an ISO image from a DVD us e the following
command:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the re s ulting
ISO image file , and path_to_image is the path to the location on your s ys te m whe re the
re s ulting ISO image will be s tore d.
To copy the file s from the ins tallation DVD to a Linux ins tance , which acts as an ins tallation
s taging s e rve r, continue with e ithe r Se ction 12.1.1, Pre paring for FTP, HTTP, and HTTPS
Ins tallation or Se ction 12.1.2, Pre paring for an NFS Ins tallation.
Warning
If your Apache we b s e rve r or t f t p FTP s e rve r configuration e nable s SSL s e curity,
make s ure to only e nable the TLSv1 protocol, and dis able SSLv2 and SSLv3. This is
due to the POODLE SSL vulne rability (CVE-2014-3566). Se e
https ://acce s s .re dhat.com/s olutions /1232413 for de tails about s e curing Apache, and
https ://acce s s .re dhat.com/s olutions /1234773 for information about s e curing t f t p.
Extract the file s from the ISO image of the ins tallation DVD and place the m in a dire ctory
that is s hare d ove r FTP, HTTP, or HTTPS.
Ne xt, make s ure that the dire ctory is s hare d via FTP, HTTP, or HTTPS, and ve rify clie nt
acce s s . Te s t to s e e whe the r the dire ctory is acce s s ible from the s e rve r its e lf, and the n
from anothe r machine on the s ame s ubne t to which you will be ins talling.
164
1. Trans fe r the ISO image to the NFS e xporte d dire ctory. On a Linux s ys te m, run:
mv /path_to_image/name_of_image.iso /publicly_available_directory/
whe re path_to_image is the path to the ISO image file , name_of_image is the name
of the ISO image file , and publicly_available_directory is a dire ctory that is available
ove r NFS or that you inte nd to make available ove r NFS.
2. Us e a SHA256 che cks um program to ve rify that the ISO image that you copie d is
intact. Many SHA256 che cks um programs are available for various ope rating
s ys te ms . On a Linux s ys te m, run:
$ sha256sum name_of_image.iso
whe re name_of_image is the name of the ISO image file . The SHA256 che cks um
program dis plays a s tring of 64 characte rs calle d a hash. Compare this has h to the
has h dis playe d for this particular image on the Downloads page in the Re d Hat
Cus tome r Portal (re fe r to Chapte r 1, Obtaining Red Hat Enterprise Linux). The two
has he s s hould be ide ntical.
3. Copy the images/ dire ctory from ins ide the ISO image to the s ame dire ctory in
which you s tore d the ISO image file its e lf. Ente r the following commands :
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/images /publicly_available_directory/
umount /mount_point
whe re path_to_image is the path to the ISO image file , name_of_image is the
name of the ISO image file , and mount_point is a mount point on which to mount
the image while you copy file s from the image . For e xample :
mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,ro
cp -pr /mnt/tmp/images /var/isos/
umount /mnt/tmp
The ISO image file and an images/ dire ctory are now pre s e nt, s ide -by-s ide , in the
s ame dire ctory.
4. Ve rify that the images/ dire ctory contains at le as t the install.img file , without
which ins tallation cannot proce e d. Optionally, the images/ dire ctory s hould contain
the product.img file , without which only the package s for a Minimal ins tallation will
be available during the package group s e le ction s tage (re fe r to Se ction 16.19,
Package Group Se le ction).
images/
directo ry
165
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
166
Us e this option to ins tall Re d Hat Ente rpris e Linux on s ys te ms without a DVD drive or
ne twork conne ction.
Hard drive ins tallations us e the following file s :
an ISO image of the ins tallation DVD. An ISO image is a file that contains an e xact copy
of the conte nt of a DVD.
an install.img file e xtracte d from the ISO image .
optionally, a product.img file e xtracte d from the ISO image .
With the s e file s pre s e nt on a hard drive , you can choos e Hard drive as the ins tallation
s ource whe n you boot the ins tallation program (re fe r to Se ction 15.3, Ins tallation Me thod).
Ens ure that you have boot me dia available on CD, DVD, or a USB s torage de vice s uch as
a flas h drive .
To pre pare a hard drive as an ins tallation s ource , follow the s e s te ps :
1. Obtain an ISO image of the Re d Hat Ente rpris e Linux ins tallation DVD (re fe r to
Chapte r 1, Obtaining Red Hat Enterprise Linux). Alte rnative ly, if you have the DVD on
phys ical me dia, you can cre ate an image of it with the following command on a
Linux s ys te m:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the
re s ulting ISO image file , and path_to_image is the path to the location on your
s ys te m whe re the re s ulting ISO image will be s tore d.
2. Trans fe r the ISO image to the hard drive .
The ISO image mus t be locate d on a hard drive that is e ithe r inte rnal to the
compute r on which you will ins tall Re d Hat Ente rpris e Linux, or on a hard drive that
is attache d to that compute r by USB.
3. Us e a SHA256 che cks um program to ve rify that the ISO image that you copie d is
intact. Many SHA256 che cks um programs are available for various ope rating
s ys te ms . On a Linux s ys te m, run:
$ sha256sum name_of_image.iso
whe re name_of_image is the name of the ISO image file . The SHA256 che cks um
program dis plays a s tring of 64 characte rs calle d a hash. Compare this has h to the
has h dis playe d for this particular image on the Downloads page in the Re d Hat
Cus tome r Portal (re fe r to Chapte r 1, Obtaining Red Hat Enterprise Linux). The two
has he s s hould be ide ntical.
4. Copy the images/ dire ctory from ins ide the ISO image to the s ame dire ctory in
which you s tore d the ISO image file its e lf. Ente r the following commands :
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/images /publicly_available_directory/
umount /mount_point
whe re path_to_image is the path to the ISO image file , name_of_image is the
167
name of the ISO image file , and mount_point is a mount point on which to mount
the image while you copy file s from the image . For e xample :
mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,ro
cp -pr /mnt/tmp/images /var/isos/
umount /mnt/tmp
The ISO image file and an images/ dire ctory are now pre s e nt, s ide -by-s ide , in the
s ame dire ctory.
5. Ve rify that the images/ dire ctory contains at le as t the install.img file , without
which ins tallation cannot proce e d. Optionally, the images/ dire ctory s hould contain
the product.img file , without which only the package s for a Minimal ins tallation will
be available during the package group s e le ction s tage (re fe r to Se ction 9.17,
Package Group Se le ction).
images/
directo ry
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
168
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
169
pe rforming an initial RAM dis k drive r update re fe r to Se ction 13.2.3, Pre paring
an Initial RAM Dis k Update .
Devices wit h an equivalent device available
Be caus e all de vice s of the s ame type are initializ e d toge the r, you cannot update
drive rs for a de vice if the ins tallation program has loade d drive rs for a s imilar
de vice . For e xample , cons ide r a s ys te m that has two diffe re nt ne twork adapte rs ,
one of which has a drive r update available . The ins tallation program will initializ e
both adapte rs at the s ame time , and the re fore , you will not be able to us e this
drive r update . Again, comple te the ins tallation with the drive rs loade d by the
ins tallation program and update to the ne w drive rs afte r ins tallation, or us e an
initial RAM dis k drive r update .
170
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
Figure 13.1. Co nt ent o f a USB f lash drive ho lding a driver updat e image f ile
Note that if you us e this me thod, the s torage de vice will contain only a s ingle file . This
diffe rs from drive r dis cs on formats s uch as CD and DVD, which contain many file s . The
ISO image file contains all of the file s that would normally be on a drive r dis c.
Re fe r to Se ction 13.3.2, Le t the Ins talle r Prompt You for a Drive r Update and
Se ction 13.3.3, Us e a Boot Option to Spe cify a Drive r Update Dis k to le arn how to s e le ct
the drive r update manually during ins tallation.
For automatic ins tallations , you will ne e d to e xtract the ISO to the root dire ctory of the
s torage de vice rathe r than s imply copy it. Copying the ISO is only e ffe ctive for manual
ins tallations . You mus t als o change the file s ys te m labe l of the de vice to OEMDRV.
The ins tallation program will the n automatically e xamine it for drive r update s and load any
that it de te cts . This be havior is controlle d by the dlabel=on boot option, which is e nable d
by de fault. Re fe r to Se ction 6.3.1, Le t the Ins talle r Find a Drive r Update Dis k
Automatically.
171
1. Us e the de s ktop file manage r to locate the ISO image file of the drive r dis c,
s upplie d to you by Re d Hat or your hardware ve ndor.
172
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
173
If you s e e only a s ingle file e nding in .iso, the n you have not cre ate d the dis c corre ctly
and s hould try again. Ens ure that you choos e an option s imilar to burn from image if you
us e a Linux de s ktop othe r than GNOME or if you us e a diffe re nt ope rating s ys te m.
Re fe r to Se ction 13.3.2, Le t the Ins talle r Prompt You for a Drive r Update and
Se ction 13.3.3, Us e a Boot Option to Spe cify a Drive r Update Dis k to le arn how to us e the
drive r update dis c during ins tallation.
174
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
Example 13.1. Preparing an init ial RAM disk updat e f ro m a driver updat e
image f ile
In this e xample , driver_update.iso is a drive r update image file that you downloade d
from the Inte rne t to a dire ctory on your ins tallation s e rve r. The targe t on your
ins tallation s e rve r that you want to boot from is locate d in
/var/lib/tftpboot/yaboot/rhel6/
At the command line , change to the dire ctory that holds the file and e nte r the following
commands :
$ cp driver_update.iso /tmp/initrd_update/dd.img
$ cd /tmp/initrd_update
$ find . | cpio --quiet -c -o -H newc | gzip -9
>/tmp/initrd_update.img
$ cp /tmp/initrd_update.img /tftpboot/yaboot/rhel6/dd.img
Edit the /var/lib/tftpboot/yaboot/yaboot.conf file and include the following e ntry:
image=rhel6/vmlinuz
label=rhel6-dd
initrd=rhel6/initrd.img,rhel6/dd.img
13.3.1. Let t he Inst aller Find a Driver Updat e Disk Aut omat ically
Attach a block de vice with the file s ys te m labe l OEMDRV be fore s tarting the ins tallation
proce s s . The ins talle r will automatically e xamine the de vice and load any drive r update s
that it de te cts and will not prompt you during the proce s s . Re fe r to Se ction 13.2.1.1,
Pre paring to us e an image file on local s torage to pre pare a s torage de vice for the
ins talle r to find.
175
176
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
If the ins talle r finds more than one location that could hold a drive r update , it
prompts you to s pe cify the location of the update . Se e Se ction 13.4, Spe cifying the
Location of a Drive r Update Image File or a Drive r Update Dis k.
13.3.4. Select an Inst allat ion Server T arget T hat Includes a Driver
Updat e
1. Configure the compute r to boot from the ne twork inte rface by s e le cting Select
Boot Options in the SMS me nu, the n Select Boot/Install Device. Finally,
s e le ct your ne twork de vice from the lis t of available de vice s .
2. In the yabo o t ins tallation s e rve r e nvironme nt, choos e the boot targe t that you
pre pare d on your ins tallation s e rve r. For e xample , if you labe le d this e nvironme nt
rhel6-dd in the /var/lib/tftpboot/yaboot/yaboot.conf file on your ins tallation
s e rve r, type rhel6-dd at the prompt and pre s s Enter.
Re fe r to Se ction 13.2.3, Pre paring an Initial RAM Dis k Update and Chapte r 30, Setting Up
an Installation Server for ins tructions on us ing a yabo o t ins tallation s e rve r to pe rform an
update during ins tallation. Note that this is an advance d proce dure do not atte mpt it
unle s s othe r me thods of pe rforming a drive r update fail.
177
If the de vice that you choos e contains no s uitable update me dia, the ins talle r will prompt
you to make anothe r choice .
If you made a drive r update dis k on CD, DVD, or USB flas h drive , the ins talle r now loads
the drive r update . Howe ve r, if the de vice that you s e le cte d is a type of de vice that could
contain more than one partition (whe the r the de vice curre ntly has more than one partition
or not), the ins talle r might prompt you to s e le ct the partition that holds the drive r update .
178
C hapt e r 13. Updat ing Dr ive r s Dur ing Ins t allat io n o n IBM Po we r Sys t e ms Se r ve r s
179
To boot an IBM Powe r Sys te ms s e rve r from a DVD, you mus t s pe cify the ins tall boot
de vice in the System Management Services (SMS) me nu.
To e nte r the System Management Services GUI, pre s s the 1 ke y during the boot proce s s
whe n you he ar the chime s ound. This brings up a graphical inte rface s imilar to the one
de s cribe d in this s e ction.
On a te xt cons ole , pre s s 1 whe n the s e lf te s t is dis playing the banne r along with the
te s te d compone nts :
180
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
181
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
/
Elapsed time since release of system processors: 276 mins 49 secs
System has 128 Mbytes in RMA
Config file read, 227 bytes
Re fe r to Se ction 3.7, Se le cting an Ins tallation Me thod for information about ins talling from
locations othe r than the me dia with which you boote d the s ys te m.
182
14.3. Boot ing from t he Net work Using a yaboot Inst allat ion
Server
To boot with a yabo o t ins tallation s e rve r, you ne e d a prope rly configure d s e rve r, and a
ne twork inte rface in your compute r that can s upport an ins tallation s e rve r. For information
on how to configure an ins tallation s e rve r, re fe r to Chapte r 30, Setting Up an Installation
Server.
Configure the compute r to boot from the ne twork inte rface by s e le cting Select Boot
Options in the SMS me nu, the n Select Boot/Install Device. Finally, s e le ct your
ne twork de vice from the lis t of available de vice s .
Once you prope rly configure booting from an ins tallation s e rve r, the compute r can boot
the Re d Hat Ente rpris e Linux ins tallation s ys te m without any othe r me dia.
To boot a compute r from a yabo o t ins tallation s e rve r:
1. Ens ure that the ne twork cable is attache d. The link indicator light on the ne twork
s ocke t s hould be lit, e ve n if the compute r is not s witche d on.
2. Switch on the compute r.
3. A me nu s cre e n appe ars . Pre s s the numbe r ke y that corre s ponds to the de s ire d
option.
If your PC doe s not boot from the ne twork ins tallation s e rve r, e ns ure that the SMS is
configure d to boot firs t from the corre ct ne twork inte rface . Re fe r to your hardware
docume ntation for more information.
183
15.1. T he T ext Mode Inst allat ion Program User Int erface
Impo rtant Graphical installatio n reco mmended
We re comme nd that you ins tall Re d Hat Ente rpris e Linux us ing the graphical
inte rface . If you are ins talling Re d Hat Ente rpris e Linux on a s ys te m that lacks a
graphical dis play, cons ide r pe rforming the ins tallation ove r a VNC conne ction s e e
Chapte r 31, Installing Through VNC. If anaco nda de te cts that you are ins talling in
te xt mode on a s ys te m whe re ins tallation ove r a VNC conne ction might be pos s ible ,
anaco nda as ks you to ve rify your de cis ion to ins tall in te xt mode e ve n though your
options during ins tallation are limite d.
If your s ys te m has a graphical dis play, but graphical ins tallation fails , try booting with
the xdriver=vesa option re fe r to Chapte r 28, Boot Options
Both the loade r and late r anaco nda us e a s cre e n-bas e d inte rface that include s mos t of
the on-s cre e n widgets commonly found on graphical us e r inte rface s . Figure 15.1,
Ins tallation Program Widge ts as s e e n in URL Setup, and Figure 15.2, Ins tallation
Program Widge ts as s e e n in Choose a Language, illus trate widge ts that appe ar on
s cre e ns during the ins tallation proce s s .
Figure 15.1. Inst allat io n Pro gram Widget s as seen in URL Setup
184
Figure 15.2. Inst allat io n Pro gram Widget s as seen in Choose a Language
The widge ts include :
Window Windows (us ually re fe rre d to as dialogs in this manual) appe ar on your
s cre e n throughout the ins tallation proce s s . At time s , one window may ove rlay anothe r;
in the s e cas e s , you can only inte ract with the window on top. Whe n you are finis he d in
that window, it dis appe ars , allowing you to continue working in the window unde rne ath.
Che ckbox Che ckboxe s allow you to s e le ct or de s e le ct a fe ature . The box dis plays
e ithe r an as te ris k (s e le cte d) or a s pace (uns e le cte d). Whe n the curs or is within a
che ckbox, pre s s Space to s e le ct or de s e le ct a fe ature .
Te xt Input Te xt input line s are re gions whe re you can e nte r information re quire d by
the ins tallation program. Whe n the curs or re s ts on a te xt input line , you may e nte r
and/or e dit information on that line .
Te xt Widge t Te xt widge ts are re gions of the s cre e n for the dis play of te xt. At time s ,
te xt widge ts may als o contain othe r widge ts , s uch as che ckboxe s . If a te xt widge t
contains more information than can be dis playe d in the s pace re s e rve d for it, a s croll
bar appe ars ; if you pos ition the curs or within the te xt widge t, you can the n us e the Up
and Down arrow ke ys to s croll through all the information available . Your curre nt pos ition
is s hown on the s croll bar by a # characte r, which move s up and down the s croll bar as
you s croll.
Scroll Bar Scroll bars appe ar on the s ide or bottom of a window to control which part
of a lis t or docume nt is curre ntly in the window's frame . The s croll bar make s it e as y to
move to any part of a file .
Button Widge t Button widge ts are the primary me thod of inte racting with the
ins tallation program. You progre s s through the windows of the ins tallation program by
navigating the s e buttons , us ing the Tab and Enter ke ys . Buttons can be s e le cte d whe n
the y are highlighte d.
185
Curs or Although not a widge t, the curs or is us e d to s e le ct (and inte ract with) a
particular widge t. As the curs or is move d from widge t to widge t, it may caus e the
widge t to change color, or the curs or its e lf may only appe ar pos itione d in or ne xt to the
widge t. In Figure 15.1, Ins tallation Program Widge ts as s e e n in URL Setup, the curs or
is pos itione d on the Enable HTTP proxy che ckbox. Figure 8.2, Ins tallation Program
Widge ts as s e e n in Choose a Language, s hows the curs or on the OK button.
Warning
Unle s s a dialog box is waiting for your input, do not pre s s any ke ys during the
ins tallation proce s s (doing s o may re s ult in unpre dictable be havior).
186
187
Figure 15.5. Select ing Part it io n Dialo g f o r Hard Drive Inst allat io n
188
Se le ct the partition containing the ISO file s from the lis t of available partitions . Inte rnal IDE,
SATA, SCSI, and USB drive de vice name s be gin with /dev/sd. Each individual drive has its
own le tte r, for e xample /dev/sda. Each partition on a drive is numbe re d, for e xample
/dev/sda1.
Als o s pe cify the Directory holding images. Ente r the full dire ctory path from the drive
that contains the ISO image file s . The following table s hows s ome e xample s of how to
e nte r this information:
T able 15.1. Lo cat io n o f ISO images f o r dif f erent part it io n t ypes
Part it io n t ype
Vo lume
Original pat h t o
f iles
Direct o ry t o use
VFAT
D:\
/home
If the ISO image s are in the root (top-le ve l) dire ctory of a partition, e nte r a /. If the ISO
image s are locate d in a s ubdire ctory of a mounte d partition, e nte r the name of the
dire ctory holding the ISO image s within that partition. For e xample , if the partition on which
the ISO image s is normally mounte d as /home/, and the image s are in /home/new/, you
would e nte r /new/.
189
190
191
By de fault, anaco nda us e s DHCP to provide ne twork s e ttings automatically for IPv4 and
automatic configuration to provide ne twork s e ttings for IPv6. If you choos e to configure
TCP/IP manually, anaco nda prompts you to provide the de tails in the Manual TCP/IP
Configuration dialog:
192
193
For e xample :
http://install:rhel6.6pw@name.example.com/mirrors/redhat/rhel6.6/Server/ppc64/
194
16.1. T he T ext Mode Inst allat ion Program User Int erface
While te xt mode ins tallations are not e xplicitly docume nte d, thos e us ing the te xt mode
ins tallation program can e as ily follow the GUI ins tallation ins tructions . Howe ve r, be caus e
te xt mode pre s e nts you with a s imple r, more s tre amline d ins tallation proce s s , ce rtain
options that are available in graphical mode are not als o available in te xt mode . The s e
diffe re nce s are note d in the de s cription of the ins tallation proce s s in this guide , and
include :
configuring advance d s torage me thods s uch as LVM, RAID, FCoE, z FCP, and iSCSI.
cus tomiz ing the partition layout
cus tomiz ing the bootloade r layout
s e le cting package s during ins tallation
configuring the ins talle d s ys te m with f irst bo o t
195
No te
If you do not wis h to us e the GUI ins tallation program, the te xt mode ins tallation
program is als o available . To s tart the te xt mode ins tallation program, us e the
following command at the yaboot: prompt:
linux text
Re fe r to Se ction 14.1, The Boot Me nu for a de s cription of the Re d Hat Ente rpris e
Linux boot me nu and to Se ction 15.1, The Te xt Mode Ins tallation Program Us e r
Inte rface for a brie f ove rvie w of te xt mode ins tallation ins tructions .
It is highly re comme nde d that ins talls be pe rforme d us ing the GUI ins tallation
program. The GUI ins tallation program offe rs the full functionality of the Re d Hat
Ente rpris e Linux ins tallation program, including LVM configuration which is not
available during a te xt mode ins tallation.
Us e rs who mus t us e the te xt mode ins tallation program can follow the GUI
ins tallation ins tructions and obtain all ne e de d information.
keyst ro kes
co nt ent s
1
2
3
ctrl+alt+f1
ctrl+alt+f2
ctrl+alt+f3
4
5
ctrl+alt+f4
ctrl+alt+f5
196
co nso le
keyst ro kes
co nt ent s
ctrl+alt+f6
197
198
No te
To change your ke yboard layout type afte r you have comple te d the ins tallation, us e
the Keybo ard Co nf igurat io n T o o l.
Type the system-config-keyboard command in a s he ll prompt to launch the
Keybo ard Co nf igurat io n T o o l. If you are not root, it prompts you for the root
pas s word to continue .
199
No te
Monitoring of LVM and s oftware RAID de vice s by the mdeventd dae mon is not
pe rforme d during ins tallation.
200
201
202
Each de vice is pre s e nte d on a s e parate row, with a che ckbox to its le ft. Click the che ckbox
to make a de vice available during the ins tallation proce s s , or click the radio button at the
le ft of the column he adings to s e le ct or de s e le ct all the de vice s lis te d in a particular
s cre e n. Late r in the ins tallation proce s s , you can choos e to ins tall Re d Hat Ente rpris e Linux
onto any of the de vice s s e le cte d he re , and can choos e to automatically mount any of the
othe r de vice s s e le cte d he re as part of the ins talle d s ys te m.
Note that the de vice s that you s e le ct he re are not automatically e ras e d by the ins tallation
proce s s . Se le cting a de vice on this s cre e n doe s not, in its e lf, place data s tore d on the
de vice at ris k. Note als o that any de vice s that you do not s e le ct he re to form part of the
ins talle d s ys te m can be adde d to the s ys te m afte r ins tallation by modifying the
/etc/fstab file .
whe n you have s e le cte d the s torage de vice s to make available during ins tallation, click
Next and proce e d to Se ction 16.13, Initializ ing the Hard Dis k
203
204
205
206
207
208
209
210
211
Valid Ho stnames
You may give your s ys te m any name provide d that the full hos tname is unique . The
hos tname may include le tte rs , numbe rs and hyphe ns .
212
Mo dem Co nfiguratio n
The ins tallation program doe s not configure mode ms . Configure the s e de vice s afte r
ins tallation with the Net wo rk utility. The s e ttings for your mode m are s pe cific to
your particular Inte rne t Se rvice Provide r (ISP).
213
No te
To change your ne twork configuration afte r you have comple te d the ins tallation, us e
the Net wo rk Administ rat io n T o o l.
Type the system-config-network command in a s he ll prompt to launch the
Net wo rk Administ rat io n T o o l. If you are not root, it prompts you for the root
pas s word to continue .
The Net wo rk Administ rat io n T o o l is now de pre cate d and will be re place d by
Net wo rkManager during the life time of Re d Hat Ente rpris e Linux 6.
To configure a ne twork conne ction manually, click the button Configure Network. The
Network Connections dialog appe ars that allows you to configure wire d, wire le s s , mobile
broadband, InfiniBand, VPN, DSL, VLAN, and bonde d conne ctions for the s ys te m us ing the
Net wo rkManager tool. A full de s cription of all configurations pos s ible with
Net wo rkManager is be yond the s cope of this guide . This s e ction only de tails the mos t
typical s ce nario of how to configure wire d conne ctions during ins tallation. Configuration of
othe r type s of ne twork is broadly s imilar, although the s pe cific parame te rs that you mus t
configure are ne ce s s arily diffe re nt.
214
de s cribe d be low. To re move a conne ction, s e le ct it in the lis t and click Delete.
Whe n you have finis he d e diting ne twork s e ttings , click Apply to s ave the ne w
configuration. If you re configure d a de vice that was alre ady active during ins tallation, you
mus t re s tart the de vice to us e the ne w configuration re fe r to Se ction 9.7.1.6, Re s tart a
ne twork de vice .
16.9.1.2. T he Wired t ab
Us e the Wired tab to s pe cify or change the media access control (MAC) addre s s for the
ne twork adapte r, and e ithe r s e t the maximum transmission unit (MTU, in byte s ) that can
pas s through the inte rface .
215
216
217
218
The IPv4 addre s s , ne tmas k, and gate way addre s s are configure d by the DHCP
s e rvice on the ne twork, but DNS s e rve rs and s e arch domains mus t be configure d
manually.
Manual
IPv4 parame te rs are configure d manually for a s tatic configuration.
Link-Local Only
A link-local addre s s in the 169.254/16 range is as s igne d to the inte rface .
Shared to other computers
The s ys te m is configure d to provide ne twork acce s s to othe r compute rs . The
inte rface is as s igne d an addre s s in the 10.42.x.1/24 range , a DHCP s e rve r and
DNS s e rve r are s tarte d, and the inte rface is conne cte d to the de fault ne twork
conne ction on the s ys te m with network address translation (NAT).
Disabled
IPv4 is dis able d for this conne ction.
If you s e le cte d a me thod that re quire s you to s upply manual parame te rs , e nte r de tails of
the IP addre s s for this inte rface , the ne tmas k, and the gate way in the Addresses fie ld.
Us e the Add and Delete buttons to add or re move addre s s e s . Ente r a comma-s e parate d
lis t of DNS s e rve rs in the DNS servers fie ld, and a comma-s e parate d lis t of domains in
the Search domains fie ld for any domains that you want to include in name s e rve r
lookups .
Optionally, e nte r a name for this ne twork conne ction in the DHCP client ID fie ld. This
name mus t be unique on the s ubne t. Whe n you as s ign a me aningful DHCP clie nt ID to a
conne ction, it is e as y to ide ntify this conne ction whe n trouble s hooting ne twork proble ms .
De s e le ct the Require IPv4 addressing for this connection to complete che ck box
to allow the s ys te m to make this conne ction on an IPv6-e nable d ne twork if IPv4
configuration fails but IPv6 configuration s ucce e ds .
219
220
221
Net wo rkManager doe s not us e RA, but re que s ts information from DHCPv6
dire ctly to cre ate a s tate ful configuration.
Manual
IPv6 parame te rs are configure d manually for a s tatic configuration.
Link-Local Only
A link-local addre s s with the fe 80::/10 pre fix is as s igne d to the inte rface .
If you s e le cte d a me thod that re quire s you to s upply manual parame te rs , e nte r de tails of
the IP addre s s for this inte rface , the ne tmas k, and the gate way in the Addresses fie ld.
Us e the Add and Delete buttons to add or re move addre s s e s . Ente r a comma-s e parate d
lis t of DNS s e rve rs in the DNS servers fie ld, and a comma-s e parate d lis t of domains in
the Search domains fie ld for any domains that you want to include in name s e rve r
lookups .
Optionally, e nte r a name for this ne twork conne ction in the DHCP client ID fie ld. This
name mus t be unique on the s ubne t. Whe n you as s ign a me aningful DHCP clie nt ID to a
conne ction, it is e as y to ide ntify this conne ction whe n trouble s hooting ne twork proble ms .
De s e le ct the Require IPv6 addressing for this connection to complete che ck box
to allow the s ys te m to make this conne ction on an IPv4-e nable d ne twork if IPv6
configuration fails but IPv4 configuration s ucce e ds .
222
223
224
4. Ve rify that the inte rface configuration file contains the line ONBOOT=yes. If the file
doe s not alre ady contain the line , add it now and s ave the file .
5. Exit the vi e ditor.
6. Move the inte rface configuration file back to the /etc/sysconfig/networkscripts/ dire ctory:
mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/
The de vice is now re conne cte d in anaco nda.
7. Pre s s Ctrl+Alt+F6 to re turn to anaco nda.
225
No te
To change your time z one configuration afte r you have comple te d the ins tallation,
us e the T ime and Dat e Pro pert ies T o o l.
Type the system-config-date command in a s he ll prompt to launch the T ime and
Dat e Pro pert ies T o o l. If you are not root, it prompts you for the root pas s word to
continue .
No te
The root us e r (als o known as the s upe rus e r) has comple te acce s s to the e ntire
s ys te m; for this re as on, logging in as the root us e r is be s t done only to pe rform
s ys te m mainte nance or adminis tration.
226
Us e the root account only for s ys te m adminis tration. Cre ate a non-root account for your
ge ne ral us e and us e the su command to change to root only whe n you ne e d to pe rform
tas ks that re quire s upe rus e r authoriz ation. The s e bas ic rule s minimiz e the chance s of a
typo or an incorre ct command doing damage to your s ys te m.
No te
To be come root, type su - at the s he ll prompt in a te rminal window and the n pre s s
Enter. The n, e nte r the root pas s word and pre s s Enter.
The ins tallation program prompts you to s e t a root pas s word [7] for your s ys te m. . You
cannot proceed to the next stage of the installation process without entering a root
password.
The root pas s word mus t be at le as t s ix characte rs long; the pas s word you type is not
e choe d to the s cre e n. You mus t e nte r the pas s word twice ; if the two pas s words do not
match, the ins tallation program as ks you to e nte r the m again.
You s hould make the root pas s word s ome thing you can re me mbe r, but not s ome thing that
is e as y for s ome one e ls e to gue s s . Your name , your phone numbe r, qwerty, password,
root, 123456, and anteater are all e xample s of bad pas s words . Good pas s words mix
nume rals with uppe r and lowe r cas e le tte rs and do not contain dictionary words :
Aard387vark or 420BMttNT, for e xample . Re me mbe r that the pas s word is cas e -s e ns itive . If
you write down your pas s word, ke e p it in a s e cure place . Howe ve r, it is re comme nde d
that you do not write down this or any pas s word you cre ate .
Cho o se yo ur o wn passwo rd
Do not us e one of the e xample pas s words offe re d in this manual. Us ing one of
the s e pas s words could be cons ide re d a s e curity ris k.
To change your root pas s word afte r you have comple te d the ins tallation, run the passwd
command as root. If you forge t the root pas s word, s e e Re s olving Proble ms in Sys te m
Re cove ry Mode s in the Re d Hat Ente rpris e Linux 6 De ployme nt Guide for ins tructions on
how to s e t a ne w one .
227
228
Whe n you have finis he d ide ntifying de vice s to be us e d for ins tallation, click Next to
continue .
229
The ins tallation s ys te m automatically de te cts any e xis ting ins tallation of Re d Hat
Ente rpris e Linux. The upgrade proce s s update s the e xis ting s ys te m s oftware with ne w
ve rs ions , but doe s not re move any data from us e rs ' home dire ctorie s . The e xis ting
partition s tructure on your hard drive s doe s not change . Your s ys te m configuration
change s only if a package upgrade de mands it. Mos t package upgrade s do not change
s ys te m configuration, but rathe r ins tall an additional configuration file for you to e xamine
late r.
Note that the ins tallation me dium that you are us ing might not contain all the s oftware
package s that you ne e d to upgrade your compute r.
230
231
232
Partitioning allows you to divide your hard drive into is olate d s e ctions , whe re e ach s e ction
be have s as its own hard drive . Partitioning is particularly us e ful if you run multiple
ope rating s ys te ms . If you are not s ure how you want your s ys te m to be partitione d, re ad
Appe ndix A, An Introduction to Disk Partitions for more information.
233
Se le ct this option to re move all partitions on your hard drive s (this include s
partitions cre ate d by othe r ope rating s ys te ms s uch as Windows VFAT or NTFS
partitions ).
Warning
If you s e le ct this option, all data on the s e le cte d hard drive s is re move d by
the ins tallation program. Do not s e le ct this option if you have information
that you want to ke e p on the hard drive s whe re you are ins talling Re d Hat
Ente rpris e Linux.
In particular, do not s e le ct this option whe n you configure a s ys te m to chain
load the Re d Hat Ente rpris e Linux boot loade r from anothe r boot loade r.
Warning
If you s hrink partitions on which othe r ope rating s ys te ms are ins talle d, you
might not be able to us e thos e ope rating s ys te ms . Although this partitioning
option doe s not de s troy data, ope rating s ys te ms typically re quire s ome
fre e s pace in the ir partitions . Be fore you re s iz e a partition that holds an
ope rating s ys te m that you might want to us e again, find out how much
s pace you ne e d to le ave fre e .
Use Free Space
Se le ct this option to re tain your curre nt data and partitions and ins tall Re d Hat
Ente rpris e Linux in the unus e d s pace available on the s torage drive s . Ens ure that
the re is s ufficie nt s pace available on the s torage drive s be fore you s e le ct this
option re fe r to Se ction 11.6, Do You Have Enough Dis k Space ?.
Creat e Cust o m Layo ut
Se le ct this option to partition s torage de vice s manually and cre ate cus tomiz e d
layouts . Re fe r to Se ction 16.17, Cre ating a Cus tom Layout or Modifying the
De fault Layout
Choos e your pre fe rre d partitioning me thod by clicking the radio button to the le ft of its
de s cription in the dialog box.
Se le ct Encrypt system to e ncrypt all partitions e xce pt the /boot partition. Re fe r to
Appe ndix C, Disk Encryption for information on e ncryption.
234
To re vie w and make any ne ce s s ary change s to the partitions cre ate d by automatic
partitioning, s e le ct the Review option. Afte r s e le cting Review and clicking Next to move
forward, the partitions cre ate d for you by anaco nda appe ar. You can make modifications
to the s e partitions if the y do not me e t your ne e ds .
235
Do no t place
/usr
or
/var
If /usr or /var is partitione d s e parate ly from the re s t of the root volume , the boot
proce s s be come s much more comple x be caus e the s e dire ctorie s contain bootcritical compone nts . In s ome s ituations , s uch as whe n the s e dire ctorie s are place d
on an iSCSI drive or an FCoE location, the s ys te m may e ithe r be unable to boot, or it
may hang with a Device is busy e rror whe n powe ring off or re booting.
This limitation only applie s to /usr or /var; not to dire ctorie s be low the m. For
e xample , a s e parate partition for /var/www will work without is s ue s .
Anaco nda can handle the partitioning re quire me nts for a typical ins tallation.
236
237
the type of partition. If the partition is a s tandard partition, this fie ld dis plays the
type of file s ys te m on the partition (for e xample , e xt4). Othe rwis e , it indicate s
that the partition is a physical volume (LVM), or part of a software RAID
Fo rmat
A che ck mark in this column indicate s that the partition will be formatte d during
ins tallation.
Be ne ath the lowe r pane are four buttons : Create, Edit, Delete, and Reset.
Se le ct a de vice or partition by clicking on it in e ithe r the graphical re pre s e ntation in the
uppe r pane of in the lis t in the lowe r pane , the n click one of the four buttons to carry out
the following actions :
Creat e
cre ate a ne w partition, logical volume , or s oftware RAID
Edit
change an e xis ting partition, logical volume , or s oftware RAID. Note that you can
only s hrink partitions with the Resize button, not e nlarge partitions .
Delet e
re move a partition, logical volume , or s oftware RAID
Reset
undo all change s made in this s cre e n
238
239
No te
You mus t de dicate at le as t one partition for this ins tallation, and optionally more . For
more information, re fe r to Appe ndix A, An Introduction to Disk Partitions.
240
us e the pull-down me nu to choos e the corre ct mount point for your partition. For a s wap
partition the mount point s hould not be s e t s e tting the file s ys te m type to swap is
s ufficie nt.
File System Type: Us ing the pull-down me nu, s e le ct the appropriate file s ys te m type
for this partition. For more information on file s ys te m type s , re fe r to Se ction 16.17.2.1,
File Sys te m Type s .
Allowable Drives: This fie ld contains a lis t of the hard dis ks ins talle d on your s ys te m.
If a hard dis k's box is highlighte d, the n a de s ire d partition can be cre ate d on that hard
dis k. If the box is not che cke d, the n the partition will never be cre ate d on that hard dis k.
By us ing diffe re nt che ckbox s e ttings , you can have anaco nda place partitions whe re
you ne e d the m, or le t anaco nda de cide whe re partitions s hould go.
Size (MB): Ente r the s iz e (in me gabyte s ) of the partition. Note , this fie ld s tarts with
200 MB; unle s s change d, only a 200 MB partition will be cre ate d.
Additional Size Options: Choos e whe the r to ke e p this partition at a fixe d s iz e , to
allow it to "grow" (fill up the available hard drive s pace ) to a ce rtain point, or to allow it
to grow to fill any re maining hard drive s pace available .
If you choos e Fill all space up to (MB), you mus t give s iz e cons traints in the fie ld
to the right of this option. This allows you to ke e p a ce rtain amount of s pace fre e on
your hard drive for future us e .
Force to be a primary partition: Se le ct whe the r the partition you are cre ating
s hould be one of the firs t four partitions on the hard drive . If uns e le cte d, the partition is
cre ate d as a logical partition. Re fe r to Se ction A.1.3, Partitions Within Partitions An
Ove rvie w of Exte nde d Partitions , for more information.
Encrypt: Choos e whe the r to e ncrypt the partition s o that the data s tore d on it cannot
be acce s s e d without a pas s phras e , e ve n if the s torage de vice is conne cte d to anothe r
s ys te m. Re fe r to Appe ndix C, Disk Encryption for information on e ncryption of s torage
de vice s . If you s e le ct this option, the ins talle r prompts you to provide a pas s phras e
be fore it write s the partition to the dis k.
OK: Se le ct OK once you are s atis fie d with the s e ttings and wis h to cre ate the partition.
Cancel: Se le ct Cancel if you do not want to cre ate the partition.
241
software RAID Cre ating two or more s oftware RAID partitions allows you to cre ate a
RAID de vice . For more information re garding RAID, re fe r to the chapte r RAID (Redundant
Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide.
physical volume (LVM) Cre ating one or more phys ical volume (LVM) partitions
allows you to cre ate an LVM logical volume . LVM can improve pe rformance whe n us ing
phys ical dis ks . For more information re garding LVM, re fe r to the Red Hat Enterprise
Linux Deployment Guide.
File syst ems
ext4 The e xt4 file s ys te m is bas e d on the e xt3 file s ys te m and fe ature s a numbe r
of improve me nts . The s e include s upport for large r file s ys te ms and large r file s , fas te r
and more e fficie nt allocation of dis k s pace , no limit on the numbe r of s ubdire ctorie s
within a dire ctory, fas te r file s ys te m che cking, and more robus t journaling. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt4. The e xt4 file s ys te m is s e le cte d by
de fault and is highly re comme nde d.
ext3 The e xt3 file s ys te m is bas e d on the e xt2 file s ys te m and has one main
advantage journaling. Us ing a journaling file s ys te m re duce s time s pe nt re cove ring a
file s ys te m afte r a cras h as the re is no ne e d to fsck [8] the file s ys te m. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt3.
ext2 An e xt2 file s ys te m s upports s tandard Unix file type s (re gular file s , dire ctorie s ,
s ymbolic links , e tc). It provide s the ability to as s ign long file name s , up to 255
characte rs .
xfs XFS is a highly s calable , high-pe rformance file s ys te m that s upports file s ys te ms
up to 16 e xabyte s (approximate ly 16 million te rabyte s ), file s up to 8 e xabyte s
(approximate ly 8 million te rabyte s ) and dire ctory s tructure s containing te ns of millions
of e ntrie s . XFS s upports me tadata journaling, which facilitate s quicke r cras h re cove ry.
The XFS file s ys te m can als o be de fragme nte d and re s iz e d while mounte d and active .
No te
The maximum s iz e of an XFS partition the ins talle r can cre ate is 100 TB.
vfat The VFAT file s ys te m is a Linux file s ys te m that is compatible with Micros oft
Windows long file name s on the FAT file s ys te m.
Btrfs Btrfs is unde r de ve lopme nt as a file s ys te m capable of addre s s ing and
managing more file s , large r file s , and large r volume s than the e xt2, e xt3, and e xt4 file
s ys te ms . Btrfs is de s igne d to make the file s ys te m tole rant of e rrors , and to facilitate
the de te ction and re pair of e rrors whe n the y occur. It us e s che cks ums to e ns ure the
validity of data and me tadata, and maintains s naps hots of the file s ys te m that can be
us e d for backup or re pair.
Be caus e Btrfs is s till e xpe rime ntal and unde r de ve lopme nt, the ins tallation program
doe s not offe r it by de fault. If you want to cre ate a Btrfs partition on a drive , you mus t
comme nce the ins tallation proce s s with the boot option btrfs. Re fe r to Chapte r 28,
Boot Options for ins tructions .
242
243
244
RAID 1 mirrors the data on one s torage de vice onto one or more othe r
s torage de vice s . Additional de vice s in the array provide incre as ing le ve ls of
re dundancy. RAID 1 re quire s at le as t two RAID partitions .
RAID 4 dis tribute s data acros s multiple s torage de vice s , but us e s one
de vice in the array to s tore parity information that s afe guards the array in
cas e any de vice within the array fails . Be caus e all parity information is s tore d
on the one de vice , acce s s to this de vice cre ate s a bottle ne ck in the
pe rformance of the array. RAID 4 re quire s at le as t thre e RAID partitions .
RAID 5 dis tribute s data and parity information acros s multiple s torage
de vice s . Le ve l 5 RAIDs the re fore offe r the pe rformance advantage s of
dis tributing data acros s multiple de vice s , but do not s hare the pe rformance
bottle ne ck of le ve l 4 RAIDs be caus e the parity information is als o dis tribute d
through the array. RAID 5 re quire s at le as t thre e RAID partitions .
RAID 6 le ve l 6 RAIDs are s imilar to le ve l 5 RAIDs , but ins te ad of s toring only
one s e t of parity data, the y s tore two s e ts . RAID 6 re quire s at le as t four RAID
partitions .
RAID 10 le ve l 10 RAIDs are nested RAIDs or hybrid RAIDs. Le ve l 10 RAIDs
are cons tructe d by dis tributing data ove r mirrore d s e ts of s torage de vice s . For
e xample , a le ve l 10 RAID cons tructe d from four RAID partitions cons is ts of two
pairs of partitions in which one partition mirrors the othe r. Data is the n
dis tribute d acros s both pairs of s torage de vice s , as in a le ve l 0 RAID. RAID 10
re quire s at le as t four RAID partitions .
245
246
247
Impo rtant
Re comme ndations in the table be low are e s pe cially important on s ys te ms with
low me mory (1 GB and le s s ). Failure to allocate s ufficie nt s wap s pace on the s e
s ys te ms may caus e is s ue s s uch as ins tability or e ve n re nde r the ins talle d
s ys te m unbootable .
248
2GB
> 2GB 8GB
> 8GB 64GB
> 64GB
At le as t 4 GB
At the borde r be twe e n e ach range lis te d above (for e xample , a s ys te m with 2GB, 8GB,
or 64GB of s ys te m RAM), dis cre tion can be e xe rcis e d with re gard to chos e n s wap
s pace and hibe rnation s upport. If your s ys te m re s ource s allow for it, incre as ing the
s wap s pace may le ad to be tte r pe rformance .
Note that dis tributing s wap s pace ove r multiple s torage de vice s particularly on
s ys te ms with fas t drive s , controlle rs and inte rface s als o improve s s wap s pace
pe rformance .
No te
Swap s pace s iz e re comme ndations is s ue d for Re d Hat Ente rpris e Linux 6.0, 6.1,
and 6.2 diffe re d from the curre nt re comme ndations , which we re firs t is s ue d with
the re le as e of Re d Hat Ente rpris e Linux 6.3 in June 2012 and did not account for
hibe rnation s pace . Automatic ins tallations of the s e e arlie r ve rs ions of Re d Hat
Ente rpris e Linux 6 s till ge ne rate a s wap s pace in line with the s e s upe rs e de d
re comme ndations . Howe ve r, manually s e le cting a s wap s pace s iz e in line with
the ne we r re comme ndations is s ue d for Re d Hat Ente rpris e Linux 6.3 is advis able
for optimal pe rformance .
A PRe P boot partition on the firs t partition of the hard drive the PRe P boot partition
contains the Yabo o t boot loade r (which allows othe r Powe r Sys te ms s e rve rs to boot
Re d Hat Ente rpris e Linux). Unle s s you plan to boot from a ne twork s ource , you mus t
have a PRe P boot partition to boot Re d Hat Ente rpris e Linux.
For IBM System p users: The PRe P boot partition s hould be be twe e n 4-8 MB, not to
e xce e d 10 MB.
A /boot/ partition (250 MB) the partition mounte d on /boot/ contains the ope rating
s ys te m ke rne l (which allows your s ys te m to boot Re d Hat Ente rpris e Linux), along with
file s us e d during the boots trap proce s s . Due to the limitations of mos t PC firmware ,
cre ating a s mall partition to hold the s e is a good ide a. For mos t us e rs , a 250 MB boot
partition is s ufficie nt.
Warning
If you have a RAID card, be aware that Re d Hat Ente rpris e Linux 6.6 doe s not
s upport s e tting up hardware RAID on an IPR card. You can boot the s tandalone
diagnos tics CD prior to ins tallation to cre ate a RAID array and the n ins tall to that
RAID array.
249
Ro o t and
/root
The / (or root) partition is the top of the dire ctory s tructure . The /root dire ctory
(s ome time s pronounce d "s las h-root") is the home dire ctory of the us e r account
for s ys te m adminis tration.
Warning
The PackageKit update s oftware downloads update d package s to
/var/cache/yum/ by de fault. If you partition the s ys te m manually, and cre ate a
s e parate /var/ partition, be s ure to cre ate the partition large e nough (3.0 GB or
more ) to download package update s .
250
251
Installing in text mo de
If you ins tall Re d Hat Ente rpris e Linux in te xt mode , you cannot make package
s e le ctions . The ins talle r automatically s e le cts package s only from the bas e and core
groups . The s e package s are s ufficie nt to e ns ure that the s ys te m is ope rational at
the e nd of the ins tallation proce s s , re ady to ins tall update s and ne w package s . To
change the package s e le ction, comple te the ins tallation, the n us e the Add/Remo ve
So f t ware application to make de s ire d change s .
252
This option provide s OpenLDAP and Ent erprise Ident it y Management (IPA) to
cre ate an ide ntity and authe ntication s e rve r.
Virt ual Ho st
This option provide s the KVM and Virt ual Machine Manager tools to cre ate a
hos t for virtual machine s .
Deskt o p
This option provide s the OpenOf f ice.o rg productivity s uite , graphical tools s uch
as the GIMP, and multime dia applications .
So f t ware Develo pment Wo rkst at io n
This option provide s the ne ce s s ary tools to compile s oftware on your Re d Hat
Ente rpris e Linux s ys te m.
Minimal
This option provide s only the package s e s s e ntial to run Re d Hat Ente rpris e Linux.
A minimal ins tallation provide s the bas is for a s ingle -purpos e s e rve r or de s ktop
appliance and maximiz e s pe rformance and s e curity on s uch an ins tallation.
Warning
Minimal ins tallation curre ntly doe s not configure the fire wall
(iptables/ip6tables) by de fault be caus e the authconfig and system-configfirewall-base package s are mis s ing from the s e le ction. To work around this
is s ue , you can us e a Kicks tart file to add the s e package s to your s e le ction.
Se e the Re d Hat Cus tome r Portal for de tails about the workaround, and
Chapte r 32, Kickstart Installations for information about Kicks tart file s .
If you do not us e the workaround, the ins tallation will comple te s ucce s s fully,
but no fire wall will be configure d, pre s e nting a s e curity ris k.
If you choos e to acce pt the curre nt package lis t, s kip ahe ad to Se ction 16.20, Ins talling
Package s .
To s e le ct a compone nt, click on the che ckbox be s ide it (re fe r to Figure 16.48, Package
Group Se le ction).
To cus tomiz e your package s e t furthe r, s e le ct the Customize now option on the s cre e n.
Clicking Next take s you to the Package Group Selection s cre e n.
253
with the various pie ce s of s oftware in the ir ve rs ions that we re curre nt at the time of
re le as e .
254
255
No te 64-bit applicatio ns
Us e rs who want s upport for de ve loping or running 64-bit applications are
e ncourage d to s e le ct the Compatibility Arch Support and Compatibility Arch
Development Support package s to ins tall archite cture s pe cific s upport for the ir
s ys te ms .
Se le ct Customize now to s pe cify the s oftware package s for your final s ys te m in more
de tail. This option caus e s the ins tallation proce s s to dis play an additional cus tomiz ation
s cre e n whe n you s e le ct Next.
256
257
258
[7] A root password is the adm inistrative password for your Red Hat Enterprise Linux system .
You should only log in as root when needed for system m aintenance. The root account does
not operate within the restrictions placed on norm al user accounts, so changes m ade as root
can have im plications for your entire system .
[8] The fsck application is used to check the file system for m etadata consistency and
optionally repair one or m ore Linux file system s.
259
17.1. You Are Unable t o Boot Red Hat Ent erprise Linux
17.1.1. Is Your Syst em Displaying Signal 11 Errors?
A s ignal 11 e rror, commonly known as a segmentation fault, me ans that the program
acce s s e d a me mory location that was not as s igne d to it. A s ignal 11 e rror may be due to a
bug in one of the s oftware programs that is ins talle d, or faulty hardware .
If you re ce ive a fatal s ignal 11 e rror during your ins tallation, it is probably due to a
hardware e rror in me mory on your s ys te m's bus . Like othe r ope rating s ys te ms , Re d Hat
Ente rpris e Linux place s its own de mands on your s ys te m's hardware . Some of this
hardware may not be able to me e t thos e de mands , e ve n if the y work prope rly unde r
anothe r OS.
Ens ure that you have the late s t ins tallation update s and image s . Re vie w the online e rrata
to s e e if ne we r ve rs ions are available . If the late s t image s s till fail, it may be due to a
260
proble m with your hardware . Commonly, the s e e rrors are in your me mory or CPU-cache . A
pos s ible s olution for this e rror is turning off the CPU-cache in the BIOS, if your s ys te m
s upports this . You could als o try to s wap your me mory around in the mothe rboard s lots to
che ck if the proble m is e ithe r s lot or me mory re late d.
Anothe r option is to pe rform a me dia che ck on your ins tallation DVD. Anaco nda, the
ins tallation program, has the ability to te s t the inte grity of the ins tallation me dia. It works
with the DVD, hard drive ISO, and NFS ISO ins tallation me thods . Re d Hat re comme nds that
you te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore re porting
any ins tallation-re late d bugs (many of the bugs re porte d are actually due to imprope rlyburne d DVDs ). To us e this te s t, type the following command at the boot: or yaboot:
prompt:
linux mediacheck
For more information conce rning s ignal 11 e rrors , re fe r to:
http://www.bitwizard.nl/sig11/
No te
To dis able frame buffe r s upport and allow the ins tallation program to run in te xt
mode , try us ing the nofb boot option. This command may be ne ce s s ary for
acce s s ibility with s ome s cre e n re ading hardware .
261
262
263
264
265
Figure 17.6. Ent er Red Hat Net wo rk aut hent icat io n det ails
Repo rt uplo ader
Spe cify a URL for uploading a compre s s e d ve rs ion of the cras h re port.
266
267
You can now cus tomiz e the re port by che cking and unche cking the is s ue s that will be
include d. Whe n finis he d, click Apply.
268
Re porting is now comple te . Click Forward to re turn to the re port s e le ction dialog. You can
now make anothe r re port, or click Close to e xit the re porting utility and the n Exit to clos e
the ins tallation proce s s .
17.3.4. Ot her Part it ioning Problems f or IBM Power Syst ems Users
If you cre ate partitions manually, but cannot move to the ne xt s cre e n, you probably have
not cre ate d all the partitions ne ce s s ary for ins tallation to proce e d.
You mus t have the following partitions as a bare minimum:
A / (root) partition
A <s wap> partition of type s wap
A PRe P Boot partition.
A /boot/ partition.
Re fe r to Se ction 16.17.5, Re comme nde d Partitioning Sche me for more information.
No te
Whe n de fining a partition's type as s wap, do not as s ign it a mount point. Anaco nda
automatically as s igns the mount point for you.
269
Warning
Change only the numbe r of the de fault runle ve l from 3 to 5.
Your change d line s hould look like the following:
id:5:initdefault:
Whe n you are s atis fie d with your change , s ave and e xit the file us ing the Ctrl+Q ke ys . A
window appe ars and as ks if you would like to s ave the change s . Click Save.
270
The ne xt time you log in afte r re booting your s ys te m, you are pre s e nte d with a graphical
login prompt.
271
272
localhost.localdomain
localhost
P art III. IBM Syst em z Archit ect ure - Inst allat ion and
Boot ing
This part of the Red Hat Enterprise Linux Installation Guide dis cus s e s ins tallation and
booting (or initial program load, IPL) of Re d Hat Ente rpris e Linux on IBM Sys te m z .
273
274
You can ins tall Re d Hat Ente rpris e Linux on Sys te m z inte ractive ly or in unatte nde d mode .
Ins tallation on Sys te m z diffe rs from ins tallation on othe r archite cture s in that it is typically
pe rforme d ove r a ne twork and not from a local DVD. The ins tallation can be s ummariz e d
as follows :
1. Bo o t ing (IPL) t he inst aller
Conne ct with the mainframe , the n pe rform an initial program load (IPL), or boot, from
the me dium containing the ins tallation program.
2. Inst allat io n Phase 1
Se t up an initial ne twork de vice . This ne twork de vice is the n us e d to conne ct to the
ins tallation s ys te m via SSH or VNC. This ge ts you a full-s cre e n mode te rminal or
graphical dis play to continue ins tallation as on othe r archite cture s .
3. Inst allat io n Phase 2
Spe cify which language to us e , and how and whe re the ins tallation program and the
s oftware package s to be ins talle d from the re pos itory on the Re d Hat ins tallation
me dium can be found.
4. Inst allat io n Phase 3
Us e anaco nda (the main part of the Re d Hat ins tallation program) to pe rform the
re s t of the ins tallation.
275
276
You can us e the following boot me dia only if Linux is to run in LPAR mode :
SE or HMC through a re mote FTP s e rve r re fe r to Se ction 20.2.1, Us ing an FTP
Se rve r for de tails .
SE or HMC DVD re fe r to Se ction 20.2.2, Us ing the HMC or SE DVD Drive for de tails
You can us e the following boot me dia for both z /VM and LPAR:
DASD re fe r to Se ction 20.1.2, Us ing a Pre pare d DASD for z /VM or Se ction 20.2.3,
Us ing a Pre pare d DASD for LPAR
SCSI de vice that is attache d through an FCP channe l re fe r to Se ction 20.1.3, Us ing a
Pre pare d FCP-attache d SCSI Dis k for z /VM or Se ction 20.2.4, Us ing a Pre pare d FCPattache d SCSI Dis k for LPAR
FCP-attache d SCSI DVD re fe r to Se ction 20.1.4, Us ing an FCP-attache d SCSI DVD
Drive for z /VM or Se ction 20.2.5, Us ing an FCP-attache d SCSI DVD Drive for LPAR
If you us e DASD and FCP-attache d SCSI de vice s (e xce pt SCSI DVDs ) as boot me dia, you
mus t have a configure d z ipl boot loade r. For more information, s e e the Chapte r on z ipl in
Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6.
277
SSH lo gin
none
vnc
VNC or te xt
VNC
none
278
X11
Paramet er
SSH lo gin
display=IP/hostname:dis
play
X11
279
dis able X11 forwarding in your SSH clie nt prior to conne cting to the te mporary Linux
ins tallation s ys te m. The loade r will the n provide a choice be twe e n te xt-mode and VNC;
choos e VNC he re . Alte rnative ly, provide the vnc variable and optionally the vncpassword
variable in your parame te r file (re fe r to Se ction 26.4, VNC and X11 Parame te rs for
de tails ).
A me s s age on the works tation SSH te rminal prompts you to s tart the VNC clie nt vie we r
and provide s de tails about the VNC dis play s pe cifications . Ente r the s pe cifications from
the SSH te rminal into the VNC clie nt vie we r and conne ct to the te mporary Linux ins tallation
s ys te m to be gin the ins tallation. Re fe r to Chapte r 31, Installing Through VNC for de tails .
18.3.5. Aut omat ing t he Inst allat ion wit h Kickst art
You can allow an ins tallation to run unatte nde d by us ing Kicks tart. A Kickstart file s pe cifie s
s e ttings for an ins tallation. Once the ins tallation s ys te m boots , it can re ad a Kicks tart file
and carry out the ins tallation proce s s without any furthe r input from a us e r.
On Sys te m z , this als o re quire s a parame te r file (optionally an additional configuration file
unde r z /VM). This parame te r file mus t contain the re quire d ne twork options de s cribe d in
Se ction 26.3, Ins tallation Ne twork Parame te rs and s pe cify a kicks tart file us ing the ks=
option. The kicks tart file typically re s ide s on the ne twork. The parame te r file ofte n als o
contains the options cmdline and RUNKS=1 to e xe cute the loade r without having to log in
ove r the ne twork with SSH (Re fe r to Se ction 26.6, Parame te rs for Kicks tart Ins tallations ).
For furthe r information and de tails on how to s e t up a kicks tart file , re fe r to Se ction 32.3,
Cre ating the Kicks tart File .
[9] Direct Access Storage Devices (DASDs) are hard disks that allow a m axim um of three
partitions per device. For exam ple, dasda can have partitions dasda1 , dasda2 , and dasda3 .
[10] Using the SC SI-over-Fibre C hannel device driver (zfcp device driver) and a switch, SC SI
LUNs can be presented to Linux on System z as if they were locally attached SC SI drives.
280
No te
The public dire ctory us e d to acce s s the ins tallation file s ove r FTP, NFS, HTTP, or
HTTPS is mappe d to local s torage on the ne twork s e rve r. For e xample , the local
dire ctory /var/www/inst/rhel6.6 on the ne twork s e rve r can be acce s s e d as
http://network.server.com/inst/rhel6.6.
In the following e xample s , the dire ctory on the ins tallation s taging s e rve r that will
contain the ins tallation file s will be s pe cifie d as /location/of/disk/space. The
dire ctory that will be made publicly available via FTP, NFS, HTTP, or HTTPS will be
s pe cifie d as /publicly_available_directory. For e xample , /location/of/disk/space
may be a dire ctory you cre ate calle d /var/isos. /publicly_available_directory
might be /var/www/html/rhel6.6, for an HTTP ins tall.
In the following, you will re quire an ISO image. An ISO image is a file containing an e xact
copy of the conte nt of a DVD. To cre ate an ISO image from a DVD us e the following
command:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the re s ulting
ISO image file , and path_to_image is the path to the location on your s ys te m whe re the
re s ulting ISO image will be s tore d.
To copy the file s from the ins tallation DVD to a Linux ins tance , which acts as an ins tallation
s taging s e rve r, continue with e ithe r Se ction 19.1.1, Pre paring for FTP, HTTP, and HTTPS
Ins tallation or Se ction 19.1.2, Pre paring for an NFS Ins tallation.
281
Warning
If your Apache we b s e rve r or t f t p FTP s e rve r configuration e nable s SSL s e curity,
make s ure to only e nable the TLSv1 protocol, and dis able SSLv2 and SSLv3. This is
due to the POODLE SSL vulne rability (CVE-2014-3566). Se e
https ://acce s s .re dhat.com/s olutions /1232413 for de tails about s e curing Apache, and
https ://acce s s .re dhat.com/s olutions /1234773 for information about s e curing t f t p.
Extract the file s from the ISO image of the ins tallation DVD and place the m in a dire ctory
that is s hare d ove r FTP, HTTP, or HTTPS.
Ne xt, make s ure that the dire ctory is s hare d via FTP, HTTP, or HTTPS, and ve rify clie nt
acce s s . Te s t to s e e whe the r the dire ctory is acce s s ible from the s e rve r its e lf, and the n
from anothe r machine on the s ame s ubne t to which you will be ins talling.
282
No te
anaco nda has the ability to te s t the inte grity of the ins tallation me dia. It works with
the DVD, hard drive ISO, and NFS ISO ins tallation me thods . We re comme nd that you
te s t all ins tallation me dia be fore s tarting the ins tallation proce s s , and be fore
re porting any ins tallation-re late d bugs (many of the bugs re porte d are actually due
to imprope rly-burne d DVDs ). To us e this te s t, type the following command at the
boot: prompt:
linux mediacheck
19.2.1. Accessing Inst allat ion Phase 3 and t he Package Reposit ory on
283
19.2.1. Accessing Inst allat ion Phase 3 and t he Package Reposit ory on
a Hard Drive
No te
Hard drive ins tallations us ing DASD or FCP-attache d SCSI s torage only work from
native e xt2, e xt3, or e xt4 partitions . If you have a file s ys te m bas e d on de vice s
othe r than native e xt2, e xt3, or e xt4 (particularly a file s ys te m bas e d on RAID or
LVM partitions ) you will not be able to us e it as a s ource to pe rform a hard drive
ins tallation.
Hard drive ins tallations us e an ISO image of the ins tallation DVD (a file that contains an
e xact copy of the conte nt of the DVD), and an install.img file e xtracte d from the ISO
image . With the s e file s pre s e nt on a hard drive , you can choos e Hard drive as the
ins tallation s ource whe n you boot the ins tallation program.
Hard drive ins tallations us e the following file s :
an ISO image of the ins tallation DVD. An ISO image is a file that contains an e xact copy
of the conte nt of a DVD.
an install.img file e xtracte d from the ISO image .
optionally, a product.img file e xtracte d from the ISO image .
With the s e file s pre s e nt on a hard drive , you can choos e Hard drive as the ins tallation
s ource whe n you boot the ins tallation program (re fe r to Se ction 22.4, Ins tallation Me thod).
Ens ure that you have boot me dia available as de s cribe d in Chapte r 20, Booting (IPL) the
Installer.
To pre pare a DASD or FCP-attache d de vice as an ins tallation s ource , follow the s e s te ps :
1. Obtain an ISO image of the Re d Hat Ente rpris e Linux ins tallation DVD (re fe r to
Chapte r 1, Obtaining Red Hat Enterprise Linux). Alte rnative ly, if you have the DVD on
phys ical me dia, you can cre ate an image of it with the following command on a
Linux s ys te m:
dd if=/dev/dvd of=/path_to_image/name_of_image.iso
whe re dvd is your DVD drive de vice , name_of_image is the name you give to the
re s ulting ISO image file , and path_to_image is the path to the location on your
s ys te m whe re the re s ulting ISO image will be s tore d.
2. Trans fe r the ISO image s to the DASD or SCSI de vice .
The ISO file s mus t be locate d on a hard drive that is activate d in ins tallation phas e
1 (re fe r to Chapte r 21, Installation Phase 1: Configuring a Network Device) or in
ins tallation phas e 2 (re fe r to Chapte r 22, Installation Phase 2: Configuring Language
and Installation Source). This is automatically pos s ible with DASDs .
For an FCP LUN, you mus t e ithe r boot (IPL) from the s ame FCP LUN or us e the
re s cue s he ll provide d by the ins tallation phas e 1 me nus to manually activate the
FCP LUN holding the ISOs as de s cribe d in Se ction 25.2.1, Dynamically Activating an
FCP LUN.
284
3. Us e a SHA256 che cks um program to ve rify that the ISO image that you copie d is
intact. Many SHA256 che cks um programs are available for various ope rating
s ys te ms . On a Linux s ys te m, run:
$ sha256sum name_of_image.iso
whe re name_of_image is the name of the ISO image file . The SHA256 che cks um
program dis plays a s tring of 64 characte rs calle d a hash. Compare this has h to the
has h dis playe d for this particular image on the Downloads page in the Re d Hat
Cus tome r Portal (re fe r to Chapte r 1, Obtaining Red Hat Enterprise Linux). The two
has he s s hould be ide ntical.
4. Copy the images/ dire ctory from ins ide the ISO image to the s ame dire ctory in
which you s tore d the ISO image file its e lf. Ente r the following commands :
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/images /publicly_available_directory/
umount /mount_point
whe re path_to_image is the path to the ISO image file , name_of_image is the
name of the ISO image file , and mount_point is a mount point on which to mount
the image while you copy file s from the image . For e xample :
mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,ro
cp -pr /mnt/tmp/images /var/isos/
umount /mnt/tmp
The ISO image file and an images/ dire ctory are now pre s e nt, s ide -by-s ide , in the
s ame dire ctory.
5. Ve rify that the images/ dire ctory contains at le as t the install.img file , without
which ins tallation cannot proce e d. Optionally, the images/ dire ctory s hould contain
the product.img file , without which only the package s for a Minimal ins tallation will
be available during the package group s e le ction s tage (re fe r to Se ction 23.17,
Package Group Se le ction).
images/
directo ry
285
286
If you are not alre ady running CMS (s ingle us e r ope rating s ys te m s hippe d with z /VM) in
your gue s t, boot it now by e nte ring the command:
#cp ipl cms
Be s ure not to us e CMS dis ks s uch as your A dis k (ofte n de vice numbe r 0191) as
ins tallation targe ts . To find out which dis ks are in us e by CMS us e the following que ry:
query disk
You can us e the following CP (z /VM Control Program, which is the z /VM hype rvis or) que ry
commands to find out about the de vice configuration of your z /VM gue s t virtual machine :
Que ry the available main me mory, which is calle d storage in Sys te m z te rminology.
Your gue s t s hould have at le as t 512 me gabyte s of main me mory.
287
288
289
290
291
4. As Load parameter fill in the numbe r corre s ponding the z ipl boot me nu e ntry that
you pre pare d for booting the Re d Hat Ente rpris e Linux ins talle r.
5. Click the OK button.
292
293
m
* NOTE: To enter default or empty values press enter twice. *
294
295
If you want to change s ome thing, e nte r r to re s tart the dialog. To s how the parame te rs as
s pe cifie d in a parame te r or configuration file or inte ractive ly e nte r p. You can the n copy
the output from your te rminal and pas te it into an e ditor to s ave it to dis k on your local
works tation. You can us e the copy as a te mplate for a parame te r or configuration file for
future ins tallations :
p
NETTYPE=qeth
IPADDR=10.0.0.42
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
HOSTNAME=host.subdomain.domain
SUBCHANNELS=0.0.f5f0,0.0.f5f1,0.0.f5f2
LAYER2=1
MACADDR=02:00:00:AB:C9:81
PORTNAME=OSAPORT
DNS=10.1.2.3:10.3.2.1
SEARCHDNS=subdomain.domain:domain
DASD=eb1c
c) continue, p) parm file/configuration, n) network state, r) restart,
s) shell
Again, to change s ome thing, re s tart the dialog with r. Finally, if all is in orde r, e nte r c to
continue :
c
Starting sshd to allow login over the network.
Connect now to 10.0.0.42 and log in as user 'install' to start the
installation.
E.g. using: ssh -x install@10.0.0.42
For VNC or text mode, disable X11 forwarding (recommended) with 'ssh x'.
For X11, enable X11 forwarding with 'ssh -X'.
You may log in as the root user to start an interactive shell.
The pre liminary ne twork s e tup is now comple te and the ins talle r s tarts an SSH dae mon.
You can log into your Linux ins tance ove r SSH. If you are us ing RUNKS=1 with kicks tart and
cmdline mode , linuxrc automatically s tarts the loade r.
296
Be aware that long-running commands might not be inte rruptible with the e s cape
s e que nce Ctrl+C. Call commands with options that make the m re turn in time voluntarily.
The s he ll on the 3270 te rminal is available throughout the whole ins tallation proce s s until
the point whe re the s ys te m ne e ds to re boot.
Once the s he ll has be e n provide d, you may e xit with an e rror le ve l of z e ro to ge t a ne w
s he ll ins tance re placing the old one , or you may e xit with an e rror le ve l diffe re nt from
z e ro to force a s hutdown of the ins tallation s ys te m.
Conne ct to the ins talle d s ys te m us ing us e r root to ge t a root s he ll without automatically
s tarting the ins talle r. For proble m de te rmination, you might conne ct with many s s h
s e s s ions .
297
22.2. T he T ext Mode Inst allat ion Program User Int erface
Both the loade r and late r anaco nda us e a s cre e n-bas e d inte rface that include s mos t of
the on-s cre e n widgets commonly found on graphical us e r inte rface s . Figure 22.1,
Ins tallation Program Widge ts as s e e n in URL Setup, and Figure 22.2, Ins tallation
Program Widge ts as s e e n in Choose a Language, illus trate widge ts that appe ar on
s cre e ns during the ins tallation proce s s .
Figure 22.1. Inst allat io n Pro gram Widget s as seen in URL Setup
298
C hapt e r 22. Ins t allat io n Phas e 2: Co nf igur ing Language and Ins t allat io n So ur c e
Figure 22.2. Inst allat io n Pro gram Widget s as seen in Choose a Language
He re is a lis t of the mos t important widge ts s hown in Figure 22.1, Ins tallation Program
Widge ts as s e e n in URL Setup and Figure 22.2, Ins tallation Program Widge ts as s e e n in
Choose a Language:
Window Windows (us ually re fe rre d to as dialogs in this manual) appe ar on your
s cre e n throughout the ins tallation proce s s . At time s , one window may ove rlay anothe r;
in the s e cas e s , you can only inte ract with the window on top. Whe n you are finis he d in
that window, it dis appe ars , allowing you to continue working in the window unde rne ath.
Che ckbox Che ckboxe s allow you to s e le ct or de s e le ct a fe ature . The box dis plays
e ithe r an as te ris k (s e le cte d) or a s pace (uns e le cte d). Whe n the curs or is within a
che ckbox, pre s s Space to s e le ct or de s e le ct a fe ature .
Te xt Input Te xt input line s are re gions whe re you can e nte r information re quire d by
the ins tallation program. Whe n the curs or re s ts on a te xt input line , you may e nte r
and/or e dit information on that line .
Te xt Widge t Te xt widge ts are re gions of the s cre e n for the dis play of te xt. At time s ,
te xt widge ts may als o contain othe r widge ts , s uch as che ckboxe s . If a te xt widge t
contains more information than can be dis playe d in the s pace re s e rve d for it, a s croll
bar appe ars ; if you pos ition the curs or within the te xt widge t, you can the n us e the Up
and Down arrow ke ys to s croll through all the information available . Your curre nt pos ition
is s hown on the s croll bar by a # characte r, which move s up and down the s croll bar as
you s croll.
Scroll Bar Scroll bars appe ar on the s ide or bottom of a window to control which part
of a lis t or docume nt is curre ntly in the window's frame . The s croll bar make s it e as y to
move to any part of a file .
299
Button Widge t Button widge ts are the primary me thod of inte racting with the
ins tallation program. You progre s s through the windows of the ins tallation program by
navigating the s e buttons , us ing the Tab and Enter ke ys . Buttons can be s e le cte d whe n
the y are highlighte d.
Curs or Although not a widge t, the curs or is us e d to s e le ct (and inte ract with) a
particular widge t. As the curs or is move d from widge t to widge t, it may caus e the
widge t to change color, or the curs or its e lf may only appe ar pos itione d in or ne xt to the
widge t. In Figure 22.1, Ins tallation Program Widge ts as s e e n in URL Setup, the curs or
is pos itione d on the Enable HTTP proxy che ckbox. Figure 8.2, Ins tallation Program
Widge ts as s e e n in Choose a Language, s hows the curs or on the OK button.
Warning
Unle s s a dialog box is waiting for your input, do not pre s s any ke ys during the
ins tallation proce s s (doing s o may re s ult in unpre dictable be havior).
300
C hapt e r 22. Ins t allat io n Phas e 2: Co nf igur ing Language and Ins t allat io n So ur c e
301
No te
To abort the ins tallation proce s s at this time , re boot your machine and the n e je ct
the boot me dia. You can s afe ly cance l the ins tallation at any point be fore the Write
changes to disk s cre e n. Re fe r to Se ction 23.16, Write Change s to Dis k for more
information.
If the DVD drive is found and the drive r loade d, the ins talle r pre s e nts you with the option
to pe rform a me dia che ck on the DVD. This take s s ome time , and you may opt to s kip
ove r this s te p. Howe ve r, if you late r e ncounte r proble ms with the ins talle r, you s hould
re boot and pe rform the me dia che ck be fore calling for s upport. From the me dia che ck
dialog, continue to the ne xt s tage of the ins tallation proce s s (re fe r to Se ction 23.5,
We lcome to Re d Hat Ente rpris e Linux).
302
C hapt e r 22. Ins t allat io n Phas e 2: Co nf igur ing Language and Ins t allat io n So ur c e
Figure 22.5. Select ing Part it io n Dialo g f o r Hard Drive Inst allat io n
Se le ct the partition containing the ISO file s from the lis t of available partitions . DASD
name s be gin with /dev/dasd. Each individual drive has its own le tte r, for e xample
/dev/dasda or /dev/sda. Each partition on a drive is numbe re d, for e xample /dev/dasda1
or /dev/sda1.
For an FCP LUN, you would have to e ithe r boot (IPL) from the s ame FCP LUN or us e the
re s cue s he ll provide d by the linuxrc me nus to manually activate the FCP LUN holding the
ISOs as de s cribe d in Se ction 25.2.1, Dynamically Activating an FCP LUN.
Als o s pe cify the Directory holding images. Ente r the full dire ctory path from the drive
that contains the ISO image file s . The following table s hows s ome e xample s of how to
e nte r this information:
T able 22.1. Lo cat io n o f ISO images f o r dif f erent part it io n t ypes
File syst em
Mo unt po int
Original pat h t o
f iles
Direct o ry t o use
/home
/us e r1/RHEL6.6
If the ISO image s are in the root (top-le ve l) dire ctory of a partition, e nte r a /. If the ISO
image s are locate d in a s ubdire ctory of a mounte d partition, e nte r the name of the
dire ctory holding the ISO image s within that partition. For e xample , if the partition on which
the ISO image s is normally mounte d as /home/, and the image s are in /home/new/, you
would e nte r /new/.
303
304
C hapt e r 22. Ins t allat io n Phas e 2: Co nf igur ing Language and Ins t allat io n So ur c e
Ente r the name or IP addre s s of the FTP, HTTP, or HTTPS s ite from which you are ins talling,
and the name of the dire ctory that contains the /images dire ctory for your archite cture .
For e xample :
/mirrors/redhat/rhel-6.6/Server/s390x/
To ins tall via a s e cure HTTPS conne ction, s pe cify https:// as the protocol.
Spe cify the addre s s of a proxy s e rve r, and if ne ce s s ary, provide a port numbe r,
us e rname , and pas s word. If e ve rything was s pe cifie d prope rly, a me s s age box appe ars
indicating that file s are be ing re trie ve d from the s e rve r.
If your FTP, HTTP, or HTTPS s e rve r re quire s us e r authe ntication, s pe cify us e r and
pas s word as part of the URL as follows :
{ftp|http|https}://<user>:<password>@<hostname>[:<port>]/<directory>/
For e xample :
http://install:rhel6.6pw@name.example.com/mirrors/redhat/rhel6.6/Server/s390x/
305
306
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
23.2. T he T ext Mode Inst allat ion Program User Int erface
While te xt mode ins tallations are not e xplicitly docume nte d, thos e us ing the te xt mode
ins tallation program can e as ily follow the GUI ins tallation ins tructions . Howe ve r, be caus e
te xt mode pre s e nts you with a s imple r, more s tre amline d ins tallation proce s s , ce rtain
options that are available in graphical mode are not als o available in te xt mode . The s e
diffe re nce s are note d in the de s cription of the ins tallation proce s s in this guide , and
include :
Inte ractive ly activating FCP LUNs
configuring advance d s torage me thods s uch as LVM, RAID, FCoE, z FCP, and iSCSI.
cus tomiz ing the partition layout
cus tomiz ing the bootloade r layout
s e le cting package s during ins tallation
configuring the ins talle d s ys te m with f irst bo o t
307
If you did not s e t the display= variable and do not us e X11 forwarding, anaco nda give s
you the choice of s tarting VNC or te xt mode .
308
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
The Welcome s cre e n doe s not prompt you for any input.
309
No te
Monitoring of LVM and s oftware RAID de vice s by the mdeventd dae mon is not
pe rforme d during ins tallation.
310
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Basic Devices
Bas ic s torage de vice s dire ctly conne cte d to the local s ys te m, s uch as hard dis k
drive s and s olid-s tate drive s . On Sys te m z , this contains activate d DASDs .
Firmware RAID
Storage de vice s attache d to a firmware RAID controlle r. This doe s not apply to
Sys te m z .
Mult ipat h Devices
Storage de vice s acce s s ible through more than one path, s uch as through multiple
SCSI controlle rs or Fibe r Channe l ports on the s ame s ys te m.
311
312
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
313
314
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
315
your organiz ation's Inte rne t domain or s ubdomain name , pre s e nte d in re ve rs e
orde r with the top-le ve l domain firs t. For e xample , re pre s e nt the s ubdomain
storage.example.com as com.example.storage
a colon followe d by a s tring that unique ly ide ntifie s this particular iSCSI initiator
within your domain or s ubdomain. For e xample , :diskarrays-sn-a8675309.
A comple te IQN the re fore re s e mble s : iqn.201009.storage.example.com:diskarrays-sn-a8675309, and anaco nda pre populate s the iSCSI Initiator Name fie ld with a name in this format to he lp you
with the s tructure .
For more information on IQNs , re fe r to 3.2.6. iSCSI Names in RFC 3720 - Internet
Small Computer Systems Interface (iSCSI) available from
http://tools .ie tf.org/html/rfc3720#s e ction-3.2.6 and 1. iSCSI Names and Addresses in
RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery
available from http://tools .ie tf.org/html/rfc3721#s e ction-1.
3. Us e the drop-down me nu to s pe cify the type of authe ntication to us e for iSCSI
dis cove ry:
316
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
317
318
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
319
320
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
321
322
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Valid Ho stnames
You may give your s ys te m any name provide d that the full hos tname is unique . The
hos tname may include le tte rs , numbe rs and hyphe ns .
Change the de fault s e tting localhost.localdomain to a unique hos tname for e ach of your
Linux ins tance s .
No te
To change your ne twork configuration afte r you have comple te d the ins tallation, us e
the Net wo rk Administ rat io n T o o l.
Type the system-config-network command in a s he ll prompt to launch the
Net wo rk Administ rat io n T o o l. If you are not root, it prompts you for the root
pas s word to continue .
The Net wo rk Administ rat io n T o o l is now de pre cate d and will be re place d by
Net wo rkManager during the life time of Re d Hat Ente rpris e Linux 6.
Us ually, the ne twork conne ction configure d e arlie r in ins tallation phas e 1 doe s not ne e d to
be modifie d during the re s t of the ins tallation. You cannot add a ne w conne ction on
Sys te m z be caus e the ne twork s ubchanne ls ne e d to be groupe d and s e t online
be fore hand, and this is curre ntly only done in ins tallation phas e 1. To change the e xis ting
323
ne twork conne ction, click the button Configure Network. The Network Connections
dialog appe ars that allows you to configure ne twork conne ctions for the s ys te m, not all of
which are re le vant to Sys te m z .
324
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Whe n Net wo rkManager runs on an ins talle d s ys te m, the Available to all users
option controls whe the r a ne twork configuration is available s ys te m-wide or not. During
ins tallation, e ns ure that Available to all users re mains s e le cte d for any ne twork
inte rface that you configure .
23.7.1.2. T he Wired t ab
Us e the Wired tab to s pe cify or change the media access control (MAC) addre s s for the
ne twork adapte r, and e ithe r s e t the maximum transmission unit (MTU, in byte s ) that can
pas s through the inte rface .
325
Us e the 802.1x Security tab to configure 802.1X port-based network access control
(PNAC). Se le ct Use 802.1X security for this connection to e nable acce s s control,
the n s pe cify de tails of your ne twork. The configuration options include :
Authentication
Choos e one of the following me thods of authe ntication:
TLS for Transport Layer Security
Tunneled TLS for Tunneled Transport Layer Security, othe rwis e known as TTLS,
or EAP-TTLS
Protected EAP (PEAP) for Protected Extensible Authentication Protocol
Identity
Provide the ide ntity of this s e rve r.
User certificate
Brows e to a pe rs onal X.509 ce rtificate file e ncode d with Distinguished Encoding
Rules (DER) or Privacy Enhanced Mail (PEM).
CA certificate
Brows e to a X.509 certificate authority ce rtificate file e ncode d with Distinguished
Encoding Rules (DER) or Privacy Enhanced Mail (PEM).
Private key
Brows e to a private key file e ncode d with Distinguished Encoding Rules (DER),
Privacy Enhanced Mail (PEM), or the Personal Information Exchange Syntax
Standard (PKCS#12).
Private key password
The pas s word for the private ke y s pe cifie d in the Private key fie ld. Se le ct Show
password to make the pas s word vis ible as you type it.
326
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
327
328
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
329
330
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Net wo rkManager doe s not us e RA, but re que s ts information from DHCPv6
dire ctly to cre ate a s tate ful configuration.
Manual
IPv6 parame te rs are configure d manually for a s tatic configuration.
Link-Local Only
A link-local addre s s with the fe 80::/10 pre fix is as s igne d to the inte rface .
If you s e le cte d a me thod that re quire s you to s upply manual parame te rs , e nte r de tails of
the IP addre s s for this inte rface , the ne tmas k, and the gate way in the Addresses fie ld.
Us e the Add and Delete buttons to add or re move addre s s e s . Ente r a comma-s e parate d
lis t of DNS s e rve rs in the DNS servers fie ld, and a comma-s e parate d lis t of domains in
the Search domains fie ld for any domains that you want to include in name s e rve r
lookups .
Optionally, e nte r a name for this ne twork conne ction in the DHCP client ID fie ld. This
name mus t be unique on the s ubne t. Whe n you as s ign a me aningful DHCP clie nt ID to a
conne ction, it is e as y to ide ntify this conne ction whe n trouble s hooting ne twork proble ms .
De s e le ct the Require IPv6 addressing for this connection to complete che ck box
to allow the s ys te m to make this conne ction on an IPv4-e nable d ne twork if IPv6
configuration fails but IPv4 configuration s ucce e ds .
331
332
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
333
4. Ve rify that the inte rface configuration file contains the line ONBOOT=yes. If the file
doe s not alre ady contain the line , add it now and s ave the file .
5. Exit the vi e ditor.
6. Move the inte rface configuration file back to the /etc/sysconfig/networkscripts/ dire ctory:
mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/
The de vice is now re conne cte d in anaco nda.
7. Pre s s Ctrl+Alt+F6 to re turn to anaco nda.
334
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
No te
To change your time z one configuration afte r you have comple te d the ins tallation,
us e the T ime and Dat e Pro pert ies T o o l.
Type the system-config-date command in a s he ll prompt to launch the T ime and
Dat e Pro pert ies T o o l. If you are not root, it prompts you for the root pas s word to
continue .
No te
The root us e r (als o known as the s upe rus e r) has comple te acce s s to the e ntire
s ys te m; for this re as on, logging in as the root us e r is be s t done only to pe rform
s ys te m mainte nance or adminis tration.
335
No te
To be come root, type su - at the s he ll prompt in a te rminal window and the n pre s s
Enter. The n, e nte r the root pas s word and pre s s Enter.
The ins tallation program prompts you to s e t a root pas s word [11] for your s ys te m. . You
cannot proceed to the next stage of the installation process without entering a root
password.
The root pas s word mus t be at le as t s ix characte rs long; the pas s word you type is not
e choe d to the s cre e n. You mus t e nte r the pas s word twice ; if the two pas s words do not
match, the ins tallation program as ks you to e nte r the m again.
You s hould make the root pas s word s ome thing you can re me mbe r, but not s ome thing that
is e as y for s ome one e ls e to gue s s . Your name , your phone numbe r, qwerty, password,
root, 123456, and anteater are all e xample s of bad pas s words . Good pas s words mix
nume rals with uppe r and lowe r cas e le tte rs and do not contain dictionary words :
Aard387vark or 420BMttNT, for e xample . Re me mbe r that the pas s word is cas e -s e ns itive . If
you write down your pas s word, ke e p it in a s e cure place . Howe ve r, it is re comme nde d
that you do not write down this or any pas s word you cre ate .
Cho o se yo ur o wn passwo rd
Do not us e one of the e xample pas s words offe re d in this manual. Us ing one of
the s e pas s words could be cons ide re d a s e curity ris k.
To change your root pas s word afte r you have comple te d the ins tallation, run the passwd
command as root. If you forge t the root pas s word, s e e Re s olving Proble ms in Sys te m
Re cove ry Mode s in the Re d Hat Ente rpris e Linux 6 De ployme nt Guide for ins tructions on
how to s e t a ne w one .
336
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
337
338
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Ce rtain RAID s ys te ms or othe r nons tandard configurations may be unre adable to the
ins tallation program and the prompt to initializ e the hard dis k may appe ar. The ins tallation
program re s ponds to the phys ical dis k s tructure s it is able to de te ct.
To e nable automatic initializ ing of hard dis ks for which it turns out to be ne ce s s ary, us e
the kicks tart command zerombr (re fe r to Chapte r 32, Kickstart Installations). This command
is re quire d whe n pe rforming an unatte nde d ins tallation on a s ys te m with pre vious ly
initializ e d dis ks .
The ins tallation s ys te m automatically de te cts any e xis ting ins tallation of Re d Hat
Ente rpris e Linux. The upgrade proce s s update s the e xis ting s ys te m s oftware with ne w
ve rs ions , but doe s not re move any data from us e rs ' home dire ctorie s . The e xis ting
partition s tructure on your hard drive s doe s not change . Your s ys te m configuration
change s only if a package upgrade de mands it. Mos t package upgrade s do not change
s ys te m configuration, but rathe r ins tall an additional configuration file for you to e xamine
late r.
Note that the ins tallation me dium that you are us ing might not contain all the s oftware
package s that you ne e d to upgrade your compute r.
339
340
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Partitioning allows you to divide your s torage de vice s into is olate d s e ctions , whe re e ach
s e ction be have s as a s e parate Linux de vice . Partitioning is particularly us e ful if you run
multiple ope rating s ys te ms , or wis h to e nforce a logical or functional dis tinction be twe e n
your s torage partitions (s uch as a /home partition that pe rs is te ntly contains us e r
information).
341
Warning
If you s e le ct this option, all data on the s e le cte d DASD and SCSI s torage
de vice s is re move d by the ins tallation program.
Replace Exist ing Linux Syst em(s)
Se le ct this option to re move only Linux partitions (partitions cre ate d from a
pre vious Linux ins tallation). This doe s not re move othe r partitions you may have
on your s torage de vice s (s uch as z /VM or z /OS partitions ).
Shrink Current Syst em
Se le ct this option to re s iz e your curre nt data and partitions manually and ins tall a
de fault Re d Hat Ente rpris e Linux layout in the s pace that is fre e d.
Warning
If you s hrink partitions on which othe r ope rating s ys te ms are ins talle d, you
might not be able to us e thos e ope rating s ys te ms . Although this partitioning
option doe s not de s troy data, ope rating s ys te ms typically re quire s ome
fre e s pace in the ir partitions . Be fore you re s iz e a partition that holds an
ope rating s ys te m that you might want to us e again, find out how much
s pace you ne e d to le ave fre e .
Use Free Space
Se le ct this option to re tain your curre nt data and partitions and ins tall Re d Hat
Ente rpris e Linux in the unus e d s pace available on the s torage drive s . Ens ure that
the re is s ufficie nt s pace available on the s torage drive s be fore you s e le ct this
option re fe r to Se ction 18.1, Pre -Ins tallation.
Creat e Cust o m Layo ut
Se le ct this option to partition s torage de vice s manually and cre ate cus tomiz e d
layouts . Re fe r to Se ction 23.15, Cre ating a Cus tom Layout or Modifying the
De fault Layout
Choos e your pre fe rre d partitioning me thod by clicking the radio button to the le ft of its
de s cription in the dialog box.
342
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
343
Do no t place
/usr
or
/var
If /usr or /var is partitione d s e parate ly from the re s t of the root volume , the boot
proce s s be come s much more comple x be caus e the s e dire ctorie s contain bootcritical compone nts . In s ome s ituations , s uch as whe n the s e dire ctorie s are place d
on an iSCSI drive or an FCoE location, the s ys te m may e ithe r be unable to boot, or it
may hang with a Device is busy e rror whe n powe ring off or re booting.
This limitation only applie s to /usr or /var; not to dire ctorie s be low the m. For
e xample , a s e parate partition for /var/www will work without is s ue s .
Anaco nda can handle the partitioning re quire me nts for a typical ins tallation.
344
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
345
T ype
the type of partition. If the partition is a s tandard partition, this fie ld dis plays the
type of file s ys te m on the partition (for e xample , e xt4). Othe rwis e , it indicate s
that the partition is a physical volume (LVM), or part of a software RAID
Fo rmat
A che ck mark in this column indicate s that the partition will be formatte d during
ins tallation.
Be ne ath the lowe r pane are four buttons : Create, Edit, Delete, and Reset.
Se le ct a de vice or partition by clicking on it in e ithe r the graphical re pre s e ntation in the
uppe r pane of in the lis t in the lowe r pane , the n click one of the four buttons to carry out
the following actions :
Creat e
cre ate a ne w partition, logical volume , or s oftware RAID
Edit
change an e xis ting partition, logical volume , or s oftware RAID. Note that you can
only s hrink partitions with the Resize button, not e nlarge partitions .
Delet e
re move a partition, logical volume , or s oftware RAID
Reset
undo all change s made in this s cre e n
Finally, note which de vice is as s ociate d with /boot. The ke rne l file s and bootloade r s e ctor
will be as s ociate d with this de vice . The firs t DASD or SCSI LUN will be us e d, and the
de vice numbe r will be us e d whe n re -IPLing the pos t-ins talle d s ys te m.
346
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
347
RAID Device combine two or more RAID partitions into a s oftware RAID de vice . Whe n
you choos e this option, you can s pe cify the type of RAID de vice to cre ate (the RAID
level). This option is only available whe n two or more RAID partitions are available on
the s ys te m.
Creat e LVM Lo gical Vo lume
Re fe r to Se ction 23.15.4, Cre ate LVM Logical Volume for more de tail.
LVM Physical Volume cre ate a physical volume in unallocate d s pace .
LVM Volume Group cre ate a volume group from one or more phys ical volume s . This
option is only available whe n at le as t one phys ical volume is available on the s ys te m.
LVM Logical Volume cre ate a logical volume on a volume group. This option is only
available whe n at le as t one volume group is available on the s ys te m.
No te
You mus t de dicate at le as t one partition for this ins tallation, and optionally more . For
more information, re fe r to Appe ndix A, An Introduction to Disk Partitions.
348
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
349
swap Swap partitions are us e d to s upport virtual me mory. In othe r words , data is
writte n to a s wap partition whe n the re is not e nough RAM to s tore the data your s ys te m
is proce s s ing. Re fe r to the Red Hat Enterprise Linux Deployment Guide for additional
information.
software RAID Cre ating two or more s oftware RAID partitions allows you to cre ate a
RAID de vice . For more information re garding RAID, re fe r to the chapte r RAID (Redundant
Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide.
physical volume (LVM) Cre ating one or more phys ical volume (LVM) partitions
allows you to cre ate an LVM logical volume . LVM can improve pe rformance whe n us ing
phys ical dis ks . For more information re garding LVM, re fe r to the Red Hat Enterprise
Linux Deployment Guide.
File syst ems
ext4 The e xt4 file s ys te m is bas e d on the e xt3 file s ys te m and fe ature s a numbe r
of improve me nts . The s e include s upport for large r file s ys te ms and large r file s , fas te r
and more e fficie nt allocation of dis k s pace , no limit on the numbe r of s ubdire ctorie s
within a dire ctory, fas te r file s ys te m che cking, and more robus t journaling. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt4. The e xt4 file s ys te m is s e le cte d by
de fault and is highly re comme nde d.
ext3 The e xt3 file s ys te m is bas e d on the e xt2 file s ys te m and has one main
advantage journaling. Us ing a journaling file s ys te m re duce s time s pe nt re cove ring a
file s ys te m afte r a cras h as the re is no ne e d to fsck [12] the file s ys te m. A maximum
file s ys te m s iz e of 16TB is s upporte d for e xt3.
ext2 An e xt2 file s ys te m s upports s tandard Unix file type s (re gular file s , dire ctorie s ,
s ymbolic links , e tc). It provide s the ability to as s ign long file name s , up to 255
characte rs .
xfs XFS is a highly s calable , high-pe rformance file s ys te m that s upports file s ys te ms
up to 16 e xabyte s (approximate ly 16 million te rabyte s ), file s up to 8 e xabyte s
(approximate ly 8 million te rabyte s ) and dire ctory s tructure s containing te ns of millions
of e ntrie s . XFS s upports me tadata journaling, which facilitate s quicke r cras h re cove ry.
The XFS file s ys te m can als o be de fragme nte d and re s iz e d while mounte d and active .
350
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Be caus e Btrfs is s till e xpe rime ntal and unde r de ve lopme nt, the ins tallation program
doe s not offe r it by de fault. If you want to cre ate a Btrfs partition on a drive , you mus t
comme nce the ins tallation proce s s with the boot option btrfs. Re fe r to Chapte r 28,
Boot Options for ins tructions .
351
352
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
353
RAID 5 dis tribute s data and parity information acros s multiple s torage
de vice s . Le ve l 5 RAIDs the re fore offe r the pe rformance advantage s of
dis tributing data acros s multiple de vice s , but do not s hare the pe rformance
bottle ne ck of le ve l 4 RAIDs be caus e the parity information is als o dis tribute d
through the array. RAID 5 re quire s at le as t thre e RAID partitions .
RAID 6 le ve l 6 RAIDs are s imilar to le ve l 5 RAIDs , but ins te ad of s toring only
one s e t of parity data, the y s tore two s e ts . RAID 6 re quire s at le as t four RAID
partitions .
RAID 10 le ve l 10 RAIDs are nested RAIDs or hybrid RAIDs. Le ve l 10 RAIDs
are cons tructe d by dis tributing data ove r mirrore d s e ts of s torage de vice s . For
e xample , a le ve l 10 RAID cons tructe d from four RAID partitions cons is ts of two
pairs of partitions in which one partition mirrors the othe r. Data is the n
dis tribute d acros s both pairs of s torage de vice s , as in a le ve l 0 RAID. RAID 10
re quire s at le as t four RAID partitions .
354
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
355
356
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
357
If you are ce rtain that you want to proce e d, click Write changes to disk.
Installing in text mo de
If you ins tall Re d Hat Ente rpris e Linux in te xt mode , you cannot make package
s e le ctions . The ins talle r automatically s e le cts package s only from the bas e and core
groups . The s e package s are s ufficie nt to e ns ure that the s ys te m is ope rational at
the e nd of the ins tallation proce s s , re ady to ins tall update s and ne w package s . To
change the package s e le ction, comple te the ins tallation, the n us e the Add/Remo ve
So f t ware application to make de s ire d change s .
358
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
359
Warning
Minimal ins tallation curre ntly doe s not configure the fire wall
(iptables/ip6tables) by de fault be caus e the authconfig and system-configfirewall-base package s are mis s ing from the s e le ction. To work around this
is s ue , you can us e a Kicks tart file to add the s e package s to your s e le ction.
Se e the Re d Hat Cus tome r Portal for de tails about the workaround, and
Chapte r 32, Kickstart Installations for information about Kicks tart file s .
If you do not us e the workaround, the ins tallation will comple te s ucce s s fully,
but no fire wall will be configure d, pre s e nting a s e curity ris k.
If you choos e to acce pt the curre nt package lis t, s kip ahe ad to Se ction 23.18, Ins talling
Package s .
To s e le ct a compone nt, click on the che ckbox be s ide it (re fe r to Figure 23.47, Package
Group Se le ction).
To cus tomiz e your package s e t furthe r, s e le ct the Customize now option on the s cre e n.
Clicking Next take s you to the Package Group Selection s cre e n.
360
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
361
362
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
No te 31-bit applicatio ns
Us e rs of IBM Sys te m z who want s upport for de ve loping or running le gacy 31-bit
applications are e ncourage d to s e le ct the Compatibility Arch Support and
Compatibility Arch Development Support package s to ins tall archite cture
s pe cific s upport for the ir s ys te ms .
Se le ct Customize now to s pe cify the s oftware package s for your final s ys te m in more
de tail. This option caus e s the ins tallation proce s s to dis play an additional cus tomiz ation
s cre e n whe n you s e le ct Next.
363
To vie w the package groups for a cate gory, s e le ct the cate gory from the lis t on the le ft.
The lis t on the right dis plays the package groups for the curre ntly s e le cte d cate gory.
To s pe cify a package group for ins tallation, s e le ct the che ck box ne xt to the group. The
box at the bottom of the s cre e n dis plays the de tails of the package group that is curre ntly
highlighte d. None of the package s from a group will be ins talle d unle s s the che ck box for
that group is s e le cte d.
If you s e le ct a package group, Re d Hat Ente rpris e Linux automatically ins talls the bas e and
mandatory package s for that group. To change which optional package s within a s e le cte d
group will be ins talle d, s e le ct the Optional Packages button unde r the de s cription of the
group. The n us e the che ck box ne xt to an individual package name to change its s e le ction.
In the package s e le ction lis t on the right, you can us e the conte xt me nu as a s hortcut to
s e le ct or de -s e le ct bas e and mandatory package s or all optional package s .
364
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Congratulations ! Your Re d Hat Ente rpris e Linux ins tallation is now comple te !
The ins tallation program prompts you to pre pare your s ys te m for re boot.
The ins tallation program automatically re boots into the ins talle d s ys te m.
Should the ins tallation program not re boot, the ins tallation program s hows information from
which de vice to do an IPL (boot). Acce pt the s hutdown option and afte r s hutdown, IPL from
the DASD or SCSI LUN whe re the /boot partition for Re d Hat Ente rpris e Linux has be e n
ins talle d.
No te
To dis conne ct from the 3270 te rminal without s topping the Linux running in your
virtual machine , us e #cp disconnect ins te ad of #cp logoff. Whe n your virtual
machine is re -conne cte d us ing the us ual logon proce dure , it might be place d in CP
cons ole function mode (CP READ). If s o, to re s ume e xe cution on your virtual
machine , e nte r the BEGIN command.
366
C hapt e r 23. Ins t allat io n Phas e 3: Ins t alling Us ing Anac o nda
Following the automatic re boot or the manual IPL of the ins talle d Re d Hat Ente rpris e Linux
ope rating s ys te m, you can log on to the s ys te m via ssh. Note that the only place from
which you can log in as root is from the 3270 te rminal or from othe r te rminal de vice s
lis te d in /etc/securetty.
The firs t time you s tart your Re d Hat Ente rpris e Linux s ys te m in a graphical e nvironme nt,
you can us e First Bo o t to guide you through Re d Hat Ente rpris e Linux configuration. Us ing
this tool, you can s e t your s ys te m time and date , ins tall s oftware , re gis te r your machine
with Re d Hat Ne twork, and more . First Bo o t le ts you configure your e nvironme nt at the
be ginning, s o that you can ge t s tarte d us ing your Re d Hat Ente rpris e Linux s ys te m quickly.
Chapte r 34, Firstboot will guide you through the configuration proce s s .
[11] A root password is the adm inistrative password for your Red Hat Enterprise Linux system .
You should only log in as root when needed for system m aintenance. The root account does
not operate within the restrictions placed on norm al user accounts, so changes m ade as root
can have im plications for your entire system .
[12] The fsck application is used to check the file system for m etadata consistency and
optionally repair one or m ore Linux file system s.
367
24.1. You Are Unable t o Boot Red Hat Ent erprise Linux
24.1.1. Is Your Syst em Displaying Signal 11 Errors?
A s ignal 11 e rror, commonly known as a segmentation fault, me ans that the program
acce s s e d a me mory location that was not as s igne d to it. A s ignal 11 e rror may be due to a
bug in one of the s oftware programs that is ins talle d, or faulty hardware .
Ens ure that you have the late s t ins tallation update s and image s from Re d Hat. Re vie w the
online e rrata to s e e if ne we r ve rs ions are available .
368
Additionally, make s ure you format the DASDs us ing the dasdfmt command within a Linux
root s he ll, ins te ad of formatting the DASDs us ing CMS. Anaco nda automatically de te cts
any DASD de vice s that are not ye t formatte d and as ks you whe the r to format the de vice s .
369
370
371
372
Figure 24.6. Ent er Red Hat Net wo rk aut hent icat io n det ails
Repo rt uplo ader
Spe cify a URL for uploading a compre s s e d ve rs ion of the cras h re port.
373
374
You can now cus tomiz e the re port by che cking and unche cking the is s ue s that will be
include d. Whe n finis he d, click Apply.
375
Re porting is now comple te . Click Forward to re turn to the re port s e le ction dialog. You can
now make anothe r re port, or click Close to e xit the re porting utility and the n Exit to clos e
the ins tallation proce s s .
No te
Whe n de fining a partition's type as s wap, do not as s ign it a mount point. Anaco nda
automatically as s igns the mount point for you.
376
The command conne cts to the re mote X11 s e rve r via XDMCP (re place
s390vm.example.com with the hos tname of the re mote X11 s e rve r) and dis plays the
re mote graphical login s cre e n on dis play :1 of the X11 s e rve r s ys te m (us ually acce s s ible
by us ing the Ctrl-Alt-F8 ke y combination).
You can als o acce s s re mote de s ktop s e s s ions us ing a nested X11 s e rve r, which ope ns
the re mote de s ktop as a window in your curre nt X11 s e s s ion. Xnest allows us e rs to ope n
a re mote de s ktop ne s te d within the ir local X11 s e s s ion. For e xample , run Xnest us ing the
following command, re placing s390vm.example.com with the hos tname of the re mote X11
s e rve r:
Xnest :1 -query s390vm.example.com
localhost.localdomain
localhost
377
No te
Make s ure the de vice is attache d or linke d to the Linux s ys te m if running unde r
z /VM.
CP ATTACH EB1C TO *
To link a mini dis k to which you have acce s s , is s ue , for e xample :
CP LINK RHEL6X 4B2E 4B2E MR
DASD 4B2E LINKED R/W
Se e z/VM: CP Commands and Utilities Reference, SC24-6175 for de tails about the s e
commands .
378
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
379
The lis t of ignore d de vice s (cio_ignore) is handle d trans pare ntly for pe rs is te nt de vice
configurations . You do not ne e d to fre e de vice s from the ignore lis t manually.
380
5e:00
5e:01
dasda
0201
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
381
0.0.0207
0.0.0200 use_diag=1 readonly=1
Modifications of /etc/dasd.conf only be come e ffe ctive afte r a re boot of the s ys te m or
afte r the dynamic addition of a ne w DASD by changing the s ys te m's I/O configuration (that
is , the DASD is attache d unde r z /VM). Alte rnative ly, you can trigge r the activation of a ne w
e ntry in /etc/dasd.conf for a DASD which was pre vious ly not active , by e xe cuting the
following commands :
Pro cedure 25.3. Permanent ly At t aching DASDs as No n-ro o t Devices
Trigge r the activation by writing to the uevent attribute of the de vice :
echo add > /sys/bus/ccw/devices/device.bus,ID/uevent
For e xample :
echo add > /sys/bus/ccw/devices/0.0.021a/uevent
Warning
This proce dure will wipe all e xis ting data on the dis k. Make s ure to back up any data
you want to ke e p be fore proce e ding.
382
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
No te
To add additional dis ks late r without bre aking e xis ting dis k e ntrie s in, for e xample ,
/etc/fstab, us e the pe rs is te nt de vice s ymbolic links unde r /dev/disk/by-path/.
383
If your s ys te m us e s LVM, you ne e d to e xpand an e xis ting volume group and one or more
logical volume s s o that the y contain the ne w DASD which you attache d by following the
proce dure s de s cribe d e arlie r in this chapte r. Othe rwis e , the DASD will be attache d to the
s ys te m, but you will not be able to us e it.
The following proce dure e xplains how to us e the e ntire capacity of the ne w DASD to
e xpand an e xis ting logical volume . If you want to us e the ne w DASD for multiple logical
volume s , you will ne e d to cre ate multiple LVM phys ical volume s on this partition, and
re pe at this proce dure for e ach logical volume (and volume group) you want to e xpand.
This proce dure as s ume s you followe d the s te ps in Se ction 25.1.1, Dynamically Se tting
DASDs Online to attach the ne w DASD dynamically, the n Se ction 25.1.2.1, DASDs Which
Are Part of the Root File Sys te m to attach it pe rs is te ntly and pre pare it to be us e d for the
root volume , and that you formatte d it as de s cribe d in Se ction 25.1.4, Pre paring a Ne w
DASD with Low-le ve l Formatting and cre ate d a s ingle partition on it.
Pro cedure 25.5. Expanding Exist ing Lo gical Vo lume t o Use a New DASD
1. Cre ate a ne w phys ical volume for LVM on the DASD us ing the pvcreate command:
# pvcreate /dev/DeviceName
Impo rtant
The de vice name mus t be s pe cifie d as a partition - for e xample ,
/dev/dasdf1. Do not s pe cify the e ntire block de vice .
2. Lis t e xis ting phys ical volume s us ing the pvs command to ve rify that the phys ical
volume has be e n cre ate d:
# pvs
PV
VG
Fmt Attr PSize
PFree
/dev/dasda2
vg_local
lvm2 a-1,29g
0
/dev/dasdd1
vg_local
lvm2 a-2,29g
0
/dev/dasdf1
lvm2 a-2,29g
2,29g
/dev/mapper/mpathb vgextnotshared lvm2 a-- 200,00g 1020,00m
As you can s e e in the above e xample , /dev/dasdf1 now contains an e mpty
phys ical volume which is not as s igne d to any volume group.
3. Us e the vgextend command to e xpand an e xis ting volume group containing the
volume you want to us e the ne w DASD for:
# vgextend VolumeGroup PhysicalVolume
Re place VolumeGroup with the name of the volume group you are e xpanding, and
PhysicalVolume with the name of the phys ical volume (for e xample , /dev/dasdf1).
4. Us e the lvextend command to e xpand a logical volume you want to us e the ne w
DASD for:
# lvextend -L +Size /dev/mapper/VolumeGroup-LogicalVolume
For e xample :
384
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
No te
If running unde r z /VM, make s ure the FCP adapte r is attache d to the z /VM gue s t
virtual machine . For multipathing in production e nvironme nts the re would be at le as t
two FCP de vice s on two diffe re nt phys ical adapte rs (CHPIDs ). For e xample :
CP ATTACH FC00 TO *
CP ATTACH FCD0 TO *
385
18:17
18:19
18:17
18:17
18:19
18:17
18:17
18:19
18:19
18:19
18:19
18:19
18:19
18:19
18:17
failed
hardware_version
host0
in_recovery
lic_version
modalias
online
peer_d_id
peer_wwnn
peer_wwpn
port_remove
port_rescan
power
status
subsystem ->
28 18:17 uevent
4. Activate the FCP LUN by adding it to the port (WWPN) through which you would like to
acce s s the LUN:
# echo 0x4020400100000000 >
/sys/bus/ccw/drivers/zfcp/0.0.fc00/0x50050763050b073d/unit_add
5. Find out the as s igne d SCSI de vice name :
# lszfcp -DV
/sys/devices/css0/0.0.0015/0.0.fc00/0x50050763050b073d/0x402040010
0000000
/sys/bus/ccw/drivers/zfcp/0.0.fc00/host0/rport-0:021/target0:0:21/0:0:21:1089355792
For more information, re fe r to the chapte r on SCSI-ove r-Fibre Channe l in Linux on System z
Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6.
386
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
Re d Hat Ente rpris e Linux provide s a parame te r to activate FCP LUNs e arly in the boot
proce s s : rd_ZFCP=. The value is a comma-s e parate d lis t containing the de vice bus ID, the
WWPN as 16 digit he xade cimal numbe r pre fixe d with 0x, and the FCP LUN pre fixe d with 0x
and padde d with z e roe s to the right to have 16 he xade cimal digits .
The following e xample zipl.conf is for a s ys te m that us e s phys ical volume s on partitions
of two FCP LUNs for an LVM volume group vg_devel1 that contains a logical volume
lv_root for the root file s ys te m. For s implicity, the e xample s hows a configuration without
multipathing.
[defaultboot]
default=linux
target=/boot/
[linux]
image=/boot/vmlinuz-2.6.32-19.el6.s390x
ramdisk=/boot/initramfs-2.6.32-19.el6.s390x.img
parameters="root=/dev/mapper/vg_devel1-lv_root
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a000000000
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a100000000
rd_LVM_LV=vg_devel1/lv_root rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us cio_ignore=all,!0.0.0009"
To add anothe r phys ical volume on a partition of a third FCP LUN with de vice bus ID
0.0.fc00, WWPN 0x5105074308c212e 9 and FCP LUN 0x401040a300000000, s imply add
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a300000000 to the parame te rs line of
your boot ke rne l in zipl.conf, for e xample :
[defaultboot]
default=linux
target=/boot/
[linux]
image=/boot/vmlinuz-2.6.32-19.el6.s390x
ramdisk=/boot/initramfs-2.6.32-19.el6.s390x.img
parameters="root=/dev/mapper/vg_devel1-lv_root
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a000000000
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a100000000
rd_ZFCP=0.0.fc00,0x5105074308c212e9,0x401040a300000000
rd_LVM_LV=vg_devel1/lv_root rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us cio_ignore=all,!0.0.0009"
Run zipl to apply the change s of /etc/zipl.conf for the ne xt IPL:
# zipl -V
Using config file '/etc/zipl.conf'
Target device information
Device..........................: 08:00
Partition.......................: 08:01
Device name.....................: sda
Device driver name..............: sd
Type............................: disk partition
Disk layout.....................: SCSI disk layout
Geometry - start................: 2048
File system block size..........: 4096
387
25.2.2.2. FCP LUNs T hat Are Not Part of t he Root File Syst em
FCP LUNs that are not part of the root file s ys te m, s uch as data dis ks , are pe rs is te ntly
configure d in the file /etc/zfcp.conf. It contains one FCP LUN pe r line . Each line contains
the de vice bus ID of the FCP adapte r, the WWPN as 16 digit he xade cimal numbe r pre fixe d
with 0x, and the FCP LUN pre fixe d with 0x and padde d with z e roe s to the right to have 16
he xade cimal digits , s e parate d by a s pace or tab. Entrie s in /etc/zfcp.conf are activate d
and configure d by ude v whe n an FCP adapte r is adde d to the s ys te m. At boot time , all FCP
adapte rs vis ible to the s ys te m are adde d and trigge r udev.
Example conte nt of /e tc/z fcp.conf:
0.0.fc00
0.0.fc00
0.0.fc00
0.0.fcd0
0.0.fcd0
0.0.fcd0
0x5105074308c212e9
0x5105074308c212e9
0x5105074308c212e9
0x5105074308c2aee9
0x5105074308c2aee9
0x5105074308c2aee9
0x401040a000000000
0x401040a100000000
0x401040a300000000
0x401040a000000000
0x401040a100000000
0x401040a300000000
388
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
# cio_ignore -r fcfc
2. To trigge r the ue ve nt that activate s the change , is s ue :
echo add > /sys/bus/ccw/devices/Device.Bus.ID/uevent
For e xample :
echo add > /sys/bus/ccw/devices/0.0.fcfc/uevent
389
The value n is an inte ge r that unique ly ide ntifie s the de vice . n is 0 for the firs t de vice of
that type , 1 for the s e cond, and s o on.
390
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
5. Optionally, you can als o pas s argume nts that are configure d on the group de vice
be fore it is s e t online :
# znetconf -a f500 -o portname=myname
Scanning for network devices...
Successfully configured device 0.0.f500 (eth1)
Now you can continue to configure the ne twork eth1 inte rface .
Alte rnative ly, you can us e s ys fs attribute s to s e t the de vice online as follows :
1. Cre ate a qe th group de vice :
# echo read_device_bus_id,write_device_bus_id,data_device_bus_id >
/sys/bus/ccwgroup/drivers/qeth/group
For e xample :
# echo 0.0.f500,0.0.f501,0.0.f502 >
/sys/bus/ccwgroup/drivers/qeth/group
2. Ne xt, ve rify that the qe th group de vice was cre ate d prope rly by looking for the
re ad channe l:
# ls /sys/bus/ccwgroup/drivers/qeth/0.0.f500
You may optionally s e t additional parame te rs and fe ature s , de pe nding on the way
you are s e tting up your s ys te m and the fe ature s you re quire , s uch as :
portno
layer2
portname
For information on additional parame te rs , re fe r to the chapte r on the qe th de vice
drive r in Linux on System z Device Drivers, Features, and Commands on Red Hat
Enterprise Linux 6.
3. Bring the de vice online by writing 1 to the online s ys fs attribute :
# echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.f500/online
4. The n ve rify the s tate of the de vice :
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.f500/online
1
A re turn value of 1 indicate s that the de vice is online , while a re turn value 0
indicate s that the de vice is offline .
5. Find the inte rface name that was as s igne d to the de vice :
391
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.f500/if_name
eth1
Now you can continue to configure the ne twork eth1 inte rface .
The following command from the s390utils package s hows the mos t important
s e ttings of your qe th de vice :
# lsqeth eth1
Device name
: eth1
--------------------------------------------card_type
: OSD_1000
cdev0
: 0.0.f500
cdev1
: 0.0.f501
cdev2
: 0.0.f502
chpid
: 76
online
: 1
portname
: OSAPORT
portno
: 0
state
: UP (LAN ONLINE)
priority_queueing
: always queue 0
buffer_count
: 16
layer2
: 1
isolation
: none
392
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
znetconf -c
Device IDs
Type
Card Type
CHPID Drv. Name
State
------------------------------------------------------------------------------0.0.8036,0.0.8037,0.0.8038 1731/05 HiperSockets
FB qeth hsi1
online
0.0.f5f0,0.0.f5f1,0.0.f5f2 1731/01 OSD_1000
76 qeth eth0
online
393
5. Make s ure the SUBCHANNELS s tate me nt matche s the hardware addre s s e s for your
qe th de vice .
6. Modify the PORTNAME s tate me nt or le ave it out if it is not ne ce s s ary in your
e nvironme nt.
7. You may add any valid s ys fs attribute and its value to the OPTIONS parame te r. The
Re d Hat Ente rpris e Linux ins talle r curre ntly us e s this to configure the laye r mode
(layer2) and the re lative port numbe r (portno) of qe th de vice s .
The qe th de vice drive r de fault for OSA de vice s is now laye r 2 mode . To continue
us ing old ifcfg de finitions that re ly on the pre vious de fault of laye r 3 mode , add
layer2=0 to the OPTIONS parame te r.
/etc/sysconfig/network-scripts/ifcfg-eth1
# IBM QETH
DEVICE=eth1
BOOTPROTO=static
IPADDR=192.168.70.87
NETMASK=255.255.255.0
ONBOOT=yes
NETTYPE=qeth
SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
PORTNAME=OSAPORT
OPTIONS='layer2=1 portno=0'
MACADDR=02:00:00:b3:84:ef
TYPE=Ethernet
Change s to an ifcfg file only be come e ffe ctive afte r re booting the s ys te m or afte r the
dynamic addition of ne w ne twork de vice channe ls by changing the s ys te m's I/O
configuration (for e xample , attaching unde r z /VM). Alte rnative ly, you can trigge r the
activation of a ifcfg file for ne twork channe ls which we re pre vious ly not active ye t, by
e xe cuting the following commands :
1. Us e the cio_ignore command to re move the ne twork channe ls from the lis t of
ignore d de vice s and make the m vis ible to Linux:
# cio_ignore -r
read_device_bus_id,write_device_bus_id,data_device_bus_id
Re place read_device_bus_id,write_device_bus_id,data_device_bus_id with the thre e
de vice bus IDs re pre s e nting a ne twork de vice . For e xample , if the
read_device_bus_id is 0.0.0600, the write_device_bus_id is 0.0.0601, and the
data_device_bus_id is 0.0.0602:
# cio_ignore -r 0.0.0600,0.0.0601,0.0.0602
2. To trigge r the ue ve nt that activate s the change , is s ue :
echo add > /sys/bus/ccw/devices/read-channel/uevent
For e xample :
echo add > /sys/bus/ccw/devices/0.0.0600/uevent
394
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
Genmask
255.255.255.0
255.255.255.0
0.0.0.0
UG
7. Ve rify your change s by us ing the ping command to ping the gate way or anothe r
hos t on the s ubne t of the ne w de vice :
# ping -c 1 192.168.70.8
PING 192.168.70.8 (192.168.70.8) 56(84) bytes of data.
64 bytes from 192.168.70.8: icmp_seq=0 ttl=63 time=8.07 ms
8. If the de fault route information has change d, you mus t als o update
/etc/sysconfig/network accordingly.
395
n is 0 for the firs t de vice of that type , 1 for the s e cond, and s o on.
396
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
/etc/sysconfig/network-scripts/ifcfg-eth0
# IBM LCS
DEVICE=eth0
BOOTPROTO=static
IPADDR=10.12.20.136
NETMASK=255.255.255.0
ONBOOT=yes
NETTYPE=lcs
SUBCHANNELS=0.0.09a0,0.0.09a1
PORTNAME=0
OPTIONS=''
TYPE=Ethernet
2. Modify the value of PORTNAME to re fle ct the LCS port numbe r (portno) you would
like to us e . You can add any valid lcs s ys fs attribute and its value to the optional
OPTIONS parame te r. Re fe r to Se ction 25.3.1.3, Pe rs is te ntly Adding a qe th De vice
for the s yntax.
3. Se t the DEVICE parame te r as follows :
DEVICE=ethn
4. Is s ue an ifup command to activate the de vice :
# ifup ethn
Change s to an ifcfg file only be come e ffe ctive afte r re booting the s ys te m. You can
trigge r the activation of a ifcfg file for ne twork channe ls by e xe cuting the following
commands :
1. Us e the cio_ignore command to re move the LCS de vice adapte r from the lis t of
ignore d de vice s and make it vis ible to Linux:
# cio_ignore -r read_device_bus_id,write_device_bus_id
Re place read_device_bus_id and write_device_bus_id with the de vice bus IDs of the
LCS de vice . For e xample :
# cio_ignore -r 0.0.09a0,0.0.09a1
2. To trigge r the ue ve nt that activate s the change , is s ue :
echo add > /sys/bus/ccw/devices/read-channel/uevent
For e xample :
echo add > /sys/bus/ccw/devices/0.0.09a0/uevent
397
25.3.4. Conf iguring a Syst em z Net work Device f or Net work Root File
Syst em
To add a ne twork de vice that is re quire d to acce s s the root file s ys te m, you only have to
change the boot options . The boot options can be in a parame te r file (re fe r to Chapte r 26,
Parameter and Configuration Files) or part of a zipl.conf on a DASD or FCP-attache d SCSI
LUN pre pare d with the zipl boot loade r. The re is no ne e d to re cre ate the initramfs .
Dracut (the mkinit rd s ucce s s or that provide s the functionality in the initramfs that in
turn re place s init rd) provide s a boot parame te r to activate ne twork de vice s on Sys te m z
e arly in the boot proce s s : rd_ZNET=.
As input, this parame te r take s a comma-s e parate d lis t of the NETTYPE (qe th, lcs , ctc), two
(lcs , ctc) or thre e (qe th) de vice bus IDs , and optional additional parame te rs cons is ting of
ke y-value pairs corre s ponding to ne twork de vice s ys fs attribute s . This parame te r
398
C hapt e r 25. Co nf igur ing an Ins t alle d Linux o n Sys t e m z Ins t anc e
399
400
cio_ignore
parameter to yo ur
To avoid ins tallation proble ms aris ing from cio_ignore s upport not be ing
imple me nte d throughout the e ntire s tack, adapt the cio_ignore= parame te r value
to your s ys te m or re move the parame te r e ntire ly from your parame te r file us e d for
booting (IPL) the ins talle r.
Whe n ins talling from an FCP-attache d DVD drive , and you e ncounte r a proble m with
ignore d de vice s , s e le ct the me nu option clear blacklist in linuxrc (re fe r to
Chapte r 21, Installation Phase 1: Configuring a Network Device) to re move the lis t of
ignore d de vice s .
401
The following parame te rs can be us e d to s e t up the pre liminary ne twork automatically and
can be de fine d in e ithe r the parame te r file or the CMS configuration file . The parame te rs
in this s e ction are the only parame te rs that can als o be us e d in a CMS configuration file .
All othe r parame te rs in othe r s e ctions mus t be s pe cifie d in the parame te r file .
NETTYPE="type"
Whe re type mus t be one of the following: qeth, lcs, or ctc. The de fault is qeth.
Choos e lcs for:
OSA-2 Ethe rne t/Toke n Ring
OSA-Expre s s Fas t Ethe rne t in non-QDIO mode
OSA-Expre s s High Spe e d Toke n Ring in non-QDIO mode
Gigabit Ethe rne t in non-QDIO mode
Choos e qeth for:
OSA-Expre s s Fas t Ethe rne t
Gigabit Ethe rne t (including 1000Bas e -T)
High Spe e d Toke n Ring
Hipe rSocke ts
ATM (running Ethe rne t LAN e mulation)
SUBCHANNELS="device_bus_IDs"
Whe re bus_IDs is a comma-s e parate d lis t of two or thre e de vice bus IDs .
Provide s re quire d de vice bus IDs for the various ne twork inte rface s :
qeth:
SUBCHANNELS="read_device_bus_id,write_device_bus_id,data_device_b
us_id"
lcs or ctc: SUBCHANNELS="read_device_bus_id,write_device_bus_id"
For e xample (a s ample qe th SUBCHANNEL s tate me nt):
SUBCHANNELS="0.0.f5f0,0.0.f5f1,0.0.f5f2"
PORTNAME="osa_portname" , PORTNAME="lcs_portnumber"
This variable s upports OSA de vice s ope rating in qdio mode or in non-qdio mode .
Whe n us ing qdio mode (NETTYPE="qeth"), osa_portname is the portname
s pe cifie d on the OSA de vice whe n ope rating in qe th mode .
Whe n us ing non-qdio mode (NETTYPE="lcs"), lcs_portnumber is us e d to pas s the
re lative port numbe r as a de cimal inte ge r in the range of 0 through 15.
PORTNO="portnumber"
You can add e ithe r PORTNO="0" (to us e port 0) or PORTNO="1" (to us e port 1 of
OSA fe ature s with two ports pe r CHPID) to the CMS configuration file to avoid
be ing prompte d for the mode .
402
403
MTU="mtu"
Whe re mtu is the Maximum Transmission Unit (MTU) for this ne twork de vice .
DNS="server1:server2:additional_server_terms:serverN"
Whe re "server1:server2:additional_server_terms:serverN" is a lis t of DNS s e rve rs ,
s e parate d by colons . For e xample :
DNS="10.1.2.3:10.3.2.1"
SEARCHDNS="domain1:domain2:additional_dns_terms:domainN"
Whe re "domain1:domain2:additional_dns_terms:domainN" is a lis t of the s e arch
domains , s e parate d by colons . For e xample :
SEARCHDNS="subdomain.domain:domain"
You only ne e d to s pe cify SEARCHDNS= if you s pe cify the DNS= parame te r.
DASD=
De fine s the DASD or range of DASDs to configure for the ins tallation. For a
de taile d de s cription of the s yntax, re fe r to the dasd_mod de vice drive r module
option de s cribe d in the chapte r on the DASD de vice drive r in Linux on System z
Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6.
Linuxrc s upports a comma-s e parate d lis t of de vice bus IDs or of range s of
de vice bus IDs with the optional attribute s ro, diag, erplog, and failfast.
Optionally, you can abbre viate de vice bus IDs to de vice numbe rs with le ading
z e ros s trippe d. Any optional attribute s s hould be s e parate d by colons and
e nclos e d in pare nthe s e s . Optional attribute s follow a de vice bus ID or a range of
de vice bus IDs .
The only s upporte d global option is autodetect. This doe s not s upport the
s pe cification of non-e xis te nt DASDs to re s e rve ke rne l de vice name s for late r
addition of DASDs . Us e pe rs is te nt DASD de vice name s (for e xample
/dev/disk/by-path/...) to e nable trans pare nt addition of dis ks late r. Othe r
global options s uch as probeonly, nopav, or nofcx are not s upporte d by linuxrc.
Only s pe cify thos e DASDs that you re ally ne e d to ins tall your s ys te m. All
unformatte d DASDs s pe cifie d he re mus t be formatte d afte r a confirmation late r
on in the ins talle r (re fe r to Se ction 23.6.1.1, DASD low-le ve l formatting). Add any
data DASDs that are not ne e de d for the root file s ys te m or the /boot partition
afte r ins tallation as de s cribe d in Se ction 25.1.3, DASDs Which Are Not Part of the
Root File Sys te m.
For FCP-only e nvironme nts , s pe cify DASD="none".
For e xample :
DASD="eb1c,0.0.a000-0.0.a003,eb10-eb14(diag),0.0.ab1c(ro:diag)"
FCP_n="device_bus_ID WWPN FCP_LUN"
Whe re :
404
n is typically an inte ge r value (for e xample FCP_1 or FCP_2) but could be any
s tring with alphabe tic or nume ric characte rs or unde rs core s .
device_bus_ID s pe cifie s the de vice bus ID of the FCP de vice re pre s e nting the
host bus adapter (HBA) (for e xample 0.0.fc00 for de vice fc00).
WWPN is the world wide port name us e d for routing (ofte n in conjunction with
multipathing) and is as a 16-digit he x value (for e xample
0x50050763050b073d).
FCP_LUN re fe rs to the s torage logical unit ide ntifie r and is s pe cifie d as a 16digit he xade cimal value padde d with z e roe s to the right (for e xample
0x4020400100000000).
The s e variable s can be us e d on s ys te ms with FCP de vice s to activate FCP LUNs
s uch as SCSI dis ks . Additional FCP LUNs can be activate d during the ins tallation
inte ractive ly or by me ans of a kicks tart file . The re is no inte ractive que s tion for
FCP in linuxrc. An e xample value may look s imilar to the following:
FCP_1="0.0.fc00 0x50050763050b073d 0x4020400100000000"
405
This parame te r s e ts the pas s word us e d to conne ct to the VNC s e rve r. The
pas s word parame te r is optional. If not us e d, the VNC s e rve r doe s not us e a
pas s word and anybody can conne ct to the VNC s e rve r.
vncconnect=IP/hostname[:port]
Whe n us e d in addition to vnc and vncpassword=, this optional parame te r
s pe cifie s the hos tname or IP addre s s (and optionally, a TCP port) whe re a VNC
clie nt is running in lis te ning mode . The ins talle r conne cts to and dis plays its
graphical us e r inte rface on this VNC clie nt.
406
Whe n cmdline is s pe cifie d, output on line -mode te rminals (s uch as 3270 unde r
z /VM or ope rating s ys te m me s s age s for LPAR) be come s re adable , as the
ins talle r dis able s e s cape te rminal s e que nce s that are only applicable to UNIX-like
cons ole s . This re quire s ins tallation with a kicks tart file that ans we rs all que s tions ,
s ince the ins talle r doe s not s upport inte ractive us e r input in cmdline mode .
Ens ure that your kicks tart file contains all re quire d parame te rs be fore you us e e ithe r the
RUNKS or cmdline options . Re fe r to Chapte r 32, Kickstart Installations for de tails .
407
The boot parame te rs de s cribe d he re are the mos t us e ful for ins tallations and trouble
s hooting on Sys te m z , but only a s ubs e t of thos e that influe nce the ins talle r. Re fe r to
Chapte r 28, Boot Options for a more comple te lis t of ins talle r boot parame te rs .
408
Linux on System z Device Drivers, Features, and Commands as available with Red Hat
Enterprise Linux 6. IBM . 2010. SC34-2597.
Linux on System z Using the Dump Tools on Red Hat Enterprise Linux 6. IBM . 2010. SC342607.
Linux on System z How to use FC-attached SCSI devices with Linux on System z9 and
zSeries. IBM . 2008. SC33-8413.
How to use Execute-in-Place Technology with Linux on z/VM. IBM . 2008. SC34-2594.
Linux on System z How to Set up a Terminal Server Environment on z/VM. IBM . 2009.
SC34-2596.
Linux on System z How to Improve Performance with PAV. IBM . 2008. SC33-8414.
Introduction to the New Mainframe: z/VM Basics. IBM Re dbooks . 2007. SG24-7316.
409
z/VM and Linux on IBM System z The Virtualization Cookbook for Red Hat Enterprise Linux
5.2. IBM Re dbooks . 2008. SG24-7492.
Linux on IBM System z: Performance Measurement and Tuning. IBM Re dbooks . 2011. SG246926.
Achieving High Availability on Linux for System z with Linux-HA Release 2. IBM Re dbooks .
2009. SG24-7711.
Securit y
Using Cryptographic Adapters for Web Servers with Linux on IBM System z9 and zSeries. IBM
Re dbooks . 2006. REDP-4131.
Net wo rking
Fibre Channel Protocol for Linux and z/VM on IBM System z. IBM Re dbooks . 2007. SG247266.
410
Sharing and maintaining RHEL 5.3 Linux under z/VM. Brad Hins on and Mike MacIs aac.
http://www.linuxvm.org/Pre s e nt/mis c/ro-root-RH5.pdf .
411
412
C hapt e r 28 . Bo o t O pt io ns
Rescue Mo de
The Re d Hat Ente rpris e Linux ins tallation and rescue discs may e ithe r boot with
rescue mode, or load the ins tallation s ys te m. For more information on re s cue dis cs
and re s cue mode , re fe r to Se ction 28.6.2, Booting Your Compute r with the Re s cue
Mode .
413
Impo rtant
The rhupdates dire ctory s hould only contain anaco nda update s . The ins tallation
may fail if you add othe r file s (s uch as e rrata RPMs ) or if you place too much conte nt
in the dire ctory.
To load the anaco nda update s from a ne twork location ins te ad, us e :
linux updates=
followe d by the URL for the location whe re the update s are s tore d.
414
C hapt e r 28 . Bo o t O pt io ns
Inst allat io n
met ho d
Opt io n f o rmat
DVD drive
Hard Drive
HTTP Se rve r
HTTPS Se rve r
FTP Se rve r
NFS Se rve r
ISO image s on an
NFS Se rve r
repo=cdrom:device
repo=hd:device/path
repo=http://host/path
repo=https://host/path
repo=ftp://username:password@host/path
repo=nfs:server:/path
repo=nfsiso:server:/path
415
be fore it actually is , caus ing any ope rations which re quire ne twork acce s s (s uch
as Kicks tart file downloads ) to fail. Maximum value of this parame te r is 30 as
de fine d by Net wo rkManager; s pe cifying a value highe r than 30 will caus e the
option to be ignore d.
This e xample configure s the ne twork s e ttings for an ins tallation s ys te m that us e s the IP
addre s s 192.168.1.10 for inte rface eth0. The inte rface is name d primary, and the
s ys te m will wait for 5 s e conds or until it can s ucce s s fully ping the gate way be fore
continuing:
linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1
dns=192.168.1.3 ksdevice=eth0 ifname=primary:01:23:45:67:89:ab
nicdelay=5
If you s pe cify the ne twork configuration and ne twork de vice at the boot: prompt, the s e
s e ttings are us e d for the ins tallation proce s s and the Networking Devices and
Configure TCP/IP dialogs do not appe ar.
416
C hapt e r 28 . Bo o t O pt io ns
28.2.2. Connect ing t he Inst allat ion Syst em t o a VNC List ener
To have the ins tallation s ys te m automatically conne ct to a VNC clie nt, firs t s tart the clie nt
in lis te ning mode . On Re d Hat Ente rpris e Linux s ys te ms , us e the -listen option to run
vncviewer as a lis te ne r. In a te rminal window, e nte r the command:
vncviewer -listen
417
418
C hapt e r 28 . Bo o t O pt io ns
Re d Hat Ente rpris e Linux us e s rsyslog to provide a s ys log s e rvice . The de fault
configuration of rsyslog re je cts me s s age s from re mote s ys te ms .
28.4. Aut omat ing t he Inst allat ion wit h Kickst art
You can allow an ins tallation to run unatte nde d by us ing Kicks tart. A Kickstart file s pe cifie s
s e ttings for an ins tallation. Once the ins tallation s ys te m boots , it can re ad a Kicks tart file
and carry out the ins tallation proce s s without any furthe r input from a us e r.
419
Opt io n f o rmat
DVD drive
Hard Drive
Othe r De vice
HTTP Se rve r
HTTPS Se rve r
FTP Se rve r
NFS Se rve r
ks=cdrom:/directory/ks.cfg
ks=hd:/device/directory/ks.cfg
ks=file:/device/directory/ks.cfg
ks=http://server.mydomain.com/directory/ks.cfg
ks=https://server.mydomain.com/directory/ks.cfg
ks=ftp://server.mydomain.com/directory/ks.cfg
ks=nfs:server.mydomain.com:/directory/ks.cfg
420
C hapt e r 28 . Bo o t O pt io ns
Impo rtant
You can us e a de vice name s uch as /dev/sdb to ide ntify a hard drive or a USB
drive containing a Kicks tart file . Howe ve r, the re is no guarante e that the de vice
ide ntifie r will re main the s ame on multiple s ys te ms . The re fore , the re comme nde d
me thod for s pe cifying a hard drive or a USB drive in Kicks tart ins tallations is by
UUID. For e xample :
ks=hd:UUID=ede47e6c-8b5f-49ad-9509-774fa7119281:ks.cfg
You can de te rmine a de vice 's UUID by us ing the blkid command as root:
# blkid /dev/sdb1
/dev/sdb1: UUID="2c3a072a-3d0c-4f3a-a4a1-ab5f24f59266" TYPE="ext4"
To obtain a Kicks tart file from a s cript or application on a We b s e rve r, s pe cify the URL of
the application with the ks= option. If you add the option kssendmac, the re que s t als o
s e nds HTTP he ade rs to the We b application. Your application can us e the s e he ade rs to
ide ntify the compute r. This line s e nds a re que s t with he ade rs to the application
http://server.mydomain.com/kickstart.cgi:
linux ks=http://server.mydomain.com/kickstart.cgi kssendmac
Opt io n
noprobe
421
Co mpat ibilit y
Opt io n
headless
nopass
xdriver=vesa
noshell
acpi=off
nomce
numa-off
mem=xxxm
libata.dma=1
nodmraid
nofirewire
noparport
nopcmcia
nonet
Impo rtant
Othe r ke rne l boot options have no particular me aning for anaco nda and do not
affe ct the ins tallation proce s s . Howe ve r, if you us e the s e options to boot the
ins tallation s ys te m, anaco nda will pre s e rve the m in the bootloade r configuration.
422
C hapt e r 28 . Bo o t O pt io ns
boot Re d Hat Ente rpris e Linux with the option mediacheck option.
423
424
Whe n you are finis he d, change the default option in /boot/grub/grub.conf to point to
the ne w firs t s tanz a you adde d:
default 0
425
space pxelinux;
pxelinux.magic code
pxelinux.configfile
pxelinux.pathprefix
pxelinux.reboottime
208 = string;
code 209 = text;
code 210 = text;
code 211 = unsigned integer 32;
426
class "pxeclients" {
match if substring (option vendor-classidentifier, 0, 9) = "PXEClient";
next-server 10.0.0.1;
if option arch =
filename
} else if option
filename
} else {
filename
}
00:06 {
"pxelinux/bootia32.efi";
arch = 00:07 {
"pxelinux/bootx64.efi";
"pxelinux/pxelinux.0";
}
host example-ia32 {
hardware ethernet XX:YY:ZZ:11:22:33;
fixed-address 10.0.0.2;
}
}
4. You now ne e d the pxelinux.0 file from the SYSLINUX package in the ISO image
file . To acce s s it, run the following commands as root:
mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o
loop,ro
cp -pr /mount_point/Packages/syslinux-version-architecture.rpm
/publicly_available_directory
umount /mount_point
Extract the package :
rpm2cpio syslinux-version-architecture.rpm | cpio -dimv
5. Cre ate a pxelinux dire ctory within tftpboot and copy pxelinux.0 into it:
mkdir /var/lib/tftpboot/pxelinux
cp publicly_available_directory/usr/share/syslinux/pxelinux.0
/var/lib/tftpboot/pxelinux
6. Cre ate a pxelinux.cfg dire ctory within pxelinux:
mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
7. Add a config file to this dire ctory. The file s hould e ithe r be name d default or
name d afte r the IP addre s s . For e xample , if your machine 's IP addre s s is 10.0.0.1,
the file name would be 0A000001.
A s ample config file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/default
might look like :
default vesamenu.c32
prompt 1
timeout 600
427
display boot.msg
label linux
menu label ^Install or upgrade an existing system
menu default
kernel vmlinuz
append initrd=initrd.img
label vesa
menu label Install system with ^basic video driver
kernel vmlinuz
append initrd=initrd.img xdriver=vesa nomodeset
label rescue
menu label ^Rescue installed system
kernel vmlinuz
append initrd=initrd.img rescue
label local
menu label Boot from ^local drive
localboot 0xffff
label memtest86
menu label ^Memory test
kernel memtest
append For ins tructions on how to s pe cify the ins tallation s ource , re fe r to Se ction 7.1.3,
Additional Boot Options
8. Copy the s plas h image into your tftp root dire ctory:
cp /boot/grub/splash.xpm.gz
/var/lib/tftpboot/pxelinux/splash.xpm.gz
9. Copy the boot image s into your tftp root dire ctory:
cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img}
/var/lib/tftpboot/pxelinux/rhel6/
10. Re boot the s ys te m, and s e le ct the ne twork de vice as your boot de vice whe n
prompte d.
428
4. Configure your DHCP s e rve r to us e the EFI boot image s package d with GRUB. (If you
do not have a DHCP s e rve r ins talle d, re fe r to the DHCP Servers chapte r in the Red
Hat Enterprise Linux Deployment Guide.)
A s ample configuration in /etc/dhcp/dhcpd.conf might look like :
option
option
option
option
option
option
option
space PXE;
PXE.mtftp-ip
code 1 = ip-address;
PXE.mtftp-cport code 2 = unsigned integer 16;
PXE.mtftp-sport code 3 = unsigned integer 16;
PXE.mtftp-tmout code 4 = unsigned integer 8;
PXE.mtftp-delay code 5 = unsigned integer 8;
arch code 93 = unsigned integer 16; # RFC4578
00:06 {
"pxelinux/bootia32.efi";
arch = 00:07 {
"pxelinux/bootx64.efi";
"pxelinux/pxelinux.0";
}
host example-ia32 {
hardware ethernet XX:YY:ZZ:11:22:33;
fixed-address 10.0.0.2;
}
}
5. Cre ate a pxelinux.cfg dire ctory within pxelinux:
mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
6. Add a config file to this dire ctory. The file s hould e ithe r be name d efidefault or
name d afte r the IP addre s s . For e xample , if your machine 's IP addre s s is 10.0.0.1,
the file name would be 0A000001.
A s ample config file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault
might look like :
default=0
timeout=1
splashimage=(nd)/splash.xpm.gz
hiddenmenu
429
title RHEL
root (nd)
kernel /rawhide-x86_64/vmlinuz
initrd /rawhide-x86_64/initrd.img
For ins tructions on how to s pe cify the ins tallation s ource , re fe r to Se ction 7.1.3,
Additional Boot Options
7. Copy the s plas h image into your tftp root dire ctory:
cp /boot/grub/splash.xpm.gz
/var/lib/tftpboot/pxelinux/splash.xpm.gz
8. Copy the boot image s into your tftp root dire ctory:
cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img}
/var/lib/tftpboot/pxelinux/rhel6/
9. Re boot the s ys te m, and s e le ct the ne twork de vice as your boot de vice whe n
prompte d.
430
5. Cre ate a yaboot dire ctory within tftpboot and copy the yaboot binary file into it:
mkdir /var/lib/tftpboot/yaboot
cp publicly_available_directory/yabootunpack/usr/lib/yaboot/yaboot /var/lib/tftpboot/yaboot
6. Add a config file name d yaboot.conf to this dire ctory. A s ample config file might
look like :
init-message = "\nWelcome to the Red Hat Enterprise Linux 6
installer!\n\n"
timeout=60
default=rhel6
image=/rhel6/vmlinuz-RHEL6
label=linux
alias=rhel6
initrd=/rhel6/initrd-RHEL6.img
append="repo=http://10.32.5.1/mnt/archive/redhat/released/RHEL6/6.x/Server/ppc64/os/"
read-only
For ins tructions on how to s pe cify the ins tallation s ource , re fe r to Se ction 7.1.3,
Additional Boot Options
7. Copy the boot image s from the e xtracte d ISO into your tftp root dire ctory:
cp /mount_point/images/ppc/ppc64/vmlinuz
/var/lib/tftpboot/yaboot/rhel6/vmlinuz-RHEL6
cp /mount_point/images/ppc/ppc64/initrd.img
/var/lib/tftpboot/yaboot/rhel6/initrd-RHEL6.img
8. Cle an up by re moving the yaboot-unpack dire ctory and unmounting the ISO:
rm -rf /publicly_available_directory/yaboot-unpack
umount /mount_point
9. Re boot the s ys te m, and s e le ct the ne twork de vice as your boot de vice whe n
prompte d.
tftp
Server
On the DHCP s e rve r, ve rify that the tftp-server package is ins talle d with the command
rpm -q tftp-server.
tftp is an xine td-bas e d s e rvice ; s tart it with the following commands :
/sbin/chkconfig --level 345 xinetd on
/sbin/chkconfig --level 345 tftp on
The s e commands configure the tftp and xinetd s e rvice s to s tart at boot time in
runle ve ls 3, 4, and 5.
431
432
433
Anaconda offe rs two mode s for VNC ins tallation. The mode you s e le ct will de pe nd on the
ne twork configuration in your e nvironme nt.
434
No te
This IP addre s s is only us e d during ins tallation. You will have an opportunity to
configure the final ne twork s e ttings , if any, late r in the ins talle r.
435
5. Once the ins talle r indicate s it is s tarting anaconda, you will be ins tructe d to conne ct
to the s ys te m us ing the VNC vie we r. Conne ct to the vie we r and follow the graphical
ins tallation mode ins tructions found in the product docume ntation.
Impo rtant
Be s ure to us e a te mporary pas s word for the vncpassword option. It s hould not be a
pas s word you us e on any s ys te ms , e s pe cially a re al root pas s word.
If you continue to have trouble , cons ide r us ing the vncconnect parame te r. In this mode of
ope ration, you s tart the vie we r on your s ys te m firs t te lling it to lis te n for an incoming
conne ction. Pas s vncconnect=HOST at the boot prompt and the ins talle r will atte mpt to
conne ct to the s pe cifie d HOST (e ithe r a hos tname or IP addre s s ).
31.4. References
Tige rVNC: http://tige rvnc.s ource forge .ne t/
RFC 1918 - Addre s s Allocation for Private Ne tworks : http://www.ie tf.org/rfc/rfc1918.txt
436
No te
Anaco nda now configure s ne twork inte rface s with Net wo rkManager.
Cons e que ntly, kicks tart us e rs that re fe re nce d the ne twork s e ttings locate d in
/tmp/netinfo in pre vious ve rs ions of Re d hat Ente rpris e Linux mus t now s ource
the ifcfg file s in /etc/sysconfig/network-scripts.
437
file /root/anaconda-ks.cfg. You s hould be able to e dit it with any te xt e ditor or word
proce s s or that can s ave file s as ASCII te xt.
Firs t, be aware of the following is s ue s whe n you are cre ating your kicks tart file :
Se ctions mus t be s pe cifie d in order. Ite ms within the s e ctions do not have to be in a
s pe cific orde r unle s s othe rwis e s pe cifie d. The s e ction orde r is :
Command s e ction Re fe r to Se ction 32.4, Kicks tart Options for a lis t of kicks tart
options . You mus t include the re quire d options .
The %packages s e ction Re fe r to Se ction 32.5, Package Se le ction for de tails .
The %pre and %post s e ctions The s e two s e ctions can be in any orde r and are not
re quire d. Re fe r to Se ction 32.6, Pre -ins tallation Script and Se ction 32.7, Pos tins tallation Script for de tails .
No te
Each s e ction s hould e nd with %end to avoid logge d warnings .
Ite ms that are not re quire d can be omitte d.
Omitting any re quire d ite m re s ults in the ins tallation program prompting the us e r for an
ans we r to the re late d ite m, jus t as the us e r would be prompte d during a typical
ins tallation. Once the ans we r is give n, the ins tallation continue s unatte nde d (unle s s it
finds anothe r mis s ing ite m).
Line s s tarting with a pound (als o known as has h) s ign (#) are tre ate d as comme nts and
are ignore d.
For kicks tart upgrades, the following ite ms are re quire d:
Language
Ins tallation me thod
De vice s pe cification (if de vice is ne e de d to pe rform the ins tallation)
Ke yboard s e tup
The upgrade ke yword
Boot loade r configuration
If any othe r ite ms are s pe cifie d for an upgrade , thos e ite ms are ignore d (note that this
include s package s e le ction).
438
No te
If the option is followe d by an e quals mark (=), a value mus t be s pe cifie d afte r it. In
the e xample commands , options in s quare bracke ts ([ ]) are optional argume nts for
the command.
Impo rtant
De vice name s are not guarante e d to be cons is te nt acros s re boots , which can
complicate us age in kicks tart s cripts . Whe n a kicks tart option calls for a de vice node
name (s uch as sda), you can ins te ad us e any ite m from /dev/disk. For e xample ,
ins te ad of:
part / --fstype=ext4 --onpart=sda1
You could us e an e ntry s imilar to one of the following:
part / --fstype=ext4 --onpart=/dev/disk/by-path/pci-0000:00:05.0scsi-0:0:0:0-part1
part / --fstype=ext4 --onpart=/dev/disk/by-id/ataST3160815AS_6RA0C882-part1
This provide s a cons is te nt way to re fe r to dis ks that is more me aningful than jus t
sda. This is e s pe cially us e ful in large s torage e nvironme nts .
Warning
Whe n us ing Ope nLDAP with the SSL protocol for s e curity, make s ure that
the SSLv2 and SSLv3 protols are dis able d in the s e rve r configuration. This
is due to the POODLE SSL vulne rability (CVE-2014-3566). Se e
https ://acce s s .re dhat.com/s olutions /1234843 for de tails .
--enablenis Turns on NIS s upport. By de fault, --enablenis us e s whate ve r
domain it finds on the ne twork. A domain s hould almos t always be s e t by hand
with the --nisdomain= option.
--nisdomain= NIS domain name to us e for NIS s e rvice s .
--nisserver= Se rve r to us e for NIS s e rvice s (broadcas ts by de fault).
439
440
No te
Note that the autopart option cannot be us e d toge the r with the
part/partition, raid, logvol, or volgroup options in the s ame kicks tart
file .
--encrypted Should all de vice s with s upport be e ncrypte d by de fault? This
is e quivale nt to che cking the Encrypt che ckbox on the initial partitioning
s cre e n.
--cipher= Spe cifie s which type of e ncryption will be us e d if the anaco nda
de fault ae s -xts -plain64 is not s atis factory. You mus t us e this option toge the r
with the --encrypted option; by its e lf it has no e ffe ct. Available type s of
e ncryption are lis te d in the Red Hat Enterprise Linux Security Guide, but Re d Hat
s trongly re comme nds us ing e ithe r ae s -xts -plain64 or ae s -cbc-e s s iv:s ha256.
--passphrase= Provide a de fault s ys te m-wide pas s phras e for all e ncrypte d
de vice s .
--escrowcert=URL_of_X.509_certificate Store data e ncryption ke ys of
all e ncrypte d volume s as file s in /root, e ncrypte d us ing the X.509 ce rtificate
441
Impo rtant
If you s e le ct te xt mode for a kicks tart ins tallation, make s ure that you
s pe cify choice s for the partitioning, bootloade r, and package s e le ction
options . The s e s te ps are automate d in te xt mode , and anaco nda cannot
prompt you for mis s ing information. If you do not provide choice s for the s e
options , anaco nda will s top the ins tallation proce s s .
Impo rtant
It is highly re comme nde d to s e t up a boot loade r pas s word on e ve ry
machine . An unprote cte d boot loade r can allow a pote ntial attacke r to modify
the s ys te m's boot options and gain acce s s to the s ys te m. Se e the chapte r
title d Workstation Security in the Red Hat Enterprise Linux Security Guide for
more information on boot loade r pas s words and pas s word s e curity in
ge ne ral.
--append= Spe cifie s ke rne l parame te rs . To s pe cify multiple parame te rs ,
s e parate the m with s pace s . For e xample :
bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"
--driveorder Spe cify which drive is firs t in the BIOS boot orde r. For
e xample :
bootloader --driveorder=sda,hda
442
--location= Spe cifie s whe re the boot re cord is writte n. Valid value s are
the following: mbr (the de fault), partition (ins talls the boot loade r on the firs t
s e ctor of the partition containing the ke rne l ne ce s s ary for UEFI), or none (do
not ins tall the boot loade r).
Impo rtant
64-bit AMD and Inte l s ys te ms with UEFI firmware re quire the boot loade r
to be ins talle d in an EFI s ys te m partition on a dis k labe le d with a GUID
Partition Table (GPT). Us ing a dis k with a Mas te r Boot Re cord (MBR) labe l
re quire s that the dis k be re labe le d us ing the clearpart and zerombr
commands . Re labe ling a dis k will re nde r all data on that dis k inacce s s ible
and it will re quire cre ating a ne w partition layout.
--password= If us ing GRUB, s e ts the GRUB boot loade r pas s word to the one
s pe cifie d with this option. This s hould be us e d to re s trict acce s s to the GRUB
s he ll, whe re arbitrary ke rne l options can be pas s e d.
--iscrypted If us ing GRUB, s hould be include d if the pas s word is alre ady
e ncrypte d. The e ncryption me thod is de te cte d automatically bas e d on the
pas s word.
--upgrade Upgrade the e xis ting boot loade r configuration, pre s e rving the
old e ntrie s . This option is only available for upgrade s .
clearpart (o pt io nal)
Re move s partitions from the s ys te m, prior to cre ation of ne w partitions . By
de fault, no partitions are re move d.
No te
If the clearpart command is us e d, the n the --onpart command cannot be
us e d on a logical partition.
--all Eras e s all partitions from the s ys te m.
Warning
This option will e ras e all dis ks which can be re ache d by the ins talle r,
including any attache d ne twork s torage . Us e this option with caution.
You can pre ve nt clearpart from wiping s torage you want to pre s e rve
by us ing the --drives= option and s pe cifying only the drive s you want to
cle ar, by attaching ne twork s torage late r (for e xample , in the %post
s e ction of the Kicks tart file ), or by blacklis ting the ke rne l module s us e d to
acce s s ne twork s torage .
443
--drives= Spe cifie s which drive s to cle ar partitions from. For e xample , the
following cle ars all the partitions on the firs t two drive s on the primary IDE
controlle r:
clearpart --drives=hda,hdb --all
To cle ar a multipath de vice , us e the format disk/by-id/scsi-WWID, whe re
WWID is the world-wide identifier for the de vice . For e xample , to cle ar a dis k
with WWID 58095BEC5510947BE8C0360F604351918, us e :
clearpart --drives=disk/by-id/scsi58095BEC5510947BE8C0360F604351918
This format is pre fe rable for all multipath de vice s , but if e rrors aris e , multipath
de vice s that do not us e logical volume management (LVM) can als o be cle are d
us ing the format disk/by-id/dm-uuid-mpath-WWID, whe re WWID is the worldwide identifier for the de vice . For e xample , to cle ar a dis k with WWID
2416CD96995134CA5D787F00A5AA11017, us e :
clearpart --drives=disk/by-id/dm-uuid-mpath2416CD96995134CA5D787F00A5AA11017
Warning
Ne ve r s pe cify multipath de vice s by de vice name s like mpatha. De vice
name s like mpatha are not s pe cific to a particular dis k. The dis k name d
/dev/mpatha during ins tallation might not be the one that you e xpe ct it
to be . The re fore , the clearpart command could targe t the wrong dis k.
--linux Eras e s all Linux partitions .
--none (de fault) Do not re move any partitions .
No te
Us ing the clearpart --all command in a Kicks tart file to re move all
e xis ting partitions during the ins tallation will caus e Anaco nda to paus e and
prompt you for a confirmation. If you ne e d to pe rform the ins tallation
automatically with no inte raction, add the zerombr command to your
Kicks tart file .
Impo rtant
The --initlabel option has be e n de pre cate d. To initializ e dis ks with
invalid partition table s and cle ar the ir conte nts , us e the zerombr command.
cmdline (o pt io nal)
Pe rform the ins tallation in a comple te ly non-inte ractive command line mode . Any
444
prompts for inte raction halts the ins tall. This mode is us e ful on IBM Sys te m z
s ys te ms with the 3270 te rminal unde r z /VM and ope rating s ys te m me s s age s
apple t on LPAR. The re comme nde d us e is in conjunction with RUNKS=1 and ks=.
Re fe r to Se ction 26.6, Parame te rs for Kicks tart Ins tallations .
device (o pt io nal)
On mos t PCI s ys te ms , the ins tallation program autoprobe s for Ethe rne t and SCSI
cards prope rly. On olde r s ys te ms and s ome PCI s ys te ms , howe ve r, kicks tart
ne e ds a hint to find the prope r de vice s . The device command, which te lls the
ins tallation program to ins tall e xtra module s , is in this format:
device <moduleName> --opts=<options>
<moduleName> Re place with the name of the ke rne l module which s hould
be ins talle d.
--opts= Options to pas s to the ke rne l module . For e xample :
--opts="aic152x=0x340 io=11"
driverdisk (o pt io nal)
Drive r dis ks can be us e d during kicks tart ins tallations . You mus t copy the drive r
dis ks 's conte nts to the root dire ctory of a partition on the s ys te m's hard drive .
The n you mus t us e the driverdisk command to te ll the ins tallation program
whe re to look for the drive r dis k.
driverdisk <partition> --source=<url> --biospart=<biospart> [-type=<fstype>]
Alte rnative ly, a ne twork location can be s pe cifie d for the drive r dis k:
driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/img
<partition> Partition containing the drive r dis k.
<url> URL for the drive r dis k. NFS locations can be give n in the form
nfs:host:/path/to/img.
<biospart> BIOS partition containing the drive r dis k (for e xample , 82p2).
--type= File s ys te m type (for e xample , vfat or e xt2).
fcoe (o pt io nal)
Spe cify which FCoE de vice s s hould be activate d automatically in addition to thos e
dis cove re d by Enhanced Disk Drive Services (EDD).
--nic= (mandatory) The name of the de vice to be activate d.
--dcb= Es tablis h Data Center Bridging (DCB) s e ttings .
--autovlan Dis cove r VLANs automatically.
445
firewall (o pt io nal)
This option corre s ponds to the Firewall Configuration s cre e n in the
ins tallation program:
firewall --enabled|--disabled [--trust=] <device> <incoming> [-port=]
--enabled or --enable Re je ct incoming conne ctions that are not in
re s pons e to outbound re que s ts , s uch as DNS re plie s or DHCP re que s ts . If
acce s s to s e rvice s running on this machine is ne e de d, you can choos e to allow
s pe cific s e rvice s through the fire wall.
--disabled or --disable Do not configure any iptable s rule s .
--trust= Lis ting a de vice he re , s uch as e th0, allows all traffic coming to and
from that de vice to go through the fire wall. To lis t more than one de vice , us e -trust eth0 --trust eth1. Do NOT us e a comma-s e parate d format s uch as
--trust eth0, eth1.
<incoming> Re place with one or more of the following to allow the s pe cifie d
s e rvice s through the fire wall.
--ssh
--telnet
--smtp
--http
--ftp
--port= You can s pe cify that ports be allowe d through the fire wall us ing the
port:protocol format. For e xample , to allow IMAP acce s s through your fire wall,
s pe cify imap:tcp. Nume ric ports can als o be s pe cifie d e xplicitly; for e xample ,
to allow UDP packe ts on port 1234 through, s pe cify 1234:udp. To s pe cify
multiple ports , s e parate the m by commas .
firstboot (o pt io nal)
De te rmine whe the r the f irst bo o t s tarts the firs t time the s ys te m is boote d. If
e nable d, the firstboot package mus t be ins talle d. If not s pe cifie d, this option is
dis able d by de fault.
--enable or --enabled The Set up Agent is s tarte d the firs t time the
s ys te m boots .
--disable or --disabled The Set up Agent is not s tarte d the firs t time
the s ys te m boots .
--reconfig Enable the Set up Agent to s tart at boot time in re configuration
mode . This mode e nable s the language , mous e , ke yboard, root pas s word,
s e curity le ve l, and time z one configuration options in addition to the de fault
one s .
graphical (o pt io nal)
Pe rform the kicks tart ins tallation in graphical mode . This is the de fault.
446
group (o pt io nal)
Cre ate s a ne w us e r group on the s ys te m. If a group with the give n name or GID
alre ady e xis ts , this command will fail. In addition, the user command can be us e d
to cre ate a ne w group for the ne wly cre ate d us e r.
group --name=name [--gid=gid]
--name= - Provide s the name of the group.
--gid= - The group's GID. If not provide d, de faults to the ne xt available nons ys te m GID.
halt (o pt io nal)
Halt the s ys te m afte r the ins tallation has s ucce s s fully comple te d. This is s imilar
to a manual ins tallation, whe re anaconda dis plays a me s s age and waits for the
us e r to pre s s a ke y be fore re booting. During a kicks tart ins tallation, if no
comple tion me thod is s pe cifie d, this option is us e d as the de fault.
The halt option is e quivale nt to the shutdown -h command.
For othe r comple tion me thods , re fe r to the poweroff, reboot, and shutdown
kicks tart options .
ignoredisk (o pt io nal)
Caus e s the ins talle r to ignore the s pe cifie d dis ks . This is us e ful if you us e
autopartition and want to be s ure that s ome dis ks are ignore d. For e xample ,
without ignoredisk, atte mpting to de ploy on a SAN-clus te r the kicks tart would fail,
as the ins talle r de te cts pas s ive paths to the SAN that re turn no partition table .
The s yntax is :
ignoredisk --drives=drive1,drive2,...
whe re driveN is one of sda, sdb,..., hda,... e tc.
To ignore a multipath de vice that doe s not us e logical volume management (LVM),
us e the format disk/by-id/dm-uuid-mpath-WWID, whe re WWID is the world-wide
identifier for the de vice . For e xample , to ignore a dis k with WWID
2416CD96995134CA5D787F00A5AA11017, us e :
ignoredisk --drives=disk/by-id/dm-uuid-mpath2416CD96995134CA5D787F00A5AA11017
Multipath de vice s that us e LVM are not as s e mble d until afte r anaco nda has
pars e d the kicks tart file . The re fore , you cannot s pe cify the s e de vice s in the
format dm-uuid-mpath. Ins te ad, to ignore a multipath de vice that us e s LVM, us e
the format disk/by-id/scsi-WWID, whe re WWID is the world-wide identifier for
the de vice . For e xample , to ignore a dis k with WWID
58095BEC5510947BE8C0360F604351918, us e :
ignoredisk --drives=disk/by-id/scsi58095BEC5510947BE8C0360F604351918
447
Warning
Ne ve r s pe cify multipath de vice s by de vice name s like mpatha. De vice
name s like mpatha are not s pe cific to a particular dis k. The dis k name d
/dev/mpatha during ins tallation might not be the one that you e xpe ct it to
be . The re fore , the clearpart command could targe t the wrong dis k.
--only-use s pe cifie s a lis t of dis ks for the ins talle r to us e . All othe r dis ks
are ignore d. For e xample , to us e dis k sda during ins tallation and ignore all
othe r dis ks :
ignoredisk --only-use=sda
To include a multipath de vice that doe s not us e LVM:
ignoredisk --only-use=disk/by-id/dm-uuid-mpath2416CD96995134CA5D787F00A5AA11017
To include a multipath de vice that us e s LVM:
ignoredisk --only-use=disk/by-id/scsi58095BEC5510947BE8C0360F604351918
install (o pt io nal)
Te lls the s ys te m to ins tall a fre s h s ys te m rathe r than upgrade an e xis ting
s ys te m. This is the de fault mode . For ins tallation, you mus t s pe cify the type of
ins tallation from cdrom, harddrive, nfs, or url (for FTP, HTTP, or HTTPS
ins tallations ). The install command and the ins tallation me thod command mus t
be on s e parate line s .
cdrom Ins tall from the firs t optical drive on the s ys te m.
harddrive Ins tall from a Re d Hat ins tallation tre e on a local drive , which
mus t be e ithe r vfat or e xt2.
--biospart=
BIOS partition to ins tall from (s uch as 82).
--partition=
Partition to ins tall from (s uch as s db2).
--dir=
Dire ctory containing the variant dire ctory of the ins tallation tre e .
For e xample :
harddrive --partition=hdb2 --dir=/tmp/install-tree
nfs Ins tall from the NFS s e rve r s pe cifie d.
--server=
448
449
450
gr Gre e k
hu Hungarian
hu101 Hungarian (101 ke y)
is-latin1 Ice landic
it Italian
it-ibm Italian (IBM)
it2 Italian (it2)
jp106 Japane s e
ko Kore an
la-latin1 Latin Ame rican
mk-utf Mace donian
nl Dutch
no Norwe gian
pl2 Polis h
pt-latin1 Portugue s e
ro Romanian
ru Rus s ian
sr-cy Se rbian
sr-latin Se rbian (latin)
sv-latin1 Swe dis h
sg Swis s Ge rman
sg-latin1 Swis s Ge rman (latin1)
sk-qwerty Slovak (qwe rty)
slovene Slove nian
trq Turkis h
uk Unite d Kingdom
ua-utf Ukrainian
us-acentos U.S. Inte rnational
us U.S. Englis h
The file /usr/lib/python2.6/sitepackages/system_config_keyboard/keyboard_models.py on 32-bit s ys te ms or
/usr/lib64/python2.6/sitepackages/system_config_keyboard/keyboard_models.py on 64-bit s ys te ms
451
452
Impo rtant
Do not us e the das h ("-") characte r in logical volume or volume group
name s whe n ins talling Re d Hat Ente rpris e Linux us ing Kicks tart. If you do,
the ins tallation will finis h normally, but the characte r will be re move d from
all ne wly cre ate d volume and volume group name s . For e xample , if you
cre ate a volume group name d volgrp-01, its name will be change d to
volgrp01.
This limitation only applie s to ne w ins tallations . If you are upgrading or
re ins talling an e xis ting ins tallation and us e the --noformat option
de s cribe d be low, das he s us e d in volume and volume group name s will be
pre s e rve d.
The <mntpoint> is whe re the partition is mounte d and mus t be of one of the
following forms :
/<path>
For e xample , /, /usr, /home
swap
The partition is us e d as s wap s pace .
To de te rmine the s iz e of the s wap partition automatically, us e the -recommended option:
swap --recommended
The s iz e as s igne d will be e ffe ctive but not pre cis e ly calibrate d for your
s ys te m.
To de te rmine the s iz e of the s wap partition automatically but als o allow
e xtra s pace for your s ys te m to hibe rnate , us e the --hibernation option:
swap --hibernation
The s iz e as s igne d will be e quivale nt to the s wap s pace as s igne d by -recommended plus the amount of RAM on your s ys te m.
For the s wap s iz e s as s igne d by the s e commands , re fe r to Se ction 9.15.5,
Re comme nde d Partitioning Sche me for x86, AMD64, and Inte l 64
Archite cture and Se ction 16.17.5, Re comme nde d Partitioning Sche me for
IBM Powe r Sys te ms s e rve rs .
453
Impo rtant
Swap s pace re comme ndations we re update d in Re d Hat Ente rpris e
Linux 6.3. Pre vious ly, s ys te ms with large amounts of RAM we re
as s igne d huge s wap s pace s . This de laye d the Out-of-Me mory Kille r
(o o m_kill) in addre s s ing critical me mory s hortage s , e ve n if a
proce s s was malfunctioning.
Cons e que ntly, if you are us ing an e arlie r ve rs ion of Re d Hat
Ente rpris e Linux 6, swap --recommended will ge ne rate large r s wap
s pace s than thos e de s cribe d in the Re comme nde d Partitioning
Sche me , e ve n on s ys te ms with large amounts of RAM. This may
ne gate the ne e d to allow e xtra s pace for hibe rnation.
Howe ve r, the s e update d s wap s pace value s are none the le s s
re comme nde d for e arlie r ve rs ions of Re d Hat Ente rpris e Linux 6 and
can be s e t manually us ing the swap --size= option.
454
455
Impo rtant
If you ne e d to manually s pe cify ne twork s e ttings during an othe rwis e automate d kicks tart ins tallation, do not us e network. Ins te ad, boot the
s ys te m with the asknetwork option (re fe r to Se ction 32.10, Starting a
Kicks tart Ins tallation), which will prompt anaco nda to as k you for ne twork
s e ttings rathe r than us e the de fault s e ttings . anaco nda will as k this be fore
fe tching the kicks tart file .
Once the ne twork conne ction is e s tablis he d, you can only re configure
ne twork s e ttings with thos e s pe cifie d in your kicks tart file .
No te
You will only be prompte d for information about your ne twork:
be fore fe tching the kicks tart file if you are us ing the asknetwork boot
option
whe n the ne twork is firs t acce s s e d once the kicks tart file has be e n
fe tche d, if the ne twork was not us e d to fe tch it and you have provide d no
kicks tart ne twork commands
456
457
The be havior of any s ubs e que nt network command is uns pe cifie d if its -device option is mis s ing. Take care to s pe cify a --device option for any
ne twork command be yond the firs t.
You can s pe cify a de vice in one of five ways :
the de vice name of the inte rface , for e xample , eth0
the MAC addre s s of the inte rface , for e xample , 00:12:34:56:78:9a
the ke yword link, which s pe cifie s the firs t inte rface with its link in the up
s tate
the ke yword bootif, which us e s the MAC addre s s that pxelinux s e t in the
BOOTIF variable . Se t IPAPPEND 2 in your pxelinux.cfg file to have
pxelinux s e t the BOOTIF variable .
the ke yword ibft, which us e s the MAC addre s s of the inte rface s pe cifie d
by iBFT
network --bootproto=dhcp --device=eth0
--ip= IP addre s s of the de vice .
--ipv6= IPv6 addre s s of the de vice . Us e auto for automatic configuration,
or dhcp for DHCPv6 only configuration (no route r adve rtis e me nts ).
--gateway= De fault gate way as a s ingle IPv4 addre s s .
--ipv6gateway= De fault gate way as a s ingle IPv6 addre s s .
--nameserver= Primary name s e rve r, as an IP addre s s . Multiple
name s e rve rs mus t e ach be s e parate d by a comma.
--nodefroute Pre ve nts the inte rface be ing s e t as the de fault route . Us e
this option whe n you activate additional de vice s with the --activate= option,
for e xample , a NIC on a s e parate s ubne t for an iSCSI targe t.
The nodefroute option is ne w in Re d Hat Ente rpris e Linux 6.1.
--nodns Do not configure any DNS s e rve r.
--netmask= Ne twork mas k of the de vice .
--hostname= Hos tname for the ins talle d s ys te m.
--ethtool= Spe cifie s additional low-le ve l s e ttings for the ne twork de vice
which will be pas s e d to the e thtool program.
--onboot= Whe the r or not to e nable the de vice at boot time .
--dhcpclass= The DHCP clas s .
--mtu= The MTU of the de vice .
--noipv4 Dis able IPv4 on this de vice .
--noipv6 Dis able IPv6 on this de vice .
--vlanid= Spe cifie s virtual LAN ID numbe r (802.1q tag).
458
Impo rtant
The --bondopts=mode= parame te r only s upports full mode name s s uch
as balance-rr or broadcast, not the ir nume rical re pre s e ntations s uch
as 0 or 3.
part o r partition (required f o r inst alls, igno red f o r upgrades)
Cre ate s a partition on the s ys te m.
If more than one Re d Hat Ente rpris e Linux ins tallation e xis ts on the s ys te m on
diffe re nt partitions , the ins tallation program prompts the us e r and as ks which
ins tallation to upgrade .
Warning
All partitions cre ate d are formatte d as part of the ins tallation proce s s
unle s s --noformat and --onpart are us e d.
Impo rtant
If you s e le ct te xt mode for a kicks tart ins tallation, make s ure that you
s pe cify choice s for the partitioning, bootloade r, and package s e le ction
options . The s e s te ps are automate d in te xt mode , and anaco nda cannot
prompt you for mis s ing information. If you do not provide choice s for the s e
options , anaco nda will s top the ins tallation proce s s .
For a de taile d e xample of part in action, re fe r to Se ction 32.4.1, Advance d
Partitioning Example .
part|partition <mntpoint> --name=<name> --device=<device> -rule=<rule> [options]
<mntpoint> Whe re the partition is mounte d. The value mus t be of one of
the following forms :
/<path>
459
Impo rtant
Swap s pace re comme ndations we re update d in Re d Hat Ente rpris e
Linux 6.3. Pre vious ly, s ys te ms with large amounts of RAM we re
as s igne d huge s wap s pace s . This de laye d the Out-of-Me mory Kille r
(o o m_kill) in addre s s ing critical me mory s hortage s , e ve n if a
proce s s was malfunctioning.
Cons e que ntly, if you are us ing an e arlie r ve rs ion of Re d Hat
Ente rpris e Linux 6, swap --recommended will ge ne rate large r s wap
s pace s than thos e de s cribe d in the Re comme nde d Partitioning
Sche me , e ve n on s ys te ms with large amounts of RAM. This may
ne gate the ne e d to allow e xtra s pace for hibe rnation.
Howe ve r, the s e update d s wap s pace value s are none the le s s
re comme nde d for e arlie r ve rs ions of Re d Hat Ente rpris e Linux 6 and
can be s e t manually us ing the swap --size= option.
raid.<id>
The partition is us e d for s oftware RAID (re fe r to raid).
pv.<id>
The partition is us e d for LVM (re fe r to logvol).
--size= The minimum partition s iz e in me gabyte s . Spe cify an inte ge r value
he re s uch as 500 (do not include the unit).
460
Impo rtant
If the --size value is too s mall, the ins tallation will fail. Se t the --size
value as the minimum amount of s pace you re quire . For s iz e
re comme ndations , re fe r to Se ction 9.15.5, Re comme nde d Partitioning
Sche me .
--grow Te lls the partition to grow to fill available s pace (if any), or up to the
maximum s iz e s e tting.
No te
If you us e --grow= without s e tting --maxsize= on a s wap partition,
Anaco nda will limit the maximum s iz e of the s wap partition. For
s ys te ms that have le s s than 2GB of phys ical me mory, the impos e d limit
is twice the amount of phys ical me mory. For s ys te ms with more than
2GB, the impos e d limit is the s iz e of phys ical me mory plus 2GB.
--maxsize= The maximum partition s iz e in me gabyte s whe n the partition is
s e t to grow. Spe cify an inte ge r value he re s uch as 500 (do not include the
unit).
--noformat Spe cifie s that the partition s hould not be formatte d, for us e with
the --onpart command.
--onpart= or --usepart= Spe cifie s the de vice on which to place the
partition. For e xample :
partition /home --onpart=hda1
puts /home on /dev/hda1.
The s e options can als o add a partition to a logical volume . For e xample :
partition pv.1 --onpart=hda2
The de vice mus t alre ady e xis t on the s ys te m; the --onpart option will not
cre ate it.
--ondisk= or --ondrive= Force s the partition to be cre ate d on a particular
dis k. For e xample , --ondisk=sdb puts the partition on the s e cond SCSI dis k on
the s ys te m.
To s pe cify a multipath de vice that doe s not us e logical volume management
(LVM), us e the format disk/by-id/dm-uuid-mpath-WWID, whe re WWID is the
world-wide identifier for the de vice . For e xample , to s pe cify a dis k with WWID
2416CD96995134CA5D787F00A5AA11017, us e :
part / --fstype=ext3 --grow --asprimary --size=100 -ondisk=disk/by-id/dm-uuid-mpath2416CD96995134CA5D787F00A5AA11017
461
Multipath de vice s that us e LVM are not as s e mble d until afte r anaco nda has
pars e d the kicks tart file . The re fore , you cannot s pe cify the s e de vice s in the
format dm-uuid-mpath. Ins te ad, to s pe cify a multipath de vice that us e s LVM,
us e the format disk/by-id/scsi-WWID, whe re WWID is the world-wide
identifier for the de vice . For e xample , to s pe cify a dis k with WWID
58095BEC5510947BE8C0360F604351918, us e :
part / --fstype=ext3 --grow --asprimary --size=100 -ondisk=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918
Warning
Ne ve r s pe cify multipath de vice s by de vice name s like mpatha. De vice
name s like mpatha are not s pe cific to a particular dis k. The dis k name d
/dev/mpatha during ins tallation might not be the one that you e xpe ct it
to be . The re fore , the clearpart command could targe t the wrong dis k.
--asprimary Force s automatic allocation of the partition as a primary
partition, or the partitioning fails .
--type= (re place d by fstype) This option is no longe r available . Us e
fstype.
--fsoptions Spe cifie s a fre e form s tring of options to be us e d whe n
mounting the file s ys te m. This s tring will be copie d into the /etc/fstab file of
the ins talle d s ys te m and s hould be e nclos e d in quote s .
--fsprofile Spe cifie s a usage type to be pas s e d to the program that
make s a file s ys te m on this partition. A us age type de fine s a varie ty of tuning
parame te rs to be us e d whe n making a file s ys te m. For this option to work, the
file s ys te m mus t s upport the conce pt of us age type s and the re mus t be a
configuration file that lis ts valid type s . For e xt2, e xt3, and e xt4, this
configuration file is /etc/mke2fs.conf.
--fstype= Se ts the file s ys te m type for the partition. Valid value s are xfs,
ext2, ext3, ext4, swap, vfat, hfs, and efi.
--recommended De te rmine the s iz e of the partition automatically.
--onbiosdisk Force s the partition to be cre ate d on a particular dis k as
dis cove re d by the BIOS.
--encrypted Spe cifie s that this partition s hould be e ncrypte d, us ing the
pas s phras e provide d in the --passphrase option. If you do not s pe cify a
pas s phras e , anaco nda us e s the de fault, s ys te m-wide pas s phras e s e t with
the autopart --passphrase command, or s tops the ins tallation and prompts
you to provide a pas s phras e if no de fault is s e t.
--cipher= Spe cifie s which type of e ncryption will be us e d if the anaco nda
de fault ae s -xts -plain64 is not s atis factory. You mus t us e this option toge the r
with the --encrypted option; by its e lf it has no e ffe ct. Available type s of
e ncryption are lis te d in the Red Hat Enterprise Linux Security Guide, but Re d Hat
s trongly re comme nds us ing e ithe r ae s -xts -plain64 or ae s -cbc-e s s iv:s ha256.
462
No te
If partitioning fails for any re as on, diagnos tic me s s age s appe ar on virtual
cons ole 3.
poweroff (o pt io nal)
Shut down and powe r off the s ys te m afte r the ins tallation has s ucce s s fully
comple te d. Normally during a manual ins tallation, anaconda dis plays a me s s age
and waits for the us e r to pre s s a ke y be fore re booting. During a kicks tart
ins tallation, if no comple tion me thod is s pe cifie d, the halt option is us e d as
de fault.
The poweroff option is e quivale nt to the shutdown -p command.
No te
The poweroff option is highly de pe nde nt on the s ys te m hardware in us e .
Spe cifically, ce rtain hardware compone nts s uch as the BIOS, APM (advance d
powe r manage me nt), and ACPI (advance d configuration and powe r inte rface )
mus t be able to inte ract with the s ys te m ke rne l. Contact your manufacture r
for more information on you s ys te m's APM/ACPI abilitie s .
For othe r comple tion me thods , re fe r to the halt, reboot, and shutdown kicks tart
options .
raid (o pt io nal)
As s e mble s a s oftware RAID de vice . This command is of the form:
raid <mntpoint> --level=<level> --device=<mddevice> <partitions*>
<mntpoint> Location whe re the RAID file s ys te m is mounte d. If it is /, the
RAID le ve l mus t be 1 unle s s a boot partition (/boot) is pre s e nt. If a boot
partition is pre s e nt, the /boot partition mus t be le ve l 1 and the root (/)
partition can be any of the available type s . The <partitions*> (which de note s
463
that multiple partitions can be lis te d) lis ts the RAID ide ntifie rs to add to the
RAID array.
464
No te
Us e of the reboot option may re s ult in an e ndle s s ins tallation loop,
de pe nding on the ins tallation me dia and me thod.
465
repo (o pt io nal)
Configure s additional yum re pos itorie s that may be us e d as s ource s for package
ins tallation. Multiple re po line s may be s pe cifie d.
repo --name=<repoid> [--baseurl=<url>| --mirrorlist=<url>]
--name= The re po id. This option is re quire d.
--baseurl= The URL for the re pos itory. The variable s that may be us e d in
yum re po config file s are not s upporte d he re . You may us e one of e ithe r this
option or --mirrorlis t, not both.
--mirrorlist= The URL pointing at a lis t of mirrors for the re pos itory. The
variable s that may be us e d in yum re po config file s are not s upporte d he re .
You may us e one of e ithe r this option or --bas e url, not both.
Impo rtant
Re pos itorie s us e d for ins tallation mus t be s table . The ins tallation may fail if
a re pos itory is modifie d be fore the ins tallation conclude s .
rootpw (required)
Se ts the s ys te m's root pas s word to the <password> argume nt.
rootpw [--iscrypted] <password>
--iscrypted If this is pre s e nt, the pas s word argume nt is as s ume d to
alre ady be e ncrypte d.
selinux (o pt io nal)
Se ts the s tate of SELinux on the ins talle d s ys te m. SELinux de faults to e nforcing in
anaconda.
selinux [--disabled|--enforcing|--permissive]
--enforcing Enable s SELinux with the de fault targe te d policy be ing
e nforce d.
No te
If the selinux option is not pre s e nt in the kicks tart file , SELinux is
e nable d and s e t to --enforcing by de fault.
--permissive Outputs warnings bas e d on the SELinux policy, but doe s not
actually e nforce the policy.
--disabled Dis able s SELinux comple te ly on the s ys te m.
For more information re garding SELinux for Re d Hat Ente rpris e Linux, re fe r to the
Red Hat Enterprise Linux 6.6 Deployment Guide.
466
services (o pt io nal)
Modifie s the de fault s e t of s e rvice s that will run unde r the de fault runle ve l. The
lis t of dis able d s e rvice s is proce s s e d be fore the lis t of e nable d s e rvice s .
The re fore , if a s e rvice appe ars on both lis ts , it is e nable d.
--disabled Dis able the s e rvice s give n in the comma s e parate d lis t.
--enabled Enable the s e rvice s give n in the comma s e parate d lis t.
Impo rtant
Do not include s pace s in the lis t of s e rvice s . If you do, kicks tart will e nable
or dis able only the s e rvice s up to the firs t s pace . For e xample :
services --disabled auditd, cups,smartd, nfslock
will dis able only the audit d s e rvice . To dis able all four s e rvice s , this e ntry
s hould include no s pace s be twe e n s e rvice s :
services --disabled auditd,cups,smartd,nfslock
shutdown (o pt io nal)
Shut down the s ys te m afte r the ins tallation has s ucce s s fully comple te d. During a
kicks tart ins tallation, if no comple tion me thod is s pe cifie d, the halt option is us e d
as de fault.
The shutdown option is e quivale nt to the shutdown command.
For othe r comple tion me thods , re fe r to the halt, poweroff, and reboot kicks tart
options .
skipx (o pt io nal)
If pre s e nt, X is not configure d on the ins talle d s ys te m.
Impo rtant
If you ins tall a dis play manage r among your package s e le ction options , this
package will cre ate an X configuration, and the ins talle d s ys te m will de fault
to run le ve l 5. The e ffe ct of the skipx option will be ove rridde n.
sshpw (o pt io nal)
During ins tallation, you can inte ract with anaco nda and monitor its progre s s ove r
an SSH conne ction. Us e the sshpw command to cre ate te mporary accounts
through which to log on. Each ins tance of the command cre ate s a s e parate
account that e xis ts only in the ins tallation e nvironme nt. The s e accounts are not
trans fe rre d to the ins talle d s ys te m.
sshpw --username=<name> <password> [--iscrypted|--plaintext] [-lock]
467
Impo rtant
By de fault, the ssh s e rve r is not s tarte d during ins tallation. To make ssh
available during ins tallation, boot the s ys te m with the ke rne l boot option
sshd=1. Re fe r to Se ction 28.2.3, Enabling Re mote Acce s s with s s h for
de tails of how to s pe cify this ke rne l option at boot time .
No te
If you want to dis able root ssh acce s s to your hardware during ins tallation,
run:
sshpw --username=root --lock
text (o pt io nal)
Pe rform the kicks tart ins tallation in te xt mode . Kicks tart ins tallations are
pe rforme d in graphical mode by de fault.
Impo rtant
If you s e le ct te xt mode for a kicks tart ins tallation, make s ure that you
s pe cify choice s for the partitioning, bootloade r, and package s e le ction
options . The s e s te ps are automate d in te xt mode , and anaco nda cannot
prompt you for mis s ing information. If you do not provide choice s for the s e
options , anaco nda will s top the ins tallation proce s s .
timezone (required)
Se ts the s ys te m time z one to <timezone> which may be any of the time z one s
lis te d in the /usr/share/zoneinfo dire ctory.
timezone [--utc] <timezone>
--utc If pre s e nt, the s ys te m as s ume s the hardware clock is s e t to UTC
(Gre e nwich Me an) time .
unsupported_hardware (o pt io nal)
468
Te lls the ins talle r to s uppre s s the Unsupported Hardware Detected ale rt. If this
command is not include d and uns upporte d hardware is de te cte d, the ins tallation
will s tall at this ale rt.
upgrade (o pt io nal)
Te lls the s ys te m to upgrade an e xis ting s ys te m rathe r than ins tall a fre s h
s ys te m. You mus t s pe cify one of cdrom, harddrive, nfs, or url (for FTP, HTTP,
and HTTPS) as the location of the ins tallation tre e . Re fe r to install for de tails .
user (o pt io nal)
Cre ate s a ne w us e r on the s ys te m.
user --name=<username> [--groups=<list>] [--homedir=<homedir>] [-password=<password>] [--iscrypted] [--shell=<shell>] [-uid=<uid>]
--name= Provide s the name of the us e r. This option is re quire d.
--groups= In addition to the de fault group, a comma s e parate d lis t of group
name s the us e r s hould be long to. The groups mus t e xis t be fore the us e r
account is cre ate d.
--homedir= The home dire ctory for the us e r. If not provide d, this de faults to
/home /<username>.
--password= The ne w us e r's pas s word. If not provide d, the account will be
locke d by de fault.
--iscrypted= Is the pas s word provide d by --pas s word alre ady e ncrypte d or
not?
--shell= The us e r's login s he ll. If not provide d, this de faults to the s ys te m
de fault.
--uid= The us e r's UID. If not provide d, this de faults to the ne xt available
non-s ys te m UID.
vnc (o pt io nal)
Allows the graphical ins tallation to be vie we d re mote ly via VNC. This me thod is
us ually pre fe rre d ove r te xt mode , as the re are s ome s iz e and language
limitations in te xt ins talls . With no options , this command will s tart a VNC s e rve r
on the machine with no pas s word and will print out the command that ne e ds to be
run to conne ct a re mote machine .
vnc [--host=<hostname>] [--port=<port>] [--password=<password>]
--host= Ins te ad of s tarting a VNC s e rve r on the ins tall machine , conne ct to
the VNC vie we r proce s s lis te ning on the give n hos tname .
--port= Provide a port that the re mote VNC vie we r proce s s is lis te ning on.
If not provide d, anaconda will us e the VNC de fault.
--password= Se t a pas s word which mus t be provide d to conne ct to the VNC
s e s s ion. This is optional, but re comme nde d.
volgroup (o pt io nal)
469
Us e to cre ate a Logical Volume Manage me nt (LVM) group with the s yntax:
volgroup <name> <partition> [options]
Impo rtant
Do not us e the das h ("-") characte r in logical volume or volume group
name s whe n ins talling Re d Hat Ente rpris e Linux us ing Kicks tart. If you do,
the ins tallation will finis h normally, but the characte r will be re move d from
all ne wly cre ate d volume and volume group name s . For e xample , if you
cre ate a volume group name d volgrp-01, its name will be change d to
volgrp01.
This limitation only applie s to ne w ins tallations . If you are upgrading or
re ins talling an e xis ting ins tallation and us e the --noformat option
de s cribe d be low, das he s us e d in volume and volume group name s will be
pre s e rve d.
Cre ate the partition firs t, cre ate the logical volume group, and the n cre ate the
logical volume . For e xample :
part pv.01 --size 3000
volgroup myvg pv.01
logvol / --vgname=myvg --size=2000 --name=rootvol
For a de taile d e xample of volgroup in action, re fe r to Se ction 32.4.1, Advance d
Partitioning Example .
The options are as follows :
--noformat Us e an e xis ting volume group and do not format it.
--useexisting - Us e an e xis ting volume group and re format it. If you us e this
option, do not s pe cify a partition. For e xample :
volgroup rhel00 --useexisting --noformat
--pesize= Se t the s iz e of the phys ical e xte nts . The de fault s iz e for
Kicks tart ins tallations is 4 MiB.
--reserved-space= Spe cify an amount of s pace to le ave unus e d in a
volume group, in me gabyte s . Only us able whe n cre ating a ne w volume group.
--reserved-percent= Spe cify a pe rce ntage of total volume group s pace to
le ave unus e d. Only us able whe n cre ating a ne w volume group.
470
No te
The --reserved-space= and --reserved-percent= options allow you to
le ave a part of the total volume group s pace unus e d by any volume s . This
allows you to re s e rve s pace for LVM s naps hots , e ve n if the logvol --grow
command is us e d during partitioning.
winbind (o pt io nal)
Configure s the s ys te m to conne ct to a Windows Active Dire ctory or a Windows
domain controlle r. Us e r information from the s pe cifie d dire ctory or domain
controlle r can the n be acce s s e d and s e rve r authe ntication options can be
configure d.
--enablewinbind Enable winbind for us e r account configuration.
--disablewinbind Dis able winbind for us e r account configuration.
--enablewinbindauth Enable windbindauth for authe ntication.
--disablewinbindauth Dis able windbindauth for authe ntication.
--enablewinbindoffline Configure s winbind to allow offline login.
--disablewinbindoffline Configure s winbind to pre ve nt offline login.
--enablewinbindusedefaultdomain Configure s winbind to as s ume that
us e rs with no domain in the ir us e rname s are domain us e rs .
--disablewinbindusedefaultdomain Configure s winbind to as s ume that
us e rs with no domain in the ir us e rname s are not domain us e rs .
xconfig (o pt io nal)
Configure s the X Windo w Syst em. If you ins tall the X Windo w Syst em with a
kicks tart file that doe s not include the xconfig command, you mus t provide the X
configuration manually during ins tallation.
Do not us e this command in a kicks tart file that doe s not ins tall the X Windo w
Syst em.
--driver Spe cify the X drive r to us e for the vide o hardware .
--videoram= Spe cifie s the amount of vide o RAM the vide o card has .
--defaultdesktop= Spe cify e ithe r GNOME or KDE to s e t the de fault de s ktop
(as s ume s that GNOME De s ktop Environme nt and/or KDE De s ktop Environme nt
has be e n ins talle d through %packages).
--startxonboot Us e a graphical login on the ins talle d s ys te m.
zerombr (o pt io nal)
If zerombr is s pe cifie d any invalid partition table s found on dis ks are initializ e d.
This de s troys all of the conte nts of dis ks with invalid partition table s . This
command is re quire d whe n pe rforming an unatte nde d ins tallation on a s ys te m
with pre vious ly initializ e d dis ks .
471
Spe cific to Sys te m z : If zerombr is s pe cifie d, any DASD vis ible to the ins talle r
which is not alre ady low-le ve l formatte d ge ts automatically low-le ve l formatte d
with dasdf mt . The command als o pre ve nts us e r choice during inte ractive
ins tallations . If zerombr is not s pe cifie d and the re is at le as t one unformatte d
DASD vis ible to the ins talle r, a non-inte ractive kicks tart ins tallation will e xit
uns ucce s s fully. If zerombr is not s pe cifie d and the re is at le as t one unformatte d
DASD vis ible to the ins talle r, an inte ractive ins tallation e xits if the us e r doe s not
agre e to format all vis ible and unformatte d DASDs . To circumve nt this , only
activate thos e DASDs that you will us e during ins tallation. You can always add
more DASDs afte r ins tallation is comple te .
No te
That this command was pre vious ly s pe cifie d as zerombr yes. This form is
now de pre cate d; you s hould now s imply s pe cify zerombr in your kicks tart
file ins te ad.
zfcp (o pt io nal)
De fine a Fibe r channe l de vice (IBM Sys te m z ).
zfcp [--devnum=<devnum>] [--wwpn=<wwpn>] [--fcplun=<fcplun>]
%include (o pt io nal)
Us e the %include /path/to/file command to include the conte nts of anothe r
file in the kicks tart file as though the conte nts we re at the location of the
%include command in the kicks tart file .
--ondrive=hda
--ondrive=hda
--ondrive=hda
--ondrive=hda
--ondrive=hda
--ondrive=hdc
--ondrive=hdc
--ondrive=hdc
--ondrive=hdc
--ondrive=hdc
472
raid.21
raid.22
raid.23
raid.24
raid.25
Us e the %packages command to be gin a kicks tart file s e ction that lis ts the package s you
would like to ins tall (this is for ins tallations only, as package s e le ction during upgrade s is
not s upporte d).
You can s pe cify package s by group or by the ir package name s . The ins tallation program
de fine s s e ve ral groups that contain re late d package s . Re fe r to the
variant/repodata/comps-*.xml file on the Re d Hat Ente rpris e Linux 6.6 Ins tallation DVD
for a lis t of groups . Each group has an id, us e r vis ibility value , name , de s cription, and
package lis t. If the group is s e le cte d for ins tallation, the package s marke d mandatory in
the package lis t are always ins talle d, the package s marke d default are ins talle d if the y
are not s pe cifically e xclude d e ls e whe re , and the package s marke d optional mus t be
s pe cifically include d e ls e whe re e ve n whe n the group is s e le cte d.
Spe cify groups , one e ntry to a line , s tarting with an @ s ymbol, a s pace , and the n the full
group name or group id as give n in the comps.xml file . For e xample :
%packages
@X Window System
@Desktop
@Sound and Video
Note that the Core and Base groups are always s e le cte d by de fault, s o it is not ne ce s s ary
to s pe cify the m in the %packages s e ction.
473
Warning
Whe n pe rforming a minimal ins tallation us ing the @Core group, the fire wall
(iptables/ip6tables) will not be configure d on the ins talle d s ys te m. This pre s e nts
a s e curity ris k. To work around this is s ue , add the authconfig and system-configfirewall-base package s to your package s e le ction as de s cribe d be low. The fire wall
will be configure d prope rly if the s e package s are pre s e nt.
A minimal ins tallation's %packages s e ction which will als o configure the fire wall will
look s imilar to the following:
%packages
@Core
authconfig
system-config-firewall-base
Se e the Re d Hat Cus tome r Portal for de tails .
Spe cify individual package s by name , one e ntry to a line . You can us e as te ris ks as
wildcards to glob package name s in e ntrie s . For e xample :
sqlite
curl
aspell
docbook*
The docbook* e ntry include s the package s docbook-dtds, docbook-simple, docbook-slides
and othe rs that match the patte rn re pre s e nte d with the wildcard.
Us e a le ading das h to s pe cify package s or groups to e xclude from the ins tallation. For
e xample :
-@ Graphical Internet
-autofs
-ipa*fonts
Impo rtant
To ins tall a 32-bit package on a 64-bit s ys te m, you will ne e d to appe nd the package
name with the 32-bit archite cture the package was built for. For e xample :
glibc.i686
Us ing a kicks tart file to ins tall e ve ry available package by s pe cifying * will introduce
package and file conflicts onto the ins talle d s ys te m. Package s known to caus e s uch
proble ms are as s igne d to the @Conflicts (variant) group, whe re variant is Client,
ComputeNode, Server or Workstation. If you s pe cify * in a kicks tart file , be s ure to
e xclude @Conflicts (variant) or the ins tallation will fail:
474
*
-@Conflicts (Server)
Note that Re d Hat doe s not s upport the us e of * in a kicks tart file , e ve n if you e xclude
@Conflicts (variant).
The s e ction mus t e nd with the %end command.
The following options are available for the %packages option:
--nobase
Do not ins tall the @Bas e group. Us e this option to pe rform a minimal ins tallation,
for e xample , for a s ingle -purpos e s e rve r or de s ktop appliance .
--resolvedeps
The --re s olve de ps option has be e n de pre cate d. De pe nde ncie s are now always
re s olve d automatically.
--ignoredeps
The --ignore de ps option has be e n de pre cate d. De pe nde ncie s are re s olve d
automatically e ve ry time now.
--ignoremissing
Ignore the mis s ing package s and groups ins te ad of halting the ins tallation to as k if
the ins tallation s hould be aborte d or continue d. For e xample :
%packages --ignoremissing
No te
The pre -ins tall s cript is not run in the change root e nvironme nt.
--interpreter /usr/bin/python
Allows you to s pe cify a diffe re nt s cripting language , s uch as Python. Re place
/usr/bin/python with the s cripting language of your choice .
475
476
No te
The pre -ins tallation s cript s e ction of kicks tart cannot manage multiple ins tall tre e s or
s ource me dia. This information mus t be include d for e ach cre ate d ks .cfg file , as the
pre -ins tallation s cript occurs during the s e cond s tage of the ins tallation proce s s .
No te
If you configure d the ne twork with s tatic IP information, including a name s e rve r, you
can acce s s the ne twork and re s olve IP addre s s e s in the %post s e ction. If you
configure d the ne twork for DHCP, the /etc/resolv.conf file has not be e n
comple te d whe n the ins tallation e xe cute s the %post s e ction. You can acce s s the
ne twork, but you can not re s olve IP addre s s e s . Thus , if you are us ing DHCP, you
mus t s pe cify IP addre s s e s in the %post s e ction.
No te
The pos t-ins tall s cript is run in a chroot e nvironme nt; the re fore , pe rforming tas ks
s uch as copying s cripts or RPMs from the ins tallation me dia do not work.
--nochroot
Allows you to s pe cify commands that you would like to run outs ide of the chroot
e nvironme nt.
The following e xample copie s the file /etc/resolv.conf to the file s ys te m that
was jus t ins talle d.
%post --nochroot
cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
--interpreter /usr/bin/python
Allows you to s pe cify a diffe re nt s cripting language , s uch as Python. Re place
/usr/bin/python with the s cripting language of your choice .
--log /path/to/logfile
477
Logs the output of the pos t-ins tall s cript. Note that the path of the log file mus t
take into account whe the r or not you us e the --nochroot option. For e xample ,
without --nochroot:
%post --log=/root/ks-post.log
with --nochroot:
%post --nochroot --log=/mnt/sysimage/root/ks-post.log
32.7.1. Examples
32.7.1.1. Regist ering and T hen Mount ing an NFS Share
Re gis te r the s ys te m to a Re d Hat Subs cription Manage me nt s e rve r (in this e xample , a
local Subs cription As s e t Manage r s e rve r):
%post --log=/root/ks-post.log
/usr/sbin/subscription-manager register --username=admin@example.com -password=secret --serverurl=sam-server.example.com --org="Admin Group" -environment="Dev"
%end
Run a s cript name d runme from an NFS s hare :
mkdir /mnt/temp
mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp
openvt -s -w -- /mnt/temp/runme
umount /mnt/temp
NFS file locking is not s upporte d while in kicks tart mode , the re fore -o nolock is re quire d
whe n mounting an NFS mount.
478
Additional options can be us e d with the re gis tration command to s e t a pre fe rre d s e rvice
le ve l for the s ys te m and to re s trict update s and e rrata to a s pe cific ope rating s ys te m
ve rs ion.
%post --log=/root/ks-post.log
/usr/sbin/subscription-manager register --username=admin@example.com -password=secret --serverurl=sam-server.example.com --org="Admin Group" -environment="Dev" --servicelevel=standard --release="6.6"
%end
For additional information about us ing subscript io n-manager, s e e the Knowle dge bas e
article at https ://acce s s .re dhat.com/s olutions /748313.
479
2. Extract the ISO image into a working dire ctory s ome whe re in your s ys te m:
# cp -pRf /mnt/iso /tmp/workdir
3. Unmount the mounte d image :
# umount /mnt/iso
4. The conte nts of the image is now place d in the iso/ dire ctory in your working
dire ctory. Add your Kicks tart file (ks.cfg) into the iso/ dire ctory:
# cp /path/to/ks.cfg /tmp/workdir/iso
5. Ope n the isolinux/isolinux.cfg configuration file ins ide the iso/ dire ctory. This
file de te rmine s all the me nu options which appe ar in the boot me nu. A s ingle me nu
e ntry is de fine d as the following:
label linux
menu label ^Install or upgrade an existing system
menu default
kernel vmlinuz
append initrd=initrd.img
Add the ks= boot option to the line be ginning with append. The e xact s yntax
de pe nds on how you plan to boot the ISO image ; for e xample , if you plan on booting
from a CD or DVD, us e ks=cdrom:/ks.cfg. A lis t of pos s ible s ource s and the
s yntax us e d to configure the m is available in Se ction 28.4, Automating the
Ins tallation with Kicks tart.
6. Us e genisoimage in the iso/ dire ctory to cre ate a ne w bootable ISO image with
your change s include d:
# genisoimage -U -r -v -T -J -joliet-long -V "RHEL-6.6" -volset
"RHEL-6.6" -A "RHEL-6.6" -b isolinux/isolinux.bin -c
isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table
-eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o
../NEWISO.iso .
This comand will cre ate a file name d NEWISO.iso in your working dire ctory (one
dire ctory above the iso/ dire ctory).
Impo rtant
If you us e a dis k labe l to re fe r to any de vice in your isolinux.cfg (e .g.
ks=hd:LABEL=RHEL-6.6:/ks.cfg, make s ure that the labe l matche s the labe l
of the ne w ISO you are cre ating. Als o note that in boot loade r configuration,
s pace s in labe ls mus t be re place d with \x20.
7. Implant a md5 che cks um into the ne w ISO image :
# implantisomd5 ../NEWISO.iso
480
Afte r you finis h the above proce dure , your ne w image is re ady to be turne d into boot
me dia. Re fe r to Chapte r 2, Making Media for ins tructions .
To pe rform a pe n-bas e d flas h me mory kicks tart ins tallation, the kicks tart file mus t be
name d ks.cfg and mus t be locate d in the flas h me mory's top-le ve l dire ctory. The
kicks tart file s hould be on a s e parate flas h me mory drive to the boot me dia.
To s tart the Kicks tart ins tallation, boot the s ys te m us ing the boot me dia you cre ate d, and
us e the ks= boot option to s pe cify which de vice contains the USB drive . Se e Se ction 28.4,
Automating the Ins tallation with Kicks tart for de tails about the ks= boot option.
Se e Se ction 2.2, Making Minimal Boot Me dia for ins tructions on cre ating boot USB me dia
us ing the rhel-variant-version-architecture-boot.iso image file that you can
download from the Software & Download Ce nte r of the Re d Hat cus tome r portal.
No te
Cre ation of USB flas hdrive s for booting is pos s ible , but is he avily de pe nde nt on
s ys te m hardware BIOS s e ttings . Re fe r to your hardware manufacture r to s e e if your
s ys te m s upports booting to alte rnate de vice s .
481
482
483
ipv6=auto, ipv6=dhcp
IPv6 configuration for the de vice . Us e auto for automatic configuration (SLAAC,
SLAAC with DHCPv6), or dhcp for DHCPv6 only configuration (no route r
adve rtis e me nts ).
keymap=<keymap>
Ke yboard layout to us e . Valid layouts include :
be-latin1 Be lgian
bg_bds-utf8 Bulgarian
bg_pho-utf8 Bulgarian (Phone tic)
br-abnt2 Braz ilian (ABNT2)
cf Fre nch Canadian
croat Croatian
cz-us-qwertz Cz e ch
cz-lat2 Cz e ch (qwe rty)
de Ge rman
de-latin1 Ge rman (latin1)
de-latin1-nodeadkeys Ge rman (latin1 without de ad ke ys )
dvorak Dvorak
dk Danis h
dk-latin1 Danis h (latin1)
es Spanis h
et Es tonian
fi Finnis h
fi-latin1 Finnis h (latin1)
fr Fre nch
fr-latin9 Fre nch (latin9)
fr-latin1 Fre nch (latin1)
fr-pc Fre nch (pc)
fr_CH Swis s Fre nch
fr_CH-latin1 Swis s Fre nch (latin1)
gr Gre e k
hu Hungarian
hu101 Hungarian (101 ke y)
484
485
card. For e xample , if your NFS s e rve r is s e rve r.e xample .com and the kicks tart file
is in the NFS s hare /mydir/ks.cfg, the corre ct boot command would be
ks=nfs:server.example.com:/mydir/ks.cfg.
ks={http|https}://<server>/<path>
The ins tallation program looks for the kicks tart file on the HTTP or HTTPS s e rve r
<server>, as file <path>. The ins tallation program us e s DHCP to configure the
Ethe rne t card. For e xample , if your HTTP s e rve r is s e rve r.e xample .com and the
kicks tart file is in the HTTP dire ctory /mydir/ks.cfg, the corre ct boot command
would be ks=http://server.example.com/mydir/ks.cfg.
ks=hd:<device>:/<file>
The ins tallation program mounts the file s ys te m on <device> (which mus t be vfat
or e xt2), and looks for the kicks tart configuration file as <file> in that file s ys te m
(for e xample , ks=hd:sda3:/mydir/ks.cfg).
ks=bd:<biosdev>:/<path>
The ins tallation program mounts the file s ys te m on the s pe cifie d partition on the
s pe cifie d BIOS de vice <biosdev>, and looks for the kicks tart configuration file
s pe cifie d in <path> (for e xample , ks=bd:80p3:/mydir/ks.cfg). Note this doe s
not work for BIOS RAID s e ts .
ks=file:/<file>
The ins tallation program trie s to re ad the file <file> from the file s ys te m; no
mounts are done . This is normally us e d if the kicks tart file is alre ady on the
initrd image .
ks=cdrom:/<path>
The ins tallation program looks for the kicks tart file on CD-ROM, as file <path>.
ks
If ks is us e d alone , the ins tallation program configure s the Ethe rne t card to us e
DHCP. The kicks tart file is re ad from NFS s e rve r s pe cifie d by DHCP option s e rve rname . The name of the kicks tart file is one of the following:
If DHCP is s pe cifie d and the boot file be gins with a /, the boot file provide d by
DHCP is looke d for on the NFS s e rve r.
If DHCP is s pe cifie d and the boot file be gins with s ome thing othe r than a /, the
boot file provide d by DHCP is looke d for in the /kickstart dire ctory on the
NFS s e rve r.
If DHCP did not s pe cify a boot file , the n the ins tallation program trie s to re ad
the file /kickstart/1.2.3.4-kickstart, whe re 1.2.3.4 is the nume ric IP
addre s s of the machine be ing ins talle d.
ksdevice=<device>
The ins tallation program us e s this ne twork de vice to conne ct to the ne twork. You
can s pe cify the de vice in one of five ways :
the de vice name of the inte rface , for e xample , eth0
the MAC addre s s of the inte rface , for e xample , 00:12:34:56:78:9a
486
the ke yword link, which s pe cifie s the firs t inte rface with its link in the up s tate
the ke yword bootif, which us e s the MAC addre s s that pxelinux s e t in the
BOOTIF variable . Se t IPAPPEND 2 in your pxelinux.cfg file to have pxelinux
s e t the BOOTIF variable .
the ke yword ibft, which us e s the MAC addre s s of the inte rface s pe cifie d by
iBFT
For e xample , cons ide r a s ys te m conne cte d to an NFS s e rve r through the e th1
de vice . To pe rform a kicks tart ins tallation on this s ys te m us ing a kicks tart file
from the NFS s e rve r, you would us e the command ks=nfs:<server>:/<path>
ksdevice=eth1 at the boot: prompt.
kssendmac
Adds HTTP he ade rs to ks =http:// re que s t that can be he lpful for provis ioning
s ys te ms . Include s MAC addre s s of all nics in CGI e nvironme nt variable s of the
form: "X-RHN-Provis ioning-MAC-0: e th0 01:23:45:67:89:ab".
lang=<lang>
Language to us e for the ins tallation. This s hould be a language which is valid to be
us e d with the 'lang' kicks tart command.
loglevel=<level>
Se t the minimum le ve l re quire d for me s s age s to be logge d. Value s for <le ve l>
are de bug, info, warning, e rror, and critical. The de fault value is info.
mediacheck
Activate s loade r code to give us e r option of te s ting inte grity of ins tall s ource (if
an ISO-bas e d me thod).
netmask=<nm>
Ne tmas k to us e for a ne twork ins tallation.
nofallback
If GUI fails , e xit.
nofb
Do not load the VGA16 frame buffe r re quire d for doing te xt-mode ins tallation in
s ome language s .
nofirewire
Do not load s upport for fire wire de vice s .
noipv6
Dis able IPv6 ne tworking during ins tallation.
487
488
Impo rtant
If you s e le ct te xt mode for a kicks tart ins tallation, make s ure that you
s pe cify choice s for the partitioning, bootloade r, and package s e le ction
options . The s e s te ps are automate d in the te xt mode , and anaco nda
cannot prompt you for mis s ing information. If you do not provide choice s for
the s e options , anaco nda will s top the ins tallation proce s s .
updates
Prompt for s torage de vice containing update s (bug fixe s ).
updates=ftp://<path>
Image containing update s ove r FTP.
updates=http://<path>
Image containing update s ove r HTTP.
updates=https://<path>
Image containing update s ove r HTTPS.
upgradeany
Offe r to upgrade any Linux ins tallation de te cte d on the s ys te m, re gardle s s of the
conte nts or the e xis te nce of the /etc/redhat-release file .
vnc
489
Enable vnc-bas e d ins tallation. You will ne e d to conne ct to the machine us ing a vnc
clie nt application.
vncconnect=<host>[:<port>]
Conne ct to the vnc clie nt name d <host>, and optionally us e port <port>.
Re quire s 'vnc' option to be s pe cifie d as we ll.
vncpassword=<password>
Enable a pas s word for the vnc conne ction. This will pre ve nt s ome one from
inadve rte ntly conne cting to the vnc-bas e d ins tallation.
Re quire s 'vnc' option to be s pe cifie d as we ll.
490
491
the file , s e le ct Encrypt root password. If the e ncryption option is s e le cte d, whe n the file
is s ave d, the plain te xt pas s word that you type d is e ncrypte d and writte n to the kicks tart
file . Do not type an alre ady e ncrypte d pas s word and s e le ct to e ncrypt it. Be caus e a
kicks tart file is a plain te xt file that can be e as ily re ad, it is re comme nde d that an
e ncrypte d pas s word be us e d.
Choos ing Target Architecture s pe cifie s which s pe cific hardware archite cture
dis tribution is us e d during ins tallation.
Choos ing Target Architecture s pe cifie s which s pe cific hardware archite cture
dis tribution is us e d during ins tallation.
Choos ing Reboot system after installation re boots your s ys te m automatically afte r
the ins tallation is finis he d.
Kicks tart ins tallations are pe rforme d in graphical mode by de fault. To ove rride this de fault
and us e te xt mode ins te ad, s e le ct the Perform installation in text mode option.
You can pe rform a kicks tart ins tallation in inte ractive mode . This me ans that the
ins tallation program us e s all the options pre -configure d in the kicks tart file , but it allows
you to pre vie w the options in e ach s cre e n be fore continuing to the ne xt s cre e n. To
continue to the ne xt s cre e n, click the Next button afte r you have approve d the s e ttings or
change the m be fore continuing the ins tallation. To s e le ct this type of ins tallation, s e le ct
the Perform installation in interactive mode option.
492
NFS Choos e this option to ins tall or upgrade from an NFS s hare d dire ctory. In the te xt
fie ld for the NFS s e rve r, e nte r a fully-qualifie d domain name or IP addre s s . For the NFS
dire ctory, e nte r the name of the NFS dire ctory that contains the variant dire ctory of
the ins tallation tre e . For e xample , if the NFS s e rve r contains the dire ctory
/mirrors/redhat/i386/Server/, e nte r /mirrors/redhat/i386/ for the NFS dire ctory.
FTP Choos e this option to ins tall or upgrade from an FTP s e rve r. In the FTP s e rve r
te xt fie ld, e nte r a fully-qualifie d domain name or IP addre s s . For the FTP dire ctory,
e nte r the name of the FTP dire ctory that contains the variant dire ctory. For e xample , if
the FTP s e rve r contains the dire ctory /mirrors/redhat/i386/Server/, e nte r
/mirrors/redhat/i386/Server/ for the FTP dire ctory. If the FTP s e rve r re quire s a
us e rname and pas s word, s pe cify the m as we ll.
HTTP Choos e this option to ins tall or upgrade from an HTTP s e rve r. In the te xt fie ld
for the HTTP s e rve r, e nte r the fully-qualifie d domain name or IP addre s s . For the HTTP
dire ctory, e nte r the name of the HTTP dire ctory that contains the variant dire ctory. For
e xample , if the HTTP s e rve r contains the dire ctory /mirrors/redhat/i386/Server/,
e nte r /mirrors/redhat/i386/Server/ for the HTTP dire ctory.
Hard Drive Choos e this option to ins tall or upgrade from a hard drive . Hard drive
ins tallations re quire the us e of ISO image s . Be s ure to ve rify that the ISO image s are
intact be fore you s tart the ins tallation. To ve rify the m, us e an md5sum program as we ll
as the linux mediacheck boot option as dis cus s e d in Se ction 28.6.1, Ve rifying Boot
Me dia. Ente r the hard drive partition that contains the ISO image s (for e xample ,
/dev/hda1) in the Hard Drive Partition te xt box. Ente r the dire ctory that contains
the ISO image s in the Hard Drive Directory te xt box.
493
GRUB is the de fault boot loade r for Re d Hat Ente rpris e Linux on x86 / x86_64
archite cture s . If you do not want to ins tall a boot loade r, s e le ct Do not install a boot
loader. If you choos e not to ins tall a boot loade r, make s ure you cre ate a boot dis ke tte or
have anothe r way to boot your s ys te m, s uch as a third-party boot loade r.
You mus t choos e whe re to ins tall the boot loade r (the Mas te r Boot Re cord or the firs t
s e ctor of the /boot partition). Ins tall the boot loade r on the MBR if you plan to us e it as
your boot loade r.
To pas s any s pe cial parame te rs to the ke rne l to be us e d whe n the s ys te m boots , e nte r
the m in the Kernel parameters te xt fie ld. For e xample , if you have an IDE CD-ROM
Write r, you can te ll the ke rne l to us e the SCSI e mulation drive r that mus t be loade d
be fore us ing cdrecord by configuring hdd=ide-scsi as a ke rne l parame te r (whe re hdd is
the CD-ROM de vice ).
You can pas s word prote ct the GRUB boot loade r by configuring a GRUB pas s word. Se le ct
Use GRUB password, and e nte r a pas s word in the Password fie ld. Type the s ame
pas s word in the Confirm Password te xt fie ld. To s ave the pas s word as an e ncrypte d
pas s word in the file , s e le ct Encrypt GRUB password. If the e ncryption option is s e le cte d,
whe n the file is s ave d, the plain te xt pas s word that you type d is e ncrypte d and writte n to
the kicks tart file . If the pas s word you type d was alre ady e ncrypte d, unche ck the
e ncryption option.
Impo rtant
It is highly re comme nde d to s e t up a boot loade r pas s word on e ve ry machine . An
unprote cte d boot loade r can allow a pote ntial attacke r to modify the s ys te m's boot
options and gain acce s s to the s ys te m. Se e the chapte r title d Workstation Security in
the Red Hat Enterprise Linux Security Guide for more information on boot loade r
pas s words and pas s word s e curity in ge ne ral.
If Upgrade an existing installation is s e le cte d on the Installation Method page ,
s e le ct Upgrade existing boot loader to upgrade the e xis ting boot loade r configuration,
while pre s e rving the old e ntrie s .
494
No te
Although anaconda and kickstart s upport Logical Volume Manage me nt (LVM), at
pre s e nt the re is no me chanis m for configuring this us ing the Kickst art
Co nf igurat o r.
495
496
497
498
If the s ys te m to be ins talle d via kicks tart doe s not have an Ethe rne t card, do not configure
one on the Network Configuration page .
Ne tworking is only re quire d if you choos e a ne tworking-bas e d ins tallation me thod (NFS,
FTP, or HTTP). Ne tworking can always be configure d afte r ins tallation with the Net wo rk
Administ rat io n T o o l (system-config-network). Re fe r to the Re d Hat Ente rpris e Linux
De ployme nt Guide for de tails .
For e ach Ethe rne t card on the s ys te m, click Add Network Device and s e le ct the ne twork
de vice and ne twork type for the de vice . Se le ct eth0 to configure the firs t Ethe rne t card,
eth1 for the s e cond Ethe rne t card, and s o on.
499
The s e me thods are not e nable d by de fault. To e nable one or more of the s e me thods ,
click the appropriate tab, click the che ckbox ne xt to Enable, and e nte r the appropriate
information for the authe ntication me thod. Re fe r to the Re d Hat Ente rpris e Linux
De ployme nt Guide for more information about the options .
500
Kicks tart can s e t SELinux to enforcing, permissive or disabled mode . Fine r graine d
configuration is not pos s ible at this time .
501
502
You can add commands to run on the s ys te m imme diate ly afte r the kicks tart file has be e n
pars e d and be fore the ins tallation be gins . If you have configure d the ne twork in the
kicks tart file , the ne twork is e nable d be fore this s e ction is proce s s e d. To include a pre ins tallation s cript, type it in the te xt are a.
Impo rtant
Do not include the %pre command. It is adde d for you.
No te
The pre -ins tallation s cript is run afte r the s ource me dia is mounte d and s tage 2 of
the bootloade r has be e n loade d. For this re as on it is not pos s ible to change the
s ource me dia in the pre -ins tallation s cript.
503
Impo rtant
Do not include the %post command. It is adde d for you.
For e xample , to change the me s s age of the day for the ne wly ins talle d s ys te m, add the
following command to the %post s e ction:
echo "Hackers will be punished" > /etc/motd
No te
More e xample s can be found in Se ction 32.7.1, Example s .
504
505
506
P ar t V. Af t e r Ins t allat io n
507
508
C hapt e r 34 . Fir s t bo o t
This s cre e n dis plays the ove rall lice ns ing te rms for Re d Hat Ente rpris e Linux.
509
No te
Eve n if a s ys te m is not re gis te re d at firs tboot, it can be re gis te re d with any of thos e
thre e s ubs cription s e rvice s late r, us ing the Re d Hat Subs cription Manage r tools
[13] .
More information about the Re d Hat Subs cription Manage r tools can be found in the
Red Hat Subscription Management Guide.
510
C hapt e r 34 . Fir s t bo o t
(hos te d s e rvice s ), Subs cription As s e t Manage r (on-pre mis e s ubs cription s e rvice
and proxie d conte nt de live ry), and CloudForms Sys te m Engine (on-pre mis e
s ubs cription and conte nt de live ry s e rvice s ).
This option is the de fault. Re d Hat Subs cription Manage me nt is s trongly
re comme nde d for organiz ations that do not run a local Sate llite s e rve r.
Red Hat Net wo rk (RHN) Classic
Se le ct the Red Hat Network (RHN) Classic option to us e the le gacy s ys te ms manage me nt fe ature s of Re d Hat Ne twork. While RHN Clas s ic can be us e d with
Re d Hat Ente rpris e Linux 6.x s ys te ms , it is inte nde d primarily for e xis ting, le gacy
s ys te ms . It is re comme nde d that ne w ins tallations us e Re d Hat Subs cription
Manage me nt.
An RHN Sat ellit e o r RHN Pro xy
Us e this option in e nvironme nts with acce s s to a local mirror of the Re d Hat
Ne twork conte nt.
511
Subs cription As s e t Manage r, an on-pre mis e s ubs cription s e rve r which proxie s conte nt
de live ry back to the Cus tome r Portal's s e rvice s
CloudForms Sys te m Engine , an on-pre mis e s e rvice which handle s both s ubs cription
s e rvice s and conte nt de live ry
The s pe cific type of s ubs cription/conte nt s e rvice doe s not ne e d to be s e le cte d; all thre e
s e rve r type s (Cus tome r Portal Subs cription Manage me nt, Subs cription As s e t Manage r, and
CloudForms Sys te m Engine ) are within Re d Hat Subs cription Manage me nt and us e the
s ame type s of s e rvice APIs . The only thing that ne e ds to be ide ntifie d is the hos tname of
the s e rvice to conne ct to and the n the appropriate us e r cre de ntials for that s e rvice .
1. To ide ntify which s ubs cription s e rve r to us e for re gis tration, e nte r the hos tname of
the s e rvice . The de fault s e rvice is Cus tome r Portal Subs cription Manage me nt, with
the hos tname subscription.rhn.redhat.com. To us e a diffe re nt s ubs cription
s e rvice , s uch as Subs cription As s e t Manage r, e nte r the hos tname of the local
s e rve r.
512
C hapt e r 34 . Fir s t bo o t
If you have los t your login or pas s word for the Cus tome r Portal, re cove r the m from
https ://www.re dhat.com/wapps /s s o/los tPas s word.html. For los t login or pas s word
information for Subs cription As s e t Manage r or CloudForms Sys te m Engine , contact
your local adminis trator.
4. Se t the s ys te m name for the hos t. This is anything which unique ly and cle arly
ide ntifie s the s ys te m within the s ubs cription s e rvice inve ntory. This is us ually the
hos tname or fully-qualifie d domain name of the machine , but it can be any s tring.
5. Optional. Se t whe the r s ubs criptions s hould be s e t manually afte r re gis tration. By
de fault, this che ckbox is unche cke d s o that the be s t-matche d s ubs criptions are
automatically applie d to the s ys te m. Se le cting this che ckbox me ans that
s ubs criptions mus t be adde d to the s ys te m manually afte r firs tboot re gis tration is
comple te . (Eve n if s ubs criptions are auto-attache d, additional s ubs criptions can be
adde d to the s ys te m late r us ing the local Subs cription Manage r tools .)
6. Whe n re gis tration be gins , firs tboot s cans for organiz ations and e nvironme nts (s ubdomains within the organiz ation) to which to re gis te r the s ys te m.
513
514
C hapt e r 34 . Fir s t bo o t
515
C hapt e r 34 . Fir s t bo o t
Cre ate a us e r account for yours e lf with this s cre e n. Always us e this account to log in to
your Re d Hat Ente rpris e Linux s ys te m, rathe r than us ing the root account.
517
518
C hapt e r 34 . Fir s t bo o t
519
afte r ins tallation, click Syst em Administ rat io n Dat e & T ime.
34.5. Kdump
Us e this s cre e n to s e le ct whe the r or not to us e Kdump on this s ys te m. Kdump is a
ke rne l cras h dumping me chanis m. In the e ve nt of a s ys te m cras h, Kdump will capture
information from your s ys te m that can be invaluable in de te rmining the caus e of the
cras h.
Note that if you s e le ct this option, you will ne e d to re s e rve me mory for Kdump and that
this me mory will not be available for any othe r purpos e .
520
C hapt e r 34 . Fir s t bo o t
521
[13] System s can also be registered with Satellite or RHN C lassic. For Satellite inform ation, see
the Satellite docum entation. For inform ation on using RHN C lassic, see the appendix in the Red
Hat Subscription Management Guide.
522
C hapt e r 35. Yo ur Ne xt St e ps
Figure 35.1. List ing Inst alled Driver Updat e RPM Packages
Alte rnative ly, you can us e the command line , as follows :
$ rpm -q a | egrep ^kmod-
523
Note the - on the e nd of kmod. This will lis t all ins talle d package s that be gin with kmod-,
which s hould include all drive r update s that are curre ntly ins talle d on your s ys te m.
Additional drive rs provide d by third-party update s oftware are not lis te d in this output.
Contact the third-party ve ndor for de tails .
To ins tall a ne w drive r update rpm package :
1. Download the drive r update rpm package from the location s pe cifie d by Re d Hat or
your hardware ve ndor. The package file name will be gin with kmod (s hort for kernel
module) and have a form s imilar to this e xample :
kmod-foo-1 .05-2.el6.6.i686
In the e xample , the drive r update rpm package s upplie s a drive r update name d
f o o with ve rs ion numbe r 1.05-2 for Re d Hat Ente rpris e Linux 6.6, on i686 s ys te ms .
Drive r update rpm package s are s igne d package s , and like all othe r s oftware
package s , the y are automatically validate d at ins tall time . To pe rform this s te p
manually, type the following at a command line :
$ rpm --c hecksig -v filename.rpm
whe re filename.rpm is the drive r update rpm package file name . This ve rifie s the
package agains t us ing the s tandard Re d Hat GPG package s igning ke y that is
alre ady ins talle d on any Re d Hat Ente rpris e Linux 6.6 s ys te m. If you ne e d this ke y
for ve rification purpos e s on anothe r s ys te m, you can can obtain it from:
https ://acce s s .re dhat.com/s e curity/te am/ke y/
2. Locate and double -click the file that you downloade d. The s ys te m might prompt you
for the root pas s word, afte r which it will pre s e nt the following Installing
Packages box:
524
C hapt e r 35. Yo ur Ne xt St e ps
Linux, your s ys te m will continue to us e the drive r update s that you have ins talle d. The re
is no ne e d to re -ins tall drive r update s following an e rrata update . Ge ne rally, whe n Re d Hat
re le as e s a ne w ve rs ion of Re d Hat Ente rpris e Linux, all drive r update s for the pre vious
ve rs ion are incorporate d in the ne w ve rs ion. Howe ve r, if it was not pos s ible to include a
particular drive r, you will ne e d to pe rform anothe r drive r update whe n you ins tall the ne w
ve rs ion of Re d Hat Ente rpris e Linux. In this cas e , Re d Hat or your hardware party ve ndor
will inform you of the location of the update .
525
Missing So ftware
Due to change s in package comple me nts be twe e n Re d Hat Ente rpris e Linux
re le as e s , it is pos s ible this me thod may not re s tore all the s oftware on your
s ys te m. You can us e the routine s above to again compare the s oftware on your
s ys te m, and re me dy any proble ms you find.
526
C hapt e r 35. Yo ur Ne xt St e ps
35.3.1.1. Enabling Access t o Sof t ware Reposit ories T hrough t he Int ernet
If you s upplie d your Re d Hat Ne twork s ubs cription numbe r during the ins tallation proce s s ,
your s ys te m is alre ady configure d to acce s s Re d Hat Ente rpris e Linux re pos itorie s
through the Inte rne t. The re fore , all you mus t do is e ns ure that the s ys te m can acce s s the
Inte rne t. If you have an e xis ting, wire d ne twork conne ction available , this proce s s is
s traightforward:
1. If you are not alre ady root, s witch us e rs to the root account:
su 2. Ens ure that the s ys te m is plugge d into your ne twork. Note that your ne twork might
be as s mall as two de vice s a compute r and an e xte rnal mode m/route r.
3. Run system-config-network. The ne twork configuration tool s tarts and dis plays
the Select Action s cre e n.
4. Se le ct Device co nf igurat io n and pre s s Enter. The ne twork configuration tool
dis plays the Select A Device s cre e n with a lis t of ne twork inte rface s pre s e nt on
your s ys te m. The firs t inte rface is name d eth0 by de fault.
5. Se le ct a ne twork inte rface to configure and pre s s Enter. The ne twork configuration
tool take s you to the Network Configuration s cre e n.
6. You can manually configure a s tatic IP, gate way, and DNS s e rve rs on this s cre e n or
le ave the s e fie lds blank to acce pt the de fault value s . Whe n you have chos e n a
configuration, s e le ct OK, and pre s s Enter. The ne twork configuration tool take s you
back to the Select A Device s cre e n.
7. Se le ct Save and pre s s Enter. The ne twork configuration tool take s you back to the
Select Action s cre e n.
527
8. Se le ct Save&Quit and pre s s Enter. The ne twork configuration tool s ave s your
s e ttings and e xits .
9. Run ifup interface, whe re interface is the ne twork inte rface that you configure d
with the ne twork configuration tool. For e xample , run ifup eth0 to s tart eth0.
Configuration of dial-up or wire le s s Inte rne t conne ctions is more complicate d and be yond
the s cope of this guide .
35.3.1.2. Using a Red Hat Ent erprise Linux Inst allat ion DVD as a Sof t ware
Reposit ory
To us e a Re d Hat Ente rpris e Linux ins tallation DVD as a s oftware re pos itory, e ithe r in the
form of a phys ical dis c, or in the form of an ISO image file .
1. If you are us ing a phys ical DVD, ins e rt the dis c into your compute r.
2. If you are not alre ady root, s witch us e rs to the root account:
su 3. Cre ate a mount point for the re pos itory:
mkdir -p /path/to/repo
whe re /path/to/repo is a location for the re pos itory, for e xample , /mnt/repo
4. Mount the DVD on the mount point that you jus t cre ate d. If you are us ing a phys ical
dis c, you ne e d to know the device name of your DVD drive . You can find the name s
of any CD or DVD drive s on your s ys te m with the command cat
/proc/sys/dev/cdrom/info. The firs t CD or DVD drive on the s ys te m is typically
name d sr0. Whe n you know the de vice name , mount the DVD:
mount -r -t iso9660 /dev/device_name /path/to/repo
For e xample : mount -r -t iso9660 /dev/sr0 /mnt/repo
If you are us ing an ISO image file of a dis c, mount the image file like this :
mount -r -t iso9660 -o loop /path/to/image/file.iso /path/to/repo
For e xample : mount -r -o loop /home/root/Downloads/RHEL6.6-Server-i386DVD.iso /mnt/repo
Note that you can only mount an image file if the s torage de vice that holds the
image file is its e lf mounte d. For e xample , if the image file is s tore d on a hard drive
that is not mounte d automatically whe n the s ys te m boots , you mus t mount the hard
drive be fore you mount an image file s tore d on that hard drive . Cons ide r a hard
drive name d /dev/sdb that is not automatically mounte d at boot time and which has
an image file s tore d in a dire ctory name d Downloads on its firs t partition:
mkdir /mnt/temp
mount /dev/sdb1 /mnt/temp
mkdir /mnt/repo
mount -r -t iso9660 -o loop mount -r -o loop
/mnt/temp/Downloads/RHEL6.6-Server-i386-DVD.iso /mnt/repo
528
C hapt e r 35. Yo ur Ne xt St e ps
If you are not s ure whe the r a s torage de vice is mounte d, run the mount command
to obtain a lis t of curre nt mounts . If you are not s ure of the de vice name or partition
numbe r of a s torage de vice , run fdisk -l and try to ide ntify it in the output.
5. Cre ate a ne w repo file in the /etc/yum.repos.d/ dire ctory. The name of the file is
not important, as long as it e nds in .repo. For e xample , dvd.repo is an obvious
choice .
a. Choos e a name for the re po file and ope n it as a ne w file with the vi te xt
e ditor. For e xample :
vi /etc/yum.repos.d/dvd.repo
b. Pre s s the I ke y to e nte r insert mode .
c. Supply the de tails of the re pos itory. For e xample :
[dvd]
baseurl=file:///mnt/repo/Server
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
The name of the re pos itory is s pe cifie d in s quare bracke ts in this
e xample , [dvd]. The name is not important, but you s hould choos e
s ome thing that is me aningful and re cogniz able .
The line that s pe cifie s the baseurl s hould contain the path to the mount
point that you cre ate d pre vious ly, s uffixe d with /Server for a Re d Hat
Ente rpris e Linux s e rve r ins tallation DVD, or with /Client for a Re d Hat
Ente rpris e Linux clie nt ins tallation DVD.
d. Pre s s the Esc ke y to e xit insert mode .
e . Type :wq and pre s s the Enter ke y to s ave the file and e xit the vi te xt
e ditor.
f. Afte r ins talling or upgrading s oftware from the DVD, de le te the re po file that
you cre ate d.
529
530
531
Re s cue mode provide s the ability to boot a s mall Re d Hat Ente rpris e Linux e nvironme nt
e ntire ly from CD-ROM, or s ome othe r boot me thod, ins te ad of the s ys te m's hard drive .
As the name implie s , re s cue mode is provide d to re s cue you from s ome thing. During
normal ope ration, your Re d Hat Ente rpris e Linux s ys te m us e s file s locate d on your
s ys te m's hard drive to do e ve rything run programs , s tore your file s , and more .
Howe ve r, the re may be time s whe n you are unable to ge t Re d Hat Ente rpris e Linux
running comple te ly e nough to acce s s file s on your s ys te m's hard drive . Us ing re s cue
mode , you can acce s s the file s s tore d on your s ys te m's hard drive , e ve n if you cannot
actually run Re d Hat Ente rpris e Linux from that hard drive .
To boot into re s cue mode , you mus t be able to boot the s ys te m us ing one of the following
me thods [14] :
By booting the s ys te m from a boot CD-ROM or DVD.
By booting the s ys te m from othe r ins tallation boot me dia, s uch as USB flas h de vice s .
By booting the s ys te m from the Re d Hat Ente rpris e Linux ins tallation DVD.
Once you have boote d us ing one of the de s cribe d me thods , add the ke yword rescue as a
ke rne l parame te r. For e xample , for an x86 s ys te m, type the following command at the
ins tallation boot prompt:
linux rescue
If your s ys te m re quire s a third-party drive r provide d on a driver disc to boot, load the
drive r with the additional option dd:
linux rescue dd
For more information on us ing a drive r dis c at boot time , re fe r to Se ction 6.3.3, Us e a
Boot Option to Spe cify a Drive r Update Dis k for x86 s ys te ms or Se ction 13.3.3, Us e a
Boot Option to Spe cify a Drive r Update Dis k for Powe r Sys te ms s e rve rs .
If a drive r that is part of the Re d Hat Ente rpris e Linux 6.6 dis tribution pre ve nts the s ys te m
from booting, blacklis t that drive r with the rdblacklist option. For e xample , to boot into
re s cue mode without the foobar drive r, run:
linux rescue rdblacklist=foobar
You are prompte d to ans we r a fe w bas ic que s tions , including which language to us e . It als o
prompts you to s e le ct whe re a valid re s cue image is locate d. Se le ct from Local CD-ROM,
Hard Drive, NFS image, FTP, or HTTP. The location s e le cte d mus t contain a valid
ins tallation tre e , and the ins tallation tre e mus t be for the s ame ve rs ion of Re d Hat
Ente rpris e Linux as the Re d Hat Ente rpris e Linux dis k from which you boote d. If you us e d a
boot CD-ROM or othe r me dia to s tart re s cue mode , the ins tallation tre e mus t be from the
s ame tre e from which the me dia was cre ate d. For more information about how to s e tup an
ins tallation tre e on a hard drive , NFS s e rve r, FTP s e rve r, or HTTP s e rve r, re fe r to the
e arlie r s e ction of this guide .
If you s e le ct a re s cue image that doe s not re quire a ne twork conne ction, you are as ke d
whe the r or not you want to e s tablis h a ne twork conne ction. A ne twork conne ction is us e ful
if you ne e d to backup file s to a diffe re nt compute r or ins tall s ome RPM package s from a
s hare d ne twork location, for e xample .
532
533
534
In e me rge ncy mode , you are boote d into the mos t minimal e nvironme nt pos s ible . The root
file s ys te m is mounte d re ad-only and almos t nothing is s e t up. The main advantage of
e me rge ncy mode ove r s ingle -us e r mode is that the init file s are not loade d. If init is
corrupte d or not working, you can s till mount file s ys te ms to re cove r data that could be
los t during a re -ins tallation.
To boot into e me rge ncy mode , us e the s ame me thod as de s cribe d for s ingle -us e r mode
in Se ction 36.1.3, Booting into Single -Us e r Mode with one e xce ption, re place the ke yword
single with the ke yword emergency.
535
7. Follow the prompts as de s cribe d in Se ction 36.2, Re s cue Mode on Powe r Sys te ms
s e rve rs . An additional prompt for the ins tallation s ource appe ars . Se le ct NFS or
FTP (as appropriate ) and comple te the following ne twork configuration s cre e n.
8. Whe n the Linux s ys te m has boote d into re s cue mode , the CD-ROM drive is
available for us e and you can mount the drive r me dia to acce s s the SCSI utilitie s .
536
2. Make the RPM package that contains the drive r available . For e xample , mount a CD
or USB flas h drive and copy the RPM package to a location of your choice unde r
/mnt/sysimage/, for e xample : /mnt/sysimage/root/drivers/.
3. Change the root dire ctory to /mnt/sysimage/:
chroot /mnt/sysimage/
4. Us e the rpm -ivh command to ins tall the drive r package . For e xample , to ins tall
the kmod-foobar drive r package from /root/drivers/, run:
rpm -i vh /root/drivers/kmod-foobar-1 .2.04 .17.el6.i686
Note that /root/drivers/ in this chroot e nvironme nt is
/mnt/sysimage/root/drivers/ in the original re s cue e nvironme nt.
Whe n you have finis he d re moving and ins talling drive rs , re boot the s ys te m.
537
[14] Refer to the earlier sections of this guide for m ore details.
538
539
38.1. Syst ems Regist ered wit h Red Hat Subscript ion
Management
Se ve ral diffe re nt s ubs cription s e rvice s us e the s ame , ce rtificate -bas e d frame work to
ide ntify s ys te ms , ins talle d products , and attache d s ubs criptions . The s e s e rvice s are
Cus tome r Portal Subs cription Manage me nt (hos te d), Subs cription As s e t Manage r (onpre mis e s ubs cription s e rvice ), and CloudForms Sys te m Engine (on-pre mis e s ubs cription
and conte nt de live ry s e rvice s ). The s e are all part of Red Hat Subscription Management.
For all s e rvice s within Re d Hat Subs cription Manage me nt, the s ys te ms are manage d with
the Re d Hat Subs cription Manage r clie nt tools .
To unre gis te r a s ys te m re gis te re d with a Re d Hat Subs cription Manage me nt s e rve r, us e
the unregister command.
[root@server ~]# subscription-manager unregister --username=name
No te
This command mus t be run as root.
T IP
If the s ys te m is be ing unre gis te re d in orde r to re gis te r it with Re d Hat Subs cription
Manage me nt (Cus tome r Portal Subs cription Manage me nt, Subs cription As s e t
Manage r, or CloudForms Sys te m Engine ), the n ins te ad of unre gis te ring the s ys te m,
us e the rhn-migrate-classic-to-rhsm s cript to migrate the s ys te m and all its
attache d s ubs criptions to the s pe cifie d Re d Hat Subs cription Manage me nt s e rve r.
Us ing the migration s cripts is cove re d in the Subscription Management Guide.
540
541
To unins tall Re d Hat Ente rpris e Linux from your x86-bas e d s ys te m, you mus t re move the
Re d Hat Ente rpris e Linux boot loade r information from your mas te r boot re cord (MBR) and
re move any partitions that contain the ope rating s ys te m. The me thod for re moving Re d
Hat Ente rpris e Linux from your compute r varie s , de pe nding on whe the r Re d Hat Ente rpris e
Linux is the only ope rating s ys te m ins talle d on the compute r, or whe the r the compute r is
configure d to dual-boot Re d Hat Ente rpris e Linux and anothe r ope rating s ys te m.
The s e ins tructions cannot cove r e ve ry pos s ible compute r configuration. If your compute r
is configure d to boot thre e or more ope rating s ys te ms , or has a highly-cus tomiz e d
partition s che me , us e the following s e ctions as a ge ne ral guide to partition re moval with
the various tools de s cribe d. In the s e s ituations , you will als o ne e d to le arn to configure
your chos e n bootloade r. Se e Appe ndix E, The GRUB Boot Loader for a ge ne ral introduction
to the s ubje ct, but de taile d ins tructions are be yond the s cope of this docume nt.
39.1. Red Hat Ent erprise Linux is t he Only Operat ing Syst em
on t he Comput er
If Re d Hat Ente rpris e Linux is the only ope rating s ys te m on your compute r, us e the
ins tallation me dia for the re place me nt ope rating s ys te m to re move Re d Hat Ente rpris e
Linux. Example s of ins tallation me dia include the Windows XP ins tallation CD, Windows
Vis ta ins tallation DVD, or the ins tallation CD, CDs , or DVD of anothe r Linux dis tribution.
542
Note that s ome manufacture rs of factory-built compute rs pre -ins talle d with Micros oft
Windows do not s upply the Windows ins tallation CD or DVD with the compute r. The
manufacture r may ins te ad have s upplie d the ir own "s ys te m re s tore dis c", or have
include d s oftware with the compute r that allowe d you to cre ate your own "s ys te m re s tore
dis c" whe n you firs t s tarte d the compute r. In s ome cas e s , the s ys te m re s tore s oftware is
s tore d on a s e parate partition on the s ys te m's hard drive . If you cannot ide ntify the
ins tallation me dia for an ope rating s ys te m that was pre -ins talle d on your compute r,
cons ult the docume ntation s upplie d with the machine , or contact the manufacture r.
Whe n you have locate d the ins tallation me dia for your chos e n ope rating s ys te m:
1. Back up any data that you want to ke e p.
2. Shut down the compute r.
3. Boot your compute r with the ins tallation dis c for the re place me nt ope rating s ys te m.
4. Follow the prompts pre s e nte d during the ins tallation proce s s . Windows , OS X, and
mos t Linux ins tallation dis cs allow you to manually partition your hard drive during
the ins tallation proce s s , or will offe r you the option to re move all partitions and
s tart with a fre s h partition s che me . At this point, re move any e xis ting partitions that
the ins tallation s oftware de te cts or allow the ins talle r to re move the partitions
automatically. "Sys te m re s tore " me dia for compute rs pre -ins talle d with Micros oft
Windows might cre ate a de fault partition layout automatically without input from you.
Warning
If your compute r has s ys te m re s tore s oftware s tore d on a partition on a hard
drive , take care whe n re moving partitions while ins talling an ope rating
s ys te m from othe r me dia. Unde r the s e circums tance s , you could de s troy the
partition holding the s ys te m re s tore s oftware .
39.2.1. Your Comput er Dual-boot s Red Hat Ent erprise Linux and a
Microsof t Windows Operat ing Syst em
39.2.1.1. Windows 2000, Windows Server 2000, Windows XP, and Windows
Server 2003
543
Warning
Once you comme nce this proce s s , your compute r may be le ft in an unbootable s tate
until you comple te the e ntire s e t of ins tructions . Care fully re ad the s te ps be low
be fore be ginning the re moval proce s s . Cons ide r ope ning the s e ins tructions on
anothe r compute r or printing the m s o that you have acce s s to the m at all time s
during the proce s s .
This proce dure re lie s on the Windo ws Reco very Co nso le that loads from the
Windows ins tallation dis k, s o you will not be able to comple te the proce dure without
acce s s to this dis k. If you s tart this proce dure and do not comple te it, you could
le ave your compute r in a condition whe re you cannot boot it. The "s ys te m re s tore
dis k" s upplie d with s ome factory-built compute rs that are s old with Windows pre ins talle d on the m might not include the Windo ws Reco very Co nso le.
During the proce s s outline d in the s e ins tructions , the Windo ws Reco very Co nso le
will prompt you for the Adminis trator pas s word for your Windows s ys te m. Do not
follow the s e ins tructions unle s s you know the Adminis trator pas s word for your
s ys te m or are ce rtain that an Adminis trator pas s word has ne ve r be e n cre ate d,
e ve n by the compute r manufacture r.
No te
This s te p is not re quire d to re move Re d Hat Ente rpris e Linux from your
compute r. Howe ve r, if you s kip this s te p, you will le ave part of your hard
drive 's s torage capacity unus able by Windows . De pe nding on your
configuration, this might be a s ignificant portion of the s torage capacity of the
drive .
544
De cide whe the r to e xte nd an e xis ting Windows partition to us e the e xtra s pace , or
cre ate a ne w Windows partition in that s pace . If you cre ate ne w a Windows partition,
Windows will allocate a ne w drive le tte r to it and will inte ract with it as if it is a
s e parate hard drive .
Ext ending an Exist ing Windo ws Part it io n
No te
The diskpart tool us e d in this s te p is ins talle d as part of the Windows XP
and Windows 2003 ope rating s ys te ms . If you are pe rforming this s te p on a
compute r running Windows 2000 or Windows Se rve r 2000, you can download
a ve rs ion of diskpart for your ope rating s ys te m from the Micros oft we bs ite .
a. Click Start>Run..., type diskpart and pre s s Enter. A command window
appe ars .
b. Type list volume and pre s s Enter. Diskpart dis plays a lis t of the
partitions on your s ys te m with a volume numbe r, its drive le tte r, volume
labe l, file s ys te m type , and s iz e . Ide ntify the Windows partition that you would
like to us e to occupy the s pace vacate d on your hard drive by Re d Hat
Ente rpris e Linux and take note of its volume numbe r (for e xample , your
Windows C: drive might be "Volume 0").
c. Type select volume N (whe re N is the volume numbe r for the Windows
partition that you want to e xte nd) and pre s s Enter. Now type extend and
pre s s Enter. Diskpart now e xte nds your chos e n partition to fill the
re maining s pace on your hard drive . It will notify you whe n the ope ration is
comple te .
Adding a New Windo ws Part it io n
a. In the Disk Management window, right-click on dis k s pace that Windows
labe ls as unallocated and s e le ct New Partition from the me nu. The New
Part it io n Wizard s tarts .
b. Follow the prompts pre s e nte d by the New Part it io n Wizard. If you acce pt
the de fault options , the tool will cre ate a ne w partition that fills all available
s pace on the hard drive , as s igns it the ne xt available drive le tte r, and
formats it with the NTFS file s ys te m.
3. Re s tore the Windows bootloade r
a. Ins e rt the Windows ins tallation dis k and re s tart your compute r. As your
compute r s tarts , the following me s s age will appe ar on the s cre e n for a fe w
s e conds :
Press any key to boot from CD
Pre s s any ke y while the me s s age is s till s howing and the Windows
ins tallation s oftware will load.
b. Whe n the Welcome to Setup s cre e n appe ars , you can s tart the Windo ws
Reco very Co nso le. The proce dure is s lightly diffe re nt on diffe re nt ve rs ions
of Windows :
545
On Windows 2000 and Windows Se rve r 2000, pre s s the R ke y, the n the C
ke y.
On Windows XP and Windows Se rve r 2003, pre s s the R ke y.
c. The Windo ws Reco very Co nso le s cans your hard drive s for Windows
ins tallations , and as s igns a numbe r to e ach one . It dis plays a lis t of Windows
ins tallations and prompts you to s e le ct one . Type the numbe r corre s ponding
to the Windows ins tallation that you want to re s tore .
d. The Windo ws Reco very Co nso le prompts you for the Adminis trator
pas s word for your Windows ins tallation. Type the Adminis trator pas s word
and pre s s the Enter ke y. If the re is no adminis trator pas s word for this
s ys te m, pre s s only the Enter ke y.
e . At the prompt, type the command fixmbr and pre s s the Enter. The f ixmbr
tool now re s tore s the Mas te r Boot Re cord for the s ys te m.
f. Whe n the prompt re appe ars , type exit and pre s s the Enter ke y.
g. Your compute r will re s tart and boot your Windows ope rating s ys te m.
Warning
Once you comme nce this proce s s , your compute r may be le ft in an unbootable s tate
until you comple te the e ntire s e t of ins tructions . Care fully re ad the s te ps be low
be fore be ginning the re moval proce s s . Cons ide r ope ning the s e ins tructions on
anothe r compute r or printing the m s o that you have acce s s to the m at all time s
during the proce s s .
This proce dure re lie s on the Windo ws Reco very Enviro nment that loads from the
Windows ins tallation dis k and you will not be able to comple te the proce dure without
acce s s to this dis k. If you s tart this proce dure and do not comple te it, you could
le ave your compute r in a condition whe re you cannot boot it. The "s ys te m re s tore
dis k" s upplie d with s ome factory-built compute rs that are s old with Windows pre ins talle d on the m might not include the Windo ws Reco very Enviro nment .
546
partitions , Windows labe ls the s pace on the hard drive pre vious ly occupie d
by thos e partitions as unallocated.
2. Enable Windows to us e the s pace on your hard drive vacate d by Re d Hat Ente rpris e
Linux (optional)
No te
This s te p is not re quire d to re move Re d Hat Ente rpris e Linux from your
compute r. Howe ve r, if you s kip this s te p, you will le ave part of your hard
drive 's s torage capacity unus able by Windows . De pe nding on your
configuration, this might be a s ignificant portion of the s torage capacity of the
drive .
De cide whe the r to e xte nd an e xis ting Windows partition to us e the e xtra s pace , or
cre ate a ne w Windows partition in that s pace . If you cre ate ne w a Windows partition,
Windows will allocate a ne w drive le tte r to it and will inte ract with it as if it is a
s e parate hard drive .
Ext ending an Exist ing Windo ws Part it io n
a. In the Disk Management window, right-click on the Windows partition that
you want to e xte nd and s e le ct Extend Volume from the me nu. The Ext end
Vo lume Wizard ope ns .
b. Follow the prompts pre s e nte d by the Ext end Vo lume Wizard. If you acce pt
the de faults that it offe rs you, the tool will e xte nd the s e le cte d volume to fill
all available s pace on the hard drive .
Adding a New Windo ws Part it io n
a. In the Disk Management window, right-click on dis k s pace that Windows
labe ls as unallocated and s e le ct New Simple Volume from the me nu. The
New Simple Vo lume Wizard s tarts .
b. Follow the prompts pre s e nte d by the New Simple Vo lume Wizard. If you
acce pt the de fault options , the tool will cre ate a ne w partition that fills all
available s pace on the hard drive , as s igns it the ne xt available drive le tte r,
and formats it with the NTFS file s ys te m.
3. Re s tore the Windows bootloade r
a. Ins e rt the Windows ins tallation dis k and re s tart your compute r. As your
compute r s tarts , the following me s s age will appe ar on the s cre e n for a fe w
s e conds :
Press any key to boot from CD or DVD
Pre s s any ke y while the me s s age is s till s howing and the Windows
ins tallation s oftware will load.
b. In the Install Windows dialog, s e le ct a language , time and curre ncy format,
and ke yboard type . Click Next
c. Click Repair your computer.
547
d. The Windo ws Reco very Enviro nment (WRE) s hows you the Windows
ins tallations that it can de te ct on your s ys te m. Se le ct the ins tallation that you
want to re s tore , the n click Next.
e . Click Command prompt. A command window will ope n.
f. Type bootrec /fixmbr and pre s s Enter.
g. Whe n the prompt re appe ars , clos e the command window, the n click Restart.
h. Your compute r will re s tart and boot your Windows ope rating s ys te m.
39.2.2. Your comput er dual-boot s Red Hat Ent erprise Linux and a
dif f erent Linux dist ribut ion
Be caus e of the diffe re nce s be twe e n the many diffe re nt Linux dis tributions , the s e
ins tructions are a ge ne ral guide only. Spe cific de tails vary according to the configuration of
your particular s ys te m and the Linux dis tribution that dual-boots with Re d Hat Ente rpris e
Linux.
1. Remo ve Red Hat Ent erprise Linux part it io ns
a. Boot your Re d Hat Ente rpris e Linux ins tallation.
b. As root or with sudo , run mo unt . Note the partitions that are mounte d. In
particular, note the partition that is mounte d as the root of the file s ys te m.
The output of mount on a s ys te m whe re the root of the file s ys te m is on a
s tandard partition s uch as /dev/sda2 might re s e mble :
/dev/sda2 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs
(rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
The output of mount on a s ys te m whe re the root of the file s ys te m is on a
logical volume might re s e mble :
/dev/mapper/VolGroup00-LogVol00 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs
(rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
c. Ens ure that any data on this s ys te m that you s till re quire is backe d up to
anothe r s ys te m or s torage location.
548
d. Shut down the s ys te m and boot the Linux dis tribution that you want to ke e p
on the s ys te m.
e . As root or with sudo , run mo unt . If any of the partitions that you pre vious ly
note d as us e d for Re d Hat Ente rpris e Linux are mounte d, re vie w the
conte nts of the s e partitions . If you no longe r re quire the conte nts of the s e
partitions , unmount the m with the umount command.
f. Re move any unwante d and unne ce s s ary partitions , for e xample , with f disk
for s tandard partitions , or lvremo ve and vgremo ve to re move logical
volume s and volume groups .
2. Remo ve Red Hat Ent erprise Linux ent ries f ro m yo ur bo o t lo ader
Example o nly
The s e ins tructions as s ume that your s ys te m us e s the GRUB bootloade r. If
you us e a diffe re nt bootloade r (s uch as LILO) cons ult the docume ntation for
that s oftware to ide ntify and re move Re d Hat Ente rpris e Linux e ntrie s from
its lis t of boot targe ts and to e ns ure that your de fault ope rating s ys te m is
corre ctly s pe cifie d.
a. At the command line , type su - and pre s s Enter. Whe n the s ys te m prompts
you for the root pas s word, type the pas s word and pre s s Enter.
b. Type gedit /boot/grub/grub.conf and pre s s Enter. This ope ns the
grub.conf file in the gedit te xt e ditor.
c. A typical Re d Hat Ente rpris e Linux e ntry in the grub.conf file cons is ts of
four line s :
Example 39.1. Example Red Hat Ent erprise Linux ent ry in
grub.conf
title Re d Hat Ente rpris e Linux (2.6.32.130.e l6.i686)
root (hd0,1)
ke rne l /vmlinuz -2.6.32.130.e l6.i686 ro root=UUID=04a07c13-e 6bf-6d5ab207-002689545705 rhgb quie t
initrd /initrd-2.6.32.130.e l6.i686.img
De pe nding on the configuration of your s ys te m, the re may be multiple Re d
Hat Ente rpris e Linux e ntrie s in grub.conf, e ach corre s ponding to a diffe re nt
ve rs ion of the Linux ke rne l. De le te e ach of the Re d Hat Ente rpris e Linux
e ntrie s from the file .
d. Grub.conf contains a line that s pe cifie s the de fault ope rating s ys te m to
boot, in the format default=N whe re N is a numbe r e qual to or gre ate r than
0. If N is s e t to 0, GRUB will boot the firs t ope rating s ys te m in the lis t. If N is
s e t to 1, it will boot the s e cond ope rating s ys te m, and s o forth.
Ide ntify the e ntry for the ope rating s ys te m that you want GRUB to boot by
de fault and note its place in the orde r within the lis t.
549
Make s ure that the default= line contains the numbe r one below the
numbe r of your chos e n de fault ope rating s ys te m in the lis t.
Save the update d grub.conf file and clos e gedit
3. Make space available t o yo ur o perat ing syst em
No te
This s te p is not re quire d to re move Re d Hat Ente rpris e Linux from your
compute r. Howe ve r, if you s kip this s te p, you will le ave part of your hard
drive 's s torage capacity unus able by your othe r Linux ope rating s ys te m.
De pe nding on your configuration, this might be a s ignificant portion of the
s torage capacity of the drive .
No te
To carry out this s te p, you re quire live me dia for a Linux dis tribution, for
e xample , the Fe dora Live CD or the Knoppix DVD.
The me thod to make the s pace fre e d by re moving the Re d Hat Ente rpris e Linux
partitions available to your othe r Linux ope rating s ys te m diffe rs , de pe nding on
whe the r your chos e n ope rating s ys te m is ins talle d on dis k partitions configure d to
us e Logical Volume Manage me nt (LVM) or not.
If yo u do no t use LVM
Boot your compute r from Linux live me dia, and ins tall part ed if it is not
alre ady pre s e nt.
As root or with sudo , run part ed disk, whe re disk is the de vice name of
the dis k that contains a partition that you want to re s iz e , for e xample ,
/dev/sda.
At the (parted) prompt, e nte r print. The part ed tool dis plays
information about the partitions on your s ys te m, including the ir partition
numbe rs , the ir s iz e s , and the ir pos itions on the dis k.
At the (parted) prompt, e nte r resize number start end, whe re
number is the partition numbe r, start is the location on the dis k at which
the partition be gins , and end is the location on the dis k at which you want
the partition to e nd. Us e the s tart pos ition that you pre vious ly obtaine d
with the print command, and re fe r to the part ed docume ntation for
diffe re nt ways to s pe cify the e nd parame te r.
Whe n part ed finis he s re s iz ing the partition, e nte r quit at the (parted)
prompt.
Run e2fsck partition, whe re partition is the partition that you jus t
re s iz e d. For e xample , if you jus t re s iz e d /dev/sda3, e nte r
e2fsck /dev/sda3.
Linux now che cks the file s ys te m of the ne wly-re s iz e d partition.
550
551
552
Warning
Be care ful to re move only the ne ce s s ary Re d Hat Ente rpris e Linux partitions .
Re moving othe r partitions could re s ult in data los s or a corrupte d s ys te m
e nvironme nt.
To re move partitions , us e the partitioning utility parted. Start parted, whe re /dev/hda is
the de vice on which to re move the partition:
parted /dev/hda
Us ing the print command, vie w the curre nt partition table to de te rmine the minor numbe r
of the partition to re move :
print
The print command als o dis plays the partition's type (s uch as linux-s wap, e xt2, e xt3,
e xt4 and s o on). Knowing the type of the partition he lps you in de te rmining whe the r to
re move the partition.
Re move the partition with the command rm. For e xample , to re move the partition with
minor numbe r 3:
rm 3
Impo rtant
The change s s tart taking place as s oon as you pre s s [Ente r], s o re vie w the
command be fore committing to it.
Afte r re moving the partition, us e the print command to confirm that it is re move d from
the partition table .
Once you have re move d the Linux partitions and made all of the change s you ne e d to
make , type quit to quit parted.
Afte r quitting parted, type exit at the boot prompt to e xit re s cue mode and re boot your
s ys te m, ins te ad of continuing with the ins tallation. The s ys te m s hould re boot automatically.
If it doe s not, you can re boot your compute r us ing Control+Alt+Delete .
553
554
555
556
557
blocks are now holding data. Howe ve r, by jus t looking at this picture , we cannot de te rmine
e xactly how many file s re s ide on this drive . The re may only be one file or many, as all
file s us e at le as t one block and s ome file s us e multiple blocks . Anothe r important point to
note is that the us e d blocks do not have to form a contiguous re gion; us e d and unus e d
blocks may be inte rs pe rs e d. This is known as fragmentation. Fragme ntation can play a part
whe n atte mpting to re s iz e an e xis ting partition.
As with mos t compute r-re late d te chnologie s , dis k drive s change d ove r time afte r the ir
introduction. In particular, the y got bigge r. Not large r in phys ical s iz e , but bigge r in the ir
capacity to s tore information. And, this additional capacity drove a fundame ntal change in
the way dis k drive s we re us e d.
No te
While the diagrams in this chapte r s how the partition table as be ing s e parate from
the actual dis k drive , this is not e ntire ly accurate . In re ality, the partition table is
s tore d at the ve ry s tart of the dis k, be fore any file s ys te m or us e r data. But for
clarity, the y are s e parate in our diagrams .
558
Value
Part it io n T ype
Value
Empty
DOS 12-bit FAT
XENIX root
XENIX us r
DOS 16-bit <=32M
Exte nde d
DOS 16-bit >=32
00
01
02
03
04
05
06
65
75
80
81
82
83
85
559
Part it io n T ype
Value
Part it io n T ype
Value
OS/2 HPFS
AIX
AIX bootable
OS/2 Boot Manage r
Win95 FAT32
Win95 FAT32 (LBA)
Win95 FAT16 (LBA)
Win95 Exte nde d (LBA)
Ve nix 80286
Nove ll
PRe P Boot
GNU HURD
Nove ll Ne tware 286
07
08
09
0a
0b
0c
0e
0f
40
51
41
63
64
Amoe ba
Amoe ba BBT
BSD/386
Ope nBSD
NEXTSTEP
BSDI fs
BSDI s wap
Syrinx
CP/M
DOS acce s s
DOS R/O
DOS s e condary
BBT
93
94
a5
a6
a7
b7
b8
c7
db
e1
e3
f2
ff
A.1.3. Part it ions Wit hin Part it ions An Overview of Ext ended
Part it ions
Of cours e , ove r time it be came obvious that four partitions would not be e nough. As dis k
drive s continue d to grow, it be came more and more like ly that a pe rs on could configure
four re as onably-s iz e d partitions and s till have dis k s pace le ft ove r. The re ne e de d to be
s ome way of cre ating more partitions .
Ente r the e xte nde d partition. As you may have notice d in Table A.1, Partition Type s ,
the re is an "Exte nde d" partition type . It is this partition type that is at the he art of
e xte nde d partitions .
Whe n a partition is cre ate d and its type is s e t to "Exte nde d," an e xte nde d partition table is
cre ate d. In e s s e nce , the e xte nde d partition is like a dis k drive in its own right it has a
partition table that points to one or more partitions (now calle d logical partitions, as
oppos e d to the four primary partitions) containe d e ntire ly within the e xte nde d partition
its e lf. Figure A.7, Dis k Drive With Exte nde d Partition, s hows a dis k drive with one primary
partition and one e xte nde d partition containing two logical partitions (along with s ome
unpartitione d fre e s pace ).
560
Impo rtant
The re mus t be a BIOS boot partition for the boot loade r to be ins talle d s ucce s s fully
onto a dis k that contains a GPT (GUID Partition Table ). This include s dis ks initializ e d
by Anaco nda. If the dis k alre ady contains a BIOS boot partition, it can be re us e d.
561
No te
Ke e p in mind that the following illus trations are s implifie d in the inte re s t of clarity
and do not re fle ct the e xact partition layout that you e ncounte r whe n actually
ins talling Re d Hat Ente rpris e Linux.
562
In Figure A.9, Dis k Drive With an Unus e d Partition, 1 re pre s e nts an unus e d partition and
2 re pre s e nts re allocating an unus e d partition for Linux.
If you find yours e lf in this s ituation, you can us e the s pace allocate d to the unus e d
partition. You firs t mus t de le te the partition and the n cre ate the appropriate Linux
partition(s ) in its place . You can de le te the unus e d partition and manually cre ate ne w
partitions during the ins tallation proce s s .
Warning
If the re was an ope rating s ys te m of s ome type ins talle d on that partition, it
ne e ds to be re ins talle d as we ll. Be aware that s ome compute rs s old with
pre -ins talle d ope rating s ys te ms may not include the CD-ROM me dia to
re ins tall the original ope rating s ys te m. The be s t time to notice if this
applie s to your s ys te m is before you de s troy your original partition and its
ope rating s ys te m ins tallation.
Afte r cre ating a s malle r partition for your e xis ting ope rating s ys te m, you can
re ins tall any s oftware , re s tore your data, and s tart your Re d Hat Ente rpris e Linux
ins tallation. Figure A.10, Dis k Drive Be ing De s tructive ly Re partitione d s hows this
be ing done .
Figure A.10 . Disk Drive Being Dest ruct ively Repart it io ned
In Figure A.10, Dis k Drive Be ing De s tructive ly Re partitione d, 1 re pre s e nts
be fore and 2 re pre s e nts afte r.
563
Warning
As Figure A.10, Dis k Drive Be ing De s tructive ly Re partitione d, s hows , any
data pre s e nt in the original partition is los t without prope r backup!
Non-Destructive Repartitioning
He re , you run a program that doe s the s e e mingly impos s ible : it make s a big
partition s malle r without los ing any of the file s s tore d in that partition. Many
pe ople have found this me thod to be re liable and trouble -fre e . What s oftware
s hould you us e to pe rform this fe at? The re are s e ve ral dis k manage me nt
s oftware products on the marke t. Do s ome re s e arch to find the one that is be s t
for your s ituation.
While the proce s s of non-de s tructive re partitioning is rathe r s traightforward,
the re are a numbe r of s te ps involve d:
Compre s s and backup e xis ting data
Re s iz e the e xis ting partition
Cre ate ne w partition(s )
Ne xt we will look at e ach s te p in a bit more de tail.
A.1.5.3.1. Co mpress exist ing dat a
As Figure A.11, Dis k Drive Be ing Compre s s e d, s hows , the firs t s te p is to compre s s the
data in your e xis ting partition. The re as on for doing this is to re arrange the data s uch that
it maximiz e s the available fre e s pace at the "e nd" of the partition.
564
No te
The following information is s pe cific to x86-bas e d compute rs only.
As a conve nie nce to our cus tome rs , we provide the parted utility. This is a fre e ly
available program that can re s iz e partitions .
If you de cide to re partition your hard drive with parted, it is important that you be familiar
with dis k s torage and that you pe rform a backup of your compute r data. You s hould make
two copie s of all the important data on your compute r. The s e copie s s hould be to
re movable me dia (s uch as tape , CD-ROM, or dis ke tte s ), and you s hould make s ure the y
are re adable be fore proce e ding.
Should you de cide to us e parted, be aware that afte r parted runs you are le ft with two
565
partitions : the one you re s iz e d, and the one parted cre ate d out of the ne wly fre e d s pace .
If your goal is to us e that s pace to ins tall Re d Hat Ente rpris e Linux, you s hould de le te the
ne wly cre ate d partition, e ithe r by us ing the partitioning utility unde r your curre nt ope rating
s ys te m or while s e tting up partitions during ins tallation.
566
No te
The re is no part of this naming conve ntion that is bas e d on partition type ; unlike
DOS/Windows , all partitions can be ide ntifie d unde r Re d Hat Ente rpris e Linux. Of
cours e , this doe s not me an that Re d Hat Ente rpris e Linux can acce s s data on e ve ry
type of partition, but in many cas e s it is pos s ible to acce s s data on a partition
de dicate d to anothe r ope rating s ys te m.
Ke e p this information in mind; it make s things e as ie r to unde rs tand whe n you are s e tting
up the partitions Re d Hat Ente rpris e Linux re quire s .
A.1.7. Disk Part it ions and Ot her Operat ing Syst ems
If your Re d Hat Ente rpris e Linux partitions are s haring a hard dis k with partitions us e d by
othe r ope rating s ys te ms , mos t of the time you will have no proble ms . Howe ve r, the re are
ce rtain combinations of Linux and othe r ope rating s ys te ms that re quire e xtra care .
567
[15] Blocks really are consistently sized, unlike our illustrations. Keep in m ind, also, that an
average disk drive contains thousands of blocks. But for the purposes of this discussion, please
ignore these m inor discrepancies.
568
Impo rtant
Be caus e Net wo rkManager is ins talle d in /usr, you cannot us e it to
configure ne twork acce s s if /usr is on ne twork-attache d s torage s uch as an
iSCSI targe t.
If iscsid is not ne e de d as the s ys te m s tarts , it will not s tart automatically. If you s tart
iscsiadm, iscsiadm will s tart iscsid in turn.
570
571
More de taile d information about LUKS is available from the proje ct we bs ite at
http://code .google .com/p/crypts e tup/.
No te
Cons ide r us ing the s ame pas s phras e for all e ncrypte d block de vice s in a give n
s ys te m. This will s implify s ys te m s tartup and you will have fe we r pas s phras e s to
re me mbe r. Jus t make s ure you choos e a good pas s phras e !
No te
Che cking the "Encrypt Sys te m" che ckbox on the "Automatic Partitioning" s cre e n and
the n choos ing "Cre ate cus tom layout" doe s not caus e any block de vice s to be
e ncrypte d automatically.
572
No te
You can us e kickstart to s e t a s e parate pas s phras e for e ach ne w e ncrypte d block
de vice .
573
Filling <de vice > (e g: /dev/sda3) with random data be fore e ncrypting it gre atly incre as e s
the s tre ngth of the e ncryption. The downs ide is that it can take a ve ry long time .
Warning
The commands be low will de s troy any e xis ting data on the de vice .
The be s t way, which provide s high quality random data but take s a long time (s e ve ral
minute s pe r gigabyte on mos t s ys te ms ):
dd if=/dev/urandom of=<device>
Fas te s t way, which provide s lowe r quality random data:
badblocks -c 10240 -s -w -t random -v <device>
Warning
The command be low will de s troy any e xis ting data on the de vice .
No te
For more information, re ad the cryptsetup(8) man page .
Afte r s upplying the pas s phras e twice the de vice will be formatte d for us e . To ve rify, us e
the following command:
cryptsetup isLuks <device> && echo Success
To s e e a s ummary of the e ncryption information for the de vice , us e the following
command:
cryptsetup luksDump <device>
574
It is us e ful to choos e a me aningful name for this mapping. LUKS provide s a UUID
(Unive rs ally Unique Ide ntifie r) for e ach de vice . This , unlike the de vice name (e g:
/dev/sda3), is guarante e d to re main cons tant as long as the LUKS he ade r re mains intact.
To find a LUKS de vice 's UUID, run the following command:
cryptsetup luksUUID <device>
An e xample of a re liable , informative and unique mapping name would be luks-<uuid>,
whe re <uuid> is re place d with the de vice 's LUKS UUID (e g: luks-50ec957a-5b5a-47ee85e6-f8085bbc97a8). This naming conve ntion might s e e m unwie ldy but is it not ne ce s s ary
to type it ofte n.
cryptsetup luksOpen <device> <name>
The re s hould now be a de vice node , /dev/mapper/<name>, which re pre s e nts the
de crypte d de vice . This block de vice can be re ad from and writte n to like any othe r
une ncrypte d block de vice .
To s e e s ome information about the mappe d de vice , us e the following command:
dmsetup info <name>
No te
For more information, re ad the dmsetup(8) man page .
C.4.5. Creat e File Syst ems on t he Mapped Device or Cont inue t o Build
Complex St orage St ruct ures Using t he Mapped Device
Us e the mappe d de vice node (/dev/mapper/<name>) as any othe r block de vice . To cre ate
an ext2 file s ys te m on the mappe d de vice , us e the following command:
mke2fs /dev/mapper/<name>
To mount this file s ys te m on /mnt/test, us e the following command:
Impo rtant
The dire ctory /mnt/test mus t e xis t be fore e xe cuting this command.
575
<name>
<device>
none
The <de vice > fie ld s hould be give n in the form "UUID=<luks _uuid>", whe re <luks _uuid>
is the LUKS uuid as give n by the command cryptsetup luksUUID <device>. This
e ns ure s the corre ct de vice will be ide ntifie d and us e d e ve n if the de vice node (e g:
/dev/sda5) change s .
No te
For de tails on the format of the /etc/crypttab file , re ad the crypttab(5) man
page .
No te
For de tails on the format of the /etc/fstab file , re ad the fstab(5) man page .
576
577
T he
/boot
On mos t archite cture s , the boot loade r cannot re ad LVM volume s . You mus t make a
s tandard, non-LVM dis k partition for your /boot partition.
Howe ve r, on Sys te m z , the zipl boot loade r s upports /boot on LVM logical volume s
with line ar mapping.
To unde rs tand LVM be tte r, imagine the phys ical volume as a pile of blocks. A block is
s imply a s torage unit us e d to s tore data. Se ve ral pile s of blocks can be combine d to make
a much large r pile , jus t as phys ical volume s are combine d to make a volume group. The
re s ulting pile can be s ubdivide d into s e ve ral s malle r pile s of arbitrary s iz e , jus t as a
volume group is allocate d to s e ve ral logical volume s .
An adminis trator may grow or s hrink logical volume s without de s troying data, unlike
s tandard dis k partitions . If the phys ical volume s in a volume group are on s e parate drive s
or RAID arrays the n adminis trators may als o s pre ad a logical volume acros s the s torage
de vice s .
You may los e data if you s hrink a logical volume to a s malle r capacity than the data on the
volume re quire s . To e ns ure maximum fle xibility, cre ate logical volume s to me e t your
curre nt ne e ds , and le ave e xce s s s torage capacity unallocate d. You may s afe ly grow
logical volume s to us e unallocate d s pace , as your ne e ds dictate .
578
Bo o t Lo aders
AMD AMD64
IBM Powe r Sys te ms
IBM Sys te m z
x86
GRUB
yaboot
z /IPL
GRUB
This appe ndix dis cus s e s commands and configuration options for the GRUB boot loade r
include d with Re d Hat Ente rpris e Linux for the x86 archite cture .
E.2. GRUB
The GNU GRand Unified Boot loader (GRUB) is a program which e nable s the s e le ction of
the ins talle d ope rating s ys te m or ke rne l to be loade d at s ys te m boot time . It als o allows
the us e r to pas s argume nts to the ke rne l.
579
Warning
During ins tallation, Micros oft's DOS and Windows ins tallation programs comple te ly
ove rwrite the MBR, de s troying any e xis ting boot loade rs . If cre ating a dual-boot
s ys te m, it is be s t to ins tall the Micros oft ope rating s ys te m firs t.
580
581
Re place disk with the name of the de vice containing the EFI Sys te m Partition (s uch as
/dev/sda) and partition_number with the partition numbe r of your EFI Sys te m Partition.
For additional information about ins talling GRUB, s e e the GNU GRUB Manual and the grubinstall(8) man page . For information about the EFI Sys te m Partition, s e e Se ction 9.18.1,
Advance d Boot Loade r Configuration. For information about the efibootmgr tool, s e e the
efibootmgr(8) man page .
Impo rtant
GRUB cannot cons truct a s oftware RAID. The re fore , the /boot dire ctory mus t re s ide
on a s ingle , s pe cific dis k partition. The /boot dire ctory cannot be s tripe d acros s
multiple dis ks , as in a le ve l 0 RAID. To us e a le ve l 0 RAID on your s ys te m, place
/boot on a s e parate partition outs ide the RAID.
Similarly, be caus e the /boot dire ctory mus t re s ide on a s ingle , s pe cific dis k
partition, GRUB cannot boot the s ys te m if the dis k holding that partition fails or is
re move d from the s ys te m. This is true e ve n if the dis k is mirrore d in a le ve l 1 RAID.
The following Re d Hat Knowle dge bas e article de s cribe s how to make the s ys te m
bootable from anothe r dis k in the mirrore d s e t:
https ://acce s s .re dhat.com/s ite /article s /7094
Note that the s e is s ue s apply only to RAID that is imple me nte d in s oftware , whe re
the individual dis ks that make up the array are s till vis ible as individual dis ks on the
s ys te m. The s e is s ue s do not apply to hardware RAID whe re multiple dis ks are
re pre s e nte d as a s ingle de vice .
The e xact s te ps to fix a broke n GRUB configuration will vary de pe nding on what kind of
proble m the re is . The GNU GRUB Manual offe rs a lis t of all pos s ible e rror me s s age s
dis playe d by GRUB in diffe re nt s tage s and the ir unde rlying caus e s . Us e the manual for
re fe re nce .
Once you have de te rmine d the caus e of the e rror, you can s tart fixing it. If you are
e ncounte ring an e rror which only appe ars afte r you s e le ct an e ntry from the GRUB me nu,
the n you can us e the me nu to fix the e rror te mporarily, boot the s ys te m, and the n fix the
e rror pe rmane ntly by running the grub-install command to re ins tall the boot loade r, or
by e diting the /boot/grub/grub.conf or /boot/efi/EFI/redhat/grub.conf with a plain
te xt e ditor. For information about the configuration file s tructure , s e e Se ction E.8, GRUB
Me nu Configuration File .
582
No te
The re are two ide ntical file s in the GRUB configuration dire ctory: grub.conf and
menu.lst. The grub.conf configuration file is loade d firs t; the re fore you s hould
make your change s the re . The s e cond file , menu.lst, will only be loade d if
grub.conf is not found.
No te
The numbe ring s ys te m for de vice s unde r GRUB always be gins with 0, not 1. Failing
to make this dis tinction is one of the mos t common mis take s made by ne w us e rs .
To give an e xample , if a s ys te m has more than one hard drive , GRUB re fe rs to the firs t
hard drive as (hd0) and the s e cond as (hd1). Like wis e , GRUB re fe rs to the firs t partition
on the firs t drive as (hd0,0) and the third partition on the s e cond hard drive as (hd1,2).
In ge ne ral the following rule s apply whe n naming de vice s and partitions unde r GRUB:
It doe s not matte r if s ys te m hard drive s are IDE or SCSI, all hard drive s be gin with the
le tte rs hd. The le tte rs fd are us e d to s pe cify 3.5 dis ke tte s .
583
To s pe cify an e ntire de vice without re s pe ct to partitions , le ave off the comma and the
partition numbe r. This is important whe n te lling GRUB to configure the MBR for a
particular dis k. For e xample , (hd0) s pe cifie s the MBR on the firs t de vice and (hd3)
s pe cifie s the MBR on the fourth de vice .
If a s ys te m has multiple drive de vice s , it is ve ry important to know how the drive boot
orde r is s e t in the BIOS. This is a s imple tas k if a s ys te m has only IDE or SCSI drive s ,
but if the re is a mix of de vice s , it be come s critical that the type of drive with the boot
partition be acce s s e d firs t.
584
The GRUB root file s ys te m is the top le ve l of the s pe cifie d de vice . For e xample , the image
file (hd0,0)/grub/splash.xpm.gz is locate d within the /grub/ dire ctory at the top-le ve l
(or root) of the (hd0,0) partition (which is actually the /boot/ partition for the s ys te m).
Ne xt, the kernel command is e xe cute d with the location of the ke rne l file as an option.
Once the Linux ke rne l boots , it s e ts up the root file s ys te m that Linux us e rs are familiar
with. The original GRUB root file s ys te m and its mounts are forgotte n; the y only e xis te d to
boot the ke rne l file .
Re fe r to the root and kernel commands in Se ction E.7, GRUB Commands for more
information.
No te
The following GRUB inte rface s can only be acce s s e d by pre s s ing any ke y within the
thre e s e conds of the GRUB me nu bypas s s cre e n.
Menu Interface
This is the de fault inte rface s hown whe n GRUB is configure d by the ins tallation
program. A me nu of ope rating s ys te ms or pre configure d ke rne ls are dis playe d as
a lis t, orde re d by name . Us e the arrow ke ys to s e le ct an ope rating s ys te m or
ke rne l ve rs ion and pre s s the Enter ke y to boot it. If you do nothing on this
s cre e n, the n afte r the time out pe riod e xpire s GRUB will load the de fault option.
Pre s s the e ke y to e nte r the e ntry e ditor inte rface or the c ke y to load a
command line inte rface .
Re fe r to Se ction E.8, GRUB Me nu Configuration File for more information on
configuring this inte rface .
Menu Entry Editor Interface
To acce s s the me nu e ntry e ditor, pre s s the e ke y from the boot loade r
The GRUB commands for that e ntry are dis playe d he re , and us e rs may
the s e command line s be fore booting the ope rating s ys te m by adding a
line (o ins e rts a ne w line afte r the curre nt line and O ins e rts a ne w line
e diting one (e), or de le ting one (d).
me nu.
alte r
command
be fore it),
Afte r all change s are made , the b ke y e xe cute s the commands and boots the
ope rating s ys te m. The Esc ke y dis cards any change s and re loads the s tandard
me nu inte rface . The c ke y loads the command line inte rface .
585
No te
For information about changing runle ve ls us ing the GRUB me nu e ntry e ditor,
re fe r to Se ction E.9, Changing Runle ve ls at Boot Time .
Command Line Interface
The command line inte rface is the mos t bas ic GRUB inte rface , but it is als o the
one that grants the mos t control. The command line make s it pos s ible to type any
re le vant GRUB commands followe d by the Enter ke y to e xe cute the m. This
inte rface fe ature s s ome advance d s he ll-like fe ature s , including Tab ke y
comple tion bas e d on conte xt, and Ctrl ke y combinations whe n typing commands ,
s uch as Ctrl+a to move to the be ginning of a line and Ctrl+e to move to the
e nd of a line . In addition, the arrow, Home, End, and Delete ke ys work as the y do
in the bash s he ll.
Re fe r to Se ction E.7, GRUB Commands for a lis t of common commands .
586
displaymem Dis plays the curre nt us e of me mory, bas e d on information from the
BIOS. This is us e ful to de te rmine how much RAM a s ys te m has prior to booting it.
initrd </path/to/initrd> Enable s us e rs to s pe cify an initial RAM dis k to us e
whe n booting. An initrd is ne ce s s ary whe n the ke rne l ne e ds ce rtain module s in orde r
to boot prope rly, s uch as whe n the root partition is formatte d with the e xt3 or e xt4 file
s ys te m.
The following is an e xample initrd command:
initrd /initrd-2.6.8-1.523.img
install <stage-1> <install-disk> <stage-2> p config-file Ins talls GRUB to
the s ys te m MBR.
<stage-1> Signifie s a de vice , partition, and file whe re the firs t boot loade r image
can be found, s uch as (hd0,0)/grub/stage1.
<install-disk> Spe cifie s the dis k whe re the s tage 1 boot loade r s hould be
ins talle d, s uch as (hd0).
<stage-2> Pas s e s the s tage 2 boot loade r location to the s tage 1 boot loade r,
s uch as (hd0,0)/grub/stage2.
p <config-file> This option te lls the install command to look for the me nu
configuration file s pe cifie d by <config-file>, s uch as (hd0,0)/grub/grub.conf.
Warning
The install command ove rwrite s any information alre ady locate d on the MBR.
kernel </path/to/kernel> <option-1> <option-N> ... Spe cifie s the ke rne l file to
load whe n booting the ope rating s ys te m. Re place </path/to/kernel> with an abs olute
path from the partition s pe cifie d by the root command. Re place <option-1> with options
for the Linux ke rne l, s uch as root=/dev/VolGroup00/LogVol00 to s pe cify the de vice
on which the root partition for the s ys te m is locate d. Multiple options can be pas s e d to
the ke rne l in a s pace s e parate d lis t.
The following is an e xample kernel command:
kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00
The option in the pre vious e xample s pe cifie s that the root file s ys te m for Linux is
locate d on the hda5 partition.
root (<device-type><device-number>,<partition>) Configure s the root partition
for GRUB, s uch as (hd0,0), and mounts the partition.
The following is an e xample root command:
root (hd0,0)
rootnoverify (<device-type><device-number>,<partition>) Configure s the
root partition for GRUB, jus t like the root command, but doe s not mount the partition.
587
Othe r commands are als o available ; type help --all for a full lis t of commands . For a
de s cription of all GRUB commands , re fe r to the docume ntation available online at
http://www.gnu.org/s oftware /grub/manual/.
No te
Note that the de fault is s pe cifie d as an inte ge r. This re fe rs to the firs t title line in
the GRUB configuration file . For the Windows s e ction to be s e t as the de fault in the
pre vious e xample , change the default=0 to default=1.
Configuring a GRUB me nu configuration file to boot multiple ope rating s ys te ms is be yond
the s cope of this chapte r. Cons ult Se ction E.10, Additional Re s ource s for a lis t of
additional re s ource s .
588
The following are dire ctive s commonly us e d in the GRUB me nu configuration file :
chainloader </path/to/file> Loads the s pe cifie d file as a chain loade r. Re place
</path/to/file> with the abs olute path to the chain loade r. If the file is locate d on the
firs t s e ctor of the s pe cifie d partition, us e the blocklis t notation, +1.
color <normal-color> <selected-color> Allows s pe cific colors to be us e d in the
me nu, whe re two colors are configure d as the fore ground and background. Us e s imple
color name s s uch as red/black. For e xample :
color red/black green/blue
default=<integer> Re place <integer> with the de fault e ntry title numbe r to be
loade d if the me nu inte rface time s out.
fallback=<integer> Re place <integer> with the e ntry title numbe r to try if the firs t
atte mpt fails .
hiddenmenu Pre ve nts the GRUB me nu inte rface from be ing dis playe d, loading the
default e ntry whe n the timeout pe riod e xpire s . The us e r can s e e the s tandard GRUB
me nu by pre s s ing the Esc ke y.
initrd </path/to/initrd> Enable s us e rs to s pe cify an initial RAM dis k to us e
whe n booting. Re place </path/to/initrd> with the abs olute path to the initial RAM dis k.
kernel </path/to/kernel> <option-1> <option-N> Spe cifie s the ke rne l file to
load whe n booting the ope rating s ys te m. Re place </path/to/kernel> with an abs olute
path from the partition s pe cifie d by the root dire ctive . Multiple options can be pas s e d to
the ke rne l whe n it is loade d.
The s e options include :
rhgb (Red Hat graphical boot) dis plays an animation during the boot proce s s ,
rathe r than line s of te xt.
quiet s uppre s s e s all but the mos t important me s s age s in the part of the boot
s e que nce be fore the Re d Hat graphical boot animation be gins .
password=<password> Pre ve nts a us e r who doe s not know the pas s word from
e diting the e ntrie s for this me nu option.
Optionally, it is pos s ible to s pe cify an alte rnate me nu configuration file afte r the
password=<password> dire ctive . In this cas e , GRUB re s tarts the s e cond s tage boot
loade r and us e s the s pe cifie d alte rnate configuration file to build the me nu. If an
alte rnate me nu configuration file is le ft out of the command, a us e r who knows the
pas s word is allowe d to e dit the curre nt configuration file .
Impo rtant
It is highly re comme nde d to s e t up a boot loade r pas s word on e ve ry machine . An
unprote cte d boot loade r can allow a pote ntial attacke r to modify the s ys te m's
boot options and gain acce s s to the s ys te m. Se e the chapte r title d Workstation
Security in the Red Hat Enterprise Linux Security Guide for more information on
boot loade r pas s words and pas s word s e curity in ge ne ral.
map Swaps the numbe rs as s igne d to two hard drive s . For e xample :
589
590
This chapte r is only inte nde d as an introduction to GRUB. Cons ult the following re s ource s
to dis cove r more about how GRUB works .
[16] For m ore on the system BIO S and the MBR, refer to Section F.2.1.1, BIO S-based x86
System s.
591
592
593
Impo rtant
The GRUB bootloade r in Re d Hat Ente rpris e Linux 6.6 s upports e xt2, e xt3, and e xt4
file s ys te ms . It doe s not s upport othe r file s ys te ms s uch as VFAT, Btrfs or XFS.
Furthe rmore , GRUB doe s not s upport LVM.
Once the s e cond s tage boot loade r is in me mory, it pre s e nts the us e r with a graphical
s cre e n s howing the diffe re nt ope rating s ys te ms or ke rne ls it has be e n configure d to boot
(whe n you update the ke rne l, the boot loade r configuration file is update d automatically).
On this s cre e n a us e r can us e the arrow ke ys to choos e which ope rating s ys te m or ke rne l
the y wis h to boot and pre s s Enter. If no ke y is pre s s e d, the boot loade r loads the de fault
s e le ction afte r a configurable pe riod of time has pas s e d.
Once the s e cond s tage boot loade r has de te rmine d which ke rne l to boot, it locate s the
corre s ponding ke rne l binary in the /boot/ dire ctory. The ke rne l binary is name d us ing the
following format /boot/vmlinuz-<kernel-version> file (whe re <kernel-version>
corre s ponds to the ke rne l ve rs ion s pe cifie d in the boot loade r's s e ttings ).
For ins tructions on us ing the boot loade r to s upply command line argume nts to the ke rne l,
re fe r to Appe ndix E, The GRUB Boot Loader. For information on changing the runle ve l at
the boot loade r prompt, re fe r Se ction E.9, Changing Runle ve ls at Boot Time .
The boot loade r the n place s one or more appropriate initramfs image s into me mory. The
initramfs is us e d by the ke rne l to load drive rs and module s ne ce s s ary to boot the
s ys te m. This is particularly important if SCSI hard drive s are pre s e nt or if the s ys te ms
us e the e xt3 or e xt4 file s ys te m.
Once the ke rne l and the initramfs image (s ) are loade d into me mory, the boot loade r
hands control of the boot proce s s to the ke rne l.
For a more de taile d ove rvie w of the GRUB boot loade r, re fe r to Appe ndix E, The GRUB
Boot Loader.
F.2.3. T he Kernel
Whe n the ke rne l is loade d, it imme diate ly initializ e s and configure s the compute r's
me mory and configure s the various hardware attache d to the s ys te m, including all
proce s s ors , I/O s ubs ys te ms , and s torage de vice s . It the n looks for the compre s s e d
initramfs image (s ) in a pre de te rmine d location in me mory, de compre s s e s it dire ctly to
/sysroot/, and loads all ne ce s s ary drive rs . Ne xt, it initializ e s virtual de vice s re late d to
the file s ys te m, s uch as LVM or s oftware RAID, be fore comple ting the initramfs
proce s s e s and fre e ing up all the me mory the dis k image once occupie d.
594
The ke rne l the n cre ate s a root de vice , mounts the root partition re ad-only, and fre e s any
unus e d me mory.
At this point, the ke rne l is loade d into me mory and ope rational. Howe ve r, s ince the re are
no us e r applications that allow me aningful input to the s ys te m, not much can be done with
the s ys te m.
To s e t up the us e r e nvironme nt, the ke rne l e xe cute s the /sbin/init program.
595
596
No te
Afte r the s ys te m is finis he d booting, it is pos s ible to log in as root and e xe cute
the s e s ame s cripts to s tart and s top s e rvice s . For ins tance , the command
/etc/rc.d/init.d/httpd stop s tops the Apache HTTP Se rve r.
Each of the s ymbolic links are numbe re d to dictate s tart orde r. The orde r in which the
s e rvice s are s tarte d or s toppe d can be alte re d by changing this numbe r. The lowe r the
numbe r, the e arlie r it is s tarte d. Symbolic links with the s ame numbe r are s tarte d
alphabe tically.
No te
One of the las t things the init program e xe cute s is the /etc/rc.d/rc.local file .
This file is us e ful for s ys te m cus tomiz ation. Re fe r to Se ction F.3, Running Additional
Programs at Boot Time for more information about us ing the rc.local file .
Afte r the init command has progre s s e d through the appropriate rc dire ctory for the
runle ve l, Upst art forks an /sbin/mingetty proce s s for e ach virtual cons ole (login
prompt) allocate d to the runle ve l by the job de finition in the /etc/event.d dire ctory.
597
Runle ve ls 2 through 5 have all s ix virtual cons ole s , while runle ve l 1 (s ingle us e r mode )
has one , and runle ve ls 0 and 6 have none . The /sbin/mingetty proce s s ope ns
communication pathways to tty de vice s [18] , s e ts the ir mode s , prints the login prompt,
acce pts the us e r's us e rname and pas s word, and initiate s the login proce s s .
In runle ve l 5, Upst art runs a s cript calle d /etc/X11/prefdm. The prefdm s cript e xe cute s
the pre fe rre d X dis play manage r [19] gdm, kdm, or xdm, de pe nding on the conte nts of
the /etc/sysconfig/desktop file .
Once finis he d, the s ys te m ope rate s on runle ve l 5 and dis plays a login s cre e n.
on
on
on
on
stopped
stopped
stopped
started
rc2
rc3
rc4
prefdm
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
exec /sbin/mingetty tty2
598
The /etc/rc.serial s cript is us e d if s e rial ports mus t be s e tup at boot time . This s cript
runs setserial commands to configure the s ys te m's s e rial ports . Re fe r to the setserial
man page for more information.
F.4.1. Runlevels
The ide a be hind Sys V init runle ve ls re volve s around the ide a that diffe re nt s ys te ms can
be us e d in diffe re nt ways . For e xample , a s e rve r runs more e fficie ntly without the drag on
s ys te m re s ource s cre ate d by the X Window Sys te m. Or the re may be time s whe n a
s ys te m adminis trator may ne e d to ope rate the s ys te m at a lowe r runle ve l to pe rform
diagnos tic tas ks , like fixing dis k corruption in runle ve l 1.
The characte ris tics of a give n runle ve l de te rmine which s e rvice s are halte d and s tarte d
by init. For ins tance , runle ve l 1 (s ingle us e r mode ) halts any ne twork s e rvice s , while
runle ve l 3 s tarts the s e s e rvice s . By as s igning s pe cific s e rvice s to be halte d or s tarte d on
a give n runle ve l, init can quickly change the mode of the machine without the us e r
manually s topping and s tarting s e rvice s .
The following runle ve ls are de fine d by de fault unde r Re d Hat Ente rpris e Linux:
0 Halt
1 Single -us e r te xt mode
2 Not us e d (us e r-de finable )
3 Full multi-us e r te xt mode
4 Not us e d (us e r-de finable )
5 Full multi-us e r graphical mode (with an X-bas e d login s cre e n)
6 Re boot
In ge ne ral, us e rs ope rate Re d Hat Ente rpris e Linux at runle ve l 3 or runle ve l 5 both full
multi-us e r mode s . Us e rs s ome time s cus tomiz e runle ve ls 2 and 4 to me e t s pe cific ne e ds ,
s ince the y are not us e d.
The de fault runle ve l for the s ys te m is lis te d in /etc/inittab. To find out the de fault
runle ve l for a s ys te m, look for the line s imilar to the following ne ar the bottom of
/etc/inittab:
599
id:5:initdefault:
The de fault runle ve l lis te d in this e xample is five , as the numbe r afte r the firs t colon
indicate s . To change it, e dit /etc/inittab as root.
Warning
Be ve ry care ful whe n e diting /etc/inittab. Simple typos can caus e the s ys te m to
be come unbootable . If this happe ns , e ithe r us e a boot CD or DVD, e nte r s ingle -us e r
mode , or e nte r re s cue mode to boot the compute r and re pair the file .
For more information on s ingle -us e r and re s cue mode , re fe r to Chapte r 36, Basic
System Recovery.
It is pos s ible to change the de fault runle ve l at boot time by modifying the argume nts
pas s e d by the boot loade r to the ke rne l. For information on changing the runle ve l at boot
time , re fe r to Se ction E.9, Changing Runle ve ls at Boot Time .
600
PAM cons ole us e rs can us e the reboot and halt commands to s hut down the s ys te m
while in runle ve ls 1 through 5. For more information about PAM cons ole us e rs , re fe r to the
Re d Hat Ente rpris e Linux De ployme nt Guide .
If the compute r doe s not powe r its e lf down, be care ful not to turn off the compute r until a
me s s age appe ars indicating that the s ys te m is halte d.
Failure to wait for this me s s age can me an that not all the hard drive partitions are
unmounte d, which can le ad to file s ys te m corruption.
[17] GRUB reads ext3 and ext4 file system s as ext2, disregarding the journal file.
[18] Refer to the Red Hat Enterprise Linux Deploym ent Guide for m ore inform ation about tty
devices.
[19] Refer to the Red Hat Enterprise Linux Deploym ent Guide for m ore inform ation about
display m anagers.
601
%pre
%post
New co mmand o r
alt ernat ive
addgroup
no
ye s
adduser
adjtimex
ar
arping
no
no
no
ye s
ye s
no
ye s
ye s
ash
awk
ye s
ye s
ye s
ye s
/usr/sbin/groupad
d
/usr/sbin/useradd
none
/usr/bin/ar
/sbin/arping or
/usr/sbin/arping
/bin/bash
/sbin/awk,
/sbin/gawk, or
/usr/bin/gawk [a]
basename
ye s
ye s
bbconfig
no
no
bunzip2
ye s
ye s
busybox
bzcat
no
ye s
no
ye s
cal
cat
catv
chattr
no
ye s
no
ye s
ye s
ye s
no
ye s
602
/bin/bash [b] ,
/usr/bin/basename
none this
command is a
s pe cific to Busybo x
/usr/bin/bunzip2,
/usr/bin/bzip2 -d
none
/usr/bin/bzcat,
/usr/bin/bzip2 dc
/usr/bin/cal
/usr/bin/cat
cat -vET or cat -A
/usr/bin/chattr
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
chgrp
chmod
chown
chroot
chvt
cksum
clear
cmp
comm
cp
cpio
crond
ye s
ye s
ye s
ye s
ye s
no
ye s
no
no
ye s
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
no
crontab
cut
date
dc
dd
deallocvt
no
ye s
ye s
no
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
delgroup
no
ye s
deluser
devfsd
no
no
ye s
no
df
diff
dirname
ye s
no
ye s
ye s
ye s
ye s
/usr/bin/chgrp
/usr/bin/chmod
/usr/bin/chown
/usr/sbin/chroot
/usr/bin/chvt
/usr/bin/cksum
/usr/bin/clear
/usr/bin/cmp
/usr/bin/comm
/usr/bin/cp
/usr/bin/cpio
none no dae mons
available to
s criptle ts
/usr/bin/crontab
/usr/bin/cut
/usr/bin/date
/usr/bin/dc
/usr/bin/dd
/usr/bin/deallocv
t
/usr/sbin/groupde
l
/usr/sbin/userdel
none Re d Hat
Ente rpris e Linux
doe s not us e devf s
/usr/bin/df
/usr/bin/diff
dmesg
dnsd
ye s
no
ye s
no
dos2unix
dpkg
no
no
no
no
dpkg-deb
no
no
du
dumpkmap
dumpleases
e2fsck
e2label
echo
ed
ye s
no
no
ye s
ye s
ye s
no
ye s
no
no
ye s
ye s
ye s
no
/bin/bash [c] ,
/usr/bin/dirname
/usr/bin/dmesg
none no dae mons
available to
s criptle ts
sed 's/.$//'
none no s upport
for De bian package s
none no s upport
for De bian package s
/usr/bin/du
none
none
/usr/sbin/e2fsck
/usr/sbin/e2label
/usr/bin/echo
/sbin/sed,
/usr/bin/sed
603
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
egrep
ye s
ye s
eject
env
ether-wake
expr
fakeidentd
ye s
ye s
no
ye s
no
ye s
ye s
no
ye s
no
false
fbset
fdflush
fdformat
fdisk
fgrep
ye s
no
no
no
ye s
ye s
ye s
ye s
no
ye s
ye s
ye s
find
findfs
fold
free
freeramdisk
fsck
fsck.ext2
ye s
no
no
no
no
ye s
ye s
ye s
no
ye s
ye s
no
ye s
ye s
fsck.ext3
ye s
ye s
fsck.minix
no
no
ftpget
ye s
ye s
ftpput
ye s
ye s
fuser
getopt
getty
grep
no
no
no
ye s
ye s
ye s
no
ye s
gunzip
ye s
ye s
gzip
hdparm
head
hexdump
ye s
ye s
ye s
no
ye s
ye s
ye s
ye s
/sbin/egrep,
/usr/bin/egrep
/usr/bin/eject
/usr/bin/env
none
/usr/bin/expr
none no dae mons
available to
s criptle ts
/usr/bin/false
/usr/sbin/fbset
none
/usr/bin/fdformat
/usr/sbin/fdisk
/sbin/fgrep,
/usr/bin/fgrep
/usr/bin/find
none
/usr/bin/fold
/usr/bin/free
none
/usr/sbin/fsck
/usr/sbin/fsck.ex
t2,
/usr/sbin/e2fsck
/usr/sbin/fsck.ex
t3,
/usr/sbin/e2fsck
none no s upport
for the Minix file
s ys te m
/usr/bin/ftp or
Python f t plib
module
/usr/bin/ftp or
Python f t plib
module
/sbin/fuser
/usr/bin/getopt
none
/sbin/grep,
/usr/bin/grep
/usr/bin/gunzip,
/usr/bin/gzip -d
/usr/bin/gzip
/usr/sbin/hdparm
/usr/bin/head
/usr/bin/hexdump
604
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
hostid
no
ye s
hostname
ye s
ye s
httpd
no
no
hush
hwclock
id
no
ye s
no
no
ye s
ye s
ifconfig
ye s
ye s
ifdown
no
no
ifup
no
no
inetd
no
no
insmod
ye s
ye s
install
no
ye s
ip
ye s
ye s
ipaddr
ipcalc
no
ye s
no
ye s
ipcrm
ipcs
iplink
iproute
iptunnel
kill
no
no
no
no
no
ye s
ye s
ye s
no
no
ye s
ye s
killall
lash
last
length
less
linux32
linux64
ln
ye s
no
no
no
ye s
no
no
ye s
ye s
no
ye s
no
ye s
no
no
ye s
/usr/bin/hostid
or Python
/sbin/hostname,
/usr/bin/hostname
none no dae mons
available to
s criptle ts
none
/usr/sbin/hwclock
/usr/bin/id or
Python
/sbin/ifconfig,
/usr/sbin/ifconfi
g
ifconfig device
down
ifconfig device
up
none no dae mons
available to
s criptle ts
/sbin/insmod,
/usr/sbin/insmod
/usr/bin/install
or
mkdir/cp/chmod/ch
own/chgrp
/sbin/ip,
/usr/sbin/ip
ifconfig or ip
/sbin/ipcalc,
/usr/bin/ipcalc
/usr/bin/ipcrm
/usr/bin/ipcs
ip
ip
/sbin/iptunnel
/sbin/kill,
/usr/bin/kill
/usr/bin/killall
none
/usr/bin/last
Python or bas h
/usr/bin/less
none
none
/sbin/ln,
/usr/bin/ln
605
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
load_policy
ye s
ye s
loadfont
loadkmap
login
logname
losetup
ls
lsattr
lsmod
lzmacat
makedevs
md5sum
mdev
mesg
mkdir
no
no
ye s
no
ye s
ye s
ye s
ye s
no
no
ye s
no
no
ye s
no
no
ye s
ye s
ye s
ye s
ye s
ye s
ye s
no
ye s
no
ye s
ye s
mke2fs
mkfifo
mkfs.ext2
ye s
no
ye s
ye s
ye s
ye s
mkfs.ext3
ye s
ye s
mkfs.minix
no
no
mknod
mkswap
mktemp
modprobe
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
more
mount
ye s
ye s
ye s
ye s
mountpoint
no
no
msh
mt
mv
nameif
nc
netstat
nice
nohup
nslookup
od
openvt
no
ye s
ye s
no
no
no
no
no
ye s
no
ye s
no
ye s
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
ye s
/sbin/load_policy,
/usr/sbin/load_po
licy
none
none
/usr/bin/login
/usr/bin/logname
/usr/bin/losetup
/usr/bin/ls
/usr/bin/lsattr
/usr/bin/lsmod
/usr/bin/lzmadec
/usr/bin/mknod
/usr/bin/md5sum
none
/usr/bin/mesg
/sbin/mkdir,
/usr/bin/mkdir
/usr/sbin/mke2fs
/usr/bin/mkfifo
/usr/sbin/mkfs.ex
t2
/usr/sbin/mkfs.ex
t3
none no s upport
for Minix file s ys te m
/usr/bin/mknod
/usr/sbin/mkswap
/usr/bin/mktemp
/sbin/modprobe,
/usr/sbin/modprob
e
/usr/bin/more
/sbin/mount,
/usr/bin/mount
Look at the output of
the mount command
none
/usr/bin/mt
/usr/bin/mv
none
/usr/bin/nc
/bin/netstat
/bin/nice
/usr/bin/nohup
/usr/bin/nslookup
/usr/bin/od
/usr/bin/openvt
606
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
passwd
patch
pidof
ping
ping6
pipe_progress
pivot_root
printenv
printf
ps
pwd
rdate
readlink
no
no
ye s
ye s
no
no
no
no
no
ye s
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
ye s
readprofile
no
ye s
realpath
no
no
renice
reset
rm
no
no
ye s
ye s
ye s
ye s
rmdir
ye s
ye s
rmmod
ye s
ye s
route
ye s
ye s
rpm
rpm2cpio
run-parts
runlevel
rx
sed
ye s
no
no
no
no
ye s
ye s
ye s
no
no
no
ye s
seq
setarch
setconsole
setkeycodes
no
no
no
no
ye s
ye s
no
ye s
setlogcons
setsid
sh
no
no
ye s
no
ye s
ye s
sha1sum
sleep
ye s
ye s
ye s
ye s
/usr/bin/passwd
/usr/bin/patch
/usr/sbin/pidof
/usr/bin/ping
/bin/ping6
none
/sbin/pivot_root
/usr/bin/printenv
/usr/bin/printf
/usr/bin/ps
/usr/bin/pwd
/usr/bin/rdate
/sbin/readlink,
/usr/bin/readlink
/usr/sbin/readpro
file
Python
os.path.realpath(
)
/usr/bin/renice
/usr/bin/reset
/sbin/rm,
/usr/bin/rm
/sbin/rmdir,
/usr/bin/rmdir
/sbin/rmmod,
/usr/bin/rmmod
/sbin/route,
/usr/sbin/route
/usr/bin/rpm
/usr/bin/rpm2cpio
none
none
none
/sbin/sed,
/usr/bin/sed
/usr/bin/seq
/usr/bin/setarch
none
/usr/bin/setkeyco
des
none
/usr/bin/setsid
/sbin/sh,
/usr/bin/sh
/usr/bin/sha1sum
/sbin/sleep,
/usr/bin/sleep
607
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
sort
start-stop-daemon
stat
ye s
no
no
ye s
no
ye s
strings
stty
su
sulogin
sum
swapoff
swapon
switch_root
sync
sysctl
tail
tar
tee
telnet
telnetd
no
no
no
no
no
ye s
ye s
no
ye s
no
ye s
ye s
ye s
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
ye s
no
test
no
ye s
tftp
time
no
no
ye s
ye s
top
touch
ye s
ye s
ye s
ye s
tr
no
ye s
traceroute
true
tty
tune2fs
udhcpc
udhcpd
no
ye s
no
ye s
no
no
ye s
ye s
ye s
ye s
no
no
umount
ye s
ye s
uname
no
ye s
uncompress
uniq
unix2dos
unlzma
unzip
no
ye s
no
no
no
no
ye s
no
ye s
ye s
/usr/bin/sort
none
/usr/bin/stat or
Python os.stat()
/usr/bin/strings
/bin/stty
/bin/su
/sbin/sulogin
/usr/bin/sum
/usr/sbin/swapoff
/usr/sbin/swapon
/sbin/switch_root
/usr/bin/sync
/sbin/sysctl
/usr/bin/tail
/usr/bin/tar
/usr/bin/tee
/usr/bin/telnet
none no dae mons
available to
s criptle ts
/usr/bin/test or [
in bas h
/usr/bin/tftp
/usr/bin/time or
Python
/usr/bin/top
/sbin/touch,
/usr/bin/touch
/usr/bin/tr or
Python
/bin/traceroute
/usr/bin/true
/usr/bin/tty
/usr/sbin/tune2fs
/sbin/dhclient
none no dae mons
available to
s criptle ts
/sbin/umount,
/usr/bin/umount
/bin/uname or
Python os.uname()
none
/usr/bin/uniq
sed 's/$//'
/usr/bin/unlzma
/usr/bin/unzip
608
Busybo x
co mmand
%pre
%post
New co mmand o r
alt ernat ive
uptime
no
ye s
usleep
no
ye s
uudecode
no
ye s
uuencode
no
ye s
vconfig
vi
vlock
watch
watchdog
wc
wget
ye s
ye s
no
no
no
ye s
ye s
ye s
ye s
no
ye s
no
ye s
ye s
which
who
whoami
xargs
yes
zcat
zcip
no
no
no
ye s
no
ye s
no
ye s
ye s
ye s
ye s
ye s
ye s
no
/usr/bin/uptime or
Python re ading
/proc/uptime
/bin/usleep or
Python
/usr/bin/uudecode
or Python
/usr/bin/uuencode
or Python
/usr/sbin/vconfig
/usr/bin/vi
none
/usr/bin/watch
none
/usr/bin/wc
/sbin/wget,
/usr/bin/wget
/usr/bin/which
/usr/bin/who
/usr/bin/whoami
/usr/bin/xargs
/usr/bin/yes
/usr/bin/zcat
Net wo rkManager
s hould take care of
this
[a] Red Hat Enterprise Linux 6 ships with GNU awk rather than the busybox awk in the
installation environm ent.
[b] GNU bash can provide basenam e functionality using string m anipulation. If
var="/usr/bin/command" , then echo ${var##*/} gives command .
[c] GNU bash can provide dirnam e functionality using string m anipulation. If
var="/usr/bin/command" , then echo ${var%/*} gives /usr/bin .
609
610
Re d Hat Ente rpris e Linux incorporate s the Ope nSSH s uite to provide re mote
acce s s to the s ys te m. The SSH s e rvice e nable s a numbe r of functions , which
include acce s s to the command-line from othe r s ys te ms , re mote command
e xe cution, and ne twork file trans fe rs . During the ins tallation proce s s anaconda
may us e the scp fe ature of Ope nSSH to trans fe r cras h re ports to re mote
s ys te ms . Re fe r to the Ope nSSH We b s ite for more information:
http://www.ope ns s h.com/.
Access Co nt ro l
SELinux provide s Mandatory Acce s s Control (MAC) capabilitie s that s upple me nt
the s tandard Linux s e curity fe ature s . Re fe r to the SELinux Proje ct Page s for more
information: http://www.ns a.gov/re s e arch/s e linux/inde x.s html.
Firewall
The Linux ke rne l us e d by Re d Hat Ente rpris e Linux incorporate s the netfilter
frame work to provide fire wall fe ature s . The Ne tfilte r proje ct we bs ite provide s
docume ntation for both netfilter, and the iptables adminis tration facilitie s :
http://ne tfilte r.org/docume ntation/inde x.html.
So f t ware Inst allat io n
Re d Hat Ente rpris e Linux us e s yum to manage the RPM package s that make up the
s ys te m. Re fe r to http://yum.bas e url.org/ for more information.
Virt ualizat io n
Virtualiz ation provide s the capability to s imultane ous ly run multiple ope rating
s ys te ms on the s ame compute r. Re d Hat Ente rpris e Linux als o include s tools to
ins tall and manage the s e condary s ys te ms on a Re d Hat Ente rpris e Linux hos t.
You may s e le ct virtualiz ation s upport during the ins tallation proce s s , or at any
time the re afte r. Re fe r to the Red Hat Enterprise Linux Virtualization Guide
available from
https ://acce s s .re dhat.com/s ite /docume ntation/Re d_Hat_Ente rpris e _Linux/ for more
information.
611
Pet r Bo ko
Pet r Bo ko
612
T hu Jul 0 3 20 14
Pet r Bo ko
Pet r Bo ko
Jack Reed
Jack Reed
T ue Dec 18 20 12
Jack Reed
613
Jack Reed
Jack Reed
614
Mo n Aug 27 20 12
Jack Reed
Update d Choos e Se rve r firs tboot s cre e n and re -arrange d e xplanatory te xt - BZ#806928
Clarifie d re comme nde d s wap s pace table - BZ#836361
Adde d fs profile parame te r to logvol kicks tart option- BZ#838642
Clarifie d role of 'Conne ct automatically' in ne twork config - BZ#846163
Adde d s iz e limits for e xt3 and e xt4 - BZ#848617
Revisio n 1.0 -83
T hu Jul 26 20 12
Jack Reed
Edite d de s cription of s tage 2=URL - BZ#795526
Fixe d incorre ct ins tance s of 'dis k' - BZ#801068
Re place d SSSD with IPA in de s cription of Ente rpris e Ide ntity Se rve r Bas e - BZ#807497
Adde d admonition to re po kicks tart option - BZ#814099
Edite d de s cription of location argume nt for bootloade r kicks tart option - BZ#820680
Adde d admonition re garding de vice node s to Kicks tart Options - BZ#821101
Adde d admonition to Updating Anaconda s e ction re garding rhupdate s dire ctoryBZ#822937
Wed Feb 0 1 20 12
Jack Reed
615
Jack Reed
Jack Reed
616
Wed Oct 5 20 11
Jack Reed
Adde d admonition about root account to s s hpw kicks tart option - BZ#741535
Update d name of initial RAM dis k folde r for POWER booting - BZ#742819
Change d ignoredisk kicks tart commands for multipath de vice s - BZ#638471
Revisio n 1.0 -51
Fri Sep 23 20 11
Corre cte d typo in ope ning line of Chapte r 38
Jack Reed
Jack Reed
Mo n Aug 15 20 11
Jack Reed
617
T hu May 19 20 11
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
618
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
Rdiger Landmann
Deo n Lackey
Fri Feb 11 20 11
Rdiger Landmann
619
Revisio n 1.0 -7
Wed Dec 22 20 10
Rdiger Landmann
Add warning about s e rial numbe rs of multipath de vice s BZ#612177
Add warning about mixing multipath and non-multipath de vice s BZ#628405
Clarify information about e s crow packe ts BZ#638332
Re move obs ole te --byte s -pe r-inode option BZ#638347
Docume nt ignoring multipath dis ks in kicks tart BZ#638471
FCoE not available for Sys te m z BZ#639190
Update d image for Unformatte d DASD De vice s Found BZ#639191
Fixe d various typos BZ#640167
Revisio n 1.0 -4
Wed Oct 27 20 10
Rdiger Landmann
re move inaccurate information about PXE ins tallations BZ#643669
620
I nde x
Revisio n 1.0 -2
Wed Oct 27 20 10
Rdiger Landmann
re move inaccurate information about PXE ins tallations BZ#643669
Revisio n 1.0 -1
T hu Oct 7 20 10
re move "nos torage " option
Rdiger Landmann
Revisio n 1.0 -0
Ve rs ion for GA re le as e
Rdiger Landmann
Wed Aug 25 20 10
Index
Symbols
/bo o t / part it io n
- re comme nde d partitioning, Re comme nde d Partitioning Sche me ,
Re comme nde d Partitioning Sche me
/ro o t /inst all.lo g
- ins tall log file location, Ins talling Package s
/var/ part it io n
- re comme nde d partitioning, Re comme nde d Partitioning Sche me ,
Re comme nde d Partitioning Sche me
A
adding part it io ns, Adding Part it io ns, Adding Part it io ns, Adding Part it io ns
- file s ys te m type , File Sys te m Type s , File Sys te m Type s , File Sys te m Type s
anacdump.t xt , T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
Anaco nda, Ot her T echnical Do cument at io n
anaco nda.lo g, T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
array (see RAID)
aut o mat ic part it io ning, Disk Part it io ning Set up, Disk Part it io ning Set up,
Disk Part it io ning Set up
B
Basic Input /Out put Syst em (see BIOS)
BIOS
- de finition of, BIOS-bas e d x86 Sys te ms
- (s e e als o boot proce s s )
BIOS (Basic Input /Out put Syst em), Bo o t ing t he Inst aller
bo o t lo ader, Updat ing t he Bo o t Lo ader Co nf igurat io n, x86, AMD64, and
Int el 64 Bo o t Lo ader Co nf igurat io n
- (s e e als o GRUB)
- configuration, x86, AMD64, and Inte l 64 Boot Loade r Configuration
621
C
canceling t he inst allat io n, Inst alling f ro m a DVD, Inst alling f ro m a DVD
CD/DVD media
- booting, Booting the Ins tallation Program on x86, AMD64, and Inte l 64
Sys te ms , Booting the Ins talle r
622
I nde x
D
DASD inst allat io n, Inst alling f ro m a Hard Drive
DHCP (Dynamic Ho st Co nf igurat io n Pro t o co l), Set t ing t he Ho st name,
Set t ing t he Ho st name, Set t ing t he Ho st name
Disk Part it io ner
- adding partitions , Adding Partitions , Adding Partitions , Adding Partitions
disk part it io ning, Disk Part it io ning Set up, Disk Part it io ning Set up, Disk
Part it io ning Set up
disk space, Do Yo u Have Eno ugh Disk Space?, Do Yo u Have Eno ugh Disk
Space?
driver disket t e, St art ing t he Inst allat io n Pro gram
drivers
- adding
- re s cue mode , Us ing Re s cue Mode to Fix or Work Around Drive r
Proble ms
- re moving
623
DVD media
- downloading, Obtaining Re d Hat Ente rpris e Linux
- (s e e als o ISO image s )
E
EFI shell, UEFI-based x86 Syst ems
- (s e e als o boot proce s s )
emergency mo de, Bo o t ing int o Emergency Mo de
Encrypt io n
- Backup pas s phras e s
- Cre ating backup pas s phras e s , Cre ating and Saving Backup
Pas s phras e s
- Saving backup pas s phras e s , Cre ating and Saving Backup
Pas s phras e s
- Pas s phras e s
- Saving pas s phras e s , Saving Pas s phras e s
ext 2 (see f ile syst ems)
ext 3 (see f ile syst ems)
ext 4 (see f ile syst ems)
ext ended part it io ns, Part it io ns Wit hin Part it io ns An Overview o f
Ext ended Part it io ns
Ext ensible Firmware Int erf ace shell (see EFI shell)
F
FCo E
- ins tallation, Advance d Storage Options , Advance d Storage Options ,
Advance d Storage Options
f co e
- via Kicks tart, Kicks tart Options
FCP devices, FCP Devices
f ile syst em
- formats , ove rvie w of, It is Not What You Write , it is How You Write It
f ile syst em t ypes, File Syst em T ypes, File Syst em T ypes, File Syst em T ypes
f ile syst ems
624
I nde x
- e xt2, Ins talling from a Hard Drive , Ins talling from a Hard Drive , Ins talling
from a Hard Drive
- e xt3, Ins talling from a Hard Drive , Ins talling from a Hard Drive , Ins talling
from a Hard Drive
- e xt4, Ins talling from a Hard Drive , Ins talling from a Hard Drive , Ins talling
from a Hard Drive
- vfat, Ins talling from a Hard Drive , Ins talling from a Hard Drive , Ins talling from
a Hard Drive
f irewall
- docume ntation, Othe r Te chnical Docume ntation
First bo o t , First bo o t
- conte nt s e rvice , Choos e Se rvice
- RHN s e tup, Subs cription Manage me nt Re gis tration
- s ubs criptions , Configuring the Subs cription Se rvice
- us e rs , Cre ate Us e r
- via Kicks tart, Kicks tart Options
FT P
- ins tallation, Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or
HTTPS, Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or HTTPS,
Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or HTTPS
G
GRUB, x86, AMD64, and Int el 64 Bo o t Lo ader Co nf igurat io n, Bo o t Lo aders
and Syst em Archit ect ure, T he GRUB bo o t lo ader f o r x86 syst ems
- (s e e als o boot loade rs )
- additional re s ource s , Additional Re s ource s
- ins talle d docume ntation, Ins talle d Docume ntation
- us e ful we bs ite s , Us e ful We bs ite s
- alte rnative s to, Alte rnative Boot Loade rs
- boot proce s s , GRUB and the Boot Proce s s on BIOS-bas e d x86 Sys te ms ,
GRUB and the Boot Proce s s on UEFI-bas e d x86 Sys te ms
- Changing Runle ve ls at Boot Time , Changing Runle ve ls at Boot Time
- changing runle ve ls with, GRUB Inte rface s
- commands , GRUB Commands
- configuration, x86, AMD64, and Inte l 64 Boot Loade r Configuration
- configuration file
- /boot/grub/grub.conf , Configuration File Structure
- s tructure , Configuration File Structure
-
625
H
halt , Shut t ing Do wn
- (s e e als o s hutdown)
Hard disk
- initializ ing, Initializ ing the Hard Dis k, Initializ ing the Hard Dis k, Initializ ing the
Hard Dis k
hard disk
- bas ic conce pts , Hard Dis k Bas ic Conce pts
- e xte nde d partitions , Partitions Within Partitions An Ove rvie w of Exte nde d
Partitions
- file s ys te m formats , It is Not What You Write , it is How You Write It
- partition introduction, Partitions : Turning One Drive Into Many
- partition type s , Partitions : Turning One Drive Into Many
- partitioning of, An Introduction to Dis k Partitions
hard drive inst allat io n, Inst alling f ro m a Hard Drive, Inst alling f ro m a Hard
Drive, Inst alling f ro m a Hard Drive
- pre paring for, Pre paring for a Hard Drive Ins tallation, Pre paring for a Hard
Drive Ins tallation, Pre paring for a Hard Drive Ins tallation
hardware
- compatibility, Is Your Hardware Compatible ?
- configuration, Sys te m Spe cifications Lis t
- s upport, Hardware Re quire me nts , Hardware Re quire me nts
hardware preparat io n, IBM Po wer Syst ems servers, Preparat io n f o r IBM
Po wer Syst ems servers
HMC vt erm, Using t he HMC vt erm
ho st name, Set t ing t he Ho st name, Set t ing t he Ho st name, Set t ing t he
Ho st name
HT T P
- ins tallation, Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or
HTTPS, Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or HTTPS,
Pre paring for a Ne twork Ins tallation, Ins talling via FTP, HTTP, or HTTPS
I
init co mmand, T he /sbin/init Pro gram
- (s e e als o boot proce s s )
- configuration file s
- /e tc/inittab , Sys V Init Runle ve ls
- role in boot proce s s , The /s bin/init Program
626
I nde x
627
K
kdump, Kdump
kernel
- role in boot proce s s , The Ke rne l
kernel o pt io ns, Kernel Opt io ns
keybo ard
- configuration, Ke yboard Configuration, Ke yboard Configuration
- navigating the ins tallation program us ing, Us ing the Ke yboard to Navigate ,
Us ing the Ke yboard to Navigate , Us ing the Ke yboard to Navigate
keymap
- s e le cting language , Language Se le ction, Language Se le ction
- s e le cting type of ke yboard, Ke yboard Configuration, Ke yboard Configuration
Kickst art , Aut o mat ing t he Inst allat io n wit h Kickst art , Aut o mat ing t he
Inst allat io n wit h Kickst art
kickst art
- how the file is found, Starting a Kicks tart Ins tallation
- parame te rs for Sys te m z parame te r file s , Parame te rs for Kicks tart
Ins tallations
- s ubs criptions , Running s ubs cription-manage r as a Pos t-Ins tall Script
628
I nde x
629
630
I nde x
L
language
- configuration, Language Se le ction, Language Se le ction
- s e le cting, Language Se le ction, Language Se le ction, Language Se le ction
lo g f iles, T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
- kicks tart ins tallations , What are Kicks tart Ins tallations ?
LVM
-
M
mast er bo o t reco rd, x86, AMD64, and Int el 64 Bo o t Lo ader Co nf igurat io n
Mast er Bo o t Reco rd, Unable t o Bo o t int o Red Hat Ent erprise Linux (see
MBR)
- re ins talling, Re ins talling the Boot Loade r
MBR
- de finition of, A De taile d Look at the Boot Proce s s , BIOS-bas e d x86 Sys te ms
- (s e e als o boot loade rs )
- (s e e als o boot proce s s )
- ins talling boot loade r on, Advance d Boot Loade r Configuration
mo dem, Set t ing t he Ho st name, Set t ing t he Ho st name, Set t ing t he
Ho st name
mo unt po int s
- partitions and, Dis k Partitions and Mount Points
Mult ipat h devices
- Mixing with non-multipath de vice s , Dis k Partitioning Se tup, Dis k Partitioning
Se tup, Dis k Partitioning Se tup
N
net wo rk
- ins tallations
- FTP, Ins talling via FTP, HTTP, or HTTPS, Ins talling via FTP, HTTP, or
HTTPS, Ins talling via FTP, HTTP, or HTTPS
- HTTP, Ins talling via FTP, HTTP, or HTTPS, Ins talling via FTP, HTTP, or
HTTPS, Ins talling via FTP, HTTP, or HTTPS
- NFS, Ins talling via NFS, Ins talling via NFS, Ins talling via NFS
Net wo rk bo nding, Co nf iguring a Bo nded Int erf ace
Net wo rk bo o t inst allat io ns
- boot me s s age , cus tom, Adding a Cus tom Boot Me s s age
631
O
OpenSSH, Ot her T echnical Do cument at io n
- (s e e als o SSH)
OS/40 0 , Bo o t Lo aders and Syst em Archit ect ure
- (s e e als o boot loade rs )
P
package gro ups, Cust o mizing t he So f t ware Select io n , Cust o mizing t he
So f t ware Select io n , Cust o mizing t he So f t ware Select io n
packages
- groups , Package Group Se le ction, Package Group Se le ction, Package Group
Se le ction
- s e le cting, Package Group Se le ction, Package Group Se le ction,
Package Group Se le ction
- ins talling, Package Group Se le ction, Package Group Se le ction, Package
Group Se le ction
- ins talling with yum, Ins talling Package s With yum
- s e le cting, Package Group Se le ction, Package Group Se le ction, Package
Group Se le ction
paramet er f iles, Paramet er and Co nf igurat io n Files
- ins tallation ne twork parame te rs , Ins tallation Ne twork Parame te rs
- kicks tart parame te rs , Parame te rs for Kicks tart Ins tallations
- loade r parame te rs , Loade r Parame te rs
- re quire d parame te rs , Re quire d Parame te rs
- s ample parame te r file , Sample Parame te r File and CMS Configuration File
- VNC parame te rs , VNC and X11 Parame te rs
632
I nde x
633
- s e tting root, Se t the Root Pas s word, Se t the Root Pas s word, Se t the Root
Pas s word
Planning f o r Inst allat io n
- Sys te m z , Pre -Ins tallation
Po wer Syst ems rescue mo de, Rescue Mo de o n Po wer Syst ems servers
- acce s s ing SCSI utilitie s , Spe cial Cons ide rations for Acce s s ing the SCSI
Utilitie s from Re s cue Mode
pro gram.lo g, T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
pro grams
- running at boot time , Running Additional Programs at Boot Time
PulseAudio , Ot her T echnical Do cument at io n
PXE (Pre-bo o t eXecut io n Enviro nment ), Bo o t ing f ro m t he Net wo rk Using
PXE
R
RAID
- hardware , RAID and Othe r Dis k De vice s , RAID and Othe r Dis k De vice s
- kicks tart ins tallations , Kicks tart Options
- Kicks tart Configurator, Cre ating Software RAID Partitions
- s oftware , RAID and Othe r Dis k De vice s , RAID and Othe r Dis k De vice s
- s ys te m unbootable afte r dis k failure , Trouble s hooting GRUB
- trouble booting from drive attache d to RAID card, Are You Unable to Boot
With Your RAID Card?
rc.lo cal
- modifying, Running Additional Programs at Boot Time
rc.serial , Running Addit io nal Pro grams at Bo o t T ime
- (s e e als o s e ts e rial command)
Red Hat Subscript io n Management , Subscript io n Management Regist rat io n
regist rat io n
- with Firs tboot, Se t Up Software Update s
- with kicks tart, Running s ubs cription-manage r as a Pos t-Ins tall Script
remo ving
- Re d Hat Ente rpris e Linux
- from IBM Sys te m z , Re moving Re d Hat Ente rpris e Linux from IBM
Sys te m z
- from x86-bas e d s ys te ms , Re moving Re d Hat Ente rpris e Linux From
x86-bas e d Sys te ms
rescue discs, Bo o t ing Yo ur Co mput er wit h t he Rescue Mo de
rescue mo de, Rescue Mo de, Bo o t ing Yo ur Co mput er wit h t he Rescue Mo de
- de finition of, Booting into Re s cue Mode
- utilitie s available , Booting into Re s cue Mode
634
I nde x
rescue mo de, Po wer Syst ems, Rescue Mo de o n Po wer Syst ems servers
- acce s s ing SCSI utilitie s , Spe cial Cons ide rations for Acce s s ing the SCSI
Utilitie s from Re s cue Mode
RHN set up
- s e le cting the s ubs cription s e rvice , Subs cription Manage me nt Re gis tration
ro o t / part it io n
- re comme nde d partitioning, Re comme nde d Partitioning Sche me ,
Re comme nde d Partitioning Sche me
ro o t passwo rd, Set t he Ro o t Passwo rd, Set t he Ro o t Passwo rd, Set t he
Ro o t Passwo rd
runlevel 1, Bo o t ing int o Single-User Mo de
runlevels (see init co mmand)
- changing with GRUB, GRUB Inte rface s
- configuration of, Runle ve l Utilitie s
- (s e e als o s e rvice s )
S
scp, Ot her T echnical Do cument at io n
- (s e e als o SSH)
screensho t s
- during ins tallation, Scre e ns hots During Ins tallation
select ing
- package s , Package Group Se le ction, Package Group Se le ction, Package
Group Se le ction
SELinux
- docume ntation, Othe r Te chnical Docume ntation
serial co nso le, Co nf iguring t he Int erf ace
serial po rt s (see set serial co mmand)
services
- configuring with chkconfig , Runle ve l Utilitie s
- configuring with nts ys v , Runle ve l Utilitie s
- configuring with Se rvice s Configuration Tool , Runle ve l Utilitie s
Services Co nf igurat io n T o o l , Runlevel Ut ilit ies
- (s e e als o s e rvice s )
set serial co mmand
- configuring, Running Additional Programs at Boot Time
shut do wn, Shut t ing Do wn
- (s e e als o halt)
single-user mo de, Bo o t ing int o Single-User Mo de
ssh
- s tarting s s h at boot time , Enabling Re mote Acce s s with s s h
635
636
I nde x
T
T CP/IP co nf igurat io n, Perf o rming a Net wo rk Inst allat io n, Perf o rming a
Net wo rk Inst allat io n, Perf o rming a Net wo rk Inst allat io n
T elnet , Enabling Remo t e Access wit h T elnet
t ext int erf ace, Co nf iguring t he Int erf ace
t f t p , St art ing t he t f t p Server
t ime zo ne
- configuration, Time Zone Configuration, Time Zone Configuration, Time Zone
Configuration
t raceback messages
- s aving trace back me s s age s without re movable me dia, Saving Trace back
Me s s age s , Saving Trace back Me s s age s , Saving Trace back Me s s age s
t ro ublesho o t ing, T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
- afte r the ins tallation, Proble ms Afte r Ins tallation, Proble ms Afte r Ins tallation,
Proble ms Afte r Ins tallation
- Apache HTTP Se rve r s tops re s ponding during s tartup, Apache HTTP
Se rve r or Se ndmail Stops Re s ponding During Startup, Apache HTTP
Se rve r or Se ndmail Stops Re s ponding During Startup, Apache HTTP
Se rve r or Se ndmail Stops Re s ponding During Startup
- booting into a graphical e nvironme nt, Booting into a Graphical
Environme nt, Booting into a Graphical Environme nt
- booting into GNOME or KDE, Booting into a Graphical Environme nt,
Booting into a Graphical Environme nt
- booting into the X Window Sys te m, Booting into a Graphical
Environme nt, Booting into a Graphical Environme nt
- graphical GRUB s cre e n, Trouble With the Graphical GRUB Scre e n on
an x86-bas e d Sys te m?
- graphical login, Re mote Graphical De s ktops and XDMCP
- logging in, Proble ms Whe n You Try to Log In, Proble ms Whe n You
Try to Log In, Proble ms Whe n You Try to Log In
- printe rs , Your Printe r Doe s Not Work, Your Printe r Doe s Not Work,
Your Printe r Doe s Not Work
- RAM not re cogniz e d, Is Your RAM Not Be ing Re cogniz e d?
- Se ndmail s tops re s ponding during s tartup, Apache HTTP Se rve r or
Se ndmail Stops Re s ponding During Startup, Apache HTTP Se rve r or
Se ndmail Stops Re s ponding During Startup, Apache HTTP Se rve r or
Se ndmail Stops Re s ponding During Startup
- X (X Window Sys te m), Proble ms with the X Window Sys te m (GUI),
Proble ms with the X Window Sys te m (GUI)
- X s e rve r cras he s , Proble ms with the X Se rve r Cras hing and NonRoot Us e rs , Proble ms with the X Se rve r Cras hing and Non-Root
Us e rs
- be ginning the ins tallation, Trouble Be ginning the Ins tallation, Trouble
Be ginning the Ins tallation
- frame buffe r, dis abling, Proble ms with Booting into the Graphical
Ins tallation, Proble ms with Booting into the Graphical Ins tallation
637
- GUI ins tallation me thod unavailable , Proble ms with Booting into the
Graphical Ins tallation, Proble ms with Booting into the Graphical
Ins tallation
- booting, You Are Unable to Boot Re d Hat Ente rpris e Linux, You Are Unable to
Boot Re d Hat Ente rpris e Linux, You Are Unable to Boot Re d Hat Ente rpris e
Linux
- RAID cards , Are You Unable to Boot With Your RAID Card?
- s ignal 11 e rror, Is Your Sys te m Dis playing Signal 11 Errors ?, Is
Your Sys te m Dis playing Signal 11 Errors ?, Is Your Sys te m Dis playing
Signal 11 Errors ?
- during the ins tallation, Trouble During the Ins tallation, Trouble During the
Ins tallation, Trouble During the Ins tallation
- comple ting partitions , Othe r Partitioning Proble ms , Othe r
Partitioning Proble ms for IBM Powe r Sys te ms Us e rs , Othe r
Partitioning Proble ms
- drive mus t have gpt dis k labe l, The "drive mus t have a GPT dis k
labe l" Error Me s s age
- No de vice s found to ins tall Re d Hat Ente rpris e Linux e rror
me s s age , The "No de vice s found to ins tall Re d Hat Ente rpris e Linux"
Error Me s s age , The "No de vice s found to ins tall Re d Hat Ente rpris e
Linux" Error Me s s age , The "No de vice s found to ins tall Re d Hat
Ente rpris e Linux" Error Me s s age
- partition table s , Trouble with Partition Table s , Trouble with Partition
Table s
- s aving trace back me s s age s without re movable me dia, Saving
Trace back Me s s age s , Saving Trace back Me s s age s , Saving
Trace back Me s s age s
- us ing re maining hard drive s pace , Us ing Re maining Space
- DVD failure
- DVD ve rification, Additional Boot Options
U
UEFI (Unif ied Ext ensible Firmware Int erf ace), Bo o t ing t he Inst aller
uninst alling
- from IBM Sys te m z , Re moving Re d Hat Ente rpris e Linux from IBM Sys te m z
- from x86-bas e d s ys te ms , Re moving Re d Hat Ente rpris e Linux From x86bas e d Sys te ms
unregist er, Unregist ering f ro m Red Hat Subscript io n Management Services
upgrade
- to Re d Hat Ente rpris e Linux 7, Upgrading Your Curre nt Sys te m
- us ing Pre upgrade As s is tant, Upgrading Your Curre nt Sys te m
- us ing Re d Hat Upgrade , Upgrading Your Curre nt Sys te m
USB f lash media
- downloading, Obtaining Re d Hat Ente rpris e Linux
- making, Making Me dia
USB media
- booting, Booting the Ins tallation Program on x86, AMD64, and Inte l 64
Sys te ms , Booting the Ins talle r
638
I nde x
V
vf at (see f ile syst ems)
virt ual co nso les, A No t e Abo ut Virt ual Co nso les, A No t e Abo ut Linux
Virt ual Co nso les
Virt ualizat io n
- docume ntation, Othe r Te chnical Docume ntation
VNC (Virt ual Net wo rk Co mput ing), Enabling Remo t e Access t o t he
Inst allat io n Syst em
- docume ntation, Othe r Te chnical Docume ntation
- e nabling, Enabling Re mote Acce s s with VNC
- ins talling clie nt, Enabling Re mote Acce s s to the Ins tallation Sys te m
- lis te ning mode , Conne cting the Ins tallation Sys te m to a VNC Lis te ne r
X
XDMCP, Remo t e Graphical Deskt o ps and XDMCP
Xo rg, Ot her T echnical Do cument at io n
Y
yabo o t , Bo o t Lo aders and Syst em Archit ect ure
- (s e e als o boot loade rs )
yabo o t inst allat io n server, Bo o t ing f ro m t he Net wo rk Using a yabo o t
Inst allat io n Server
yum
- docume ntation, Othe r Te chnical Docume ntation
- ins talling with yum, Ins talling Package s With yum
yum.lo g, T ro ublesho o t ing Inst allat io n o n an Int el o r AMD Syst em,
T ro ublesho o t ing Inst allat io n o n an IBM Po wer Syst ems server,
T ro ublesho o t ing Inst allat io n o n IBM Syst em z
Z
z/IPL, Bo o t Lo aders and Syst em Archit ect ure
- (s e e als o boot loade rs )
639