hal/doc/spec hal-spec.html,1.22,1.23 hal-spec.xml.in,1.20,1.21

[David Zeuthen]

Update of /cvs/hal/hal/doc/spec
In directory gabe:/tmp/cvs-serv21612/doc/spec

Modified Files:
	hal-spec.html hal-spec.xml.in 
Log Message:
2004-09-19  David Zeuthen  <david at fubar.dk>

	* doc/spec/hal-spec.xml.in: Add section about policy agents and
	media insertion into drives that another application is holding
	a lock on.



Index: hal-spec.html
===================================================================
RCS file: /cvs/hal/hal/doc/spec/hal-spec.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- hal-spec.html	19 Sep 2004 16:32:15 -0000	1.22
+++ hal-spec.html	19 Sep 2004 16:49:15 -0000	1.23
@@ -431,6 +431,20 @@
 HREF="#enforcing-storage"
 >Storage Devices</A
 ></DT
+><DD
+><DL
+><DT
+><A
+HREF="#enforcing-storage-fstab"
+>File systems file</A
+></DT
+><DT
+><A
+HREF="#enforcing-storage-locking"
+>Disabling policy agents</A
+></DT
+></DL
+></DD
 ></DL
 ></DD
 ></DL
@@ -6386,39 +6400,64 @@
 NAME="enforcing-storage"
 >Storage Devices</A
 ></H2
+><DIV
+CLASS="sect2"
+><H3
+CLASS="sect2"
+><A
+NAME="enforcing-storage-fstab"
+>File systems file</A
+></H3
 ><P
->&#13;
-	An operating system vendor should maintain the 
-	<TT
+>&#13;	  An operating system vendor should maintain the 
+	  <TT
 CLASS="literal"
 >/etc/fstab</TT
 > file through the HAL callout
-	mechanism such that every device object of capability
-	<TT
+	  mechanism such that every device object of capability
+	  <TT
 CLASS="literal"
 >volume</TT
 > has a corresponding entry. The
-	reasoning behind this is, among other things, to maintain the
-	invariant that <TT
+	  reasoning behind this is, among other things, to maintain the
+	  invariant that <TT
 CLASS="literal"
 >/etc/fstab</TT
 > list all
-	available filesystems. In addition
-	the <TT
+	  available filesystems. In addition
+	  the <TT
 CLASS="literal"
 >mount(1)</TT
 > program should enable users
-	without superuser privileges to mount filesystems mentioned in
-	the <TT
+	  without superuser privileges to mount filesystems mentioned in
+	  the <TT
 CLASS="literal"
 >/etc/fstab</TT
 > file as long as they have
-	the <TT
+	  the <TT
 CLASS="literal"
 >user</TT
 > option set.
 
-      </P
+	</P
+></DIV
+><DIV
+CLASS="sect2"
+><HR><H3
+CLASS="sect2"
+><A
+NAME="enforcing-storage-locking"
+>Disabling policy agents</A
+></H3
+><P
+>&#13;	  Policy agents like volume mounters should ignore when media
+	  is inserted into a drive that is locked by another
+	  application. Thus, CD burning applications should lock the
+	  device to disable auto mounting or automatic start of the
+	  users preferred CD burning application when respectively
+	  non-blank rewritable or blank media is inserted.
+	</P
+></DIV
 ></DIV
 ></DIV
 ></DIV

Index: hal-spec.xml.in
===================================================================
RCS file: /cvs/hal/hal/doc/spec/hal-spec.xml.in,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- hal-spec.xml.in	19 Sep 2004 16:32:15 -0000	1.20
+++ hal-spec.xml.in	19 Sep 2004 16:49:15 -0000	1.21
@@ -3307,21 +3307,39 @@
     
     <sect1 id="enforcing-storage">
       <title>Storage Devices</title>
-      <para>
 
-	An operating system vendor should maintain the 
-	<literal>/etc/fstab</literal> file through the HAL callout
-	mechanism such that every device object of capability
-	<literal>volume</literal> has a corresponding entry. The
-	reasoning behind this is, among other things, to maintain the
-	invariant that <literal>/etc/fstab</literal> list all
-	available filesystems. In addition
-	the <literal>mount(1)</literal> program should enable users
-	without superuser privileges to mount filesystems mentioned in
-	the <literal>/etc/fstab</literal> file as long as they have
-	the <literal>user</literal> option set.
+      <sect2 id="enforcing-storage-fstab">
+	<title>File systems file</title>
+
+	<para>
+	  An operating system vendor should maintain the 
+	  <literal>/etc/fstab</literal> file through the HAL callout
+	  mechanism such that every device object of capability
+	  <literal>volume</literal> has a corresponding entry. The
+	  reasoning behind this is, among other things, to maintain the
+	  invariant that <literal>/etc/fstab</literal> list all
+	  available filesystems. In addition
+	  the <literal>mount(1)</literal> program should enable users
+	  without superuser privileges to mount filesystems mentioned in
+	  the <literal>/etc/fstab</literal> file as long as they have
+	  the <literal>user</literal> option set.
+
+	</para>
+
+      </sect2>
+
+      <sect2 id="enforcing-storage-locking">
+	<title>Disabling policy agents</title>
+	<para>
+	  Policy agents like volume mounters should ignore when media
+	  is inserted into a drive that is locked by another
+	  application. Thus, CD burning applications should lock the
+	  device to disable auto mounting or automatic start of the
+	  users preferred CD burning application when respectively
+	  non-blank rewritable or blank media is inserted.
+	</para>
+      </sect2>
 
-      </para>
     </sect1>
 
   </chapter>