hal/doc/spec hal-spec.html,1.12,1.13 hal-spec.xml.in,1.11,1.12
David Zeuthen
david at freedesktop.org
Thu Aug 12 07:34:39 PDT 2004
Update of /cvs/hal/hal/doc/spec
In directory pdx:/tmp/cvs-serv5701/doc/spec
Modified Files:
hal-spec.html hal-spec.xml.in
Log Message:
2004-08-12 David Zeuthen <david at fubar.dk>
* doc/spec/hal-spec.xml.in: Rewrite block.no_partitions spec.
Add storage.[serial|firmware_version] which was forgotton.
* hald/linux/block_class_device.c (detect_media): Set to
value of storage.no_partitions_hint to honor the new spec when
creating a volume for media with no partition tables.
* tools/fstab-sync.c: Remove DeviceType datatype; document entries
in Volume datatype.
(udi_is_volume_or_nonpartition_drive): Renamed from udi_is_volume
(compute_cdrom_name): New function
(volume_determine_device_type): Rewrite
(volume_new): Call udi_is_volume_or_nonpartition_drive. Always use
"auto" as target filesystem if not known
(fs_table_has_volume): Remove debug printfs
(fs_table_add_volume): Use hal properties to determine mount flags
(add_udi): Don't process volumes spawned from media w/o partitions
(remove_udi): Don't process volumes spawned from media w/o partitions
(main): Also handle capability 'storage'
Index: hal-spec.html
===================================================================
RCS file: /cvs/hal/hal/doc/spec/hal-spec.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- hal-spec.html 11 Aug 2004 18:53:50 -0000 1.12
+++ hal-spec.html 12 Aug 2004 14:34:36 -0000 1.13
@@ -384,26 +384,26 @@
><DL
><DT
><A
-HREF="#AEN1690"
+HREF="#AEN1704"
>Interface org.freedesktop.Hal.Manager</A
></DT
><DD
><DL
><DT
><A
-HREF="#AEN1701"
+HREF="#AEN1715"
>Example</A
></DT
></DL
></DD
><DT
><A
-HREF="#AEN1709"
+HREF="#AEN1723"
>Interface org.freedesktop.Hal.Device</A
></DT
><DT
><A
-HREF="#AEN1718"
+HREF="#AEN1732"
>Interface org.freedesktop.Hal.AgentManager</A
></DT
></DL
@@ -3174,14 +3174,25 @@
><TD
>Yes</TD
><TD
->True only when the device object represents an
- entire storage device and no known partition table
- have been identified. In this case, if the storage
- device contain a file system it will be accessible
- using the same special device file as the one for this
- device object and the device object representing the
- filesystem will appear as a separate device object as
- a child.
+>For toplevel block devices, this is TRUE only
+ when no known partition tables have been found on the
+ media (In this case, if the storage device contain a
+ file system it will be accessible using the same
+ special device file as the one for this device object
+ and the device object representing the filesystem will
+ appear as a separate device object as a child). For
+ the child, that is
+ when <TT
+CLASS="literal"
+>block.is_volume</TT
+> is true, this
+ property is TRUE exactly when it was created for a
+ storage device with
+ the <TT
+CLASS="literal"
+>storage.no_partitions_hint</TT
+> set
+ to TRUE.
</TD
></TR
><TR
@@ -3283,7 +3294,7 @@
><P
></P
><A
-NAME="AEN906"
+NAME="AEN908"
></A
><TABLE
BORDER="1"
@@ -3417,7 +3428,7 @@
><P
></P
><A
-NAME="AEN959"
+NAME="AEN961"
></A
><TABLE
BORDER="1"
@@ -3563,7 +3574,7 @@
><P
></P
><A
-NAME="AEN1004"
+NAME="AEN1006"
></A
><TABLE
BORDER="1"
@@ -3825,7 +3836,7 @@
><P
></P
><A
-NAME="AEN1111"
+NAME="AEN1113"
></A
><TABLE
BORDER="1"
@@ -4173,9 +4184,35 @@
><TD
> </TD
><TD
+>Yes</TD
+><TD
>The vendor of the drive</TD
+></TR
+><TR
+><TD
+><TT
+CLASS="literal"
+>storage.serial</TT
+> (string)</TD
+><TD
+> </TD
+><TD
+>No</TD
+><TD
+>The serial number of the drive</TD
+></TR
+><TR
+><TD
+><TT
+CLASS="literal"
+>storage.firmware_revision</TT
+> (string)</TD
><TD
> </TD
+><TD
+>No</TD
+><TD
+>The revision of the firmware of the drive</TD
></TR
></TBODY
></TABLE
@@ -4218,7 +4255,7 @@
><P
></P
><A
-NAME="AEN1268"
+NAME="AEN1282"
></A
><TABLE
BORDER="1"
@@ -4417,7 +4454,7 @@
><P
></P
><A
-NAME="AEN1348"
+NAME="AEN1362"
></A
><TABLE
BORDER="1"
@@ -4544,7 +4581,7 @@
><P
></P
><A
-NAME="AEN1394"
+NAME="AEN1408"
></A
><TABLE
BORDER="1"
@@ -4668,7 +4705,7 @@
><P
></P
><A
-NAME="AEN1439"
+NAME="AEN1453"
></A
><TABLE
BORDER="1"
@@ -4735,7 +4772,7 @@
><P
></P
><A
-NAME="AEN1459"
+NAME="AEN1473"
></A
><TABLE
BORDER="1"
@@ -4800,7 +4837,7 @@
><P
></P
><A
-NAME="AEN1479"
+NAME="AEN1493"
></A
><TABLE
BORDER="1"
@@ -4927,7 +4964,7 @@
><P
></P
><A
-NAME="AEN1523"
+NAME="AEN1537"
></A
><TABLE
BORDER="1"
@@ -5074,7 +5111,7 @@
><P
></P
><A
-NAME="AEN1571"
+NAME="AEN1585"
></A
><TABLE
BORDER="1"
@@ -5428,7 +5465,7 @@
><P
></P
><A
-NAME="AEN1648"
+NAME="AEN1662"
></A
><TABLE
BORDER="1"
@@ -5588,7 +5625,7 @@
><HR><H2
CLASS="sect1"
><A
-NAME="AEN1690"
+NAME="AEN1704"
>Interface org.freedesktop.Hal.Manager</A
></H2
><P
@@ -5704,7 +5741,7 @@
><HR><H3
CLASS="sect2"
><A
-NAME="AEN1701"
+NAME="AEN1715"
>Example</A
></H3
><P
@@ -5822,7 +5859,7 @@
><HR><H2
CLASS="sect1"
><A
-NAME="AEN1709"
+NAME="AEN1723"
>Interface org.freedesktop.Hal.Device</A
></H2
><P
@@ -5975,7 +6012,7 @@
><HR><H2
CLASS="sect1"
><A
-NAME="AEN1718"
+NAME="AEN1732"
>Interface org.freedesktop.Hal.AgentManager</A
></H2
><P
Index: hal-spec.xml.in
===================================================================
RCS file: /cvs/hal/hal/doc/spec/hal-spec.xml.in,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- hal-spec.xml.in 11 Aug 2004 18:53:50 -0000 1.11
+++ hal-spec.xml.in 12 Aug 2004 14:34:36 -0000 1.12
@@ -1508,14 +1508,19 @@
<entry><literal>block.no_partitions</literal> (bool)</entry>
<entry></entry>
<entry>Yes</entry>
- <entry>True only when the device object represents an
- entire storage device and no known partition table
- have been identified. In this case, if the storage
- device contain a file system it will be accessible
- using the same special device file as the one for this
- device object and the device object representing the
- filesystem will appear as a separate device object as
- a child.
+ <entry>For toplevel block devices, this is TRUE only
+ when no known partition tables have been found on the
+ media (In this case, if the storage device contain a
+ file system it will be accessible using the same
+ special device file as the one for this device object
+ and the device object representing the filesystem will
+ appear as a separate device object as a child). For
+ the child, that is
+ when <literal>block.is_volume</literal> is true, this
+ property is TRUE exactly when it was created for a
+ storage device with
+ the <literal>storage.no_partitions_hint</literal> set
+ to TRUE.
</entry>
</row>
<row>
@@ -2055,8 +2060,21 @@
<row>
<entry><literal>storage.vendor</literal> (string)</entry>
<entry></entry>
+ <entry>Yes</entry>
<entry>The vendor of the drive</entry>
+ </row>
+
+ <row>
+ <entry><literal>storage.serial</literal> (string)</entry>
<entry></entry>
+ <entry>No</entry>
+ <entry>The serial number of the drive</entry>
+ </row>
+ <row>
+ <entry><literal>storage.firmware_revision</literal> (string)</entry>
+ <entry></entry>
+ <entry>No</entry>
+ <entry>The revision of the firmware of the drive</entry>
</row>
</tbody>
More information about the hal-commit
mailing list