Wait. Is liblockfile1 obsolete?
On Sat, Jul 12, 2025 at 10:15 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the liblockfile1 package: > > #95326: UUCP-style device locking > > It has been closed by Chris Hofstaedtler <z...@debian.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Chris Hofstaedtler < > z...@debian.org> by > replying to this email. > > > -- > 95326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95326 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Chris Hofstaedtler <z...@debian.org> > To: 95326-cl...@bugs.debian.org > Cc: > Bcc: > Date: Sat, 12 Jul 2025 22:12:09 +0200 > Subject: Re: Bug#95326: UUCP-style device locking > On Tue, Jan 03, 2017 at 11:19:09PM +0100, Miquel van Smoorenburg wrote: > > tag 95326 +wontfix > > thanks > > > > noone uses uucp anymore... > > This feature request was wontfix'ed over 8 years ago, and nobody > said anything about it. I think it's safe to completely close the > bug now. > > Best, > Chris > > > ---------- Forwarded message ---------- > From: Ole Aamot <o...@student.matnat.uio.no> > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 26 Apr 2001 15:16:34 +0200 > Subject: UUCP-style device locking > Package: liblockfile1 > Severity: wishlist > > Hi, > > Thanks for all your great work. > > As the maintainer, would you support UUCP-style device locking in > liblockfile - or must this be implemented (alone) somewhere else? > > I haven't found a standard library to do it. > > Examples of non-blocking devices that this might be useful for: > > - digital cameras > - modems > - palm pilot cradles > > The principle is described and encouraged in FHS 2.1 section 5.6: > > -- > 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 file. 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). > -- > > Thoughts? > > -- Ole > > >
