mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Ed Sweetman <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs
Date: Tue, 20 Aug 2002 22:49:11 -0600	[thread overview]
Message-ID: <200208210449.g7L4nBo23764@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <1029712550.3331.43.camel@psuedomode>

Ed Sweetman writes:
> Ok, that all makes sense.  I removed the dev entries because they
> weren't needed by me anymore but I suppose it doesn't hurt anything
> to just keep them there anyways so I've fixed all that.  Either way,
> removing devfs did nothing but apparently it was asked to be done to
> allow better testing and/or debugging to be done.  But i've yet to
> get any reason why I removed devfs to investigate promise ide
> controller's dma related memory failures.  I've removed devfs and
> replaced the old /dev entries, no problem.  I'm not getting off
> topic about that.  It's all done so i'm waiting for the next step
> here.

It seems the reason you removed devfs is that you followed Al's bad
advice:
Alexander Viro writes:
> Don't be silly - if you want to test anything, devfs is the last
> thing you want on the system.

In fact, devfs works quite robustly for many people, and wasn't
involved in the IDE problems you were having. Al is an absolutist: if
it's not 100% provably correct, it falls into his other category,
"spawn of satan".

So next time someone claims devfs is causing you problems, treat it
with the skepticism it deserves.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-08-21  4:45 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  6:44 cerberus errors on 2.4.19 (ide dma related) Ed Sweetman
2002-08-18  7:15 ` Ed Sweetman
2002-08-18  9:19   ` Andre Hedrick
2002-08-18 18:11     ` Ed Sweetman
2002-08-18 18:31     ` Ed Sweetman
2002-08-18  7:26 ` Ed Sweetman
2002-08-18  9:00   ` Barry K. Nathan
2002-08-18  9:13     ` Ed Sweetman
2002-08-18 17:50   ` Jonathan Lundell
2002-08-18 18:04     ` Ed Sweetman
2002-08-18  9:10 ` Alexander Viro
2002-08-18  9:16   ` Ed Sweetman
2002-08-18 18:10     ` Ed Sweetman
2002-08-18 18:20       ` Sean Neakums
2002-08-18 18:29         ` Ed Sweetman
2002-08-18 18:36           ` Sean Neakums
2002-08-18 21:53             ` Barry K. Nathan
2002-08-18 22:26               ` devfs Ed Sweetman
2002-08-18 22:47                 ` devfs Sean Neakums
2002-08-18 23:03                 ` devfs Alexander Viro
2002-08-18 23:15                   ` devfs Ed Sweetman
2002-08-21  4:49                     ` Richard Gooch [this message]
2002-08-21  5:03                       ` devfs Ed Sweetman
2002-08-19  1:06                   ` devfs Olivier Galibert
2002-08-19  2:01                     ` devfs Greg KH
2002-08-18 23:18                 ` devfs Barry K. Nathan
2002-08-18 22:41           ` cerberus errors on 2.4.19 (ide dma related) Andrew Rodland
2002-08-18 22:55             ` Ed Sweetman
2002-08-19 21:46               ` Ed Sweetman
2002-08-18 19:53       ` Ed Sweetman
2002-08-18 20:07         ` Andre Hedrick
2002-08-18 20:29           ` Ed Sweetman
2002-08-23  0:03             ` Samuel Flory
2002-08-19  0:06       ` Denis Vlasenko
2002-11-12  9:32 devfs Ian Molton
2002-11-12  9:43 ` devfs Xavier Bestel
2002-11-12  9:49   ` devfs john slee
2002-11-12 10:01     ` devfs Sean Neakums
2002-11-12 12:51       ` devfs Oliver Neukum
2002-11-12 10:05     ` devfs Xavier Bestel
2002-11-12 10:04   ` devfs Alexander Viro
2002-11-12 10:25     ` devfs Ian Molton
2002-11-12 10:46       ` devfs Dave Jones
2002-11-12 11:08         ` devfs Ian Molton
2002-11-12 11:24         ` devfs Rando Christensen
2002-11-12 13:30           ` devfs Alexander Viro
2002-11-12 14:53         ` devfs Alan Cox
2002-11-12 15:37           ` devfs Ian Molton
2002-11-12 11:29     ` devfs Helge Hafting
2002-11-12 15:40   ` devfs Greg KH

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=200208210449.g7L4nBo23764@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safemode@speakeasy.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®