public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brett <brettspamacct@fastclick.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: File Permissions are incorrect. Security flaw in Linux
Date: Wed, 01 Oct 2003 10:23:12 -0700	[thread overview]
Message-ID: <3F7B0D80.5020303@fastclick.com> (raw)
In-Reply-To: <1065019077.2995.22.camel@localhost.localdomain>

Just a helpful hint for the future: Do no jump to conclusions so easily. 
  You originally stated there's a bug in linux.  This probably rubbed 
people the wrong way, people here work hard on linux, some are grumpy, 
and for someone to come in here and tell them "here's a big fat bug in 
linux" when in fact it isn't a bug, well, many good people could become 
not so friendly.  If you would have said "Clarification needed, is this 
a bug?" or something, I think you would have gotten less hostile replies.

Then again, maybe you're on to something, I've been very nice, 
unassuming and cordial about my filesystem cache question, maybe I need 
to post a message with the subject "Bug in vm/filesystem cache" so I can 
get a response. :(



Sincerely,

Brett


Lisa R. Nelson wrote:

> Ok, ok, I get it... It was an oversight on my part.  But I'm sure
> surprised about some of the hostile replies I received.  So much for a
> friendly group.  People should remember that there's ALWAYS someone that
> knows more that YOU.  In my case it was about permissions, what is it in
> your case?  Microsoft scores points on being friendly... Yuck...
> Microsoft....
> 



  parent reply	other threads:[~2003-10-01 17:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 12:40 File Permissions are incorrect. Security flaw in Linux Lisa R. Nelson
2003-10-01 13:08 ` Måns Rullgård
2003-10-01 13:08 ` Mathieu Chouquet-Stringer
2003-10-01 13:23 ` viro
     [not found]   ` <1065017722.2995.10.camel@localhost.localdomain>
2003-10-01 15:40     ` viro
2003-10-01 19:27       ` DervishD
2003-10-01 13:53 ` Jurjen Oskam
2003-10-01 14:09   ` Richard B. Johnson
2003-10-01 14:22     ` Andreas Schwab
2003-10-01 15:01   ` John Bradford
2003-10-01 13:58 ` Felipe Alfaro Solana
2003-10-01 14:21 ` DervishD
     [not found] ` <1065044031.2158.23.camel@wynken.reefedge.com>
2003-10-01 14:37   ` Lisa R. Nelson
2003-10-01 15:11     ` Bas Mevissen
2003-10-01 15:12     ` Randy.Dunlap
2003-10-01 16:08     ` Richard B. Johnson
2003-10-01 19:21       ` DervishD
2003-10-01 20:30         ` viro
2003-10-01 17:23     ` Brett [this message]
2003-10-01 19:24       ` DervishD
2003-10-02 10:32 ` Christian

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=3F7B0D80.5020303@fastclick.com \
    --to=brettspamacct@fastclick.com \
    --cc=linux-kernel@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