Mailinglist Archive: opensuse (3729 mails)

< Previous Next >
Re: [SLE] Linux kernel coder puts SCO on notice [OT]
  • From: Curtis Rey <crrey@xxxxxxxxxxx>
  • Date: Mon, 16 Jun 2003 09:53:13 -0700
  • Message-id: <200306160953.13101.crrey@xxxxxxxxxxx>
On Monday 16 June 2003 05:47, Kelly Fulks wrote:
> On Sunday 15 June 2003 22:13, Rohit wrote:
> > On Mon, 16 Jun 2003, Jim Barnes wrote:
> > > As the worm turns
> > > http://www.theinquirer.net/?article=10018
> >
> > Why is there no name to this author?
> >
> > It might even be strategic advantage to Linux community if heroes like
> > this came out in public!
> >
> > Rohit
>
> [disclaimer deleted]
>
> Have you ever thought that this might be the response of one of the other
> distributions? Could be this guy is employed by SuSE, RedHat, Mandrake,
> etc. They all have folks outside the US, IIRC.

Right! And by keeping his/her anonimity they absolve any problems legally
that they might entangle with respect to their employer. I mean, if the name
is known and this person is an employee of say Mandrake or SuSE, or whoever,
then the legal implications become more complicated. By keeping these things
seperate, a name that could be associated with a company that SCO has
contentions against, SCO can't claim he/she is acting as an agent of the
company and therefore has alterior motives or drags said company into the
legal fray.

This person may indeed have alterior motives, or not. The whole things
revolves around a person asserting his/her rights in light of the present
state of litigation and claims of wrong doing. By not bringing in a
corporate entity then this person can persue the matter in a more unfettered
matter.

I think that many of the devs would have to seperate themselves from their
employers, at least initially, if they were to follow in the footsteps of
this person. This way SCO couldn't claim that, say SuSE, was manipulating
the situation. This has been suggested by the action of LinuxTag, wherein
rather than have SuSE get in the middle of this mess while being an IBM and
SCO partner, they prompted LinuxTag to act on their behalf. If the author
of the email to SCO were to be associated with a specific Linux company then
it's likely the SCO would claim that "X" company was taking hostile action
against SCO. This would most likely be a problem for SuSE for instance,
given SCOs latest stunt of looking of peripheral companies to bring suits
against and SuSE's relationship with both IBM and SCO.


Cheers, Curtis.


< Previous Next >
Follow Ups