mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Greg KH <greg@kroah.com>
Cc: mikem <mikem@beardog.cca.cpqcorp.net>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: CSMI questions
Date: Thu, 24 Feb 2005 15:25:02 +0100	[thread overview]
Message-ID: <20050224142502.GC13226@harddisk-recovery.com> (raw)
In-Reply-To: <20050222231450.GB10067@kroah.com>

On Tue, Feb 22, 2005 at 03:14:50PM -0800, Greg KH wrote:
> On Tue, Feb 22, 2005 at 11:16:56AM -0600, mikem wrote:
> > I'd also like an (brief) explanation of why ioctls are so bad. I've seen the 
> > reasons of them never going away, etc. But from the beginning of time (UNIX)
> > ioctls have been the preferred method of user space/kernel communication.
> 
> That's because there was no other method.  See the lkml archives for why
> ioctls are considered bad, I don't want to dredge it up again.

Here's a quote from the official syndicated kernelnewbies fortunes
file (http://www.kernelnewbies.org/kernelnewbies-fortunes.tar.gz ):

"Basically, ioctl's will _never_ be done right, because of the way people
 think about them. They are a back door. They are by design typeless and
 without rules. They are, in fact, the Microsoft of UNIX."

	- Linus Torvalds on linux-kernel

For the full story, see http://lkml.org/lkml/2001/5/20/81 .


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2005-02-24 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 17:16 mikem
2005-02-22 23:14 ` Greg KH
2005-02-24 14:25   ` Erik Mouw [this message]
2005-02-22 18:15 Miller, Mike (OS Dev)

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=20050224142502.GC13226@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikem@beardog.cca.cpqcorp.net \
    /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®