mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Pimlott <andrew@pimlott.ne.mediaone.net>
To: erich@uruk.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Julian Anastasov <ja@ssi.bg>,
	Szekeres Bela <szekeres@lhsystems.hu>,
	Daniel Gryniewicz <dang@fprintf.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Network Security hole (was -> Re: arp bug )
Date: Sat, 2 Mar 2002 18:31:03 -0500	[thread overview]
Message-ID: <20020302233103.GA3018@pimlott.ne.mediaone.net> (raw)
In-Reply-To: <E16hG1r-0008Kh-00@the-village.bc.nu> <E16hGAW-0000Rw-00@trillium-hollow.org>
In-Reply-To: <E16hGAW-0000Rw-00@trillium-hollow.org>

On Sat, Mar 02, 2002 at 12:31:48PM -0800, erich@uruk.org wrote:
> My general contention is that the system should, by default, behave as
> non-experts would expect, but this might be a point where we can't
> agree.
> 
> It is, unfortunately, the cardinal rule when designing any usable
> interfaces.  I reference Donald Norman's "The Design of Everyday
> Things".  But I digress.

I must agree with Alan.  Low level technical interfaces should
behave according to standards, and should follow a consistent logic
understood by experts in the field (even if it is difficult for the
beginner).  If people try to push "usability" (and I'm as much a fan
of that book as you) onto kernel interfaces, we'll wade into a swamp
and never get out.

Such interfaces need not be exposed to ordinary users.  Indeed, by
keeping the low-level layer simple and orthogonal, it becomes easier
to build multiple user-facing layers (for different purposes, or for
comparison at the same purpose).  I think this principle is much
more powerful than the one you advance.

Andrew

  parent reply	other threads:[~2002-03-02 23:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 23:33 arp bug Julian Anastasov
2002-03-02 18:42 ` Network Security hole (was -> Re: arp bug ) erich
2002-03-02 19:14   ` Alan Cox
2002-03-02 19:58     ` erich
2002-03-02 20:22       ` Alan Cox
2002-03-02 20:31         ` erich
2002-03-02 20:52           ` Alan Cox
2002-03-02 21:14             ` erich
2002-03-02 23:31           ` Andrew Pimlott [this message]
2002-03-03  1:00             ` erich
2002-03-03  3:21           ` David Ford
     [not found]       ` <Your message of "Sat, 02 Mar 2002 19:14:55 GMT." <E16hEy7-000875-00@the-village.bc.nu>
2002-03-03  0:50         ` Stevie O
2002-03-02 21:52   ` Julian Anastasov
2002-03-02 20:23     ` Alan Cox
2002-03-02 20:26       ` Ben Greear
2002-03-02 23:23       ` Karl
2002-03-03  0:20       ` Julian Anastasov
2002-03-02 22:40         ` Alan Cox
2002-03-03  0:46           ` Julian Anastasov
2002-03-02 23:27             ` Alan Cox
2002-03-03  2:38               ` Julian Anastasov
2002-03-03  0:21             ` erich
2002-03-03  0:33               ` Russell King
2002-03-03  0:43                 ` erich
2002-03-03  0:49                   ` erich
     [not found]                     ` <Your message of "Sat, 02 Mar 2002 16:43:23 PST." <E16hK5z-0000vI-00@trillium-hollow.org>
2002-03-03  1:05                       ` Stevie O
2002-03-04 18:14                         ` Paul Jakma

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=20020302233103.GA3018@pimlott.ne.mediaone.net \
    --to=andrew@pimlott.ne.mediaone.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dang@fprintf.net \
    --cc=erich@uruk.org \
    --cc=ja@ssi.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szekeres@lhsystems.hu \
    /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®