From owner-freebsd-hackers Mon Aug 12 20:04:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09346 for hackers-outgoing; Mon, 12 Aug 1996 20:04:40 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA09333 for ; Mon, 12 Aug 1996 20:04:32 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA07249; Mon, 12 Aug 1996 20:03:55 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma007247; Mon Aug 12 20:03:52 1996 Message-ID: <320FF06B.15FB7483@whistle.com> Date: Mon, 12 Aug 1996 20:03:07 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org CC: julian@whistle.com Subject: Rebooting and related topics.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've added a small callout list to the reboot code so that we and other third party types can add modules which require actions at shutdown. looking at the boot code however, I see that about 90% of boot() in machdep.c is in fact NOT mach dependent at all. I'd like to move most of this out to somewhere more generic while I'm adding my callout code.. several questions.. 1/ am I correct? 2/ can anyone suggest the correct place for it? 3/ The callout code has a prototype for the function at_reboot() where should this prototype live? (I've dropped it into systm.h at the moment) the reason for a kerenl based callout list rather than a user-based rc.shutdown is to do with the nature of the modules being added here.. I'd eventually like to add similar callout lists to exit() and fork() but they are not needed for these particular modules.