1
0

booting 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  1. .TH BOOTING 8
  2. .SH NAME
  3. booting \- bootstrapping procedures
  4. .SH SYNOPSIS
  5. none
  6. .SH DESCRIPTION
  7. This manual page collects the incantations required to bootstrap Plan 9 machines.
  8. Some of the information here is specific to the installation at Bell Labs;
  9. some is generic.
  10. .PP
  11. If a CPU server is up, BOOTP/DHCP and TFTP will run from there;
  12. if not, the necessary files and services must be available on a separate machine,
  13. such as a Unix system, to use these protocols for bootstrapping.
  14. .PP
  15. Be sure to read
  16. .IR boot (8)
  17. to understand what happens after the kernel is loaded.
  18. .SS Terminals
  19. To bootstrap a diskless terminal or a CPU server, a file server must be running.
  20. PCs can boot from a floppy disk or any FAT16 partition.
  21. On all the terminals, typing two control-T's followed by a lower-case
  22. .B r
  23. reboots the machine;
  24. other methods of rebooting are mentioned for some machines.
  25. .SS PCs
  26. To boot a PC, it is necessary to get
  27. .B /386/9load
  28. loaded into memory.
  29. There are many ways to do this. A Plan 9 boot floppy prepared by
  30. .B format
  31. (see
  32. .IR prep (8))
  33. will load
  34. .B 9load
  35. when the PC is reset or powered on.
  36. Other methods are described in
  37. .IR 9load (8).
  38. .B 9load
  39. then locates and loads a Plan 9 kernel, using configuration information
  40. from the file
  41. .B plan9.ini
  42. stored in the
  43. .B 9fat
  44. configuration partition or on a DOS file system.
  45. See
  46. .IR 9load (8)
  47. for details.
  48. .PP
  49. Once the kernel is booted, it behaves like the others.
  50. See
  51. .IR boot (8)
  52. for details.
  53. .SS Alpha PCs
  54. Alpha PCs must be booted via TFTP using the SRM console.
  55. If the system has ARC firmware instead, SRM may be downloaded from
  56. .IP
  57. .EX
  58. http://www.compaq.com/
  59. .EE
  60. .PP
  61. You must configure the SRM firmware to load the file
  62. .BR /alpha/bootalphapc .
  63. The following commands may be used (replace
  64. .B ewa0
  65. with the name of your ethernet device, if different):
  66. .IP
  67. .EX
  68. set boot_reset ON
  69. set boot_file /alpha/bootalphapc
  70. set bootdef_dev ewa0
  71. set ewa0_inet_init bootp
  72. set ewa0_protocols BOOTP
  73. .EE
  74. .PP
  75. This secondary bootstrap program will first load the file
  76. .BR /alpha/conf/ <IP-address>
  77. (substituting the IP address of the system as obtained via bootp).
  78. This file is expected to be in
  79. .IR plan9.ini (8)
  80. format (the file
  81. .B /alpha/conf/10.0.0.2
  82. may be used as a template).
  83. It then loads the kernel via tftp, using the value of
  84. .B bootfile
  85. to tell it which file to load; this should be
  86. .B /alpha/9apc
  87. for terminals.
  88. .SS CPU Servers
  89. The Plan 9 CPU servers are multi-user, so they do not request a user name
  90. when booting.
  91. On the CPU servers, typing a control-P on the console reboots the machine.
  92. .SS PC CPU Server
  93. Proceed as for the PC terminal, but load
  94. .B /386/9pccpu
  95. or
  96. .BR /386/9pccpudisk .
  97. .SS Alpha PC CPU Server
  98. Proceed as for the Alpha PC terminal, but use
  99. .B /alpha/9apccpu
  100. as the value of
  101. .BR bootfile .
  102. .SS SGI Challenge multiprocessor CPU Server
  103. The Challenge ROM monitor can boot from the Ethernet.
  104. To boot from the Ethernet, type
  105. .IP
  106. .EX
  107. .B bootp()/mips/9ch
  108. .EE
  109. .PP
  110. or use the ROM command
  111. .B setenv
  112. to set the variable
  113. .B bootfile
  114. to that same string and type
  115. .BR boot .
  116. To load a different file, tell
  117. .B bootp
  118. which file to load,
  119. and to force the download to come from a particular system,
  120. .BR bootp()system:file .
  121. Any arguments after
  122. .B bootp()file
  123. are passed to
  124. .BR /boot .
  125. If you are running a Plan 9
  126. .SM BOOTP
  127. server (see
  128. .IR dhcpd (8)),
  129. the file name can be omitted and the
  130. file specified by the
  131. .B bootf
  132. parameter for the machine in
  133. .BR /lib/ndb
  134. will be downloaded by default.
  135. .PP
  136. Once the kernel is loaded,
  137. it prompts for the Ethernet
  138. protocol to use to reach the root file server; request the default.
  139. .PP
  140. .SS File servers
  141. The CPU servers and terminals run essentially the same program, but
  142. the Plan 9 file servers run a distinct system.
  143. The file servers accept only the commands described in
  144. .IR fs (8)
  145. on their consoles.
  146. .SS PC File Server
  147. Boot the PC file server like a regular PC, loading the appropriate file system kernel.
  148. .SH "SEE ALSO"
  149. .IR 9load (8),
  150. .IR boot (8),
  151. .IR fs (8),
  152. .IR init (8),
  153. .IR plan9.ini (8)
  154. .SH SOURCE
  155. Sources for the various boot programs are under
  156. .BR /sys/src/boot .
  157. .SH BUGS
  158. The file server should be able to boot from its own disk.