From owner-freebsd-hackers Mon Jul 15 12:07:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02108 for hackers-outgoing; Mon, 15 Jul 1996 12:07:56 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02102 for ; Mon, 15 Jul 1996 12:07:53 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA20025; Mon, 15 Jul 1996 13:06:10 -0600 (MDT) Date: Mon, 15 Jul 1996 13:06:10 -0600 (MDT) Message-Id: <199607151906.NAA20025@rocky.mt.sri.com> From: Nate Williams To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: Adding reboot/exit callouts.. comments please In-Reply-To: <199607151835.LAA25108@ref.tfs.com> References: <199607151835.LAA25108@ref.tfs.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to add the following two callouts to the system: > > 1/ a callout list for things to do at shutdown > 2/ a callout list of things to do on process exit. > > I see these as being useful for several purposes.. > 1/ third party modules that need to notify hardware of shutdown > 2/ LKMs that need to clean up on process exit. > > does anyone have work underway in this? > does anyone object? > does anyone have comments? Well, I'd like to see a 'generic' unload module instead. In the PCCARD/PCMCIA realm, devices can come and go 'on the fly', so having an unload module and moving towards a more dynamic scheme would be a good thing. For example, in the network devices there is no way of removing an interface from the list although we can add one 'on the fly'. By doing this I think you'd be support a large percentage of the above, and it would also be useful for other parts of the system. However, I think finishing DEVFS would be a better thing to do with your FreeBSD hacking time right now, don't you think? ;) Nate