This repository has been archived by the owner on Oct 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
416 lines (322 loc) · 16.6 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
wr-installer
============
This layer provides a target-based installer for Wind River Linux. It requires
most of the layers that Wind River Linux provides.
Dependencies
------------
This layer depends on the Wind River Linux version of bitbake, oe-core,
meta-filesystems, meta-gnome, and wr-base layer.
Maintenance
-----------
This layer is maintained by Wind River Systems, Inc.
Contact <support@windriver.com> or your support representative for more
information on submitting changes.
Building the target installer
-----------------------------
1. Summary
The target installer is enabled by passing "--layers=wr-installer"
to setup.sh. There are two images in target installer, one is target
image which to be installed to target, another is installer image
which to do the installation.
A target image requires specific components to be compatible with
the installer. To install these components set WRTEMPLATE +=
'feature/installer-support' in local.conf.
For installer image, you are not supposed to change the 'DISTRO'
setting in target build directory. It may work, but it's not
recommended. Instead we should recommend the user run a
oe-init-build-env and create a new build directory for the installer.
Set DISTRO = 'wrlinux-installer' in local.conf file.
There are two kinds of installer builds: "Image Based Install" and
"Package Based Install". The former is to install a prebuilt image,
the latter is to install RPM packages.
For Image Based Install, set INSTALLER_TARGET_BUILD =
'<target-build-image>' in local.conf to specify an .ext2, .ext3,
or ext4 image file, then the installer will copy this image to the
target.
For Package Based Install, set INSTALLER_TARGET_BUILD =
'<target-build-topdir>' to specify the path to target build directory
that will supply RPMs, and INSTALLER_TARGET_IMAGE = '<target-image-pn>'
to specify the image recipe name, then the installer will install its
RPMs to the target;
2. Two main use cases
2.1 Installer image with ext2, ext3 or ext4 image from the target
build to be copied to local disk.
2.2 Installer image with RPMs from the target build to be installed
to local disk.
Note: Each option requires two builds, one is for the target build,
the other one is for the installer itself. The build and installer
board (BSP) configuration should be the same.
3. Examples for the use cases
3.1 Image Based Install
3.1.1 Setup with wr-installer layer and installer-support template.
$ mkdir <wr9-project>
$ cd <wr9-project>
$ git clone --branch WRLINUX_9_BASE --single-branch \
git://pek-git.wrs.com/git/wrlinux-x
$ ./wrlinux-x/setup.sh --machines=[intel-x86-64|qemux86-64] \
--distros=wrlinux --dl-layers \
--layers=wr-installer \
--templates=feature/installer-support
Note: The machine of qemux86-64 is used for qemu test
3.1.2 Build target image (such as wrlinux-image-glibc-std) in target_build.
$ . <wr9-project>/oe-init-build-env <target_build-dir>
$ bitbake wrlinux-image-glibc-std
3.1.3 Build installer image in installer_build.
$ . <wr9-project>/oe-init-build-env <installer_build-dir>
edit local.conf
---
DISTRO = 'wrlinux-installer'
INSTALLER_TARGET_BUILD = '<target_build-dir>/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-std-intel-x86-64.ext4'
---
$ bitbake wrlinux-image-installer
3.2 Package Based Install
3.2.1 Setup with wr-installer layer and installer-support template.
The same with 3.1.1
3.2.2 Build target image in target_build.
The same with 3.1.2
3.2.3 Build installer image in installer_build.
$ . <wr9-project>/oe-init-build-env <installer_build-dir>
edit local.conf
---
DISTRO = 'wrlinux-installer'
INSTALLER_TARGET_BUILD = '<target_build-dir>'
INSTALLER_TARGET_IMAGE = 'wrlinux-image-glibc-std'
---
$ bitbake wrlinux-image-installer
4. Install
4.1 Burn the output ISO to a DVD or dd it to a USB disk, and use it to
boot the target board and start the install.
4.2 Use qemu for testing
Build target installer with machine of qemux86-64
Create the qemu disk:
$ <build-topdir>/tmp/sysroots/x86_64-linux/usr/bin/qemu-img create -f qcow hd0.vdisk 5000M
Start qemu with installer image:
$ runqemu qemux86-64 wrlinux-image-installer iso slirp qemuparams="hd0.vdisk"
Add "-vnc :4" to qemuparams to start a VNC capable session.
Add "-usbdevice wacom-tablet" to qemuparams to correct mouse
pointer position, it works with the Linux 3.14, but does not work with
Linux 3.17.
4.3 Use virtualbox for testing
4.3.1 Prepare virtualbox
Take Ubuntu 14.04 for example, the virtualbox is 4.3.10
sudo apt-get install virtualbox
4.3.2 Create virtual machine
'New'-> Name:***
Type:Linux
Version:Linux 2.6/3.x(64 bit)
'Next'-> Memory size
'Next'-> Hard drive:create a virtual hard drive now
'Create'-> VDI(Virtualbox Disk Image)
'Next'-> Dynamically allocated
'Next'-> File location and size
4.3.3 Add ISO storage to virtual machine
Select newly created virtual machine
'Setting'-> 'Storage'-> 'Controller:IDE'->
'Empty'->'CD/DVD Drive: IDE Primary Master'->
'Choose a virtual CD/DVD disk file'->
'export/intel-x86-64-installer-standard-dist.iso'
4.3.4 Config net for virtual machine
Select newly created virtual machine
'Setting'-> 'Network'-> Attached to: Bridged Adapter
Name: eth0
4.3.5 Add serial port to virtual machine
Select newly created virtual machine
'Setting'-> 'Serial Ports'-> 'Port 1'->
'Enable Serial Port'-> Port Number: COM1
Port Mode: Host Pipe
Create Pipe
Port/File Path: /tmp/pipe
4.3.6 Use minicom to connect virtual machine's serial port
sudo minicom -s
'Serial port setup'->
'A - Serial Device : unix#/tmp/pipe'->
'Exit'
4.3.7 Start virtual machine
Select newly created virtual machine-> 'Start'
After the installation finished, delete ISO storage and
start virtual machine again to check the installed target.
4.4 Need 1G memory size at least
While starting qemu/virtualbox/vmware for testing, please make
sure virtual machine has 1G memory at least.
5. Use custom installer.conf
The second build can use installer.conf to help speed up the build
process when package based installs, the user can set WRL_INSTALLER_CONF
in the conf file, for example:
edit local.conf
WRL_INSTALLER_CONF = "/my/installer.conf"
You can customize the contents of installer.conf when needed, for example,
add packages that you will like to install, but if you do, you must ensure
that the added packages are in the target build (target_build).
6. Perform the kickstart installation
The installer can support kickstart installs. To do this, use the ks file
from /root/anaconda-ks.cfg after the installation and edit it for later
installs. You can specify the ks file by setting KICKSTART_FILE in the conf
file, for example:
KICKSTART_FILE = "/my/anaconda-ks.cfg"
Then the second build will take it and start the kickstart installs
by default when you start the target with installer image.
7. About Grub version
The current installer only supports grub 2.
8. How to create RPM metadata in build
bitbake package-index
There are multiple repodata in deploy dir:
$ find tmp/deploy/rpm/ -name repodata
tmp/deploy/rpm/corei7_64/repodata
tmp/deploy/rpm/intel_x86_64/repodata
tmp/deploy/rpm/all/repodata
9. Put multiple target builds into one installer image
9.1 Create and build multiple target build projects.
Refer to section 3.1.1 on how to setup and build each target project.
In this example, the projects are named target_build1, target_build2 and
target_build3. The target_build1 and target_build2 are build dirs,
target_build3 is ext4 file. Build 'wrlinux-image-glibc-std' in
target_build1 and build 'core-image-minimal' in target_build2.
9.2 Edit local.conf, use variable INSTALLER_TARGET_BUILD to point to
"<target_build1> <target_build2> <target_build3>", and set
INSTALLER_TARGET_IMAGE = "wrlinux-image-glibc-std core-image-minimal",
the space is the separator:
$ bitbake wrlinux-image-installer
Then the installer image will contain all target builds specified,
including target_build1, target_build2 and target_build3.
When you boot the installer image, you will get a selection menu:
NOTE: target_buildX is the basename of project
=============== Found the following products ===============
1) DISTRO1 target_build1 DISTRO_NAME1 DISTRO_VERION1
2) DISTRO2 target_build2 DISTRO_NAME2 DISTRO_VERION2
3) <target_build3-ext4-file>-3
Please enter your choice (0 to quit):
NOTE: You need to use a proper name for the target build project
since its basename will be used in the selection menus.
NOTE: The number of the entries in WRL_INSTALLER_CONF or
KICKSTART_FILE must be the same as the number of target build
projects.
For example, if you want to use WRL_INSTALLER_CONF or
KICKSTART_FILE for target_build1, target_build2 and
target_build3, set each of the three in the conf file.
WRL_INSTALLER_CONF = "/my/target1.conf /my/target2.conf \
/my/target3.conf"
KICKSTART_FILE = "/my/target1.ks /my/target2.ks \
/my/target3.ks"
Then target_build1 will use /my/target1.conf and /my/target1.ks,
target_build2 and target_build3 will work similarly.
10. BIOS-based PXE (legacy)
10.1 Preparation
Refer "Wind River Linux USER GUIDE 6"
- About Configuring PXE, P422
- Configuring PXE, P424
- Configuring DHCP, P427
- Configuring DHCP for PXE, P428
- Configuring NFS, P430
- Configuring TFTP, P431
The PXELinux Boot Loader File pxelinux.0 located in syslinux package,
you could directly copy it to the tftp download dir.
Copy kernel (bzImage) to tftp download dir. In ISO, it named vmlinuz.
10.2 initrd boot
Use recipe wrlinux-image-installer-initramfs to support initrd boot,
please copy initramfs (wrlinux-image-installer-initramfs-intel-x86-64.cpio.gz)
to tftp download dir.
We must add param "LABEL=initrd-install" to PXE config file.
There is an example in examples/pxe/pxelinux.cfg/default.initramfs
10.3 initrd boot with kickstart
Based on 10.2 initrd boot, we should prepare a kickstart file on
web server, and add param "ks=http://webserver_ip/anaconda-ks.cfg"
to PXE config file.
There is an example in examples/pxe/pxelinux.cfg/default.initramfs_ks
10.4 nfs boot
About PXE config file, there is an example in
examples/pxe/pxelinux.cfg/default.nfs
11. Download file from http/ftp server to target image
Add key in kickstart to support downloading file from http/ftp
server to target image:
'download --dest=[file://dir/filename|/dir/filename] --src=[http url| ftp url]'
Here is the example in kickstart file:
---start---
download --dest=/etc/rpm/keys/0x100001 --src=http://128.224.162.159/testkey
download --dest=file://etc/rpm/keys/0x100002 --src=http://128.224.162.159/testkey2
---end---
The file be download to target image (/mnt/image/****). For host image,
we could make use of "%pre" section with invoking shell to do that)
12. How to authenticate while downloading kickstart from web server
12.1 We add boot options 'ksuser' and 'kspasswd'(listed in /proc/cmdline)
to support authentication while downloading kickstart from web server.
You could integrate them to installer image by set APPEND_append =
" ks=<url-ks> ksuser=<username> kspasswd=<password>" in local.conf
12.2 Currently, we support basic/digest authentication, which decided by
your web server.
13. How to add the http repository mirror list
1. Create the mirror list file, the format is the same as the output of
invoking "smart mirror --show", you should make sure the mirror listed
in the file are correct:
...
http://origin.url/some/path/
http://mirror.url/another/path/
http://some.mirror.url/to/the/same/content/
...
2. Next, place the mirror list file on the web server.
3. When starting anaconda, choose to add an http repository, input the URL
of the mirror list, be sure to select 'This URL refers to a mirror list'
checkbox. Then click the 'Done' button to add the mirror list.
14 UEFI-based PXE
The main difference between BIOS-based and UEFI-based on PXE is the former
uses pxelinux.0 provided by syslinux package as the PXELinux Boot Loader File;
and UEFI-based PXE use a generated bootx64-pxe.efi as PXELinux Boot Loader
File. Here is the introduction of bootx64-pxe.efi generation.
In installer build, after installer image built:
1. Configure grub.cfg:
1.1 If you are familiar with PXE and grub, set PXE_UEFI_GRUB_CONF to
point your own grub.cfg, you could customize it as you wish.
1.2 Or set APPEND_append = " ks=<url-ks>" in local.conf, it configures a
default grub.cfg which tells PXE image where to download the kickstart
file.
2. Generate UEFI-base PXE image
$ bitbake grub-efi -cmkpxeimage
3 Copy UEFI-base PXE image to tftp download dir
$ cp tmp/deploy/images/intel-x86-64/bootx64-pxe.efi /srv/tftpboot/boot
3. Update the DHCP server config
$ vi /etc/dhcp/dhcpd.conf
----start----
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578
subnet 128.224.162.0 netmask 255.255.255.0 {
range 128.224.162.195 128.224.162.200;
option routers 128.224.162.194;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 128.224.162.194;
if option arch = 00:06 {
filename "bootia32.efi";
} else if option arch = 00:07 {
filename "boot/bootx64-pxe.efi";
} else {
filename "pxelinux.0";
}
}
}
----end----
4. Restart dhcpd and go start PXE UEFI installation.
License
-------
Copyright (C) 2013-2014 Wind River Systems, Inc.
Source code included in the tree for individual recipes is under the LICENSE
stated in the associated recipe (.bb file) unless otherwise stated.
The metadata is under the following license unless otherwise stated.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.