Oracle Solaris 9：文件格式（Section 4）详解

需积分: 5 84 浏览量更新于2024-06-22 收藏 2.13MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

Oracle Solaris 9 的第 4 部分（man pages）专门介绍了文件格式的相关信息，这是 Sun Microsystems, Inc. 为其操作系统提供的一系列技术文档的一部分。这部分文档详细记录了系统中不同类型的文件结构、标准和规范，旨在帮助管理员和开发者理解如何正确处理和解析这些文件。在 Oracle Solaris 9 的文档集中，第 4 部分（man pages）的 4: File Formats-746 节主要涵盖了以下几个关键知识点： 1. **文件类型与分类**：这部分可能包括了系统中常见的文件类型，如文本文件、二进制文件、设备文件、特殊文件（如管道、命名管道、套接字等）以及网络相关的文件格式，如配置文件、日志文件、数据库文件等。每个文件类型的特点、用途和访问权限都会被详细解释。 2. **文件结构与标准**：Oracle Solaris 9 使用特定的文件系统，如 UFS（Ultra Fast File System），可能涉及到文件头信息、inode结构、磁盘布局等细节。这有助于用户理解文件在存储层面上的组织方式和数据的物理定位。 3. **文件格式解析**：针对某些特定的文件格式，例如配置文件（如 ini 文件、XML 或 JSON），可能会有章节解释如何解析这些格式，包括语法规则、属性解析和错误处理策略。 4. **文件系统特性**：Oracle Solaris 9 可能还涵盖了文件系统的高级特性和优化，如压缩文件、硬链接、符号链接、ACLs（访问控制列表）以及安全相关设置等。 5. **兼容性与历史**：考虑到 Solaris 可能基于 Berkeley BSD 系统，文档可能会提及与 BSD 文件格式的继承关系和差异，以及 Solaris 对其他开放源代码项目的贡献。 6. **版权与许可**：文档强调了所有内容的版权保护，并提醒用户在复制、分发或解构产品文档时必须获得 Sun Microsystems 和其供应商的书面授权。此外，文档中还会提到使用的第三方软件和版权许可情况。 7. **商标与标识**：最后，文档明确了哪些是 Sun Microsystems 的商标，以及 UNIX、SPARC 等品牌的注册状态和许可使用情况。 Oracle Solaris 9 的 man pages section 4: File Formats-746 是一个重要的参考资料，它为 IT 管理者和开发人员提供了关于文件系统操作、文件格式理解和管理的深入指南，确保他们能够高效地维护和扩展 Oracle Solaris 9 的系统环境。

资源详情

资源推荐

Intro – introduction to ﬁle formats

This section outlines the formats of various ﬁles. The C structure declarations for the

ﬁle formats are given where applicable. Usually, the headers containing these structure

declarations can be found in the directories /usr/include or /usr/include/sys.

For inclusion in C language programs, however, the syntax #include <ﬁlename.h>or

#include <sys/ﬁlename.h> should be used.

Intro(4)

NAME

DESCRIPTION

16 man pages section 4: File Formats • Last Revised 16 Apr 2003

admin – installation defaults ﬁle

admin is a generic name for an ASCII ﬁle that deﬁnes default installation actions by

assigning values to installation parameters. For example, it allows administrators to

deﬁne how to proceed when the package being installed already exists on the system.

/var/sadm/install/admin/default is the default admin ﬁle delivered with this

release. The default ﬁle is not writable, so to assign values different from this ﬁle,

create a new admin ﬁle. There are no naming restrictions for admin ﬁles. Name the

ﬁle when installing a package with the -a option of pkgadd(1M). If the -a option is

not used, the default admin ﬁle is used.

Each entry in the admin ﬁle is a line that establishes the value of a parameter in the

following form:

param=value

All of the parameters listed below can be deﬁned in an admin ﬁle, but it is not

required to assign values to all of these. If a value is not assigned, pkgadd(1M) asks

the installer how to proceed.

The valid parameters and their possible values are shown below except as noted. They

can be speciﬁed in any order. Any of these parameters (except the mail and proxy

parameters) can be assigned the value ask, which means that, when the parameter is

reached during the installation sequence, the installer is notiﬁed and asked to supply

instructions (see NOTES).

basedir

Indicates the base directory where relocatable packages are to be installed. If there

is no basedir entry in the ﬁle, the installer will be prompted for a path name, as if

the ﬁle contained the entry basedir=ask. This parameter can also be set to

default (entry is basedir=default). In this instance, the package is installed

into the base directory speciﬁed by the BASEDIR parameter in the pkginfo(4) ﬁle.

mail

Deﬁnes a list of users to whom mail should be sent following installation of a

package. If the list is empty, no mail is sent. If the parameter is not present in the

admin ﬁle, the default value of root is used. The ask value cannot be used with

this parameter.

runlevel

Indicates resolution if the run level is not correct for the installation or removal of a

package. Options are:

nocheck Do not check for run level.

quit Abort installation if run level is not met.

conflict

Speciﬁes what to do if an installation expects to overwrite a previously installed

ﬁle, thus creating a conﬂict between packages. Options are:

admin(4)

NAME

DESCRIPTION

18 man pages section 4: File Formats • Last Revised 2 Sep 2003

nocheck Do not check package dependencies.

quit Abort installation if package dependencies are not met.

rdepend

Controls resolution if other packages depend on the one to be removed. Options

are:

nocheck Do not check package dependencies.

quit Abort removal if package dependencies are not met.

space

Controls resolution if disk space requirements for package are not met. Options are:

nocheck Do not check space requirements (installation fails if it runs out

of space).

quit Abort installation if space requirements are not met.

authentication

Controls resolution when a datastream package with signature is to be installed.

Options are:

nocheck Do not verify package signature. This also disables the use of

the Online Certiﬁcate Status Protocol (OCSP) to validate the

package’s signing certiﬁcate.

quit Abort installation if package signature cannot be veriﬁed.

networktimeout

Number of seconds to wait before giving up a network connection when

downloading a package. This entry must be a positive integer. If not present, the

default value of 60 is used.

networkretries

Number of times to retry a failed network connection when downloading a

package. This entry must be a positive integer. If not present, the default value of 5

is used.

keystore

Location of trusted certiﬁcates used when downloading packages over SSL and

when verifying signatures on packages. This is the base directory of the certiﬁcate

location for trusted certiﬁcates used when validating digital signatures on

packages. For example, if this setting is /var/sadm/security, then pkgadd will

use /var/sadm/security/pkgadd/truststore, then

/var/sadm/security/truststore when searching for trusted certiﬁcates. See

KEYSTORE LOCATIONS and KEYSTORE AND CERTIFICATE FORMATS in

pkgadd(1M) for details on certiﬁcate store format and usage.

proxy

The default proxy to use when installing packages from the network. Currently,

only HTTP or HTTPS proxies are supported. If this ﬁeld is blank or nonexistent,

then no proxy will be used.

admin(4)

20 man pages section 4: File Formats • Last Revised 2 Sep 2003

剩余745页未读，继续阅读

weixin_40191861_zj

粉丝: 69
资源: 1万+

会员权益专享

Oracle Solaris 9：文件格式（Section 4）详解

Oracle Solaris 9 - man pages section 4: File Formats-732

Oracle Solaris 9 -man pages section 4: File Formats-698

C#怎么判断一个字符串是yyyyMMddHHmmss 还是yyyy-MM-dd 还是yyyy-MM-dd HH:mm:ss、还是yyyy年MM月dd日 HH:mm:ss、还是yyyy-MM-ddTHH:mm:ss.fffffffzzz

@JsonDeserialize(using = DateDeserializer.class) 能动态转换yyyy-MM-dd HH:mm:ss或者yyyy-MM-dd吗？

在ts中使用ajv,在properties中的dataTime满足以下校验条件:（1）必填字段 （2）时间格式不正确，格式为【yyyy-MM-dd hh:mm:ss】 （3）结束时间必须大于开始时间

exceljs.min.js 日期格式

typeorm-ts-node-commonjs migration:generate的完整指令

v4l2-ctl --list-formats-ext -d /dev/video0 ioctl: VIDIOC_ENUM_FMT Type: Video Capture Multiplanar [0]: 'BGR3' (24-bit BGR 8-8-8) [1]: 'NV24' (Y/CbCr 4:4:4) [2]: 'NV16' (Y/CbCr 4:2:2) [3]: 'NV12' (Y/CbCr 4:2:0)

<style scoped lang="scss"> // 调整样式 :deep(.ql-editor) { min-height: 180px; } :deep(.ql-formats) { height: 21px; line-height: 21px; } </style>

python date format

play FAIL formats: can t open input file `*.mp3 : No such file or directory怎么解决

k8s yml --help

react-quill 为什么文字颜色不生效

quill-editor自定义行间距

会员权益专享

最新资源

在ts中使用ajv,在properties中的dataTime满足以下校验条件:（1）必填字段（2）时间格式不正确，格式为【yyyy-MM-dd hh:mm:ss】（3）结束时间必须大于开始时间