Lines Matching +full:block +full:- +full:copy

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),
241 Copy a root filesystem from the
262 Note that an HP SCSI magneto-optical disk will work fine for this case.
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
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
290 An example command to copy the image from tape to the beginning of a disk is:
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.
305 Any machine and operating system that will allow you to copy the
306 raw disk image out to block 0 of the disk will do.
310 HP-IB cartridge tape drive.
312 standalone copy program from the tape, and using that to copy the
315 (the root image), copy it over to a machine with a cartridge drive
316 and then copy the image onto tape.
326 copy program from it.
327 The copy program is loaded just as any other program would be loaded
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)
342 \fBCopy completed: 1728 records copied\fP
346 This copy will likely take 30 minutes or more.
352 the HP-UX drive.
354 destroying the HP-UX disk.
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
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
529 In the latter, some of the partitions may map non-existent sectors
553 \fB#\fP \fIdisklabel -r -e /dev/r\fBXX#\fPd
565 \fB#\|\fP\fIdisklabel -rw \fBXX# type\fP \fI"optional_pack_name"\fP
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,
643 Sun-supplied boot loader will be used to boot \*(4B; you must copy
698 You can build an old-format filesystem on \*(4B by giving the \-O
710 you must build an old-style root filesystem
714 Mount the new root, then copy the SunOS
717 to enable disk-based booting.
744 ok boot sd(0,3)kernel -s [for old proms] OR
745 ok boot disk3 -s [for new proms]
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''
773 simply need to copy all the dynamic linker files from an existing
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.
855 .Sh 4 "Procedure A: copy root filesystem to disk"
859 under ULTRIX to copy the root filesystem image to the beginning
863 An example command to copy the image to the beginning of a disk is:
875 DEC 3100: boot \-f rz(0,0,0)kernel
885 kernel and mini-root from tape or the network, and using it to restore
899 mini-root filesystem that the PROM can copy into memory.
905 DEC 3100: boot \-f tz(0,5,0) m # 5 is the SCSI id of the TK50
909 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
921 DEC 3100: boot \-f 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
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
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
1159 Each filesystem is parameterized according to its block size,
1170 Filesystem Block size Fragment size
1178 The root filesystem block size is
1180 The large block size is important as many of the most
1189 The filesystems for users have a 4 kbyte block
1193 block size provides adequate bandwidth while the
1198 but the factors involved in choosing a block
1200 ways. Larger block sizes result in better
1208 12 direct block pointers, 1 single indirect block
1209 pointer, 1 double indirect block pointer,
1210 and 1 triple indirect block pointer.
1212 it will be optimized by maximizing the block size.
1213 If a file spills over into an indirect block,
1214 increasing the block size of the filesystem may
1216 by eliminating the need to allocate an indirect block.
1217 However, if the block size is increased and an indirect
1218 block is still required, then more disk space will be
1220 according to the block size of the filesystem.
1224 tradeoffs observed are between an 8 kbyte block filesystem
1225 and a 4 kbyte block filesystem. Because of implementation
1226 constraints, the block size versus fragment size ratio can not
1229 a filesystem is created with a 4 kbyte block size and a
1230 1 kbyte fragment size, then upgraded to an 8 kbyte block size
1232 observed. However, if a filesystem has a 4 kbyte block size
1234 filesystem will result in 4-8% more space being
1235 used. This implies that 4 kbyte block filesystems that
1242 on the disk. With an 8:1 fragment to block ratio, storage fragmentation
1245 4:1 fragment to block ratio filesystem is one tenth as severe. This
1253 block specifies a minimum acceptable free space threshold. When
1254 normal users (i.e. anyone but the super-user) attempt to allocate
1260 or by updating the super block of an existing filesystem using
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.
1270 As of the 4.4 release, the maximum block size has been increased to 64k.
1271 This allows an entirely new set of block/fragment combinations for which
1278 implementation limits the block size to at most 64 kbytes
1279 and the ratio of block size versus fragment size must be 1, 2, 4, or 8.
1282 affects the block layout policies employed. The file
1298 sizes, and default block and fragment sizes. To
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
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
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
1638 be sure to use its `\-p' option when reading the files back. No matter