Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #333
Difficulty: Easy
Linux was first developed as an alternative to Windows XP.
True or False?
Linux & Unix Commands - Search Man Pages

hotswaprc(5) [debian man page]

HOTSWAPRC(5)							File Formats Manual						      HOTSWAPRC(5)

NAME
hotswaprc - configuration file for hotswap DESCRIPTION
/etc/hotswaprc is the global configuration file for the hotswap utility. It allows system administrators to specify arbitrary shell scripts to be run after a device is inserted, as well as before and after it is removed. Scripts are selected according to the model name retrieved from the device. This is particularly helpful for automatic configura- tion of CD-RW drives, which require SCSI emulation and bypass normal access via the IDE subsystem. hotswaprc is implemented as an Extensible Mark-up Language (XML) application. XML documents are structured using elements of the form <tag-name> content <tag-name>. A Document Type Definition (DTD) describes the possible content of each element. Please refer to the XML specification for more information. The hotswap distribution also contains an example file, doc/hotswaprc.example, which includes the DTD for the configuration file format. ELEMENTS
<hotswap> This is the root element of the document. Each valid hotswaprc must contain exactly one <hotswap> element. The <hotswap> element may contain an arbitrary number of <device> elements. <device> The configuration file contains one <device> element for every device for which scripts are defined. The <device> element is com- posed of the following elements in this order: <name>, <post-insert>, <pre-remove>, <post-remove>. All but <name> are optional. <name> The content of this element is the model identification string of the IDE device the current <device> element refers to. <post-insert> Contains the shell script that is to be executed after the device has been inserted and registered with the kernel. <pre-remove> Contains the shell script that is to be run before hotswap attempts to unregister the device. <post-remove> Contains the shell script that is to be run after the device had been unregistered. REPORT BUGS
Report bugs to t.stadelmann1@physics.ox.ac.uk. AUTHOR
Written by Tim Stadelmann. SEE ALSO
hotswap(1), xhotswap(1). COPYRIGHT
Copyright (c) 2002-2003 Tim Stadelmann. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License (GPL), Version 2 or any later version published by the Free Software Foundation. 26th November 2002 HOTSWAPRC(5)

Check Out this Related Man Page

LaTeXML::Model(3pm)					User Contributed Perl Documentation				       LaTeXML::Model(3pm)

NAME
"LaTeXML::Model" - represents the Document Model DESCRIPTION
"LaTeXML::Model" encapsulates information about the document model to be used in converting a digested document into XML by the LaTeXML::Document. This information is based on the document schema (eg, DTD, RelaxNG), but is also modified by package modules; thus the model may not be complete until digestion is completed. The kinds of information that is relevant is not only the content model (what each element can contain contain), but also SGML-like information such as whether an element can be implicitly opened or closed, if needed to insert a new element into the document. Currently, only an approximation to the schema is understood and used. For example, we only record that certain elements can appear within another; we don't preserve any information about required order or number of instances. Model Creation "$model = LaTeXML::Model->new(%options);" Creates a new model. The only useful option is "permissive=>1" which ignores any DTD and allows the document to be built without following any particular content model. Document Type "$model->setDocType($rootname,$publicid,$systemid,%namespaces);" Declares the expected rootelement, the public and system ID's of the document type to be used in the final document. The hash %namespaces specifies the namespace prefixes that are expected to be found in the DTD, along with the associated namespace URI. These prefixes may be different from the prefixes used in implementation code (eg. in ltxml files; see RegisterNamespace). The generated document will use the namespaces and prefixes defined here. Namespaces Note that there are two namespace mappings between namespace URIs and prefixes that are relevant to LaTeXML. The `code' mapping is the one used in code implementing packages, and in particular, constructors defined within those packages. The prefix "ltx" is used consistently to refer to LaTeXML's own namespace ("http://dlmf.nist.gov/LaTeXML)". The other mapping, the `document' mapping, is used in the created document; this may be different from the `code' mapping in order to accommodate DTDs, for example, or for use by other applications that expect a rigid namespace mapping. "$model->registerNamespace($prefix,$namespace_url);" Register $prefix to stand for the namespace $namespace_url. This prefix can then be used to create nodes in constructors and Document methods. It will also be recognized in XPath expressions. "$model->getNamespacePrefix($namespace);" Return the prefix to use for the given $namespace. "$model->getNamespace($prefix);" Return the namespace url for the given $prefix. Model queries "$boole = $model->canContain($tag,$childtag);" Returns whether an element with qualified name $tag can contain an element with qualified name $childtag. The tag names #PCDATA, #Document, #Comment and #ProcessingInstruction are specially recognized. "$auto = $model->canContainIndirect($tag,$childtag);" Checks whether an element with qualified name $tag could contain an element with qualified name $childtag, provided an `autoOpen'able element $auto were inserted in $tag. "$boole = $model->canContainSomehow($tag,$childtag);" Returns whether an element with qualified name $tag could contain an element with qualified name $childtag, either directly or indirectly. "$boole = $model->canAutoClose($tag);" Returns whether an element with qualified name $tag is allowed to be closed automatically, if needed. "$boole = $model->canHaveAttribute($tag,$attribute);" Returns whether an element with qualified name $tag is allowed to have an attribute with the given name. Tag Properties "$value = $model->getTagProperty($tag,$property);" Gets the value of the $property associated with the qualified name $tag Known properties are: autoOpen : This asserts that the tag is allowed to be opened automatically if needed to insert some other element. If not set, the tag can only be opened explicitly. autoClose : This asserts that the $tag is allowed to be closed automatically if needed to insert some other element. If not set, the tag can only be closed explicitly. afterOpen : supplies code to be executed whenever an element of this type is opened. It is called with the created node and the responsible digested object as arguments. afterClose : supplies code to be executed whenever an element of this type is closed. It is called with the created node and the responsible digested object as arguments. "$model->setTagProperty($tag,$property,$value);" sets the value of the $property associated with the qualified name $tag to $value. Rewrite Rules "$model->addRewriteRule($mode,@specs);" Install a new rewrite rule with the given @specs to be used in $mode (being either "math" or "text"). See LaTeXML::Rewrite for a description of the specifications. "$model->applyRewrites($document,$node,$until_rule);" Apply all matching rewrite rules to $node in the given document. If $until_rule is define, apply all those rules that were defined before it, otherwise, all rules AUTHOR
Bruce Miller <bruce.miller@nist.gov> COPYRIGHT
Public domain software, produced as part of work done by the United States Government & not subject to copyright in the US. perl v5.10.1 2009-06-11 LaTeXML::Model(3pm)

Featured Tech Videos