📄 1119-1120.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:File Formats:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=05 //-->
<!-- PAGES=1103-1208 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="1118-1118.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1121-1122.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1119"><P>Page 1119</P></A>
<TABLE>
<TR><TD>
</TD><TD>
in order, the tagname, operation (add for tag, mov for tag -F, and del for tag -d), <BR>
and repository, and any remaining are pairs of filename revision. A nonzero exit <BR>
of the filter program will cause the tag to be aborted. For commitinfo, the rest of <BR>
the line is a command-line template to execute. The template can include not <BR>
only a program name but also whatever list of arguments you want. The full path <BR>
to the current source repository is appended to the template, followed by the <BR>
filenames of any files involved in the commit (added, removed, and modified <BR>
files). For rcsinfo, the rest of the line is the full path to a file that should be<BR>
loaded into the log message template. For editinfo, the rest of the line is a <BR>
command-line template to execute. The template can include not only a <BR>
program name but also whatever list of arguments you want. The full path to the <BR>
current log message template file is appended to the template. You can use one of <BR>
two special strings instead of a regular expression: ALL specifies a command-line <BR>
template that must always be executed, and DEFAULT specifies a command-line <BR>
template to use if no regular expression is a match. The commitinfo file contains <BR>
commands to execute before any other commit activity, to allow you to check <BR>
any conditions that must be satisfied before commit can proceed. The rest of the <BR>
commit will execute only if all selected commands from this file exit with exit <BR>
status 0. The rcsinfo file allows you to specify log templates for the commit <BR>
logging session; you can use this to provide a form to edit when filling out the <BR>
commit log. The field after the regular expression, in this file, contains filenames <BR>
(of files containing the logging forms) rather than command templates. The <BR>
editinfo file allows you to execute a script before the commit starts but after the <BR>
log information is recorded. These "edit" scripts can verify information recorded <BR>
in the log file. If the edit script exits with a nonzero exit status, the commit is <BR>
aborted. The loginfo file contains commands to execute at the end of a commit. <BR>
The text specified as a commit log message is piped through the command; <BR>
typical uses include sending mail, filing an article in a newsgroup, or appending <BR>
to a central file.
</TD></TR><TR><TD>
cvsignore, .cvsignore
</TD><TD>
The default list of files (orsh(1) filename patterns) to ignore during cvs update. <BR>
At startup time, cvs loads the compiled default list of filename patterns (see <BR>
cvs(1)). Then the per-repository list included in $CVSROOT/CVSROOT/cvsignore is <BR>
loaded, if it exists.
</TD></TR><TR><TD>
</TD><TD>
Then the per-user list is loaded from $HOME/.cvsignore. Finally, as cvs traverses <BR>
through your directories, it will load any per-directory .cvsignore files whenever <BR>
it finds one. These per-directory files are only valid for exactly the directory that <BR>
contains them, not for any subdirectories.
</TD></TR><TR><TD>
history
</TD><TD>
Create this file in $CVSROOT/CVSROOT to enable history logging (see the description <BR>
of cvs history).
</TD></TR></TABLE>
<P><B>
SEE ALSO
</B></P>
<P>cvs(1)
<P><B>
COPYING
</B></P>
<P>Copyright <SUP>"</SUP> 1992, Cygnus Support, Brian Berliner, and Jeff Polk.
</P>
<P>Permission is granted to make and distribute verbatim copies of this manual, provided the copyright notice and
this permission notice are preserved on all copies.
</P>
<P>Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim
copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
</P>
<A NAME="PAGENUM-1120"><P>Page 1120</P></A>
<P>Permission is granted to copy and distribute translations of this manual into another language, under the
preceding conditions for modified versions, except that this permission notice may be included in translations approved by the
Free Software Foundation instead of in the original English.
</P>
<P>
12 February 1992
</P>
<H3><A NAME="ch05_ 11">
DEVINFO
</A></H3>
<P>
DEVINFO—Device entry database.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>DEVINFO is a text file that describes all the possible devices for a system. It is used by
MAKEDEV(8) to create special file entries in /dev. It may be named either
/dev/DEVINFO or /etc/devinfo. Information about custom local devices, if any, should be
placed in DEVINFO.local or /etc/devinfo.local, which has the same syntax.
</P>
<P>The file format is free-form. C, C++, and shell comments are understood. There are basically four statements:
</P>
<TABLE>
<TR><TD>
ignore { proc-device... }
</TD><TD>
This causes the specified names to be ignored if found in /proc/devices.
</TD></TR><TR><TD>
batch { device... }
</TD><TD>
This creates a "batch"—a collection of devices that will all be created when the batch is <BR>
invoked. For example, in the standard DEVINFO, "generic" is a batch.
</TD></TR><TR><TD>
block device-spec
</TD><TD>
This defines one or more block devices.
</TD></TR><TR><TD>
char device-spec
</TD><TD>
This defines one or more character devices.
</TD></TR></TABLE>
<P>Here is a sample device-spec:
</P>
<!-- CODE SNIP //-->
<PRE>
(std, 1) {
mem (kmem) : 1
null (public) : 3
core -> "/proc/kcore"
}
</PRE>
<!-- END CODE SNIP //-->
<P>This example defines a group of devices called
std, with major number 1. Running will create all the devices in the
group; running, for example, would make just the one device
null.
</P>
<P>It is possible to specify, instead of just std, something like
std=foo. In this case, the stuff on the right-hand side of the
equals sign specifies a name from /proc/devices, and the major number will be retrieved from there if present. If an entry from
/proc/devices is specified, the explicit major number may be omitted. In this case, if the number is not found in
/proc/devices, attempts to create the device will be rejected.
</P>
<P>Inside the braces is a list of specific devices. The name in parenthesis is the "class"; this is something specified in
MAKEDEV.cfg that determines the ownership and permissions of the special file created. In the preceding example, the device
mem was set to have the class kmem, but null was set to be
public. Ordinarily, you'd define public to be mode 666 but
kmem to be mode 660 and owned by group kmem. The number after the colon is the minor number for this particular device; for instance,
3 for null.
</P>
<P>You may also specify a symbolic link with ->. For instance,
core was made a link to /proc/kcore. Note that names
may contain any characters, but names that contain things other than alphanumerics, dash, and underscore should be put
in double quotes.
</P>
<P>An entire range of devices can be created. You may specify a range of numbers in brackets:
<!-- CODE SNIP //-->
<PRE>
tty[1-8] (tty) : 1
</PRE>
<!-- END CODE SNIP //-->
<P>This creates tty1_tty8 with minor device numbers starting with 1. If you specify the range in hex (prefixed by
0x), the device names will be created numbered in hex, as is normal for
ptys. The range may appear inside the name string, but there
may only be one range.
</P>
<P><CENTER>
<a href="1118-1118.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1121-1122.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -