public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Devlinks. Code. (Dcache abuse?)
Date: Sat, 24 Nov 2001 15:44:30 -0500	[thread overview]
Message-ID: <01112415443000.02001@localhost.localdomain> (raw)
In-Reply-To: <15352.57742.799052.405674@notabene.cse.unsw.edu.au> <E165mO5-0006En-00@the-village.bc.nu> <15352.60223.1832.897635@notabene.cse.unsw.edu.au>
In-Reply-To: <15352.60223.1832.897635@notabene.cse.unsw.edu.au>

On Monday 19 November 2001 06:21, Neil Brown wrote:
> On Monday November 19, alan@lxorguk.ukuu.org.uk wrote:
> > > I think you missed part of my point.
> > > There are lots of different name spaces in the kernel.
> > > Filesystem names.  Driver names.  Module names.
> > >
> > > But the namespace that is the current issue, the namespace of
> > > currently available devices, is not a namespace where I would expect
> > > trademarks to ever come up.  It is name space of interfaces and
> > > instances.
> >
> > You mean like adaptec/aic7xxx/0 for the first aic7xxx controller when you
> > want to refer to an adaptec card ? And yes - you do need the ability to
> > do that kind of thing, not just talk generically about "disks".
> >
> > So I still seek an answer. "Shrug, probably wont happen" isnt a good
> > one
>
> I was thinking:
>
>    devid/9005/00cf/0
>
> Now maybe the numbers can be trade marks too (I always liked "S3"'s id:
> 5333). However this number is extracted from the device in question. 

The reason Intel came up with the name "Pentium" is that a judge ruled 
they couldn't trademark a number like "386" or "486" to stop AMD from using 
it.  Just a data point.  What the law REALLY says these days is anybody's 
guess, and you can be sure somebody's lobbying to make it worse...

The law is a lot like poker: bluffing and wagering more than your opponent 
can afford is often more important than what your cards say.  The MS 
antitrust trial shows how when you stonewall it can take years for any 
enforcement action to work its way through the bureaucracy, by which point 
the issue is moot.  And the RIAA shows how somebody without a leg to stand on 
can get a really biased and/or ignorant judge to decide that PI should 
henceforth be 3 in all government documents.  But if you live your life in 
fear of being sued, you can't even go out and buy groceries...

So a vendor THREATENING to sue is normal.  Making threats is really cheap.  
Actually following through requires spending money and taking a potential 
public relations hit that can make it onto yahoo's business report where 
investors read it and drive the stock price down, which they'd generally 
rather like to avoid.  Doesn't mean they won't, but it doesn't mean a form 
letter on company letterhead justifies digging a bomb shelter...

Rob

  parent reply	other threads:[~2001-11-24 23:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 10:08 Devlinks. Code. (Dcache abuse?) Neil Brown
2001-11-16 10:26 ` Alan Cox
2001-11-19  3:47   ` Neil Brown
2001-11-19  8:52     ` Andreas Dilger
2001-11-19 10:30       ` Neil Brown
2001-11-19 10:17     ` Alan Cox
2001-11-19 10:40       ` Neil Brown
2001-11-19 11:14         ` Alan Cox
2001-11-19 11:21           ` Neil Brown
2001-11-19 11:27             ` Alexander Viro
2001-11-20  1:06               ` Neil Brown
2001-11-24 20:44             ` Rob Landley [this message]
2001-11-19 20:41           ` Alex Bligh - linux-kernel
2001-11-19 21:36             ` Alan Cox
2001-11-19 22:06               ` Alex Bligh - linux-kernel
2001-11-19 11:05       ` Erik Andersen
2001-11-16 10:33 ` Alexander Viro
2001-11-19  4:02   ` Neil Brown
2001-11-16 19:14 ` Andrew Pimlott
2001-11-16 20:42   ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01112415443000.02001@localhost.localdomain \
    --to=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox