public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: mount me <linladn@yahoo.co.in>
Cc: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: SCO vs Rtlinux  <--> embedded linux Vs SCO
Date: Fri, 29 Aug 2003 22:47:21 -0400	[thread overview]
Message-ID: <000601c36ea1$0aaff6c0$0100a8c0@who5> (raw)
In-Reply-To: 20030829165636.51884.qmail@web8204.mail.in.yahoo.com

Hello from Gregg C Levine
No your not. And this is not an Embedded Linux list. This is a list for
ELKS. Two completely different platforms. The stunt SCO is pulling is the
last gasp of a dying company trying to hold onto an image that
disintergrated many years ago. Therefore I do not see your point, as
illogical as you might thing. Furthermore what prompted you to bother us
here?
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "mount me" <linladn@yahoo.co.in>
To: <Linux-8086@Vger.Kernel.Org>
Sent: Friday, August 29, 2003 12:56 PM
Subject: SCO vs Rtlinux <--> embedded linux Vs SCO


> Hi,
> SCO tries to fake linux ( I think i am right ....).
> Many street fights with the Open World and this
> SCO attack with the comparitive display of codes
> in linux and unix really has something behind the
> scenes.
>
> Could SCO penetrate the embedded linux world also ?
> FIRST ----->>>>>  WHAT ABOUT RTLINUX ?
> What is the fate of the thousands of Tiny
> Linux flavours available throughout the world ?
> What about the Embedded World ? . What is in store
> with RTLINUX ?? Will Rtlinux liscence get affected ?
> what about the rtlinux kernel codings ? any loop
> holes ?
>
> I found the following fuming discussion some time back
>
> in rtlinux mailing list and nothing else w.r.t SCO--->
> SCO: "thread creation is about a thousand times faster
> than on native Linux" . what is there in rtlinux site
> in reference to SCO attack ?
>
> I found the following in Montavista's website ------>
> MontaVista is also rallying its strategic partners and
> customers to band together with it in order to
> "...take a public stand against SCO and its attempts
> to intimidate."
>
> WHAT ABOUT RTLINUX ?
>
> I think ....bad_men@SCO / SCO_virus@microsoft !!!
>
> regards,
> karthik bala guru                     SHADOW WARRIOR
> vikki
>
>
> ________________________________________________________________________
> Yahoo! India Promos: Win TVs, Bikes, DVD players & more!
> Go to http://in.promos.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2003-08-30  2:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  4:47 kernel panic mount me
2003-07-24  7:29 ` Gábor Lénárt
2003-07-26  1:21   ` Fname Lname
2003-08-29 16:56 ` SCO vs Rtlinux <--> embedded linux Vs SCO mount me
2003-08-30  2:47   ` Gregg C Levine [this message]
2003-08-30 16:00     ` Dan Olson
2003-08-30 19:20       ` Gregg C Levine

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='000601c36ea1$0aaff6c0$0100a8c0@who5' \
    --to=obiwanthejediknight@worldnet.att.net \
    --cc=Linux-8086@Vger.Kernel.Org \
    --cc=linladn@yahoo.co.in \
    /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