Lines Matching +full:boot +full:- +full:up
49 Intel 386/486-based machines (ISA/AT or EISA bus only)
51 Sony News MIPS-based workstations
53 Omron Luna 68000-based workstations
150 HP-IB/CS80 (7912, 7914, 7933, 7936, 7945, 7957, 7958, 7959, 2200, 2203)
151 and SCSI-I (including magneto-optical).
155 Low-density CS80 cartridge (7914, 7946, 9144),
156 high-density CS80 cartridge (9145),
162 98644 built-in single-port, 98642 4-port and 98638 8-port interfaces.
185 Battery-backed real time clock,
186 builtin and 98625A/B HP-IB interfaces,
188 serial printers and plotters on HP-IB,
196 port, 1/2" tape drives (7980), CD-ROM, and the PVRX/TVRX 3D graphics displays.
210 ``rd'' for HP-IB CS80 disks,
211 ``ct'' for HP-IB CS80 cartridge tapes, or
212 ``sd'' for SCSI-I disks
213 (SCSI-I tapes are currently not supported).
214 The \fIadaptor\fP field is a logical HP-IB or SCSI bus adaptor card number.
217 0 for devices on the ``slow'' HP-IB interface (usually tapes) and
218 1 for devices on the ``fast'' HP-IB interface (usually disks).
219 To get a complete mapping of physical (select-code) to logical card numbers
222 HP-IB or SCSI bus.
224 for HP-IB the range is 0 to 7.
227 and disks: for disks it is a disk partition (in the range 0-7),
237 The basic steps involved in bringing up the HP300 are as follows:
244 Boot the UNIX system on the new disk.
262 Note that an HP SCSI magneto-optical disk will work fine for this case.
263 \*(4B will boot and run (albeit slowly) using one.
265 you will need at least 640MB (at least a 2213A SCSI or 2203A HP-IB disk).
272 Since most HP disk drives come pre-formatted
275 you can format a disk under HP-UX using the
278 Once you have \*(4B up and running on one machine you can use the
281 Any additional HP-IB disks will have to be formatted using HP-UX.
286 command under HP-UX to copy the root filesystem image from
296 the version of HP-UX that is running.
297 Consult the HP-UX
304 HP-UX (or an HP) to create the boot disk.
309 you may still be able to install and boot \*(4B if you have an
310 HP-IB cartridge tape drive.
325 Once this tape is created you can boot and run the standalone tape
337 \fBFrom:\fP \fI^C\fP (control-C to see logical adaptor assignments)
340 \fBFrom:\fP \fIct(0,7,0,0)\fP (HP-IB tape, target 7, first tape file)
352 the HP-UX drive.
354 destroying the HP-UX disk.
358 the machine and do another attended boot (see previous section),
360 Once loaded and running the boot program will display the CPU type and
361 prompt for a kernel file to boot:
365 Boot
370 After providing the kernel name, the machine will boot \*(4B with
377 Copyright (c) 1992 Hewlett-Packard Company
383 HP9000/433 (33MHz MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches)
421 a description of your machine from which to configure a site-dependent
423 The messages printed at boot here contain much of the information
427 is printed out at boot time as the system verifies that each device
437 or with ``rd0'' if you are booting from an HP-IB disk.
451 \fBWARNING: preposterous time in filesystem \-\- CHECK AND RESET THE DATE!\fP
464 from the Bourne shell, and lets you know that you are the super-user,
467 At this point, the root filesystem is mounted read-only.
475 \fB#\fP \fImount_mfs -s 1000 -T type /dev/null /tmp\fP (create a writable filesystem)
478 \fB#\fP \fImount \-uw /tmp/\*(Dk#a /\fP (read-write mount root filesystem)
496 overwrite your initial HP-UX disk, as it will no longer
497 be needed (assuming you have no plans to run HP-UX again).
506 \fB#\fP\|\fIdump 0f \- /dev/r\*(Dk0a | restore xf \-\fP
512 you should then shut down the system, and boot on the disk that
529 In the latter, some of the partitions may map non-existent sectors
533 However, as long as you are willing to give up a little space,
553 \fB#\fP \fIdisklabel -r -e /dev/r\fBXX#\fPd
565 \fB#\|\fP\fIdisklabel -rw \fBXX# type\fP \fI"optional_pack_name"\fP
571 contents of a disk, and may be up to 16 characters long. This procedure
584 you should substitute the name ``rd'' if you are running on an HP-IB disk.
623 Battery-backed real time clock,
624 built-in serial devices,
631 anything VME-based,
641 have SunOS 4.1.x or Solaris to bring up \*(4B.
643 Sun-supplied boot loader will be used to boot \*(4B; you must copy
653 boot either system as needed simply by changing the EEPROM's boot
665 boot, swap, and root filesystem.
674 to print the boot up messages to the console.
680 Bring up SunOS (preferably SunOS 4.1.x or Solaris 1.x, although
698 You can build an old-format filesystem on \*(4B by giving the \-O
710 you must build an old-style root filesystem
712 so that the SunOS boot program will work.
717 to enable disk-based booting.
722 # cp /boot /mnt/boot
724 # installboot /mnt/boot bootsd /dev/rsd3a
740 Boot the supplied kernel:
744 ok boot sd(0,3)kernel -s [for old proms] OR
745 ok boot disk3 -s [for new proms]
746 \&... [\*(4B boot messages]
758 to set up \*(4B to reboot automatically:
762 ok setenv boot-from sd(0,3)kernel [for old proms] OR
763 ok setenv boot-device disk3 [for new proms]
765 If you build backwards-compatible filesystems, either with the SunOS
766 newfs or with the \*(4B ``\-O'' option, you can mount these under
769 superblock fields that are updated in \*(4B. Running ``fsck \-b32''
777 # rcp sunos-host:/etc/ld.so.cache /etc/
778 # rcp sunos-host:'/usr/lib/*.so*' /usr/lib/
796 SCSI-I (tested RZ23, RZ55, RZ57, Maxtor 8760S).
800 SCSI-I (tested DEC TK50, Archive DAT, Emulex MT02).
808 TURBOchannel PMAD-AA and internal LANCE based interfaces.
814 TURBOchannel PMAG-AA, PMAG-BA, PMAG-DV.
822 Battery-backed real time clock,
823 internal and TURBOchannel PMAZ-AA SCSI interfaces.
846 B) kernel.tape: \fIdd\fP image for creating boot tapes
870 This system is now ready to boot. You can boot the kernel with one of the
875 DEC 3100: boot \-f rz(0,0,0)kernel
876 DEC 5000: boot 5/rz0/kernel
885 kernel and mini-root from tape or the network, and using it to restore
888 First, you will need to create a boot tape. This can be done using
898 The first file on the boot tape contains a boot header, kernel, and
899 mini-root filesystem that the PROM can copy into memory.
902 PROM commands to boot from tape.
905 DEC 3100: boot \-f tz(0,5,0) m # 5 is the SCSI id of the TK50
906 DEC 5000: boot 5/tz6 m # 6 is the SCSI id of the TK50
909 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
918 Here are two example PROM commands to boot across the net:
921 DEC 3100: boot \-f tftp()kernel.net m
922 DEC 5000: boot 6/tftp/kernel.net m
924 This command should load the kernel and mini-root into memory and
933 # mount \-uw /
939 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
942 There are five steps to create a disk-based root filesystem.
947 # disklabel -W /dev/rrz?c # This enables writing the label
948 # disklabel -w -r -B /dev/rrz?c $DISKTYPE
960 # mount \-uw /
968 # mt \-f /dev/nrmt0 rew
969 # restore \-xsf 2 /dev/rmt0
978 When the restore finishes, clean up with:
987 Reset the system and initialize the PROM monitor to boot automatically.
990 DEC 3100: setenv bootpath boot \-f rz(0,?,0)kernel
991 DEC 5000: setenv bootpath 5/rz?/kernel -a
1005 cfb0 raw interface to TURBOchannel PMAG-BA color frame buffer
1014 All architectures now have a root filesystem up and running and
1020 Each physical disk drive can be divided into up to 8 partitions;
1056 disk sizes are always reported in units of 512-byte sectors\**.
1059 requiring that 512-byte blocks be the units that programs report.
1080 large enough to accommodate most high-water marks.
1083 is constructed from a memory-based filesystem (see
1088 If you plan to use a disk-based
1234 filesystem will result in 4-8% more space being
1254 normal users (i.e. anyone but the super-user) attempt to allocate
1265 physical sector size of the disk. As an example, the HP magneto-optical
1269 Note that the above discussion considers block sizes of up to only 8k.
1319 This is the organization used if you loaded the disk-image root filesystem.
1320 With the addition of a memory-based
1328 /dev/\*(Dk0b /tmp mfs rw,-s=14000,-b=8192,-f=1024,-T=sd660 0 0
1355 directory is a memory-based filesystem.
1370 /dev/\*(Dk0b /tmp mfs rw,-s=14000,-b=8192,-f=1024,-T=sd660 0 0
1381 \fB#\fP \fIdisklabel -wr \*(Dk1 "disk type" "disk name"\fP
1391 At a minimum you need to set up the
1402 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP
1408 \fB#\fP \fIrsh foo mt -f /dev/nr\*(Mt0 fsf\fP
1409 \fB#\fP \fIrsh foo dd if=/dev/nr\*(Mt0 bs=\*(Bzb | tar xbpf \*(Bz -\fP
1422 and the ``my.domain'' fields are the names of your machine and the tape-hosting
1424 See sections 4.4 and 5 for more information on setting up the network.
1435 \fB#\fP \fImount \-uw /dev/\*(Dk#a /\fP (read-write mount root filesystem)
1438 \fB#\fP \fIpasswd -l root\fP (set password for super-user)
1441 \fB#\fP \fIpasswd -l toor\fP (set password for super-user)
1450 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1458 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1460 (this takes about 15-20 minutes)
1463 \fB#\fP \fIrm -r /usr/*\fP (remove excess bootstrap binaries)
1477 \fB#\fP \fImt -f /dev/nr\*(Mt0 rew\fP
1478 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf 1\fP
1489 requires about 250-340Mb of space.
1509 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1512 (this takes about 15-30 minutes)
1522 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1524 (this takes about 30-60 minutes)
1539 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1542 (this takes about 30-60 minutes)
1557 \fB#\fP \fImt -f /dev/nr\*(Mt0 fsf\fP (space to end of previous tape file)
1559 (this takes about 30-60 minutes)
1589 ** Phase 1 - Check Blocks and Sizes
1590 ** Phase 2 - Check Pathnames
1591 ** Phase 3 - Check Connectivity
1592 ** Phase 4 - Check Reference Counts
1593 ** Phase 5 - Check Cyl groups
1617 After setting up the new \*(4B filesystems, you may restore the user
1638 be sure to use its `\-p' option when reading the files back. No matter