public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Robert Collins <rbcollins@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Beginnings of a patch: /etc/hosts
Date: Thu, 12 Sep 2002 01:27:00 -0000	[thread overview]
Message-ID: <1031813381.22459.132.camel@lifelesswks> (raw)
In-Reply-To: <Pine.GSO.4.44.0209112003300.1269-100000@slinky.cs.nyu.edu>

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

On Thu, 2002-09-12 at 10:10, Igor Pechtchanski wrote:

> > Rule #1: The user knows better than the tool. If the user wants to fool
> > the script, they can, even with uname. If a user is doing that, assume
> > they have a reason and let them do it with grace.
> >
> > Rob
> 
> True.  Hey, I'm a control freak myself...  I was not speaking against
> "fooling the script", I was just making an observation.  However, the
> issue here is not the intentional "fooling" that you describe, but
> unintentional.  It's much harder to do that with 'uname -s' than with an
> environment variable.

Ok, I mis-interpreted your intention.
 
> Besides, why would anyone want to fool a post-install script?
> Mmm, I guess I could think of a few reasons, but then shouldn't all
> post-install scripts be susceptible to fooling in the same way, i.e.,
> "with grace"?  Should this be documented somewhere?

I wasn't suggesting they *should* or *should not* be foolable. I was
really trying to say that the design should not be based on whether or
not a user can *intentionally* override something - because one way or
another the user can. The design should be whatever is:
* easy to maintain
* robust in the face of usual and common-unusual conditions.

Rob

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-09-12  6:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09  2:45 Suggestion: /etc/hosts Paul Johnston
2002-09-09  5:38 ` Nicholas Wourms
2002-09-09  5:40   ` Marcos Lorenzo de Santiago
2002-09-09  6:51 ` Joe Buehler
2002-09-09  7:32   ` Christopher Faylor
2002-09-10  2:19     ` Paul Johnston
2002-09-11  7:43       ` Jim
2002-09-09 11:25 ` news
     [not found] ` <E17oTbC-0001AV-00@quimby.gnus.org>
2002-09-10  9:52   ` Shankar Unni
2002-09-10 11:46 ` Beginnings of a patch: /etc/hosts Paul Johnston
2002-09-10 13:36   ` Igor Pechtchanski
2002-09-11  0:59     ` John Morrison
2002-09-11  2:06       ` Corinna Vinschen
2002-09-11  9:57   ` Joe Buehler
2002-09-11 11:17     ` Igor Pechtchanski
2002-09-11 11:42       ` Joe Buehler
2002-09-11 12:39         ` Igor Pechtchanski
2002-09-11 14:24           ` Paul Johnston
2002-09-11 14:53             ` Warren Young
2002-09-11 15:37               ` Igor Pechtchanski
2002-09-11 15:40                 ` Paul Johnston
2002-09-11 16:15                   ` Igor Pechtchanski
2002-09-11 16:35                     ` Robert Collins
2002-09-11 17:10                       ` Randall R Schulz
2002-09-11 17:26                         ` OT " Igor Pechtchanski
2002-09-12  4:33                           ` Nicholas Wourms
2002-09-12  4:46                             ` Nicholas Wourms
2002-09-11 19:00                         ` Christopher Faylor
2002-09-12  8:56                           ` Joe Buehler
2002-09-11 23:25                         ` Robert Collins
2002-09-12  4:11                         ` Nicholas Wourms
2002-09-11 17:14                       ` Igor Pechtchanski
2002-09-12  1:27                         ` Robert Collins [this message]
2002-09-11 17:54                 ` Igor Pechtchanski
2002-09-12  4:08                 ` Nicholas Wourms
2002-09-12 10:08                   ` Warren Young
2002-09-12 10:11                 ` Warren Young
2002-09-10 13:54 ` Suggestion: /etc/hosts Warren Young

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=1031813381.22459.132.camel@lifelesswks \
    --to=rbcollins@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).