From owner-freebsd-bugs Thu Mar 11 1:50:16 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B211D14D95 for ; Thu, 11 Mar 1999 01:50:14 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id BAA46748; Thu, 11 Mar 1999 01:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 11 Mar 1999 01:50:01 -0800 (PST) Message-Id: <199903110950.BAA46748@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Daniel C. Sobral" Subject: Re: kern/10540: Problems with the boot program Reply-To: "Daniel C. Sobral" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10540; it has been noted by GNATS. From: "Daniel C. Sobral" To: root@huygens.uvt.ro Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/10540: Problems with the boot program Date: Thu, 11 Mar 1999 18:46:19 +0900 > When the system is booted automatically he doesn't read the > kernel.config file build by the previous "boot -c" command, and thus if for > any reason (e.g an powerfail) the system is rebooted automatically he doesn't > "see" the network, because the Ethernet drive is in conflict with other > drives. Funny... I didn't know /kernel.config was being written on 3.1-RELEASE... Create a file /boot/loader.rc with the following lines: load kernel load -t userconfig_script /kernel.config Have fun! :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message