Lines Matching full:system

28 .\".ds RH "System Building Process
31 SYSTEM BUILDING PROCESS
33 In this section we consider the steps necessary to build a bootable system
34 image.  We assume the system source is located in the ``/sys'' directory
35 and that, initially, the system is being configured from source code.
37 Under normal circumstances there are 5 steps in building a system.
39 Create a configuration file for the system.
41 Make a directory for the system to be constructed in.
46 to compile and load the system image.
49 configured system with
54 Compile and load the system with 
57 Steps 1 and 2 are usually done only once.  When a system configuration
61 and remake the system.  Sometimes,
64 in the system's directory; this will be discussed later.
76 which the configured system is to be built.  
82 system has a configuration file ``/sys/conf/GENERIC'' and an accompanying
84 Although it is not required that the system sources and configuration
87 as most of the system code and the files created by
90 If the system files are not located in ``/sys,''
92 of other parts of the system that share files with the kernel.
96 cpu type, timezone, system identifier, maximum users, and root device
100 supported by the system).  Section 4 of this document
104 the system.  If the devices to be configured are not already
112 and look for any errors.  Never try and use a system which
126 in compiling and loading the system,
129 One file for each possible system image for this machine,
133 is the name of the system image,
134 which describes where swapping, the root file system, and other
135 miscellaneous system devices are located.
138 system supports, which define the hardware configured.
140 A file containing the I/O configuration tables used by the system
148 system path for handling interrupts,
153 or are curious how the system's autoconfiguration scheme
160 is done generating the files needed to compile and link your system it
163 directory for the system just configured and type ``make depend''
166 to recognize interdependencies in the system source code.
167 This will insure that any changes to a piece of the system
174 to the system include files.  The rules generated specify which source code
178 due to the modification of a system header file.
180 and reflect the global system options.
184 is used to regenerate the system makefile.
186 Building the system
190 should allow a new system to be rebuilt by simply typing ``make image-name''.
191 For example, if you have named your bootable system image ``kernel'',
193 will generate a bootable image named ``kernel''.  Alternate system image names
194 are used when the root file system location and/or swapping configuration
197 creates has entry points for each system image defined in
199 Thus, if you have configured ``kernel'' to be a system with the root file
200 system on an ``hp'' device and ``hkkernel'' to be a system with the root
201 file system on an ``hk'' device, then ``make kernel hkkernel'' will generate
203 As the system will generally use the disk from which it is loaded
204 as the root filesystem, separate system images are only required
207 Note that the name of a bootable image is different from the system
208 identifier.  All bootable images are configured for the same system;
209 only the information about the root file system and paging devices differ.
212 The last step in the system building process is to rearrange certain commonly
213 used symbols in the symbol table of the system image;  the makefile
222 the currently executing system to be named ``/kernel''.  If you install
223 a new system and name it something other than ``/kernel'', many programs
229 there are at least two approaches to saving time in building system
230 images.  The best way is to have a single system image which is run on
234 configured system image.  This may be due to limited memory (building
235 a system with many unused device drivers can be expensive), or to
243 To share object modules, a generic system should be built.  Then, for
244 each system configure the system as before, but before recompiling and
245 linking the system, type ``make links'' in the system compilation directory.
246 This will cause the system
260 per-system dependencies in an include file, they will not be recognized
265 It is simple to configure a system which will automatically
269 to obtain information regarding the system's operation.  Profiled
273 system and propagate time spent in each routine along the arcs
275 The program counter sampling can be driven by the system clock, or
277 latter is highly recommended, as use of the system clock will result
281 To configure a profiled system, the
284 A profiled system is about 5-10% larger in its text space due to
285 the calls to count the subroutine invocations.  When the system
288 profiled system varies; under normal load we see anywhere from 5-25%
289 of the system time spent in the profiling code.