mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Satchell <list@fluent2.pyramid.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	kernelnewbies@nl.linux.org
Subject: Re: Job Announcements (was Linux TCP/IP Stack Developer)
Date: Sat, 11 Oct 2003 13:25:08 -0700	[thread overview]
Message-ID: <5.2.1.1.0.20031011130522.011e97b0@fluent2.pyramid.net> (raw)
In-Reply-To: <20031011105843.074c6443.davem@redhat.com>

At 10:58 AM 10/11/2003 -0700, you wrote:

>By spamming job opennings to our kernel development lists where such
>things are not considered allowed, you fucknuts are basically
>guarenteeing that no kernel programmer with a brain is going to
>respect your company enough to apply for these jobs.
>
>Please stop posting this crap now.

Are you speaking for yourself, or for Red Hat as well?

Just for grins, I took a look at http://www.redhat.com/about/careers/ to 
see what your company was offering for work.  Hey, no TCP/IP Stack 
programming jobs there.  In fact, very little in the way of work for 
back-room types at all in the United States, nothing west of the Rockies, 
and only Australia seems to have anything when you get outside of the CONUS.

There are some people desperate enough to receive money for their efforts 
that such job announcements may well be welcome, at least as long as they 
are real positions. Obviously you are not that hungry.  I'm working right 
now in a system admin position, changing the oil and wiping the windshield 
of 200 Red Hat Linux servers, in a position that does not allow for any 
kernel development at all.  What makes you believe that all 30,000+ readers 
of LKML would not welcome short, tasteful, single-shot announcements of 
such development positions?  Particularly if the announcement was for work 
within moving distance of where a reader lives?

(I suspect the poor guy was inundated with resumes, good taste or 
no.  That's what seems to happen when a company makes any kind of public 
announcement for work in California or Nevada.  Sometimes principles give 
way to other necessities.)

As an aside, I'm not happy with the few Linux-specific job boards that are 
out there.  Has Red Hat considered hosting one that works, and advertising 
its existence?


-- 
"Fragmentation is like classful addressing -- an interesting early 
architectural error that shows how much experimentation was going on while 
IP was being designed."   -- Paul Vixie  


  reply	other threads:[~2003-10-11 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 22:55 Linux TCP/IP Stack Developer hotjobs
2003-10-11 17:58 ` David S. Miller
2003-10-11 20:25   ` Stephen Satchell [this message]
2003-10-11 20:35     ` Job Announcements (was Linux TCP/IP Stack Developer) David S. Miller
2003-10-11 22:12       ` jdow
2003-10-11 22:11         ` David S. Miller
2003-10-11 21:29     ` Willy TARREAU
2003-10-11 22:16       ` Stephen Satchell
2003-10-11 23:39         ` Mark Mielke
2003-10-12 11:03         ` Jamie Lokier
2003-10-12 14:59           ` Stephen Satchell
2003-10-13  1:47           ` Adam Sulmicki
2003-10-13  1:58             ` Adam Sulmicki
2003-10-14  9:23               ` Jamie Lokier

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=5.2.1.1.0.20031011130522.011e97b0@fluent2.pyramid.net \
    --to=list@fluent2.pyramid.net \
    --cc=davem@redhat.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®