Your message dated 17 Jan 2001 23:13:12 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#11094: Policy should mention that serial lines require
UUCP-style locking
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 8 Jul 1997 02:43:13 +0000
Received: (qmail 22911 invoked from network); 8 Jul 1997 02:43:04 -0000
Received: from onyx.southwind.net ([EMAIL PROTECTED])
by master.debian.org with SMTP; 8 Jul 1997 02:42:50 -0000
Received: (from [EMAIL PROTECTED]) by onyx.southwind.net (8.8.6/8.8.3) with
UUCP id VAA15517 for [EMAIL PROTECTED]; Mon, 7 Jul 1997 21:36:09 -0500 (CDT)
Received: from glockenspiel.complete.org ([EMAIL PROTECTED] [10.0.0.10])
by complete.org (8.8.5/8.8.5) with ESMTP id SAA01077;
Mon, 7 Jul 1997 18:03:17 -0500
Received: (from [EMAIL PROTECTED])
by glockenspiel.complete.org (8.8.5/8.8.5) id RAA00300;
Mon, 7 Jul 1997 17:42:16 -0500
Date: Mon, 7 Jul 1997 17:42:16 -0500
Message-Id: <[EMAIL PROTECTED]>
From: <[EMAIL PROTECTED]>
Subject: debian-policy: Missing UUCP-locking info
To: [EMAIL PROTECTED]
X-Mailer: bug 2.95
Package: debian-policy
Version: 2.1.3.2
There is no mention of the UUCP-style locking required for serial lines to
prevent multiple communications programs from attempting to use the same
line at once. For a brief description of UUCP-style serial locking, see the
discussion for bug #10575.
-- System Information
Debian Release: 1.3
Kernel Version: Linux glockenspiel 2.0.29 #4 Sun Jun 29 22:29:23 CDT 1997 i586
unknown
---------------------------------------
Received: (at 11094-done) by bugs.debian.org; 18 Jan 2001 05:14:31 +0000
>From [EMAIL PROTECTED] Wed Jan 17 23:14:31 2001
Return-path: <[EMAIL PROTECTED]>
Received: from cm-199-3-110-51.mobile.mediacom.ispchannel.com
(glaurung.green-gryphon.com) [199.3.110.51] (srivasta)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14J7P4-0003NQ-00; Wed, 17 Jan 2001 23:14:30 -0600
Received: (from [EMAIL PROTECTED])
by glaurung.green-gryphon.com (8.11.1/8.11.1/Debian 8.11.0-6) id
f0I5DD304430;
Wed, 17 Jan 2001 23:13:13 -0600
X-Mailer: emacs 20.7.2 (via feedmail 9-beta-7 I)
Sender: [EMAIL PROTECTED]
X-Time: Wed Jan 17 23:13:12 2001
Mail-Copies-To: nobody
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#11094: Policy should mention that serial lines require
UUCP-style locking
From: Manoj Srivastava <[EMAIL PROTECTED]>
X-URL: http://www.datasync.com/%7Esrivasta/
Organization: Manoj Srivastava's Home
X-Face: [EMAIL PROTECTED]/;Y^gTjR\T^"B'fbeuVGiyKrvbfKJl!^e|e:iu(kJ6c|QYB57LP*|t
&YlP~HF/=h:[EMAIL PROTECTED]:6Cj0kd#4]>*D,|0djf'CVlXkI,>aV4\}?d_KEqsN{Nnt7
78"OsbQ["56/!nisvyB/uA5Q.{)gm6?q.j71ww.>b9b]-sG8zNt%KkIa>xWg&1VcjZk[hBQ>]j~`Wq
Xl,y1a!(>6`UM{~'X[Y_,Bv+}=L\SS*mA8=s;!=O`ja|@PEzb&i0}Qp,`Z\:6:OmRi*
Date: 17 Jan 2001 23:13:12 -0600
Message-ID: <[EMAIL PROTECTED]>
Lines: 41
User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
Hi,
The FHS, now included by policy, already lays this out in
detail. I think there is no need to duplicate this in policy itself
(given the size the document has evolved to, any such redundancy is
undesirable).
I am closing this report; if you feel that this can pass
muster in a new policy process, please feel free to reopen and push a
proposal through.
manoj
======================================================================
5.6 /var/lock : Lock files
Lock files should be stored within the /var/lock directory structure.
Device lock files, such as the serial device lock files that were
originally found in either /usr/spool/locks or /usr/spool/uucp, must now
be stored in /var/lock. The naming convention which must be used is
"LCK.." followed by the base name of the device. For example, to lock
/dev/cua0 the file "LCK..cua0" would be created.
The format used for device lock files must be the HDB UUCP lock file
format. The HDB format is to store the process identifier (PID) as a
ten byte ASCII decimal number, with a trailing newline. For example, if
process 1230 holds a lock file, it would contain the eleven characters:
space, space, space, space, space, space, one, two, three, zero, and
newline.
Then, anything wishing to use /dev/cua0 can read the lock file and act
accordingly (all locks in /var/lock should be world-readable).
======================================================================
--
In article <[EMAIL PROTECTED]> Jason bitches about IBM screwing
all of the people who were dumb enough to buy RTs, then... Rad
Morrison
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
