From owner-freebsd-current Fri May 29 20:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08770 for freebsd-current-outgoing; Fri, 29 May 1998 20:35:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08761 for ; Fri, 29 May 1998 20:35:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA17272; Fri, 29 May 1998 20:35:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 19:58:10 PDT." <356F75C2.7566F4CF@whistle.com> Date: Fri, 29 May 1998 20:35:39 -0700 Message-ID: <17268.896499339@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > E.g. I can shoot my foot off, but I can't sew it back on. :-) OK, I understand the dummy_mount problem a little better now. Now what about the issue I raised of not being able to mknod back things which have been removed? :-) -Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message