From owner-freebsd-current Tue Jan 5 10:43:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18329 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:43:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18310 for ; Tue, 5 Jan 1999 10:43:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA06089; Tue, 5 Jan 1999 10:42:47 -0800 (PST) To: "Daniel C. Sobral" cc: current@FreeBSD.ORG, Mike Smith , Andrzej Bialecki Subject: Re: /boot/boot.rc && /boot/rc.d In-reply-to: Your message of "Wed, 06 Jan 1999 03:18:40 +0900." <36925780.75AB6581@newsguy.com> Date: Tue, 05 Jan 1999 10:42:46 -0800 Message-ID: <6086.915561766@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was thinking about possible on-comings "patches" in boot.rc > (currently known as boot.conf :), when I realized that for > third-party drivers or ports making use of loader it would better to > source files from a boot/rc.d directory. > > Is this already planned? We hadn't really thought this far ahead, but I see no reason why following such a "hook chain" couldn't be a part of the system. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message