blob: b3e283f523ef745faad4932fc7b7e84accb0238f [file] [log] [blame]
<?xml version='1.0'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section>
<title>udevstart</title>
<refentry>
<refentryinfo>
<title>udevstart</title>
<date>August 2005</date>
<productname>udev</productname>
</refentryinfo>
<refmeta>
<refentrytitle>udevstart</refentrytitle>
<manvolnum>8</manvolnum>
</refmeta>
<refnamediv>
<refname>udevstart</refname><refpurpose>populate initial device directory</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>udevstart</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1><title>DESCRIPTION</title>
<para>udevstart scans the kernel exported device information available in
sysfs for devices which require a device node to operate and creates the node
using the specified udev rules. udevstart is used to create the initial
device directory after system bootup.</para>
</refsect1>
<refsect1><title>AUTHOR</title>
<para>Written by Harald Hoyer <email>harald@redhat.com</email>.</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><citerefentry>
<refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum>
</citerefentry></para>
</refsect1>
</refentry>
</section>
</article>