public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Wilkens <robw@optonline.net>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: Valdis.Kletnieks@vt.edu, David Schwartz <davids@webmaster.com>,
	linux-kernel@vger.kernel.org
Subject: Re: RT - who cares.. (Off Topic)
Date: Sun, 12 Jan 2003 10:39:22 -0500	[thread overview]
Message-ID: <1042385962.848.54.camel@RobsPC.RobertWilkens.com> (raw)
In-Reply-To: <1042383903.848.33.camel@RobsPC.RobertWilkens.com>

On Sun, 2003-01-12 at 10:05, Rob Wilkens wrote:
> On Sun, 2003-01-12 at 03:28, Mark Mielke wrote:
> > be quite a bit more sophisticated than VxWorks. The reason for making
> > the point is that a guy jumped on linux-devel saying that anybody can
> > write a kernel, and he knows, because he has contributed to
> > VxWorks. He then went on to say that he has personally submitted
> > several dozen patches to VxWorks.

By the way, I neve never said "I can write a kerenl, and I know, because
I contributed to VxWorks".. Dig back around and you'll find my exact
quote.  We're off-topic, so let's try to drop this.  I referred to an
earlier period in life when I had read two books relating to O.S.
development which probably aren't even in stores anymore because who
would buy a book on reinventing the wheel.  I only referred to my
limitted professional experience to show that I have professional
experience where I was paid to work on a professional kernel, back
around 1996-1998, when I was doing that, I don't think you could've said
that Linux was a comparable system in terms of capabilities or speed --
it's grown over time to become what it is today.

In fact, someone else looked up my background when I happenend to have
mentioned that my first gig out of college was working on OS development
for a small company in florida (the job was handed to me by my linux
kernel hacking class professor, basically --  he asked if I was
interested in moving to ft. lauderdale and gave me a busines card, I
called, went down for an interview, and took the job).  I never claimed
it was a _good_ os that I worked on, nor did I claim it was a good
company.  I'm not claiming the opposite either.  With the right staff,
any company has potential, and they hired 10 people last year for their
linux efforts (to hire anyone in this economy says something).

-Rob


  reply	other threads:[~2003-01-12 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  7:58 inefficient RT vs efficient non-RT Mark Mielke
2003-01-12  8:04 ` Valdis.Kletnieks
2003-01-12  8:28   ` Mark Mielke
2003-01-12 15:05     ` Rob Wilkens
2003-01-12 15:39       ` Rob Wilkens [this message]
2003-01-13  9:38 ` Giuliano Pochini

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=1042385962.848.54.camel@RobsPC.RobertWilkens.com \
    --to=robw@optonline.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@mark.mielke.cc \
    /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