Lines Matching full:filesystem

77 (SPARC) image of the root filesystem
83 filesystem
89 filesystem
116 Transfer a bootable root filesystem from the tape to a disk
241 Copy a root filesystem from the
246 (Optional) Build a root filesystem optimized for your disk.
282 .Sh 4 "Step 2: copying the root filesystem from tape to disk"
286 command under HP-UX to copy the root filesystem image from
288 For HP's, the root filesystem image is the first file on the tape.
289 It includes a disklabel and bootblock along with the root filesystem.
313 root filesystem image from the tape to the disk.
347 .Sh 4 "Step 3: booting the root filesystem"
349 You now have a bootable root filesystem on the disk.
431 to ask you for the name of the root filesystem to use.
451 \fBWARNING: preposterous time in filesystem \-\- CHECK AND RESET THE DATE!\fP
467 At this point, the root filesystem is mounted read-only.
468 Before continuing the installation, the filesystem needs to be ``updated''
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)
481 .Sh 4 "Step 4: (optional) restoring the root filesystem"
483 The root filesystem that you are currently running on is complete,
488 this machine, and build and restore a properly laid out root filesystem
499 To really create the root filesystem on drive 1
532 the filesystem code resulting in reduced performance.
665 boot, swap, and root filesystem.
685 Note that the root filesystem currently requires at least 10 MB; 16 MB
691 to build the root filesystem.  You may also
695 builds a filesystem that SunOS will not handle; if you
697 performance gain from the new filesystem format for compatibility.)
698 You can build an old-format filesystem on \*(4B by giving the \-O
710 you must build an old-style root filesystem
718 Note that the filesystem must be mounted when you do the ``installboot'':
731 does not handle the new \*(4B filesystem format.
733 Restore the contents of the \*(4B root filesystem.
757 After completing the filesystem installation you may want
845 A) root.image: \fIdd\fP image of the root filesystem
848 D) root.dump: \fIdump\fP image of the root filesystem
855 .Sh 4 "Procedure A: copy root filesystem to disk"
859 under ULTRIX to copy the root filesystem image to the beginning
861 The root filesystem image includes a disklabel and bootblock along with the
862 root filesystem.
886 the root filesystem.
899 mini-root filesystem that the PROM can copy into memory.
908 The `m' argument tells the kernel to look for a root filesystem in memory.
909 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
939 Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
940 .Sh 3 "Label disk and create the root filesystem"
942 There are five steps to create a disk-based root filesystem.
957 Restore the root filesystem.
1014 All architectures now have a root filesystem up and running and
1023 is used for a root filesystem, a backup thereof,
1024 or a small filesystem like,
1029 holds a user filesystem.
1033 and a root filesystem of about 17 megabytes.
1040 filesystem as delivered on the tape is only 2Mb,
1046 filesystem.
1050 measured in disk sectors (usually 512 bytes), while the UNIX filesystem
1079 directory, so the filesystem where this is stored also should be made
1083 is constructed from a memory-based filesystem (see
1090 filesystem to avoid loss across system reboots, it makes
1092 filesystem on another disk.
1106 The root filesystem.
1116 filesystem.
1146 Intelligent experimentation with a few filesystem arrangements can
1157 .Sh 3 "Filesystem parameters"
1159 Each filesystem is parameterized according to its block size,
1162 characteristics or haphazard choice of the filesystem parameters
1170 Filesystem	Block size	Fragment size
1178 The root filesystem block size is
1185 with a filesystem.  With a 1 kbyte fragment size
1187 as with the earlier versions of the filesystem.
1201 throughput to large files in the filesystem as
1205 found in the filesystem and the performance of the
1214 increasing the block size of the filesystem may
1220 according to the block size of the filesystem.
1222 In selecting a fragment size for a filesystem, at least
1224 tradeoffs observed are between an 8 kbyte block filesystem
1225 and a 4 kbyte block filesystem.  Because of implementation
1227 be greater than 8.  This means that an 8 kbyte filesystem
1229 a filesystem is created with a 4 kbyte block size and a
1232 observed.  However, if a filesystem has a 4 kbyte block size
1234 filesystem will result in 4-8% more space being
1241 fragment size for a filesystem is the level of fragmentation
1243 occurs much sooner, particularly with a busy filesystem running
1245 4:1 fragment to block ratio filesystem is one tenth as severe.  This
1248 space exhaustion because of fragmentation.  That is, when the filesystem
1251 byte filesystem than on a 1 kbyte filesystem.  To minimize
1256 returned an error as if the filesystem were really full.  This
1260 or by updating the super block of an existing filesystem using
1273 In general though, unless a filesystem is to be used
1281 The disk geometry information used by the filesystem
1286 a filesystem with
1291 specify the type of disk on which the filesystem resides;
1297 filesystem partition
1307 command to create each new filesystem.
1308 Each filesystem must also be added to the file
1314 the root filesystem goes in the ``a'' partition,
1319 This is the organization used if you loaded the disk-image root filesystem.
1322 filesystem, its fstab entry would be as follows:
1341 and the \*(Dk1a partition left as a spare root filesystem
1345 the root filesystem in \*(Dk0a, and the primary swap area in \*(Dk0b.
1355 directory is a memory-based filesystem.
1379 filesystem we would do:
1383 (information about filesystem prints out)
1435 \fB#\fP \fImount \-uw /dev/\*(Dk#a /\fP	(read-write mount root filesystem)
1445 \fB#\fP \fInewfs r\*(Dk#p\fP	(create empty user filesystem)
1448 \fB#\fP \fImount /dev/\*(Dk#p /var\fP	(mount the var filesystem)
1453 \fB#\fP \fInewfs r\*(Dk#p\fP	(create empty user filesystem)
1490 Ideally sources should be in a separate filesystem;
1493 filesystem, it will need at least 500Mb of space.
1494 Assuming that you will be using a separate filesystem on \*(Dk0f for
1499 (information about filesystem prints out)
1570 filesystem is consistent.
1598 If there are inconsistencies in the filesystem, you may be prompted
1605 filesystem, you should now remount it with:
1621 program does its work on a mounted filesystem using normal system operations.
1622 This means that filesystem dumps may be restored even
1623 if the characteristics of the filesystem changed.
1626 filesystem something like the following would be used:
1639 how you restore a filesystem, be sure to unmount it and check its