devfs
[Top] [All Lists]

Re: devfs & /var/lock

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: devfs & /var/lock
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Wed, 27 Feb 2002 00:30:24 +0100
Cc: devfs@xxxxxxxxxxx
In-reply-to: <200202261701.g1QH17j23033@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <E16fff7-00012o-00@localhost> <20020226154224.1C04CF667@xxxxxxxxxxxxxxxxx> <200202261701.g1QH17j23033@xxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
On Tue, 26 Feb 2002 18:01, Richard Gooch wrote:
> > > I am currently writing a small application using the serial port. To
> > > respect standards, my application create a file in /var/lock, for
> > > example /var/lock/LCK..ttyS0
> > >
> > > What is the standard when using devfs and devices in /dev/tts ?
> > > /var/lock/LCK..tts0 ?
> >
> > Most code is using /var/lock/LCK..0, which will work OK as long as
> > only serial ports are locked.  We need something better though.
> > Maybe /var/lock/...tts.0 (and as a general rule make it
> > /var/lock/...ZZ where ZZ is the device name with /dev/ stripped off
> > and all '/' characters replaced by '.' characters)?
>
> Why not use '!', just like emacs does?

No reason.  We have to choose something, and I guess that using a '!' is as 
good as anything.

> > Signatures >4 lines are rude.  If you send email to me or to a mailing
> > list that I am subscribed to which has >4 lines of legalistic junk at the
> > end then you are specifically authorizing me to do whatever I wish with
> > the message (the sig won't be read).
>
> Are you really automatically discarding the .sig? Can you do that

No, I just look at the start and if it's legalistic and long then I ignore it.

> reliably? If so, you could bounce the messages, if you want to be
> really mean...

No.  Bouncing such messages does not do anything.  I've tried configuring my 
mail server to bounce messages from domains that put such sigs on but it does 
no good.

An idiot lawyer from one of those companies could argue that my sig is 
unenforcable (it probably is), in which case their sig is unenforcable too 
and there's no point in adding it.  But if their sig is enforcable then mine 
is too.  So if someone wants their long legalistic sig to be considered as 
enforcable then they have to refrain from posting to mailing lists where I 
post.

I started using this sig when a user was posting incoherant and off-topic 
messages to a list that I'm on while using a long legalistic sig.  Other 
methods gave no result, so on that user's first post after seeing my new sig 
I replied to the user (and CC'd the postmaster at the domain) thanking them 
for granting me full rights to do whatever I like with their message without 
regard to their sig.  I never heard from them again (on the list or in 
private mail).  I know that I was being a bit of a bastard, but they 
challenged me to make them stop using that overly long sig and I did so.

This sig works!

-- 
Signatures >4 lines are rude.  If you send email to me or to a mailing list
that I am subscribed to which has >4 lines of legalistic junk at the end
then you are specifically authorizing me to do whatever I wish with the
message (the sig won't be read).

<Prev in Thread] Current Thread [Next in Thread>