[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#304106: marked as done (Policy for devfs support)

Your message dated Tue, 25 Apr 2006 13:08:09 -0500
with message-id <87mze9le9i.fsf@glaurung.internal.golden-gryphon.com>
and subject line Devfs is dead
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: debian-policy
Version: 3.6.1.1

md@Linux.IT (Marco d'Itri) writes:

> On Mar 29, Roger Leigh <rleigh@whinlatter.ukfsn.org> wrote:
>
>> - - the traditional device names should be used by default
> This is basically something which only concerns the maintainers of udev
> and makedev, so I don't think it's useful to define it in policy
> considering that there is an agreement that to do this anyway.

This is aimed at writers of programs that open device nodes, rather
than create them.  They would try opening both the devfs and
traditional device names (if applicable), falling back to the
traditional name if the defvs node is unavailale.

>> - - ideally, device names should be configurable by the user, though
>>   this isn't required
> For hard disks this *must* required, or supporting complex setups will
> be impossible. Usually they have a naming scheme not similar to the
> traditional ones, and which is usually developed locally.

OK.  I've updated the policy diff to accommodate this (attached), and
filed a bug against policy.


Regards,
Roger

- -- 
Roger Leigh
                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                Debian GNU/Linux        http://www.debian.org/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFCWaZSVcFcaSW/uEgRAuzyAJ9ezF/hfktifj3Hd7J5CFLtmVklPwCfTfmB
/oD9TyLWLIhS2+gRrWdjVLg=
=9pFY
-----END PGP SIGNATURE-----

--- debian-policy-3.6.1.1.orig/policy.sgml	2004-06-25 22:11:36.000000000 +0100
+++ debian-policy-3.6.1.1/policy.sgml	2005-04-10 23:13:07.000000000 +0100
@@ -6688,8 +6688,32 @@
 	</p>
 
 	<p>
-	  Debian uses the serial devices
-	  <file>/dev/ttyS*</file>. Programs using the old
+	  For the Debian Linux port, packages which hard-code device
+	  names, or provide default device names in their
+	  configuration files, should use the standard Linux device
+	  names specified by <url
+	    id="http://www.lanana.org/docs/device-list/devices.txt";
+	    name="LANANA">, and should additionally also support the
+	  alternate <url
+	    id="http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html#kernel-names";
+	    name="DevFS"> device naming scheme which is also in common
+	  use.
+	</p>
+
+	<p>
+	  Packages may allow specification of devices, for example
+	  using command-line options or configuration files.  If
+	  devices are automatically detected, the LANANA device names
+	  should be used by default, and the DevFS names should also
+	  be checked for.  Packages must allow specification of
+	  devices for devices with a wide variety of device names (for
+	  example, hard discs), since autodetection is both
+	  impractical and imposes arbitrary limits on its use.
+	</p>
+
+	<p>
+	  Debian uses the serial devices <file>/dev/ttyS*</file>
+	  (<file>/dev/tts/*</file> with DevFS). Programs using the old
 	  <file>/dev/cu*</file> devices should be changed to use
 	  <file>/dev/ttyS*</file>.
 	</p>

--- End Message ---
--- Begin Message --- 
Hi,

        We should certainly not be moving into Etch and beyond with
 brand new policy directives catering to devfs.  Secondly, packages
 needed to have working implementations first anyway for this to have
 been a viable policy change.

        I am closing this report.

        manoj
-- 
Thank goodness modern convenience is a thing of the remote
future. Pogo, by Walt Kelly
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

--- End Message ---
Reply to: