From owner-cvs-sys  Wed Aug 16 14:11:08 1995
Return-Path: cvs-sys-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA28912
          for cvs-sys-outgoing; Wed, 16 Aug 1995 14:11:08 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA28883
          ; Wed, 16 Aug 1995 14:10:47 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id OAA11808; Wed, 16 Aug 1995 14:10:29 -0700
To: nate@sneezy.sri.com (Nate Williams)
cc: "Jordan K. Hubbard" <jkh@freefall.FreeBSD.org>,
        CVS-commiters@freefall.FreeBSD.org, cvs-sys@freefall.FreeBSD.org
Subject: Re: cvs commit: src/sys/i386/i386 userconfig.c 
In-reply-to: Your message of "Wed, 16 Aug 1995 09:22:56 MDT."
             <199508161522.JAA11126@rocky.sri.MT.net> 
Date: Wed, 16 Aug 1995 14:10:29 -0700
Message-ID: <11806.808607429@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: cvs-sys-owner@FreeBSD.org
Precedence: bulk

> Actually, the probe command is somewhat helpful.  I used it to make sure
> that the probe command can find my hardware during the initial boot.flp
> when I couldn't catch the probe output on the screen because sysinstall
> quickly cleared it.  However, the attach command is definitely a
> land-mine.

Well, a number of people have blown themselves up with probe() and
it's hard to tell which drivers will happily let themselves be
probe()'d and which won't, so I figured better safe than sorry.

					Jordan