From owner-freebsd-hackers Wed May 10 10:13:16 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA26635 for hackers-outgoing; Wed, 10 May 1995 10:13:16 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA26629 for ; Wed, 10 May 1995 10:13:15 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA25853; Wed, 10 May 95 11:06:28 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505101706.AA25853@cs.weber.edu> Subject: Re: A question of downloading device drivers To: hm@altona.hamburg.com Date: Wed, 10 May 95 11:06:27 MDT Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from "Hellmuth Michaelis" at May 10, 95 08:33:48 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Really, it should be done with kernel level vnode I/O, just like the > > > UFS disk quotas. > > Do you mean that the device driver code should access a file in the > filesystem directly ? Yes; at attach time, it should do the download by reading a download file from the root FS. Not at interrupt level, of course. You could actually delay until first open. Like a "touch" instance in /etc/rc, or whatever. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.