1
0
mirror of https://github.com/systemd/systemd.git synced 2025-03-25 18:50:18 +03:00

extras: delete man pages for private udev tools

These are mostly dummy man pages, without real content, some even
outdated. None of these tools are part of any offered public interface,
and they should not pretend to be by offering a man page.
This commit is contained in:
Kay Sievers 2009-06-17 21:57:40 +02:00
parent 0373056e45
commit bcee964977
14 changed files with 0 additions and 250 deletions

View File

@ -10,6 +10,3 @@ ata_id_SOURCES = \
../../libudev/libudev.c \
../../libudev/libudev-list.c \
../../libudev/libudev-util.c
dist_man_MANS = \
ata_id.8

View File

@ -1,28 +0,0 @@
.TH ATA_ID 8 "November 2005" "" "Linux Administrator's Manual"
.SH NAME
ata_id \- udev callout to read product/serial number from ATA drives
.SH SYNOPSIS
.BI ata_id
[\fI--export\fP] \fIblockdevice\fP
.SH "DESCRIPTION"
.B ata_id
is normally called from a udev rule, to provide udev with a unique string and
additional information (uuid, label) for an ATA drive. Udev can use this
information to create symlinks in /dev/disk/by-id and /dev/disk/by-label
to the real device node.
.SH USAGE
.B ata_id
opens the blockdevice node specified at the commandline and prints the
information chosen by the options.
.SH OPTIONS
The following commandline switches are supported to specify what ata_id
should print:
.TP
.BI --export
print all values (instead of only the id)
.RE
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Kay Sievers <kay.sievers@vrfy.org>.

View File

@ -13,6 +13,3 @@ cdrom_id_SOURCES = \
../../libudev/libudev.c \
../../libudev/libudev-list.c \
../../libudev/libudev-util.c
dist_man_MANS = \
cdrom_id.8

View File

@ -1,36 +0,0 @@
.TH CDROM_ID 8 "January 2009" "" "Linux Administrator's Manual"
.SH NAME
cdrom_id \- udev callout to determine the capabilities of optical drives and media
.SH SYNOPSIS
.B cdrom_id
[\fB--export\fP] [\fB--debug\fP] \fIdevice\fP
.br
.B cdrom_id
\fB--help\fP
.SH "DESCRIPTION"
.B cdrom_id
is normally called from a udev rule, to provide udev with the list of
capabilities of a optical drive.
.SH USAGE
.B cdrom_id
opens the device node specified at the commandline and prints the
discovered capabilities.
.SH OPTIONS
The following commandline switches are supported to specify what cdrom_id
should print:
.TP
.B -x, --export
Print all values as environment keys. This is the default at present, so this
option is currently redundant.
.TP
.B -d, --debug
Print a debug trace.
.TP
.B -h, --help
Print usage help.
.RE
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Kay Sievers <kay.sievers@vrfy.org>.

View File

@ -12,6 +12,3 @@ edd_id_SOURCES = \
../../libudev/libudev.c \
../../libudev/libudev-list.c \
../../libudev/libudev-util.c
dist_man_MANS = \
edd_id.8

View File

@ -1,27 +0,0 @@
.TH EDD_ID 8 "November 2005" "" "Linux Administrator's Manual"
.SH NAME
edd_id \- udev callout to identify BIOS disk drives via EDD
.SH SYNOPSIS
.BI edd_id
[\fI--export\fP] \fIblockdevice\fP
.SH "DESCRIPTION"
.B edd_id
is normally called from a udev rule, to provide udev with the edd id for
a BIOS disk drive. Udev can use this information to create symlinks in
/dev/disk/by-id and /dev/disk/by-label to the real device node.
.SH USAGE
.B edd_id
opens the blockdevice node specified at the commandline and prints the
information chosen by the options.
.SH OPTIONS
The following commandline switches are supported to specify what edd_id
should print:
.TP
.BI --export
print all values (instead of only the id)
.RE
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by John Hull <john_hull@dell.com> and Kay Sievers <kay.sievers@vrfy.org>.

View File

@ -20,6 +20,3 @@ create_floppy_devices_SOURCES += \
create_floppy_devices_LDADD = \
$(SELINUX_LIBS)
endif
dist_man_MANS = \
create_floppy_devices.8

View File

@ -1,46 +0,0 @@
.TH CREATE_FLOPPY_DEVICES 8 "January 2009" "" "Linux Administrator's Manual"
.SH NAME
create_floppy_devices \- udev callout to create all possible floppy devices
based on the CMOS type.
.SH SYNOPSIS
create_floppy_devices [\fIoptions\fP] \fIdevice\fP
.SH OPTIONS
Note that no output will be produced unless the \fB-t\fP option is set.
.TP
.B -c
Create nodes.
.TP
.B -d
Print nodes to stdout.
.TP
.BI "-t " type
Set CMOS floppy type. Type numbers are based on the six floppy types specified
in the kernel's drivers/block/floppy.c, as follows.
.TS
lb lb
l l.
Type Device
0 Unknown. (Produces no output.)
1 5 1/4" 360KB PC
2 5 1/4" HD AT
3 3 1/2" DD
4 3 1/2" HD
5 3 1/2" ED
6 Same as 5.
.TE
.TP
.BI "-m " number
Set major number.
.TP
.BI "-U " user
Set user ownership.
.TP
.BI "-G " group
Set group ownership.
.TP
.BI "-M " mode
Set device node mode.
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Hannes Reinecke <hare@suse.de>.

View File

@ -21,6 +21,3 @@ modem_modeswitch_LDADD = \
dist_udevrules_DATA = \
61-option-modem-modeswitch.rules \
61-mobile-action.rules
dist_man_MANS = \
modem-modeswitch.8

View File

@ -1,39 +0,0 @@
.TH MODEM_MODESWITCH 8 "November 2005" "" "Linux Administrator's Manual"
.SH NAME
modem-modeswitch \- udev callout to switch mobile broadband devices to their
intended modem mode
.SH SYNOPSIS
.BI modem-modeswitch
\fI--vendor <vendor id>\fP \fI--product <product id>\fP [\fI--debug\fP]
\fI--type <type>\fP \fI<devpath>\fP
.SH "DESCRIPTION"
.B modem-modeswitch
is normally called from a udev rule, to eject the driver CD that many mobile
broadband devices mount by default, and switch them into modem mode.
.SH USAGE
.B modem-modeswitch
switches the device into modem mode
.SH OPTIONS
The following commandline switches are supported:
.TP
.BI \-\-vendor\ <vid>
the USB vendor ID of the mobile broadband device to switch
.TP
.BI \-\-product\ <pid>
the USB product ID of the mobile broadband device to switch
.TP
.BI \-\-type\ <type>
the type of switch to perform (one of: option-zerocd, mobile-action-8280p)
.TP
.BI \-\-log\ <file>
log verbose debugging information about the switching process
.TP
.BI \-\-debug
print verbose debugging information about the switching process
.RE
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Dan Williams <dcbw@redhat.com> based off code by Peter Henn
<p.henn@option.com>.

View File

@ -11,6 +11,3 @@ path_id_SOURCES = \
../../libudev/libudev-enumerate.c \
../../libudev/libudev-list.c \
../../libudev/libudev-util.c
dist_man_MANS = \
path_id.8

View File

@ -1,15 +0,0 @@
.TH PATH_ID 8 "April 2007" "" "Linux Administrator's Manual"
.SH NAME
path_id \- udev callout to create a device path based unique name
for a device to implement the Linux Persistent Device Naming scheme
.SH SYNOPSIS
path_id <devpath>
.SH "DESCRIPTION"
.B path_id
is normally called from a udev rule, to create a unique name, based on
the device properties along the chain of parent devices. Udev uses this
information to create a persistent symlink to the real device node.
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Hannes Reinecke <hare@suse.de>.

View File

@ -11,6 +11,3 @@ usb_id_SOURCES = \
../../libudev/libudev-util.c \
../../libudev/libudev-device.c \
../../libudev/libudev-enumerate.c
dist_man_MANS = \
usb_id.8

View File

@ -1,38 +0,0 @@
.TH USB_ID 8 "January 2009" "" "Linux Administrator's Manual"
.SH NAME
usb_id \- udev callout to read information from USB devices
.SH SYNOPSIS
.B usb_id
[\fB--usb-info\fP] [\fB--num-info\fP] [\fB--export\fP] [\fB--debug\fP]
.I devpath
.br
.B usb_id --help
.SH "DESCRIPTION"
.B usb_id
is normally called from a udev rule, to provide udev with a unique string and
additional information (uuid, label) for a USB device. Udev can use this
information to create symlinks in /dev to the real device node.
.SH USAGE
.B usb_id \fIdevpath\fP
opens the device node specified at the commandline and prints the
information chosen by the options.
.SH OPTIONS
The following commandline switches are supported to specify what usb_id
should print:
.TP
.B -u, --usb-info
print USB strings instead of, e.g. SCSI strings for a mass storage device
.TP
.B -n, --num-info
print numerical values instead of strings. Implies \fB--usb-info\fP.
.TP
.B -x, --export
print values as environment keys
.TP
.B -h, --help
print usage help
.RE
.SH SEE ALSO
.BR udev (7)
.SH AUTHORS
Developed by Hannes Reinecke <hare@suse.de>.