This section highlights updates and changes that relate to filesystems, filesystem commands, and disk configuration:
SCO OpenServer Release 6.0.0 provides support for the following filesystems:
All of the filesystem types supported on SCO OpenServer Release 6.0.0 offer the following enhancements:
Available for the first time on SCO OpenServer, the VERITAS VxFS (vxfs) filesystem type is the default Release 6 root filesystem, offering high performance, journaling, and large file support.
Highlights of this filesystem include:
See ``VERITAS filesystem (VxFS) documentation overview'' for more information.
Note the following about vxfs support:
The HTFS driver has been ported to the SVR5 kernel for this release. It also provides support for the EAFS, AFS, S51K, and ES51K filesystem types. Note the following:
Because there is no versioning support, the maxvdepth and minvtime options to mount(ADM) are ignored for HTFS filesystems.
See ``Filesystem mount options (HTFS, EAFS, AFS, S51K)'' for more information.
The /stand filesystem is now always mounted read/write. All of the SCO OpenServer Release 6.0.0 idtools expect to find /stand mounted in this manner.
The cdfs filesystem replaces the SCO OpenServer Release 5 High Sierra (HS) filesystem, providing the same support for the underlying ISO9660 format, plus the UNIX RockRidge (RCKRDG) extension. In addition, SCO OpenServer Release 6.0.0 now supports the JOLIET extension of Windows 95 (and later Microsoft Windows family operating systems).
Two new mount options have been added to the mount(ADM) command for cdfs: joliet and nojoliet. By default, mount first attempts to mount a CD-ROM with RockRidge extensions. If that fails, it attempts to mount the CD-ROM with JOLIET extensions if they exist on the CD-ROM. See the mount_cdfs(ADM) manual page for more information.
Note that all of the SCO OpenServer Release 5 CD-ROM filesystem types can still be used with SCO OpenServer Release 6.0.0 filesystem commands.
See ``cdfs advanced mount options'' for more information.
The dosfs filesystem replaces the SCO OpenServer Release 5 DOS filesystem. The existing versions of the DOS filesystem type (FAT12 and FAT16) are still supported. Additionally, there is now support for the FAT32 and VFAT (``Extended FAT'', offering support for long filenames) filesystem types.
Note the following:
See ``Managing the dosfs filesystem'' for more information.
In previous releases, /tmp and /var/tmp are regular directories, and their contents remain there until explicitly deleted (done, by default, once a week via a cron job). In this release, you can select memfs, a volatile in-memory filesystem, as the filesystem type for /tmp and /var/tmp. While memfs provides the highest possible system performance, the volatile nature of memfs may not be expected by applications, utilities, or features that depend on a non-volatile /tmp or /var/tmp.
For example: the vi program crash recovery mechanism relies on its memory files existing in /tmp. If you are editing a file when the machine suddenly reboots (e.g., panic or power failure), your edit buffer is recoverable. If /tmp is memfs, this does not work. As a workaround, individual users can set the "directory" directive in the .exrc file -- see the vi(C) manual page for details. (Note that a volatile /tmp does not affect the vi preserve mechanism, which preserves the edited version of a file when the user's shell quits unexpectedly.)
See ``Managing the memfs filesystem'' for more information.
Filesystem encryption has been added to the marry(ADM) driver. Using the marry(ADM) command, an empty regular file is associated with a block special device name, and encryption is enabled on the file. After a filesystem is created on the block special device and mounted, all data written to the file is encrypted using the 128-bit Advanced Encryption Standard (also known as 128-bit AES and the Rijndael block cipher); all data read from the file is decrypted.
See ``Encrypting filesystems'' and the marry(ADM) manual page for more information.
To fix this problem:
Add ``.html'' to the end of this line, then save and exit the file.
The ``Encrypting filesystems'' topic is now available from the Filesystems category in the online documentation.
This section describes enhancements and changes that have been made to the following disk configuration and filesystem commands:
|These commands have been removed. All bad block operations are now handled transparently by the system.|
This command has been updated to add more HTFS
filesystem support. Specifically, a new htinode
command prints the inode table for the
HTFS, EAFS, AFS, and S51K
filesystems. Use the -i option, together with the
-e option, to print inactive inodes. The
-e option alone prints only active inodes.
Use -l to display the free lists. Specific inodes
can be specified by the address in kernel memory, or by inode
number. However, if inode number is used, then inodes might
be found in more than one filesystem. In that case, all of
those found are printed.
The inode command is no longer applicable on SCO OpenServer Release 6.0.0.
This command now supports up to 15 user-defined divisions on any
partition. On the active/boot partition:
-- Division 0 is the /dev/stand filesystem
-- Division 1 is the swap/dump area
-- Division 2 is the /dev/root filesystem
-- Division 7 is the whole partition
-- Division 13 is used by the boot loader
To ensure that the divvy table fits on the screen, unused divisions above division 8 are not displayed. The unlisted divisions are, however, available for use.
|The Virtual Disk Manager (VDISK) is not provided in SCO OpenServer Release 6.0.0. All related commands have been removed from the system.|
This command has been removed.
All hard disk parameters in use reflect the values
used by the system BIOS. In SCO OpenServer Release 6.0.0,
there is no way to change or override hard disk parameters.
To write to the masterboot block, run fdisk(ADM) and select Option 0, Overwrite system master boot code.
|fdisk(ADM)||The -a, -c, -d, -t, and -V options are no longer necessary or supported. The -f option does not need to be specified anymore because the raw device associated with the boot hard disk is automatically specified.|
|fsdb_vxfs(ADM)||The -z option can only be used with /u95/bin/fsdb. /etc/fsdb does not pass the -z option through to /etc/fscmd.d/vxfs/fsdb. See the fsdb_vxfs(ADM) manual page for more information.|
The hwconfig(C) command is obsolete and no longer
provided in SCO OpenServer Release 6.0.0. Use the
A new version of the hw(ADM) command is provided. It has the same options as the hw command available in earlier releases and serves the same purpose, but produces somewhat different output in a somewhat different format. It also numbers processors from "0", rather than from "1" as in the old command.
|mount(ADM)||The spongy and tcp NFS mount options are no longer supported.|
When the parallel fsck command,
is run, it produces the following messages:
/etc/p_fsck: don't understand extended major (50, 3) /etc/p_fsck: don't understand extended major (50, 4) /etc/p_fsck: don't understand extended major (50, 5) /etc/p_fsck: don't understand extended major (50, 2)These messages can be ignored.
|/dev/string devices||The /dev/string devices are no longer part of the system. Similar system information can be viewed using the resmgr(ADM) and dcu(ADM) commands.|
SCO OpenServer Release 6.0.0 includes the /etc/vfstab file but
this file is not the standard SVR5 table of filesystem defaults
that you might be familiar with. Rather, it is a symlink to
the standard SCO OpenServer /etc/default/filesys file.
There are still places in the online documentation and manual pages that refer to the vfstab file. In all these cases, please refer to the /etc/default/filesys file instead. The SVR5-format version of vfstab is not included in SCO OpenServer Release 6.0.0.